Turning Shelly Plus Plug S on/off with Shelly Button1

[Ash]

Hi

I am totally new to webhooks, so please this might be a noob question 😀

I want something very basiv - to turn a Plus Plug S on or off with a Button1.

I managed to do so with my Shelly 4PM, but I can't make it work with the plug.

For the 4PM, I used the code http://192.168.0.232/relay/1?turn=toggle - which then toggles channel 1. Works perfectly.

What code should I use to toggle the Plus Plug S? I have tried the same but with 0? instead of 1?, but it does not work. (and yes, I used another IP 😁)

Perhaps the relay in the Plus Plug S is not called "relay" but something else?

Thanks in advance

/Ash

[Dreckfresse]

Bei einem Gen1 Plug S ist es relay 0, so sollte es auch bei einem Gen2 Plus sein

http://192.168.178.xxx/relay/0?turn=on

Teste mal bitte mit on oder off im Browser mit der richtigen IP

[Ash]

Ok, it works fine through a browser...

Any guesses why it's not working with the Button1?

 

[tvbshelly]

Can you please send a screenshot of the button configuration?

[Ash]

Sure thing.

The plug is now in another IP range than mentioned before - just to rule that out.

Result is the same, though...

I use a fixed IP for the plug to be sure it is reachable through the same IP every time.

Edited August 22 by Ash

[tvbshelly]

6 minutes ago, Ash said:

I use a fixed IP for the plug to be sure it is reachable through the same IP every time.

That definitely makes sense.

It looks absolutely correct to me, that's how it should actually work.

Have you tried what happens if you configure 2x click or long click with the same webhook?

[Ash]

Tried 2x click and 1x long click - it doesn't work either.

Strange that it works in the browser and that the button can toggle my 4PM just fine...

[tvbshelly]

That's really weird, yes

[Olsche]

can you show us the result of

http://IP_your_Button1/settings/actions

(powered with USB) please?

[Ash]

10 hours ago, Olsche said:

can you show us the result of

http://IP_your_Button1/settings/actions

(powered with USB) please?

Here you go:

{"actions":{"shortpush_url":[{"index":0,"urls":["http://10.1.30.206/relay/0?turn=on"],"enabled":true}],"longpush_url":[{"index":0,"urls":[],"enabled":false}],"double_shortpush_url":[{"index":0,"urls":[],"enabled":false}],"triple_shortpush_url":[{"index":0,"urls":[],"enabled":false}]}}

[tvbshelly]

    "shortpush_url": [
      {
        "index": 0,
        "urls": [
          "http://10.1.30.206/relay/0?turn=on"
        ],
        "enabled": true
      }
    ],

This looks correct to me (is enabled) and the URL is exactly the same as in the screenshot @Olsche

[Olsche]

really strange, can you please try with RPC Command?:

http://10.1.30.206/rpc/switch.set?id=0&on=true

or for toggle:

http://10.1.30.206/rpc/switch.toggle?id=0

 

 

BTW: authentication is not set?

[Ash]

7 minutes ago, Olsche said:

really strange, can you please try with RPC Command?:

http://10.1.30.206/rpc/switch.set?id=0&on=true

or for toggle:

http://10.1.30.206/rpc/switch.toggle?id=0

 

 

BTW: authentication is not set?

Doesn't work either and I have not set any authentication (actually I haven't even looked for the setting).
Do I need to make some settings to the plug, perhaps?

[Olsche]

Isn't it a guest network with its restrictions?

[Ash]

15 minutes ago, Olsche said:

Isn't it a guest network with its restrictions?

Actually it is an IOT network, but I have disabled restrictions for these tests...
BUT... Let me try to change the network on the switch and plug to see if it makes a difference - sometimes there are firewall rules you are not in charge of...

[Ash]

After changing to another non-guest/non-IOT network it still doesn't work.

With the code in a browser it works flawlessly and it can still flip the 4PM relays just fine.

This is strange...

[Ash]

1 hour ago, Ash said:

After changing to another non-guest/non-IOT network it still doesn't work.

With the code in a browser it works flawlessly and it can still flip the 4PM relays just fine.

This is strange...

Ok, this IS actually related to the network.

I created a new WiFi profile with the exact same settings as the old one, and now it works.

There must be some settings in the old profile that prevents communication.

 

Thanks guys! Now it works as desired!