-
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
Unavailable in Home Assistant #81
Comments
check serial messages on startup to see mqtt conenction logs |
Does anything in the serial log show any idea whats going on? The
|
okay, it says mqtt is connected. is lamp the only mqtt entity on your home assistant? can you check if you can receive any mqtt messages at all? |
Sorry, for the delay. I have been playing with settings and mqtt, and what i have found is odd. I have found an mqtt explorer which allows me to see whats going on in the world of mqtt. I can see that the lamp has 3 nodes config, state and available. I noticed that available has a value of false. I simply published I also tested this by publishing the available=true from within home assistant. No idea where the issue lies, with mqtt, home assistant or the lamp itself |
I am not sure if this is a home assistant or mqtt.org server update change. But the lamp, which has been working fine has suddenly become unavailable in home assistant
I can still see and interact with the lamp via the webui. I can see that the device is registered in MQTT. I have changed the settings with a new name, uploaded to the device and can see the new device appear in MQTT as well as home assistant, but with the same issue of being unavailable. I have even reflashed both firmware.bin and fs.bin with a latest build
Does the code need updating with patches to support a new version of home assistant/mqtt?
Settings:
MQTT Diagnostics
mqtt-514072268cec2d4aa391b17e1c927ea4-firelamp-77831687de9b8825071da4cac8df4500.json.txt
The text was updated successfully, but these errors were encountered: