-
-
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
Fritz!DECT 440: accType „Button“ could not be found #344
Comments
My home bridge was updated to 2.0. now i have the same issue with fritz and dect buttons. it would be fantastic, if you can fix this issue. |
A similar (and probably related) issue here. Before the update of the Fritzbox 5690 Pro to FritzOS 8.01 (from 7.62) and the subsequent update of the AVM 440 to the latest firmware, the 440's buttons worked fine are were useable in homekit/Eve App. If this could be fixed, it would be superb. |
Still on 1.85 but all my 440s are not working anymore all of a sudden in Homebridge. Please provide fix. |
Hallo, the same here. Environment:
|
Same issue after update Fritz!Box FritzOS to 8.0.1 |
"I think this issue will be solved by itself when AVM will present the integration of Matter into the Fritz!Box" Yes and no. You might be able to control certain Matter devices via the Fritzbox. That will require taking them out of the Homekit, as they can be connected only to a single Border Router. The versatility of automations you can set up with Apple Home and the Eve App is however infinitely greater than what you can do with the FritzBox automations. |
Describe the bug
the configuration of FRITZ!DECT 440 as a new device with the Accessory Type „Button“ generates an error message in the Logs like „xxx (smarthome-Button): can not find Button Data - „accType and/or options correct?“
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No error Logs, FRITZ!DECT 440 will be exposed to Apple HomeKit to define the 4 buttons for adding scenes.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: