Shelly Pro 4PM

condiosz

Hi,

Since the Shelly Pro 4PM was released, I was wondering where Shelly wants to discuss issues found with this new device.

Are we supposed to create a ticket for every single issue? That would create a lot of tickets

The image below is for reference of one of many issues I found, where I am unable to enter a static IP address.

It just always says 'invalid format', though I assure you: they are valid

So, where to throw all the feedback? Anyone knows?

Thanks!

Seven of Nine

This is a known bug.. I've reported yesterday evening and direclty forwarded to the DEVs..

Workaround until it gets fixed: use curl command line tool to set the fixed IP via API.. this is an example request for the wifi interface (sta):

Code

curl -X POST -d '{"id":1, "src":"user_1", "method":"WiFi.SetConfig",
>  "params":{"config":{"sta":{"ipv4mode":"static","ip":"192.168.178.137","netmask":"255.255.255.0","gw":"192.168.178.1","nameserver":"192.168.178.1"}}}}' http://192.168.178.137/rpc

for Ethernet (Eth) it's similar:
https://shelly-api-docs.shelly.cloud/gen2/Component…mComponents/Eth

If you find additional issues please report here.. I'll validate an create bug reports in their internal bugtracking system..

condiosz

Hi,

Thank you so much for that.

Firmware version: 0.6.10

Firmware build ID: 20210810-125223/0.6.10-g11bf9a3

Web build ID: 1.3.0-HEAD+g941e9d9

So far :

1. for Ethernet (Eth) it's similar: it doesn't work

Code

curl -X POST -d '{"id":1, "src":"user_1", "method":"Eth.SetConfig", "params":{"config":{"sta":{"ipv4mode":"static","ip":"172.16.2.120","netmask":"255.255.252.0","gw":"172.16.0.1","nameserver":"172.16.0.1"}}}}' http://172.16.2.120/rpc

result:

Code

{"id":1,"src":"shellypro4pm-xxxxxxxxxxxx","dst":"user_1","result":{"restart_required":false}}

But the setting is not updated

2. Authentication works well with

Code

curl --digest -u admin:password 'http://172.16.2.120/rpc/Switch.Set?id=0&on=true'

for example, though it is a pity only 'admin' is allowd as name of a user.

Also, I do not get any response, and have to relay on the curl exit code:

Code

{"was_on":false}

Not a bug, just a remark

Took me some time to figure out the new curl syntax with authentication.

I have not found a way to use syntax in point 1 url yet, to send a valid command.

This is no issue, devices that have a password are merely child protected
Small remark is that since everything goes over http protocol, all is visible on the network with a sniffer.

Finally, it is SO cool the device supports http callbacks. The PRO didn't and so had to rely on other methods to get the status of the relays in sync with the server.

Further: Also cool is now timer in seconds in stead of minutes.

And what a cool API spec documentation! It looks fabulous!

I'll be testing the switch functionality a little bit later...

Thanks again for your valuable information and sharing of this. I really do appreciate it!

condiosz

And, "Webhook Edit" does not seem to save changes made to the URL.

It seems, to update a URL for a WebHook, one needs to delete and create the WebHook again.

"Apply Webhook" complains the Webhook already exists (which is true, but I simply wanted to update the modified URL).

condiosz

Actually, when I access the device over LAN in stead of over Wifi (whilst both are connected to the same network), the Wifi stopped responding, even though the icon indicates it is still connected. Maybe this is a feature.