homebridge-fritz
Homebridge platform plugin for FRITZ!Box.
This plugin exposes:
- WLAN guest access switch
- Fritz!DECT outlets (200, 210)
- Fritz!Powerline outlets (510, 540)
- Fritz!DECT (300) and Comet!DECT thermostats
- Fritz!DECT repeaters as temperature sensor (100)
- Window sensors including HAN FUN devices e.g. of Deutsche Telekom
Installation
Follow the homebridge installation instructions at homebridge.
Install this plugin globally:
npm install -g homebridge-fritz
Add platform to config.json
, for configuration see below.
Configuration
{
"platforms": [
{
"platform": "Fritz!Box",
"name": "My FritzBox",
"username": "<username>",
"password": "<password>",
"url": "http://fritz.box",
"interval": 60,
"hide": ["wifi", "<ain>"],
"concurrent": false,
"wifiName": "Guest WLAN",
"options": {
"strictSSL": false
}
}
]
}
The following settings are optional:
url
: Fritz!Box addressinterval
: polling interval for updating accessories if state was changed outside homebringehide
: a list of device AINs to exclude from homebridge controlconcurrent
: allow concurrent api requests for newer Fritz!BOXes with better performance (experimental)wifiName
: custom name for the WLAN guest access switch (fallbackGuest WLAN
)
The hide
config options allows to specify an array of device AINs that will not be added to homebridge. Use wifi
for hiding the WLAN guest access switch.
Common Issues / Frequently Asked Questions
-
homebridge-fritz can't login to the FritzBox
Some users have reported that logging into the FritzBox internally via
https
fails. This seems to be caused by the FritzApp occupying the same port. In this case you can connect internally viahttp
or use the external IP.Fritz!Box platform login failed
messages can be caused by invalid login data or wrong url.Log messages if the form of:
{ error: { [Error: self signed certificate] code: 'DEPTH_ZERO_SELF_SIGNED_CERT' }
indicate that there are SSL security problems- most likely due to self-signed certificates. Use the
"strictSSL": false
option to disable the respective check. -
homebridge-fritz is not able to update my thermostat
Current FritzBox firmwares seem to ignore API updates when the thermostat has been key-locked. No workaround available- please contact AVM to change this behaviour or don't use the locking mechanism.
-
homebridge-fritz can login but not update thermostat battery charge
Battery charge is not an API function. That means that the user must have access to FritzBox administration, not only to the SmartHome API in order to use this functionality. Update your Fritz!Box user accordingly.
Debugging
If you experience problems with this plugin please provide a homebridge logfile by running homebridge with debugging enabled:
homebridge -D
For even more detailed logs set "debug": true
in the platform configuration.
Acknowledgements
- homebridge-fritz is based on the fritzapi library
- Original non-working fritz accessory https://github.com/tommasomarchionni/homebridge-FRITZBox
- Platform implementation inspired by https://github.com/rudders/homebridge-platform-wemo.