Shelly Dimmer integration broken when using CoIoT after 2024.5 update about core HOT 12 CLOSED

Thank you for your help

from core.

Hey there @balloob, @bieniu, @thecode, @chemelli74, @bdraco, mind taking a look at this issue as it has been labeled with an integration (shelly) you are listed as a code owner for? Thanks!

_{^{(message by CodeOwnersMention)}}

shelly documentation
shelly source
_{^{(message by IssueLinks)}}

from core.

@gsenas are you on latest build, 2024.6.3 ?

I so please add the following to configuration.yaml , restart HA, and post the log:

logger:
  default: warning
  logs:
    homeassistant.components.shelly: debug
    aioshelly: debug

Note: it is better to drag the log into the comment (which will add it as an attachment) and not copy paste as it is hard to read logs in GitHub.

And add diagnostics (menu configuration -> integration -> shelly -> download diagnostics )

from core.

Home assistant doesn't control the physical switch, you probably have an automation or something that turn the device on/off.

from core.

home-assistant_shelly_2024-06-19T14-35-36.266Z.log

Please find attached the log. The snipped covers a period of time when I manually pressed the physical switch attached to a Shelly Dimmer (IP: 192.168.1.47), the light turned on, and then pressed the physical switch again with no results (except for a brief "bounce" effect).

Core: 2024.6.3
Supervisor: 2024.06.0
Operating System: 12.4
Frontend: 20240610.1

There are no automations involved with that switch. If I revert the Home Assistant Core to 2024.4.4 the physical switch works again without doing anything else.

from core.

This is from your log:

1101: output
2101: input(binary)
2102: inputEvent
2103: inputEventCnt

2024-06-19 16:35:09.721 [0, 1101, 0], [0, 2101, 1], [0, 2102, ''], [0, 2103, 37],
2024-06-19 16:35:24.725 [0, 1101, 0], [0, 2101, 1], [0, 2102, ''], [0, 2103, 37],
2024-06-19 16:35:25.428 [0, 1101, 1], [0, 2101, 0], [0, 2102, ''], [0, 2103, 37],
2024-06-19 16:35:26.559 [0, 1101, 1], [0, 2101, 0], [0, 2102, ''], [0, 2103, 37],
2024-06-19 16:35:28.560 [0, 1101, 1], [0, 2101, 0], [0, 2102, ''], [0, 2103, 37],
2024-06-19 16:35:29.349 [0, 1101, 0], [0, 2101, 1], [0, 2102, ''], [0, 2103, 37],
2024-06-19 16:35:29.362 http request: /light/0 (params={'turn': 'on', 'brightness': 90})
2024-06-19 16:35:29.635 [0, 1101, 1], [0, 2101, 1], [0, 2102, ''], [0, 2103, 37],
2024-06-19 16:35:30.147 [0, 1101, 1], [0, 2101, 1], [0, 2102, 'L'], [0, 2103, 38],
2024-06-19 16:35:30.556 [0, 1101, 1], [0, 2101, 1], [0, 2102, 'L'], [0, 2103, 38],
2024-06-19 16:35:32.556 [0, 1101, 1], [0, 2101, 1], [0, 2102, 'L'], [0, 2103, 38],

I cut down some non-important parts of the log lines since they are very long.
There are two things in this log.

1. There is a request from HA to turn on the device, unless you started it using the UI (please confirm) there is an automation that trigger it, we don't send a light command to the device without something that trigger it.
2. There are very close on/off input changes in the switch.

If you can create another log with the exact steps you pressed it would help understanding what is causing it.

from core.

Adding another line which I forgot:

2024-06-19 16:35:29.361 DEBUG (MainThread) [homeassistant.components.shelly] Setting state for entity Rele entrada, state: {'turn': 'on', 'brightness': 90}

This is a trigger from UI/automation

from core.

Thank you for you super quick response.

• I can confirm I did not use Home Assistant at all to switch on/off any shelly during the period covered by the log.
• To be more precise, these are specific steps:

1. Initial state: all lights turned off, showing in HA as off. All shellys configured as edge switch.
2. Manually pressed physical switch attached to shelly: light turns on, shows in HA "on" as well
3. Manually pressed physical switch attached to shelly: light "bounces" (turns off only to turn on again after a fraction of a second). Show in HA "on".

Regarding the automation, actually YES, there is an automation I forgot about previously to adjust the brightness through the time of day. I attach both involved. This may be the cause, however as soon as I reverted back to 2024.4.4 everything went back to normal.

automations.zip

from core.

What happen if you disable this automation(s)? (one of the files you attached in the zip is empty)

from core.

Sorry, let me upload the file with the automations again while I upgrade the HA core again.

automations.zip

from core.

Good news! Upgraded again to 2024.6.3, disabled the automation (the one that sets the "default" brightness) and its working as expected.

I'll try to find a way to set the default brightness without these unintended side effect, however the integration has different behavior since 2024.4.4.

Should we close the issue?

from core.

Automations now runs faster, this is not related to Shelly but other performance improvements in HA.
Making an automation to react on the input change is very tricky, you can either make the automation run on the out state change (e.g., Light state changed to on) or configure the device as detached switch and create an automation that turns the light on (with brightness) or off according to the input (I do something similar, drawback doesn't work when HA is down).

Thanks for reporting back, I highly recommend to try our Community Forum or join our Discord chat server and get suggestions from other members.

Yes we should close this issue.

from core.