Any news about the Plus 2PM device? Have exactly the same issue with the new firmware v1.4.2. The rollershutter is not controllable from OH.
Or is there a chance to downgrade to v1.3.3?
I have about 9 Plus 2PM Devices configured as rollershutters and with firmware 1.4.2. No Problems so far on my setup. But I didnāt try to add a new one. All installed rollershuters are working fine. I am using the included binding version of openhab 4.2.1.
Had issues with 1 out of 5 and deleted it. Did firmware update and want to re add it to OH but this is not possible. The configuration cannot be finished.
Reboot the Shelly device. The Shellies with 1.4.0 firmware then appeared in my OH inbox.
This is not the problem. Device was in inbox and thing was added but initial configuration is not working and so the device is unusable!
Today I performed an update from my OH instance and now the actor is working again.
@markus7017, I see firmware 1.4.2 is out. I assume the binding still has trouble with it?
Added today my first Shelly Flood sensor to my three OH systemās.
Has been working like a charme 
Hopefully OH will never send my a Whatsapp and an Email that the sensor state is ON
in the corridor in the basementā¦
Thanks to @markus7017 and OH developersā¦
Hello and Good Day,
This is my first post to any community forum, so if I break protocol, forgive me.
Over the last few monthās Iāve been building up my openHab system and basically replacing all my devices with ones that can be managed locally. I was really excited with my initial tests with Shelly devices and purchased additional one. Currently have 2 Humidity/Temp Monitors, a Power Monitor, three plugs, and a button.
In setting them up with openHab and the Shelly Binding, most is good, but I keep running into strange situations. The three plugs I got were all received at the same time, are identical devices. Two worked great out of the box, their third just would not connect even though I could reach it directly. All of the devices work in the shelly app. Iāve got the plug to work, but now my button is failing. After uninstalling and reinstalling the ShellyBinding, Iām now getting issues to connect.
An unexpected API response. Please verify the logfile to get more detailed information. But shelly manager seems to have no issues.
And while had the button working, it isnāt even being recognized anymore.
Iām on latest ubuntu, and openHab 4.2.1 (updated today).
Would appreciate some help in trying to figure this out.
Thanks in advance,
Doug
Some small tipps in principle.
So first not OH related,
- Are all you devices have a static IP adress? (in the router, and in the device itself)
- The configuration from battery based device is somehow tricky. You need to connected the via
an USB power to configure them. In battery mode it sends commands you have configured but goes directly into sleep more again, Max livetime via internal bettery is 5 sec, that also this need to be configured.
Have you marked the settings always to find to best APās?, in case you have more APās. - Have you been able to flash the button with the latest firmware?
Now OH specifig:
How you are adding the button to OH?
- via Scanning the network via shelly binding seach support, or direct add them via an IP adress?
The scanning has here and there some issue and will not find the new device.(in my case I need to restart the OH service to find new devices)
Once found they work under the given limitation, e.g. max 5 sec alive.
What does the logfile tell you, when you have enabled the shelly binding for debug or trace mode?
Are you running the latest version. I was fixed here
Hi,
Maybe someone can help me out: Iām on openhab 4.2.1, Iāve got a bunch of Shelly Mini 1PM Gen3 devices, I notice that a button press event doesnāt seem to reach openhab. Iāve created a rule that should be triggered by a long button press, but that doesnāt happen at least half of the time. I havenāt researched the isseu yet, so I havenāt detected any pattern that I can report here, Iām just wondering if anybody else can confirm this behaviour or that it has something to do with my setup.
Are there any developers or users who recognize the issue and can point me to a solution?
Best regards,
Jesse
yes, In my case, the fix works. Means all my devices are now visible. Main Problem was that older shelly devices does not have a name field, in this case the mac address is used as a unique identifier.
Hello @holger_hees
Curiously there are some Shelly 1 devices in the listā¦ā¦so it seems not to be the same problem.
Thanks for taking time to respond and help.
- Re: Static IP Address. Yes for in router. Not necessarily on devices. The IPs of the device seems to be constant. My router matches consistently the devices uses Mac address and Iām typically able to get directly to them by web page. Also, the shelly app also consistently indicates the same address per device.
- All of the devices Iām using are constant USB power, even the button. Max live time is 5 for all devices. I have not configured for next AP; all of my router AP have the same name (mesh routing).
- The button now seems to be connected; but still working to test if button presses are recognized. And yes, Iāve flashed it with the latest firmware (not the beta release).
- My issue continues to be the three shellyplugs.
- Two of the plugs are original 0.11 while the third plug is on 1.4.2. At this point, Iām actually afraid to update the two from 0.11.
I have two openHab systems. As I was looking for solutions, I did the first installation on an older ubuntu box; fairly recent ubuntu, but the machine itself leaves much to be desired and so I bought a new mini-pc that is extremely powerful.
The older openHab is also connected with Alexa and the two plugs on 0.11 and is configured to receive commands from Alexa to turn on and off and that works. The third plug never worked and so I tried upgrading firmware on it but it never worked or was able to be controlled by the first openhab.
Because the first one was a lot of testing, I wanted to start the the new one with a fresh clean install. New one does not have Alexa at this point and so I have the new openhab talking to the first openhab for status updates. But not the plugs or button. If I can get plugThree working, then Iāll considering updating the first two firmwares.
At this point, scanning under the Shelly Binding does seem to find the plugs and so Iāve added them that way, I have added them manually (pick device type, define IP) before as well.
That said, Iāve learned a little more about logs and have found where the API response issue is coming from.
2024-09-02 06:47:39.538 [TRACE] [shelly.internal.api.ShellyHttpClient] - shellyplugus-d4d4da08ecb0: HTTP GET http://192.168.4.169/shelly
2024-09-02 06:47:39.558 [TRACE] [shelly.internal.api.ShellyHttpClient] - shellyplugus-d4d4da08ecb0: HTTP Response 200: {"name":"PlugThree","id":"shellyplugus-d4d4da08ecb0","mac":"D4D4DA08ECB0","slot":0,"model":"SNPL-00116US","gen":2,"fw_id":"20240819-074316/1.4.2-gc2639da","ver":"1.4.2","app":"PlugUS","auth_en":true,"auth_domain":"shellyplugus-d4d4da08ecb0"}
**2024-09-02 06:47:39.559 [TRACE] [shelly.internal.api.ShellyHttpClient] - shellyplugus-d4d4da08ecb0: HTTP GET http://192.168.4.169/settings**
2024-09-02 06:47:39.582 [TRACE] [shelly.internal.api.ShellyHttpClient] - shellyplugus-d4d4da08ecb0: HTTP Response 404: Not Found
2024-09-02 06:47:39.582 [DEBUG] [y.internal.handler.ShellyBaseHandler] - shellyplugus-d4d4da08ecb0: Unexpected API result: 404/Not Found
The address is looks like is supposed to be http://192.168.4.169**/#/**settings
Unless that ā#ā is only for the UI as http://192.168.4.169/shelly responds correctly with json.
Thanks in Advance,
Doug
Are your not properly working devices on firmware 1.4 ?
This version is not approved by our developer AFAIK.
On the new server, they are not working with either firmware version.
I opened a case with Shelly asking how to downgrade the Shelly plus 2PM to 1.3.3.
Their response was Why ?.
I said : Worked fine on OH with 1.3.3, and no longer with 1.4.2
a few minutes ago, they stated: āWe are investigating the issue further and await more information from our developers. Please give us time to investigate and we will notify you as soon as we have more information.ā
My experience is that everything works, but autodiscovery only happens after a reboot of the Shelly device.