core: MQTT sensors unavailable in 0.114.0bx, others stay unknown
The problem
A lot of my MQTT sensors are unavailable after a restart. The solution to get them back is to delete the entity, and resend the discovery message.
Environment
- Home Assistant Core release with the issue: 0.114.0b0 and 0.114.0b2
- Last working Home Assistant Core release (if known): 0.113.3
- Operating environment (OS/Container/Supervised/Core): Supervised
- Integration causing this issue: MQTT
- Link to integration documentation on our website: https://www.home-assistant.io/integrations/mqtt/
Problem-relevant configuration.yaml
No yaml, but an example of a discovery message :
topic :
homeassistant/binary_sensor/sensorvoordeur/config
Discovery message :
{"name": "voordeur", "device_class": "door", "state_topic": "sensor/voordeur", "unique_id": "voordeur", "device": {"identifiers": ["voordeur"],"name": "voordeur", "model": "Digoo door sensor", "manufacturer": "Digoo"}}
Many Tasmota devices stay ‘unknown’
Traceback/Error logs
Nothing relevant in the log
Additional information
Both point to the same mqtt broker (on a separate machine)
0.114.0b2
https://img.techpowerup.org/200808/01140b2.png [IMG]https://img.techpowerup.org/200808/01140b2.png[/IMG]
0.113.3
https://img.techpowerup.org/200808/01133.png [IMG]https://img.techpowerup.org/200808/01133.png[/IMG]
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 41 (21 by maintainers)
Commits related to this issue
- Adjust slow add entities timeouts to accomodate worst known case With this change, we should still be able to startup in under 10 minutes if something really goes wrong. The testing done in #38661 w... — committed to bdraco/home-assistant by bdraco 4 years ago
- Adjust slow add entities timeouts to handle slowest known case (#38876) With this change, we should still be able to startup in under 10 minutes if something really goes wrong. The testing done i... — committed to home-assistant/core by bdraco 4 years ago
- Adjust slow add entities timeouts to handle slowest known case (#38876) With this change, we should still be able to startup in under 10 minutes if something really goes wrong. The testing done i... — committed to home-assistant/core by bdraco 4 years ago
- Adjust slow add entities timeouts to handle slowest known case (#38876) With this change, we should still be able to startup in under 10 minutes if something really goes wrong. The testing done i... — committed to brg468/core by bdraco 4 years ago
- Adjust slow add entities timeouts to handle slowest known case (#38876) With this change, we should still be able to startup in under 10 minutes if something really goes wrong. The testing done i... — committed to weissm/core by bdraco 4 years ago
So, there are 354 discovered MQTT entities which will all race to be created in parallel.
With #38821 I guess there will be up to 64 of them running in parallel, and there is basically no IO or waiting needed to set up any MQTT entity. The Pi1 only has a single core, so this probably gets really messy.
Changing SLOW_ADD_ENTITIES_MAX_WAIT in homeassistant\helpers\entity_platform.py to 1800 did help. Everything available and updating !