-
Notifications
You must be signed in to change notification settings - Fork 421
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
Problem with custom device_class after Hass v2024.1 #1333
Comments
I had a similar problem after updating the core and operating system: all (!) SONOFF devices were not recognized. I then also updated the SONOFF LAN in HACS, then rebooted. After that everything works again. |
That is not similar to my problem; no restart could save the day. I've tested all core versions after 2024.12.3 (last stable) with the latest SonoffLAN versions (3.5.3 and 3.5.4). Same, reproducible error, yet no feedback. I will either skip updating the core for ever, or replace the problematic L1s with other led strips. |
Please show full device diagnostics |
Thanks @AlexxIT. Just updated to core v.2024.1.6 just to get the device diag:
One of the two (L1) devices having the issues is "deviceid": "1000f7d8f7" In the Settings/System/Logs is get the following:
The device remains unresponsive through the HA, however, it is fully functional in eWelink: |
Finally. You should have done this a month ago :) |
Now that you mention there are still some left overs in my yaml config file from the era (can't remember when exactly) when we manually added the sonoff: integration details. It seems that I still have:
sonoff: Shall I remove them all? Thanks for pointing to the problem! |
It's up to you to decide what you need. |
Yeap you are right. I still had few lines in my config yaml to overwrite the class of some devices (those ran by sonoff mini mostly). Now everything is back to normal. Thanks for the support. |
Thank you for posting error. Most users stop at "nothing works for me after update". |
In v.3.5.4 and core v.2024.1.5 my two L1 led strips are not seen by the integration and I get the following debug:
Tried so far 3.5.3 and 3.5.4 will all core versions since 2023.12.4 (last one working fine) but with no luck.
In core v.2023.12.4 I get this device diag:
Whereas in core v.2024.1.5 the same device diag is:
Any ideas?
The text was updated successfully, but these errors were encountered: