-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
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
Platform switch unavailable after every HA Core update #102000
Comments
Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) switch documentation |
Following lines ar in the supervisor log: Core log is surprisingly short:
|
I would think that there is some invalid config in there. Do you run any custom integrations? |
quite a few. How would I find out which one? Trial and error? |
Does it only happen after update or also after a restart? |
Only after update. |
Heh, that doesn't make sense. What if you only restart core? |
Hmm, didn't try that in a while - I believe it did not, but not sure anymore. |
Latest update shows the same behaviour, but now without even correctly updating. |
I am seeing following repeated for sensor and switch.
It looks the device no longer provides Serial Number, as Serial Number shows as "Not Available" in the Flo App and debug data has May be we should switch to Device ID ('macAddress') instead of Serial Number? Edit: is this the correct thread or should I open a new issue for serial number issue? |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
The problem
When I update HA core to a new release, after the restart, All my switches are not working.
I get messaes like "service switch.turn-on is not available". It seems, that the whole switch platform is not available.
After doing a host restart (Raspi 3), everything is back to normal.
Happens after every update. Started sometime earlier this year (about 3-5 months ago)
After the last update today, I restarted, so no logs yet - will provide after the next update.
What version of Home Assistant Core has the issue?
core-2023.10.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: