Actions not triggering

    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.

    Code
    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

    Hi, i Head exactly that issue, rebooting was useless but shutting and putting back power soldes the issue… rEm: i had the problem on a Shelly dimmer2 and had it again with a i3 i’ve just installed

    Hope this helps

    I'm having issues with the Output switched on/off URL aswell. I have tried with both a local https-url, a local http-url and an external website (https://webhook.site) and neither register anything from the three devices I have tested (Plug S and Shelly1 and Shelly2). The URLs work fine when tested in a browser.

    Am I wrong to believe that the URL should be accessed every time the plug/relay is switched on/off regardless if it's triggered from the physical lamp button, through the app or through the Shelly URL API?

    /L

    I also have the same problem with Shelly Plug S NOT calling the action URL I set up on the device!

    In fact if I configure the URL:s for ON/OFF and save them nothing happens when the switch goes on or off, but if I revisit the plug's home page then I see that the URL:s are not there!

    Is there some kind of procedure that is not obvious one has to go through in order to actually make the entered URL:s be saved on the device?

    Just hitting the SAVE button does not work.

    I am working in off-line mode on a LAN that does not have Internet access.

    No cloud function has been activated.

    Meanwhile I have found out what the problem is:

    Too old f/w in the device!

    But it does not offer an update when I check on the website of the plug.

    I solved it as described here in my other thread!

    Basically I had to force an archived f/w on it and then it could update itself further.

    After that it accepts Action URLs and they do work.

  • Dieses Thema enthält 8 weitere Beiträge, die nur für registrierte Benutzer sichtbar sind, bitte registrieren Sie sich oder melden Sie sich an um diese lesen zu können.