Homebridge v1.30 update kills main bridge
See original GitHub issueDescribe The Bug:
After updating to HB v 1.30 all existing devices go unresponsive. Checking the bridge settings in the home app shows that the firmware version still shows 1.25. Interestingly, Child bridges and accessories under them work just fine, and the child bridges show correct firmware, 1.30. Seems like something in the update process is preventing HomeKit from seeing the updated main instance. To Reproduce:
-
Open home app and watch, update homebridge, all devices unresponsive. check bridge firmware, still shows 1.25
-
Add plugin, move to child bridge, pair bridge, plugin and accessories work. check bridge firmware, shows 1.30.
-
Remove child bridge, downgrade homebridge to 1.25, all accessories once again respond in home app.
Expected behavior:
Main instance/bridge of homebridge should update to 1.30 and reflect updates in homekit and allow devices to interact
Logs:
Logs do not throw any errors and show homebridge to be functioning fine.
Secondary Homebridge Logs here
Homebridge Config:
Show your homebridge config.json here
Screenshots:
Environment:
- Node.js Version: node -v14.15.1
- NPM Version: npm -v 6.14.8
- Homebridge Version: homebridge -V1.2.5
- Operating System: Raspbian Offical Homebridge Image
- Process Supervisor: hb-service
Issue Analytics
- State:
- Created 3 years ago
- Comments:56 (17 by maintainers)
Top GitHub Comments
Hi @oznu , I tried version 1.3.1 beta 5 and now the Homebridge devices appear normal in Homekit. Even though at least one plugin is still not ready for 1.3.x “[homebridge-rituals] This plugin threw an error from the characteristic ‘Rotation Speed’: characteristic value expected float and received undefined. See https://git.io/JtMGR for more info.”
many thanks, that helps alot
Once the bridge is unpaired from HomeKit your pretty out of luck in this regard. There are some iOS apps that claim to backup your automations / rooms / etc. I have not tested them with Homebridge though.