Shelly Plug S Gen3 communication issue

Setup, Configuration and Use Beginners
,
1

Hello,

I have just purchased 2 new Shelly Plug S Gen3 as i wanted to extend the range of my smart plugs.
I’m facing an issue to add them into OH. After configuring them in their own Shelly application and assigning static IP, I can not get them to communicate with OH.

I have another 2 older model Shelly Plug S, and have no issues having them connected.

I have also tried to update to the latest stable OH version (I’m on 4.2.3), without any success.
The error what I have is "An unexpected API response. Please verify the logfile to get more detailed information. "

I have checked in the Shelly debug logs in the webinterface, which shows shelly_http_server.:267 no handler for ‘/settings’

Searching the forum, I found that others do have issues with new gen Shelly items and the current Shelly binding. I just wanted to check if anybody has any solution, and how to add them into the system…

2

I had some issues with my Shelly S plugs getting same error as you posted and I was able to correct it by manually defining mine as ShellyPlus plugs I am in US so may not be same .Oddly my older Shelly plug US plugs worked fine too until I upgraded then I had to change them as well. Might be worth a shot setting them manually and see.

1 Like
3

This worked for me also. Thank you very much!

4

I had the same problem with a new Shelly Plug S Gen3.

Looks like the shelly binding does not support it yet and this device type is falsy identified as Shelly Plug S in the inbox. The ShellyThingCreator does not list the new device types S3PL-00112EU (where “EU” will probably be replaced for the other markets like “IT”, “UK”, “US”).

BTW the Shelly Plus Plug S V2 that has improved mechanical properties seems also not to be supported yet with its device id SNPL-10112EU.

Manually adding a “shelly:shellyplusplug” thing also solved the problem for me.

5

Thanks!
I just wanted to upgrade to 4.3.0M5 (without success) to test if this GEN3 type device is supported in the new addon version.
Hopefully someone who can upgrade to the latest milestone or snapshot could verify if these devices will be supported or not.

6

It is not a matter of updating openhab. You need to install the latest version of Markus‘ binding (snapshot version) from his GitHub repo.

7

I opened a pull request but I have no feedback from Markus yet. Let’s see what he thinks about it.

8

Hi, I had the same problem that fortunately I solved by updating to the stable version 4.3.0 released in recent days. In fact, with my Shelly 1 gen3, I always got a communication error because the bind asked to authenticate the Shelly with user and pwd. With the new release, however, the shelly 1 gen3 is recognized correctly because it is no longer necessary to enter the username but only the password. Obviously this is asked of you only if during the configuration of the Shelly, you decided to protect access to the device with a pwd. Try…
Good luck.

1 Like