Replies: 1 comment 2 replies
|
Hiya, if you're testing on 0.12.6 the hassio discovery should be triggered when it sees your home assistant come back online - however, a couple of questions - is your MQTT daemon tied in with your home assistant instance - I'm wondering if the MQTT goes down at the same time? Is home assistant on the default mqtt discovery prefix (/homeassistant)? |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I started to write a bug report, but the more I looked into it and as time went on I became less sure it is a bug. So instead I'll ask the question first as I can't find anything documented about this in the HA or MQTT docs sections.
When HA is restarted, does HA have to wait until the ESPG does it's next autodiscovery walk before the entities are available?
My HA is fully up to date and so are my ESPGs. All ESPGs are ESP8266 flavour.
When I restart my HA all of my ESPGs appear 'Unavailable' but then it seems after quite some minutes they start to appear again. If an ESPG is rebooted, when it starts back up it connects to MQTT and does it's HA autodiscovery walk. The ESPG entities then change from 'Unavailable' to 'Unknown' and then on first MQTT submission the entities show their values.
Is this intended, by design?
I don't recall ever seeing it this way, but then, I rarely restart my HA and when updating HA I'm generally not looking at the ESPGs. Though I suspect I will from now on!
Thanks!
All reactions