-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
Shelly Dimmer - Can't shut off in Homebridge #104
Comments
UPDATE: I ran homebridge in debug mode to get more logs. When using the Home app, when I tap "on" or adjust the dimming slider, I can see information in the logs and the device responds. When I tap "off" nothing shows up in the logs. The plugin isn't sending the off signal. When I drag the dimmer slider to 0%, then the logs show "off" and the device turns off. The problem is that the plugin is not sending an "off" message when I just tap off. |
Ok this is getting stranger now. Currently it WILL send the command to turn the dimmer OFF. But now it won't send the command to turn the dimmer ON. The problem has flip flopped |
I wiped the device to factory. Re-paired it. It worked for 24 hours. I could see commands in homebridge and everything was lovely. Today it went back to not being able to shut it off via homebridge. Bummer. |
Solved!!!!! Turn off the WMM on the 2.4ghz spectrum of your router. This solved the issue. WMM can be troublesome for Shelly devices even when running natively. It would make sense it could cause problems with the plugin. |
Hi there! I am running a Shelly dimmer using this plugin. Occasionally it works correctly. But most of the time I can turn on the device using homebrige, but cannot turn it off. Oddly, I am able to dim the light all the time. But the command to shut it off doesn't work.
On always does.
Using the Shelly app it works perfectly. I have tried adding the ID of the device to my config.json and it did not make a difference. I am running homebridge 1.0.3 (but this issue happened before I updated to the latest version).
If I go into the Shelly app and reboot the device it works again for a while. But eventually goes back to this issue. I’m not running the plugin requiring authorization. It’s open. I’ve tried adding the device ID in my config.json and it doesn’t help. So weird. Haha
The text was updated successfully, but these errors were encountered: