Shelly Dimmer can't turn off

[romanobaturina]

Since last Shelly firmware update I can't turn off the dimmer, but I can turn it on and regulate the brightest. Also light status does not update in hoobs when changed on the switch.

Thank you

[sailor25462]

I have tested home bridge 1.1.6 (also 1.2.3) with config-ui 4.29.0, shelly plugin 0.15.5 (also 0.15.4) and Dimmer 2 firmwares 1.7.7, 1.8.3, 1.8.4 and 1.8.5. All seem to have problems at present. It neither seems to be a firmware problem, nor a HomeKit issue because I can turn on/off the dimmer through the shelly app correctly all the time, and well as through the internal web interface. Only through homebridge, I can switch on/off each dimmer only one time. After this the switches will not react anymore, although the status will still change within homebridge UI. (on the contrary, switching on/off in the shelly app will not update the state within homebridge UI, either) With every service restart, I can again issue one change.

When using debug mode, the log gives very little info, however, there's always on one "type" of log entry. Depending on which h the state was after service restart (on/off), the log will show a shelly entry only for switching off (e.g. "[2020-10-13 18:22:41] [Shelly] Setting light of device SHDM-2 E0980695B675 to off, 29 %" when it was on), or switching on (when it was initially off). Another click will not show any log entry, but still change the sate in UI. When you click one again, there's again a log entry... and so on.

Update: Ok, so more digging.... As said above, homebridge will only issue the command in "one direction", i.e only on or off. Now, when I "adjust" the state with the Shelly app, I can successfully switch on/off. For example, if the switch was turned on at the service restart and I have switched off via homebridge, I cannot switch on again. But if I switch on through shelly app and then witch off again through homebridge, this will work.

[jotzet79]

Hey folks, having this problem too! ;(

[Dominik-1980]

I have no solution that works with this plugin, but I know why this happens.

In my case, I have 3 Shelly 1. Two of them are directly connected to the FRITZ!Box. They work perfectly with this plugin.

The third Shelly 1 is connected to a Devolo dLAN Wifi Adapter. Here I have got the same issue. The problem is, that the Devolo connects to the FRITZ!Box over a LAN-Bridge. Here is where the required packages to control the Shelly correctly gets lost.

The only way to get this work for me was to disable the cloud and control the shelly over mqtt instead of this plugin.

It would be great if someone gets a workaround for this, because I would like to use this homebridge-shelly.

[mibbi1802]

@sailor25462 my issue sounds exactly the same. did the last updates change something for you? @Dominik-1980 I first thought that my signal strength had something to do with this, but when I use the shelly app it works without any latency over the same wifi connection. Did you use the default timeout settings for the plugin?

[Dominik-1980]

@mibbi1802 I am pretty sure that it is a problem with mDNS/Bonjour within your Wifi-Network. What is your setup? Which router do you use? Do you use Wifi-Repeaters or dLAN-Adapters?

[mibbi1802]

@Dominik-1980 I am using a OPNsense with mDNS. AppleTV and all Apple devices are in one subnet, Shellys, homebridge and other internet connected devices are in another subnet. I have three Aruba Access Points with separate SSID's and VLANs for the two subnets connected via cat6 cable. No dLAN-Adapters. But even with mDNS disabled the issue persists. I can switch a shelly 1pm on directly via homebridge ui (without HomeKit and without mDNS) and when I try to switch the same device off after a few seconds, home bridge shows no issue and the device seems to be off but in fact its still on. When I wait for a minute the status in home bridge switches back to on and I can switch it off without an issue. Sadly I do not know which changed this behavior since you normally do not switch a device on and off within a few seconds, but I know that it was working a few months ago. since than I created the different subnets updated reinstalled homebridge two times, updated the Shellys and added some more Shellys to my network.

[sailor25462]

Sorry for not having answered here earlier, but I was horribly busy over the past weeks.

@Dominik-1980 Thanks for you input, but honestly I do not believe it's due to mDNS.

The point is that I started to set up two systems, i.e. home bridge and iobroker on the same pi, after I realized these issues. to make it short: None of these problems occur in iobroker, using the Shelly Adapter (4.0.3) and HomeKit Adapter (0.11.0).

It's all in the same network, running on the same pi, using the same hardware and LAN/WiFi settings, thus we can clearly track it down to the shelly plugin in homebridge.

@mibbi1802, I can only recommend to try and set up also iobroker in your environment to see if it solves also your issues. In case it does, it might be time to verify both code bases and identify the potential bug.

Homebridge does not solve all my issues, but frankly speaking, running both does. For example, integration of hue bulbs works, but correct setting for colors, etc. appears to be a nightmare compared to Homebridge. My goal is to have it all shown in HomeKit after all, so I do not care if I have a slight defragmentation on the server systems. Works for me, may not for others.

[sailor25462]

please also have a look here, it seems this is a duplicate issue.. [https://github.com/alexryd/homebridge-shelly/issues/199#issuecomment-734984579]

[mibbi1802]

@sailor25462 Thanks for your recommendation. with iobroker it seems to work as expected. keeping both seems to be a good option for me as well. 👍

[mibbi1802]

I found my issue and a solution. Have look here: https://github.com/alexryd/homebridge-shelly/issues/199#issuecomment-754702712

[nubek]

Hello together :) I just bought myself a Shelly Dimmer 2 and facing the same issue :( It seems that there is (at least until now) no real fix for that :( FYI: I am using this plugin inside HomeBridge v1.5.0 on my Synology NAS.

But I actually found a quiet nice solution, which I want to share with you and what will work directly inside HomeKit (with Shortcuts):

1. Create a new automation inside the Home app (Mac, iPhone or iPad)
2. Tap "An Accessory is Controlled"
3. Choose your Shelly Dimmer and "next"
4. Select "inactive" and "next"
5. Scroll to the bottom and select "Convert to Shortcut"
6. Delete the default action (if there is already one) -> you will only need the following action
7. Find "Get Contents of URL" action and select it.
8. And now the Magic: Set "http://LOCAL-IP-OF-SHELLY-DIMMER/light/0?turn=off" as the URL (replace LOCAL-IP-OF-SHELLY-DIMMER with your direct shelly dimmer IP -> example: "http://192.168.1.99/light/0?turn=off")
9. Then "next" and "done" :)

So if you turn your Shelly Dimmer now off inside the Home app, the new created automation will always trigger a HTTP GET request to the URL you set in point 8 above. And this URL is a direct endpoint of the Shelly Dimmer and will trigger the Shelly Dimmer to turn off :)

I hope this automation will help someone here =)