
ioBroker.fritzdect


Fritzbox DECT adapter for ioBroker
Installation:
released version on npm with
npm install iobroker.fritzdect
or the actual version from github with
npm install https:
Setup
IP-address and password of Fritzbox should be defined in io-package.json or via admin page, before the first start of the instance.
The devices are detected automatically during startup of fritzdect instance.
the widget requires that also vis-metro and vis-jqui-mfd are installed
objects
Object | Value | settable | Description |
---|
DECT200.state | boolean | x | true/false -> ON/OFF |
DECT200.mode | string | - | manual, auto |
DECT200.lock | number | - | 0,1 |
DECT200.present | boolean | - | true/false -> connected/not available |
DECT200.temp | value | - | actual temperature in °C |
DECT200.power | value | - | actual power in W |
DECT200.voltage | value | - | actual voltage in V |
DECT200.energy | value | - | actual energy consumption in Wh |
DECT200.name | text | - | name of device |
COMET.temp | value | - | actual temperature in °C |
COMET.targettemp | value | x | target temperature in °C |
COMET.comfytemp | value | - | comfort temperature in °C |
COMET.nighttemp | value | - | night temperature in °C |
COMET.battery | value | - | actual capacity in % |
COMET.mode | number | x | 0=AUTO/1=OFF/2=ON state of thermostat |
COMET.lasttarget | value | - | last target temperature in °C |
COMET.name | text | - | name of device |
DECT100.present | boolean | - | true/false -> connected/not available |
DECT100.temp | value | - | actual temperature in °C |
DECT100.name | text | - | name of device |
Contact.present | boolean | - | true/false -> connected/not available |
Contact.name | text | - | name of device |
Contact.state | boolean | - | true/false -> ON/OFF |
GuestWLAN.state | boolean | x | true/false -> ON/OFF |
Known Issues:
Sometimes the setting of a command for switch or targetTemp does not work. Seems a combination of certain FW and fritzBox model.
TODO:
- contact bitmask=8208 / DECT100 bitmask=1280 may be not universal enough
- create objects according transmitted data
- include groups if feasable
Changelog
0.0.14
- correction of temp offset influence
0.0.13
- DECT200 voltage new object
- DECT200 mode/lock value polling
- Comet mode as number and not array
- ADMIN v3
0.0.12
- changed state to mode AUTO/OFF/ON for thermostat (including datapoint lasttarget when going back to AUTO)
- added name state for thermostat
- DECT100 temperature reading
- Contact reading
0.0.11
- added state OFF/ON for thermostat
0.0.10
- change to object oriented interface
- getOSversion when starting for log
0.0.9
- values '1' accepted for ON
- values '0' accepted for OFF
0.0.8
- messages info-> debug
- values 1/true/on/ON accepted for ON
- values 0/false/off/OFF accepted for OFF
0.0.7
- current temp of Comet/DECT300
- cyclic polling GuestWLAN
0.0.6
- correction targettemp in DECT200 section
0.0.5
- setTemp on COMET
- GuestWlan corrected
0.0.4
0.0.3
0.0.2
- metro widget for Dect200
- smartfritz-promise->fritzapi
- running version, tested with 1x DECT200 and Fritzbox FW=6.51 on Win10 with 4.5.0 and raspberry 4.7.0
0.0.1
- running version, tested with 1x DECT200 and Fritzbox FW=6.30