Thanks for the contributions, matanza & @drbob. I'm keen to know if the Fibaro bypass works better too.
For me and my setup, however, everything is still working 100%, ever since enabling "Dettached Switch" mode and updating the firmware. Wish I had held off on updating the firmware to see what fixed it but if I were a betting man, I'd guess that changing to dettached mode is what sorted it out.
Of course if a installed Shelly sends on/off commands via WIFI to a remote Shelly, this won't work without WIFI.
This was my specific question, sorry I didn't make it clear. I have my Shelly configured to send messages using MQTT, and rely on those to turn the lights on or off (the lights are Hue, so they seem to behave better when always powered). Of course, now I fear that if my wifi network goes down, I won't be able to operate the lights. 🤔
Thanks for the response.
Is there a way to enable a fallback mode so that if a Shelly switch can't get onto the wifi network, it defaults to standard switch mode, i.e. when a connected switch is in the on position power is connected to the output pin, and when it is in the off position no power is connected?
Just thinking this would add some peace-of-mind for setups that upgrade existing switches to be smart, if the home wifi network is down at least they can continue to function in "dumb" mode.
Same problem here with a Shelly 1L in detached mode. I have the setup as per the chart in the attachment.
The Shelly 1L is configured as "detached" with power to be always on. The actual light is behind another Shelly 1. The Shelly 1L keeps losing connection after some time. Sometimes it's minutes, sometimes days. The WiFi connection is strong, so that should not be the issue.
At the same time however, Shelly 1 keeps connected. If I turn on the light via Shelly 1, the Shelly 1L restarts and becomes available again.
I tried enabling the debug log on the Shelly 1L, but it doesn't seem to contain anything interesting after the reboot.
Ah, interesting. I'm planning on doing something similar eventually, with a fan behind a Shelly 1. But for my test, I was using a simpler setup where there were two lights behind the Shelly 1L, and I attached the bypass to one of them.
I think it's a good guess that the lack of logs and the lack of any response when running as a standard (not-detached) type of button means that the entire system has hung.
Have you tried the latest firmware?
Same here. Try switching off the relay with no lights on. That's where my Shelly stops responding with button type "detached". There's another thread where a user reports that the Shelly bypass may cause issues with irresponsive Shellys. He bought a bypass from another vendor and is happy now ...
I saw that thread about the other bypass. Interesting.
My Shelly ran all week without any problems. Unfortunately, though, I made two changes: latest firmware and switching to "detached" mode. So hard to say what fixed it, but I'm ok withe either.
Since it's managed to work without any hiccups for the week, I'll probably be buying a bunch more Shelly's switches including bypasses. I tested the Shelly bypass and it wasn't overheating like some others mentioned, I wonder if that depends on how clean/stable the electricity is on a particular circuit. Happy to upgrade to another bypass that, if I understand correctly, can handle more power variance, if required.
Hey Misha,
I have a similar issue. For me the Shelly 1L works fine with button state „Edge“ but always looses connection with button state „Detached“ and when operating the relay via the app. Not the answer you were hoping for, I guess, but maybe this gives you a hint …
Hello Dr Bob, thanks for the response.
I've now configured the 1L to be in "Detached" mode now, leaving the relay always connected and relying on NodeRed to control the lights. So far, no hangs for over 24 hours. 🤞
I've noticed there's a new firmware available now. Hoping my lucky streak continues with it.
Cheers.
I have shelly's everywhere in the house, but now I bought a Philips Hue for one location. I want to operate the light with the Shelly 1, using detached mode.
I've just set this up using NodeRed. I have my Shelly 1L sending events out via MQTT, and a workflow in NodeRed picks those up, runs a little bit of logic around the time of day, and sets the lights to a scene accordingly. Nothing fancy, just bright during the day and progressively dimming down into the evening.
So far works smooth as silk, aside from the 1L hanging on occasion, which was an issue before I setup the above workflow.
Hi all,
I've got my Shelly 1L configured on my network and working with both CoIoT and MQTT. However it seems to completely stop responding at times, at least once a day or more. If I leave it, it sometimes sorts itself out after some hours; otherwise I can generally cycle the power to the switch and it will come back. I've tried a factory reset and minimal configuration (WiFi network, DHCP, device name set, CoIoT (unicast) and MQTT enabled), but I just experienced another one of these hangs.
I've tried enabling debug logging, and oddly it didn't hang during the period I had that on, but I disabled it since and it's hung again. I'm trying with debug logging on again
Any suggestions for what may fix this? Or am I just stuck with a faulty unit?
Thanks,
--Misha
