You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I set up the addon in a second instance on a raspberry pi 3 and got the lock connected but I never see any MQ messages come through. I am not seeing the "MQTT connected" message in the logs so something isn't working but I'm not sure why. I get my birth/will messages when HA starts/stops so I know the MQ stuff is working but nothing from this addon. Thoughts?
Here is my entire configuration.yaml (note I did try adding the default_config entry in case that was important but I didn't see anything different)
I also see this in the logs and I am wondering if the service is not enabled but I'm not sure what Service it is referring to.
[08:12:28] ERROR: Got unexpected response from the API: Service not enabled
Debug MQTT
> [email protected] start
> node ./index.js
Monitor started
Server started
The text was updated successfully, but these errors were encountered:
So I dug into this a little bit and I think I figured out the problem (I am not that familiar with the addon development so I might be wrong). The config.json services > mqtt:want will provide settings if it's an addon service, not just magically pulling it from configuration.yaml and because I am using an MQ broker on another machine it doesn't work for me.
My proposed solution would be to add config options and use that if the addon service isn't available. Thoughts?
Hello, I set up the addon in a second instance on a raspberry pi 3 and got the lock connected but I never see any MQ messages come through. I am not seeing the "MQTT connected" message in the logs so something isn't working but I'm not sure why. I get my birth/will messages when HA starts/stops so I know the MQ stuff is working but nothing from this addon. Thoughts?
Here is my entire configuration.yaml (note I did try adding the default_config entry in case that was important but I didn't see anything different)
configuration.yaml
I also see this in the logs and I am wondering if the service is not enabled but I'm not sure what Service it is referring to.
The text was updated successfully, but these errors were encountered: