-
Notifications
You must be signed in to change notification settings - Fork 38
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
Second service added via Homebridge-MQTT not remembered on Homebridge restart #89
Comments
How did you add the accessory and the second service? |
Try to reset your mqtt broker. A retained “delete” message (if you previously made some add/remove tests) could be the cause of this problem. |
No such messages are retained on the MQTT broker. Topic: Payload:
Added to an accessory that already have a thermostat service. |
If you want to retain it in the MQTT broker, you have to set retain true. But you don't need it, because all the settings of your accessories are stored in the Search for When adding the service, what do you get in |
The response is But cachedAccessories is empty ... hm... are there other paths where a duplicate could be stored ? I use DietPi based on Raspbian. This is odd because all other accessories (created via MQTT) are restored perfectly. EDIT: Found the cachedAccessories in use. |
In order to be able to help you I need more infos and exactly what you did.
see also https://github.com/nfarina/homebridge/wiki/Basic-Troubleshooting and post your log here. If you are using node-red, build a short test showing how you are adding the accessory and the service and upload the flow here and post the result in the debug tab. |
No answer! closing for now. |
My versions are all the latest as per today. Other Homebridge plugins are Homebridge-Hue. However I have not been able to reproduce on the latest restarts of Homebridge. Then it is suddenly cached after all. Dont know what happened. Closing issue is ok. |
Has anyone else encountered the same? When I add a second service to an accessory only the first is remembered on Homebridge restart. Both in Home.app and reading all of this plugin's config via MQTT. Is there a change in HomeKit in iOS 13.2 that messes this up ?
The text was updated successfully, but these errors were encountered: