-
-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SmartHome device no longer found #36
Comments
U need the active tag setted to true and devType Can u set debug to true and post your log pls |
Here you go: [5/22/2019, 8:54:19 PM] [FritzPlatform] Initializing FritzPlatform platform... The last lines do not sound promising :-) But what do I do? |
hm the plugin removed the config from FritzPlatform? |
It did from time to time but right now it remains in the config. What abount the follogin options:
Are these correct? |
If u have not any problems with auto search i would recommend to turn off ‚disableAutoSearch‘ So: disableAutoSearch: false |
disableAutoSearch: false lead to removing the FritBox from the devices. Any more ideas or directions how to analyze? |
can u post your whole config here pls |
Here you go: { |
in smarthome devtype need to be called "devType" and the unit can be removed from config.json if you want to see the fritzbox in your config.json you need to activate it >> "active": true |
Didn't expect the tags to be case sensitive. That solved it. Thank you for your support. |
Allright, happy to solve this issue Closing |
After updating to v4.x a SmartHome device (Fritz!Dect outlet) connected to the FritzBox is no longer avaiable.
The FritzBox itself is found.
In my configuration I added:
"smarthome": {
"Espressomaschine": {
"active": true,
"devtype": "switch",
"ain": "",
"tempSensor": true,
"unit": "celsius"
}
},
I tried "type": "switch" and "devtype": "switch"; found both in the documentation.
I tried with an without the "active" tag.
I use the oznu/homebridge docker image, the homebridge version is 0.4.49.
With 3.x I was able to use the outlet as expected.
Any idea how to analyze this further?
Regards
Bernd
The text was updated successfully, but these errors were encountered: