Shelly Binding

markus7017 · March 29, 2024, 8:17am

The PR is merged, so the fix should be included in the SNAPSHOT build. If this doesn’t work try the DEV build I uploaded 10min ago (follow the READMEbeta instructions)

@MartOs @life_is_life @the.gangster @glilienthal Please verify and report test result

Note: The DEV build is always newer than the version in the official Distro or Milestone builds. Current development is based on 4.2-SNAPSHOT, 4.1/4.0.x and 3.4.x are outdated (not the latest feature/fix level).

MartOs · March 29, 2024, 8:28am

I tried your 4.2 DEV build but get this error:

Error while starting bundle: file:/openhab/addons/org.openhab.binding.shelly-4.2.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.shelly [309]
  Unresolved requirement: Import-Package: org.eclipse.californium.core; version="[2.7.0,3.0.0)"

	at org.eclipse.osgi.container.Module.start(Module.java:463) ~[org.eclipse.osgi-3.18.0.jar:?]
	at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:445) ~[org.eclipse.osgi-3.18.0.jar:?]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [bundleFile:3.7.4]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [bundleFile:3.7.4]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:520) [bundleFile:3.7.4]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [bundleFile:3.7.4]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [bundleFile:3.7.4]

ohuser · March 29, 2024, 9:51am

Hi @markus7017 ,
I have never reverted back to the original code after I had success with my hack. But as the thing has now gone over the hurdle of initialization, probably reverting to the 4.2ML code would also not make a difference ?

However: I am now seeing the problem that I have also read in other posts. After restarting the gateway, everything runs fine for a couple of hours, but then OH stops receiving events from the BLU sensor. There is nothing suspicious in the OH logs (also with TRACE level), while the script console and also diagnostics on the gateway still show that the notifications go out, e.g.

shelly_notification:209 Event from script:1:
{"component":"script:1","id":1,"event":"oh-blu.data","data":
{"encryption":false,"BTHome_version":2,"pid":32,"Battery":72,"Illuminance":45,"Motion":0,"addr":"3c:2e:f5:bb:c6:67","rssi":-62},
"ts":1711704727.37}

I have now enabled MQTT in parallel, this works fine, all messages arrive on the broker and in OH.

I would be happy to provide more debug information, but the logs really show nothing.

markus7017 · March 29, 2024, 12:14pm

as I said follow the instructions READMEbeta, you need to do the feature:install

MartOs · March 29, 2024, 1:28pm

I finally managed to install this. I can see, discover etc. and no more errors in the logs, but there is still no Total kWh.

Now on the latest openhab snapshot too

markus7017 · March 30, 2024, 4:11pm

are you using the snapshot build or my dev build, bundle:list shows an older version

lamazze · March 30, 2024, 4:50pm

@markus7017 does the 4.2 DEV supports shellyblugw (blu gateway) ? Thank you

markus7017 · March 30, 2024, 6:03pm

yep

lamazze · March 30, 2024, 6:13pm

Cool thank you, I will test it tomorrow or Monday.

lamazze · April 1, 2024, 5:24pm

I’ve installed the 4.2 DEV and indeed now the Bluetooth Gateway is now added.
The “Enable BLU Gateway support” is checked.
I press the BLU door/window button, and I check in the Inbox and I don’t see the device.
I’ve tried several times.
In the log window of the Gateway I see this message:

shelly_bluetooth_sca:65 bluetoth scanner already taken
Unable to start OH-BLU Scanner, make sure Shelly Gateway Support is disabled in device config.

I also see this message

shos_rpc_inst.c:355 0x3ffe1ec4: duplicate id ‘shellyblugw-3ce90e7d66fc’
shos_rpc_inst.c:230 Shelly.GetStatus via HTTP_in POST 192.168.1.3:36944

What am I doing wrong ?

PS: both device have the latest software

markus7017 · April 2, 2024, 5:00pm

Did you unchecked the „enable BT gatewa“‘in the device UI. My script will not start until you‘ll see a „started successful“ message

lamazze · April 2, 2024, 5:25pm

OK I’ve added the door/window thing
What I don’t understand is why do I have to uncheck the “Enable Bluetooth gateway”… in the gateway.
Do I have to leave it always unchecked ?

MartOs · April 3, 2024, 2:05pm

Hi,

I tried this again. Reset everything to scratch and followed the instructions very carefully.
The binding discovers my things, but totalkWh is still missing from my EM50 meters.

What am I doing wrong?

Simon_B · April 5, 2024, 1:29pm

Hi, do you know if the new shelly uni plus would be supported?
Regards
Simon

markus7017 · April 5, 2024, 9:24pm

yes, it is
check README.md, it lists all supported devices

Simon_B · April 6, 2024, 4:59am

i cant find the Shelly Plus Uni only the shelly uni.
https://www.shelly.com/de/products/shop/shelly-plus-uni

markus7017 · April 7, 2024, 12:51pm

the link you sent is the Plus UNI, wehre is the problem?

markus7017 · April 7, 2024, 12:56pm

Enable Bluetooth gateway is the Shelly support for redirecting those messages to their cloud
Obviously it is not compatible to local scanners
Keep if off

markus7017 · April 7, 2024, 12:56pm

I updated the DEV build to include support for Plus HT Gen3

It also includes a change to use a different value for src in RPC messages, this might help to get rid of “duplicate id” messages in the device debug log, which seems to create trouble when running devices for a longer time. Check here: Non deterministic malfunction of shelly 1 plus

As well as

github.com/openhab/openhab-addons

[shelly] Enable accumulated channels for Shelly Pro 3EM

openhab:main ← leifbladt:fix-accumulated-channels-shelly-pro-3em

opened 10:24AM - 24 Mar 24 UTC

leifbladt

+2 -1

# Description The Shelly Pro 3EM does not show the accumulated channels on the …device, although the values are transferred from the device. The reason seems to be this [commit](https://github.com/openhab/openhab-addons/pull/15922/commits/3e120b7ecd4cfd0593a09c22fb2de0afebe9bdaf). The **Pro 3EM** has no internal relay (only available as an add-on), unlike the **3EM** and the **Pro EM**. Fixes #16552 openHAB Community: [Discussion](https://community.openhab.org/t/shelly-binding/56862/3742)

@MartOs try this build

and

github.com/openhab/openhab-addons

[shelly] Add support for Range Extender feature

openhab:main ← markus7017:shelly_rextender

opened 10:33PM - 16 Feb 24 UTC

markus7017

+337 -202

The Plus and Pro series have the so called Range Extender feature. In this case …a Shelly could connect to another Shelly having this feature enabled as hub device via the access point of the hub device. The hub device then acts as a bridge between the host application (OH) and the linked device, which would not be able to connect to OH, because of missing WiFi coverage.

Updated jar
https://github.com/markus7017/myfiles/blob/master/shelly/org.openhab.binding.shelly-4.2.0-SNAPSHOT.jar?raw=true

I need testers

the.gangster · April 7, 2024, 3:23pm

To be honest, I came across that recently as well when I was considering if one of the UNI models would help me in my environment. So I checked the readme and if I am not mistaken it only mentioned Shelly Uni but not explicitly PLUS Uni.
I found it in this commit though.
There you added it to the ShellyThingCreator.java but not to the Readme.md as far a I could see.