Shelly Binding

[alaub81 (Andreas)]

@markus7017

The binding configures the web socket connection automatically and receives status notifications from the device dynamically.

OK, but on my relais there is nothing configured. Is this a mistake? On my HT devices I see the correct ws URL configured.

[alaub81 (Andreas)]

@markus7017

The log entries for BLU Gateway support on 2PM in roller mode here

this log entry (warning) is comming every 1 to 3 seconds:

361 381.704 1 1|shelly_pm_ade7953.c:565 chip_id:0 meas, retrying setup (attempt 1), pend: 1...

after disabling the oh-blu-scanner.js script, the warnings are gone.

On 2pm devices configured as normal 2 output switch, everything is fine!

[markus7017 (Markus Michels)]

try it out, while switching the relays you should see status updates in OH, more or less instantly
The H&T is different, because it goes to sleep mode Therefore it needs an Outbound WebSocket. In this case the device create the WS connection, whereas for devices connected to WiFi this outbound connection is not required.
= all ok

[markus7017 (Markus Michels)]

No clue what that means, maybe contact Shelly support

[Matej_Kotnik]

Hi i had issues with Shelly EM3 Pro not refreshing items via the binding reliably, as i didn’t recognize the exact topic i made my own.
I have 1.5.1 firmware and OH 4.3.2 and it apeaes i dont get measurements regurally when they change so i made my own integration via MQTT.

As i was discusing the topic with a member he pointed me to chime in on official thread, so i make the noise spread about integration options.

So i welcome anyone to take a look at my MQTT project with Shelly EM3 Pro and Shelly Plus S plug.

Shelly Pro EM3 - not refreshing states via Binding, so i Made my own MQTT integration, lets test it out

Hi I have a balcony solar, so i want to mesaure the export to the grid with openhab so i can utilize all the solar power by trigering smart plugs and sync power consumption with solar. The issue i have is that connecting Shelly Pro EM3 to Openhab 4 isn’t working as expected. I installed Shelly binding, added the EM3 Pro to the OH4 with typing in fixed IP of the device and it apears to work, but it stops worrkin in no time at all, like when i turn off EM3 Pro it wont reconect to OH every time,…

Welcome to coment and test it out.

Cheers Matej

[lamazze]

Hello all,

Is this the last DEV build: myfiles/shelly/org.openhab.binding.shelly-4.3.6-SNAPSHOT.jar at master · markus7017/myfiles · GitHub ?

That’s the one I’ve installed, I’ve delete my Shelly Things, but after that the openhab inbox doesn’t show any of my Shelly appliance, even if I click on the + and then scan for Shelly.

Am I doing something wrong ?

My version of OpenHab is 4.3.5-1

Edit: I’ve found two types of errors:

2025-05-07 11:54:20.887 [WARN ] [core.thing.internal.ThingManagerImpl] - Could not normalize configuration for ‘shelly:shellyplugs:b58617’ because the thing type was not found in registry.

2025-05-07 12:01:12.092 [INFO ] [g.discovery.internal.PersistentInbox] - ThingTypeUID shelly:shellyem for discovery result with ThingUID shelly:shellyem:34945473e8eb not found, retried 20 times, aborting

[lamazze]

Update. I’ve tried what the BETA readme says:

stop OH
run "openhab-cli clean-cache"
start OH wait a while until fully initialized
open OH console, run "feature:install openhab-transport-coap"
copy jar to addons folder
run bundle:list on the OH console and make sure, Shelly binding shows up with status active

But I still see these kind of error and nothing in inbox

2025-05-08 19:51:53.253 [INFO ] [g.discovery.internal.PersistentInbox] - ThingTypeUID shelly:shellyem for discovery result with ThingUID shelly:shellyem:34945473e8eb not found, retried 20 times, aborting

Any ideas ?

Update 2: I’ve switched back to v4.3.0. I’ve got back all my Shelly items except for one strange thing, one of my Shelly Door Window BLU (shelly:shellybludw) has lost all his channels except for device#alarm and device#wifiSignal. What could explain that ??

Update 3: this will be my last edit for a while since I’m mostly talking to myself. v4.3.0 works for me but not 4.3.6 or 5.0.0 (error about “normalize configuration” or “discovery result not found”). Lost some channels, was about to that them manually from a previous configuration and a last test of adding/removing the jar fixed the problem. Going to monitor the accuracy of the BLE Door Window I’ve placed recently: one is outside and at a serious distance from the Gateway (BLE Gateway) but it works and the signal is really not bad.

[scheuerer]

Today I noticed some problem with my Shelly plus 1 with FW 1.6.1

I have had some power down in the garden (water) and therefor the power from the Shelly plus 1 went off. After putting back the fuse, the Shelly bootet, but was not going to become online in the OH 4.3.5. Message in the Thing: “Error Connection” I have had to disable him and enable him, to bring him back to online.

Has some also noticed somthing like that?
What can I to bring him online again, without manuell doing something?
Older Shelly1, oder Shelly 2.5 have not this problem. Only the shelly 1 Plus…

This problem has been already reported in the Shelly forum:

Shelly1plus und openhab - Shelly Forum

Additionally information… I’m using the AddOn module here for temperature and humidity….

[milo (M)]

Hi everyone,

I’m seeing an issue with one of my Shelly devices after updating to firmware 1.6.1.

Thing status:

Thing 'shelly:shellyplus1pm:441793cea354' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Unerwarteter Fehler - WebSocket error

This happens frequently, and the device keeps going offline/online intermittently.

Important note: All my other Shelly devices still running on firmware 1.5.1 are working perfectly fine and do not show this issue.

Is anyone else experiencing this with 1.6.1? Could this be a firmware-related problem?
Would appreciate any feedback or suggestions.

Thanks!

[BG56 (Bernhard Geis)]

Yes, I have the same problem with two shellyplus2pm on 1.6.1. The other shelly devices run perfect with 1.5.1.

[milo (M)]

Is there a way to downgrade?

[BG56 (Bernhard Geis)]

In the past it was possible to downgrade from https://archive.shelly-tools.de/assets/images/shelly_logo.png
This site is no longer accessible … so we have to wait for the next version or until Shelly provide a downgrade possibility. I have several shellyplus1 devices but only one provide 1.6.1 update. The other shellyplus1 devices only provide 1.6.0-beta2. This is possibly an indication that Shelly stopped 1.6.1 upgrade.

Wenn I go with the mouse over “ERROR: COMM” it says “Unerwarteter Fehler - WebSocket error”. After a while it is online again and than again “ERROR: COMM”.
I’m not sure if this is the right error message in the openhab.log:

2025-05-18 14:16:46.328 [INFO ] [b.core.io.websocket.log.LogWebSocket] - WebSocket error: java.util.concurrent.TimeoutException: Idle timeout expired: 10000/10000 ms

Not sure if this is a Shelly or Openhab problem

[Oliver2 (Oliver)]

1.6.1 is a controlled release, meaning it is being rolled out in phases, not all devices will receive the update immediately. You need to check from time to time if it is available for your device.

[Oliver2 (Oliver)]

@BG56

provide a downgrade possibility

Did you try downgrading with the Shelly-manager?

[DrRSatzteil (Thomas Lauterbach)]

Same for me

[milo (M)]

You can access it via mobile still…but I can’t find firmware 1.5.1

[scheuerer]

Here comes a litte guide how to downgrade:

1. Go to the list with links with contains links for get the right firmware to download later:
   → Manuelles FW Download ab Gen2 !!! Es muss erst FW. 1.3.3 oder höher installiert sein !!! - Shelly Inside - Shelly Forum

Name	Link
Shelly Blue Gateway	https://updates.shelly.cloud/update/BluGw
	https://updates.shelly.cloud/update/EMG3
	https://updates.shelly.cloud/update/I4G3
Shelly Mini 1 Gen3	https://updates.shelly.cloud/update/Mini1G3
Shelly Mini 1 Gen4	https://updates.shelly.cloud/update/Mini1G4
Shelly Mini 1 PM Gen3	https://updates.shelly.cloud/update/Mini1PMG3
Shelly Mini 1 PM Gen4	https://updates.shelly.cloud/update/Mini1PMG4
Shelly Mini PM Gen3	https://updates.shelly.cloud/update/MiniPMG3
Shelly Plug S Gen 3	https://updates.shelly.cloud/update/PlugSG3
Shelly Plus 1	https://updates.shelly.cloud/update/Plus1
	https://updates.shelly.cloud/update/Plus10V
Shelly Plus 1 PM	https://updates.shelly.cloud/update/Plus1PM
Shelly Plus 2 PM	https://updates.shelly.cloud/update/Plus2PM
Shelly Plus H&T	https://updates.shelly.cloud/update/PlusHT
	https://updates.shelly.cloud/update/PlusI4
Shelly Plus Plug S	https://updates.shelly.cloud/update/PlusPlugS
	https://updates.shelly.cloud/update/PlusPMMini
	https://updates.shelly.cloud/update/PlusRGBWPM
	https://updates.shelly.cloud/update/PlusSmoke
Shelly Plus Uni	https://updates.shelly.cloud/update/PlusUni
	https://updates.shelly.cloud/update/PlusWallDimmer
Shelly Pro 1	https://updates.shelly.cloud/update/Pro1
Shelly Pro 1 PM	https://updates.shelly.cloud/update/Pro1PM
Shelly Pro 2	https://updates.shelly.cloud/update/Pro2
Shelly Pro 2 PM	https://updates.shelly.cloud/update/Pro2PM
Shelly Pro 3	https://updates.shelly.cloud/update/Pro3
Shelly Pro 3 EM	https://updates.shelly.cloud/update/Pro3EM
Shelly Pro 4 PM	https://updates.shelly.cloud/update/Pro4PM
	
Shelly Dual Cover	
	https://updates.shelly.cloud/update/ProDimmerx
Shelly Pro PM	https://updates.shelly.cloud/update/ProEM
	https://updates.shelly.cloud/update/ProRGBWWPM
	https://updates.shelly.cloud/update/S3EMG3
Shelly Wall Display	https://updates.shelly.cloud/update/WallDisplay

So e.g. for a Shelly Plus 1: https://updates.shelly.cloud/update/Plus1

Copy and paste this into any browser, and you will get this e.g. back:

	
stable	
version	"1.5.1"
build_id	"20250318-152131/1.5.1-g01dd7ff"
url	"https://fwcdn.shelly.cloud/gen2/Plus1/97cbb4cc3bede3f3acd5b12acf132358aa40ffb8189e11b865c15a737a62bb71"
beta	
version	"1.6.0-beta2"
build_id	"20250428-114746/1.6.0-beta2-g88148f5"
url	"https://fwcdn.shelly.cloud/gen2/Plus1/1441cf9c6540fc706d9e7326747811bde17d930b8dbc66f4aa52a63f40397afe"
time	1747582199

Then you go via the UI to the Shelly Plus 1, to the section setting, firmware,
and paste the line you got back with starts with “https://fwcdn…” from the browser to the field “Firmware file image link”

Press the “update from Link” button, and your shelly plus 1 will be flashed (downgraded) with the 1.5.1 version and will do a reboot.

Thats it… Have fun by doing a downgrade…

PS: 1.5.1 works fine now for me and OH and getting alone online again…
PSS: I would recommend to also flag in the Shelly the setting “not to do an autoupdate”:

[BG56 (Bernhard Geis)]

Thank you for your help! The downgrade to 1.5.1 worked on the two shellyplus2pm (Markise, Markise-Rollo). The shellyplusi4 (Kueche Taster) is still on 1.6.1 as I didn’t experience problems.

[milo (M)]

It’s already fixed

https://github.com/openhab/openhab-addons/issues/18684

You can download the jar file no need to downgrade

[scheuerer]

Some update. There is now a Firmware 1.6.2 ready for download, which makes the scenario much much worser. So far, it was possible to bring the shelly with an disable and enable in the thing back with the 1.6.1. Now this works only for a minute and the websocket error is there..´
Also it it not more possible down downgrade to the 1.5.1. The file is missing on the backend server.

So all of you which want to try the 1.6.2, please be aware, that you cannot downgrade anymore to the 1.5.1