Closed mossc001 closed 11 months ago
Same problem for me with 0.3.3
@mossc001 you have solved? i have lost all automations with this bug...
@nanni85 , same, every automation relating to the light entity is not working. I tried everything, upper case entity ID, lower case, changing some settings around, but it still does not work.
I cannot see any errors either. How about you?
Hello, @hakana can you help us?
Same here. Lost all controls and related automations.
@nanni85 & @b2eboy , any success or have you changed your automations now?
I was not able to make it work. There's too many shellies on my network to change it manually everywhere. I downgraded back to old version until it will be more clear based on this discussion.
Same here.
Is there any work arround yet? Should I remove the yaml configuration to get the lights automatically? Thanks!
I'm not sure that this is being maintained anymore as it's been almost 3 months; look at the other issue. I'm personally planning a migration to the main HA integration.
It is maintained but my time is limited so I'm trying to fix things as fast as possible. I will spend some time coming days and this is an issue I will try to fix.
Hi hakana, thanks! It will be great to get those shellys as lights again. It's hard to get the google assistant working if they're not lights anymore.
If I can help you in some way just tell me. I've got a bunch of shelly 1 and a shelly 2.5
What can I do to fix this issue? It is really bad that there is no fix for that for so a long time.
Environment
Describe the bug
Override settings written into the config.yaml are being ignored; Shelly 1's and 2.5's which were configured as "light_switch" are now configured as a standard switch, and the configuration seems to be ignored.
` shelly: sensors:
Steps to Reproduce
Update to Shelly 3.x and reboot.
Expected behavior
The device/switch is recognised as a light.
Screenshots
Screenshots attached.
Traceback/Error logs
Additional context