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
snips can not be setup after update to core-2023.5.0b2 #92236
Comments
since i could not reproduce this on a fresh (ish) install, i tried to revert #91790 which solved my problem. re-enabling the check let’s the snips integration be setup on my production instance again without error with core-2023.05.0b4 i have quiet a lot of mqtt entities (~954) and the the mqtt integration takes about 23 seconds to start up, according to home assistant. so i guess this might be an edge case, where it’s still not safe to remove the snips-integration check for MQTT availability and waiting for mqtt to become available under some circumstances. |
cc @jbouwh |
@diplix A fix is provided, so with 2023.5.0 I expect this bug to be resolved. I opened #92297 to trigger further investigation. May be you can help us a bit to understand why the snips setup stopped waiting for |
thanks for looking into this. i left a description regarding startup times of my HA instance over at #92297 (comment). |
The problem
After installing the current beta (.0b2) snips can not be set up.
It was working fine in 2023.4.x
A similar problem due to timing issues while staring up occured a while ago in #81431
What version of Home Assistant Core has the issue?
core-2023.5.0b2
What was the last working version of Home Assistant Core?
core-2023.4.6
What type of installation are you running?
Home Assistant Core
Integration causing the issue
snips, mqtt
Link to integration documentation on our website
https://www.home-assistant.io/integrations/snips/
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: