Beiträge von dcleal

Hi,

I have a Shelly 1L wired up in no-neutral style, with a bypass, as per the manual. Everything works fine (the light goes on and off!), but HTTPS action URLs don't work.

In more detail: I set up the device to hit an action URL (on the 'Output switched on' action). If the target URL is HTTP, everything works perfectly. If I type in an HTTPS URL, not only does it not hit that URL, but the device seems to get into a bad state. When I re-enter the HTTP URL, it still doesn't trigger until I reboot the device. After that, it works fine until the next time I enter an HTTPS URL. The device remains fully responsive through its web interface throughout this.

<later> I also have a Shelly 1 which was able to hit the same HTTPS URL on its 'Output switched on' action. I say "was able" because in a spirit of investigating the problem I upgraded its firmware, and now it behaves like the Shelly 1L. When it worked, it was on firmware version 20191217-140757/1047-long-id-for-shelly-devices@a0661583, but now it's on 20211109-124958/v1.11.7-g682a0db and it doesn't.

I've also tried to use the debug logs to get more detail. This seemed to work in my early testing, though "current log" always downloaded something which was the oldest part of "previous log" which seems strange. Now neither log captures anything. Here's a piece of log that might be a clue, though this is when the Shelly 1L first behaved strangely and I was investigating less systematically.

842794434 switch1pm.c:337         ==== inputs changed: 00000000 -> 00000001 initial=0
842797572 switch1pm.c:367         ========= output 0 state=1 same=0
842800094 switch1pm.c:237         idx 0 ison 1
842802601 action_url_queue.c:136  MAX_ACTION_URL_Q_SIZE reached! Drop https://maker.ifttt.com/trigger/xxxxxxxxxxxxxxxxxxxx/with/key/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx switch1pm.c:325         idx=0 setting 1 for 0
842818516 switch1pm.c:424         Relay on pin 5 changed state 0 to 1

Finally, I have tried a factory reset of the Shelly 1L. Not only did this not fix anything, but the log files survived it, which seems odd. And it was after the reset that the logs stopped recording, though that might be a coincidence as I didn't try to log anything for a while after the reset.

Any ideas?

- Dave

Thanks to both - the Shelly 1L looks like the answer. I have another project for my Shelly 1, so it's all fine.

Hi, I'm a bit of a noob, but here goes:

I have a room with wall lights controlled by a physical switch, and lamps plugged into a socket. I would like to have the socket turn on and off when the light switch is switched. The smart socket I have responds to a simple URL.

I can make this work on the bench easily by having the Shelly permanently powered and the output of the switch connected to the SW terminal, and using the switch on/off actions to trigger the socket. Really nice and easy...

However, I just looked at the wiring in this (old) house. There's no neutral at the switch and no live at the wall light (other than the switch output), so it's not easy to power the Shelly while the light is turned off. Is there anything I can do in this case? It seems that the Shelly doesn't have an action for power-on (feature request?!). I also did try wiring as per the diagram for "Turning On/Off 'Special'", but still couldn't get any actions to fire. Before I start tearing up floorboards, is there anything else to try? In particular,

- might I be able to do something with MQTT?

- if I had a different Shelly relay (this is a Shelly 1) would anything change?

- can I get a script to run at startup with the latest firmware?

- Dave