I was on OH 3.3 (Windows 10) until I updated to 3.4.3 today due to my new Shelly Plus Plugs were not supported by former binding version. After the update, I unistalled the official Shelly binding, did feature:install openhab-transport-coap via console and put org.openhab.binding.shelly-3.4.3-SNAPSHOT into addons folder. After restarting OH, all Shelly things showed up Error:Handler (not sure about the exact wording). I then tried to install Shelly Beta from Marketplace, but I got the same error-message in Main UI as mentioned a few times at the beginning of this thread (Installation of add-on marketplace:139554 failed). I then went through this thread compeltely and recoginzed that the official binding does support plus devices also. I then deleted the jar and installed the official binding again. All existing Shelly Things come back online, and the plus plugs were found by autodiscover. However, both plus plugs are shown offline and following errors are shown:
English: IP-address of shelly device not configured
English: the device is currently not supported. A newer version of the binding might be required.
Clearing cache and tmp, restarting OH and Windows did not help. Any hint what to do now?
Edit: I also get tons of log entries - not sure whether this is somehow related to the issue above:
2023-04-28 12:31:00.001 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler ShellyRelayHandler tried updating the thing status although the handler was already disposed.
I found this thread on github where changing CoIoT to peer mode solves the issue for others. But unfortunately not for me Any help is appreciated!
You need to use the DEV build, this is linked above. The market place installation doesn‘t work. I assume a syntax error in the definition, but couldn‘t figure out the problem.
Download the 3.4.3-SNAPSHOT jar
remove the version, which comes with the dist
re-install the coap transport feature
copy jar into addons folder
run discovery
I just added a ShellyPlus 1PM (FW 0.14.1) to my Home and integrated it to my OH 3.4.4 installation. I replaced the Shelly binding with your current 3.4.5-SNAPSHOT release. The ShellyPlus 1PM gets found and added to the list of things - great!
Yet there are a few issues or questions:
channel shelly:shellyplus1pm:[id]:device#accumulatedWTotal is of type Number:Power - that should be of type Number:Energy when reporting kWh, no?
that channel is reported as kWh and incrementing very slowly. Looks like its divided by 1000, so its actually reporting MWh?!?
how is that channel related to the MQTT status? Right now the item linked to that channel is reporting 0.002kWh while this is the MQTT message: shelly_notification:161 Status change of switch:0: {"id":0,"aenergy":{"by_minute":[42.844,43.326,43.326],"minute_ts":1687111259,"total":6743.324}}
in the Shelly Manager I see a large count (>1k) of “Protocol Messages”. When hovering over that count is says: “CoIOT Status: Events are disabled”. What does this mean and how do I enable CoIOT, if needed?
When trying to install the Shelly Beta version from the OH marketplace, installation was aborted with a genetic message “installation failed”. The syntax on the page Shelly Beta with Plus/Pro and BLU Support has been updated to fix the issue.
However, you might need to clean the Marketplace cache folder ‘/var/lib/openhab/marketplace/bundles/139554’.
There should be only one file: org.openhab.binding.shelly-4.1.0-SNAPSHOT.jar
Remove all others.
You might need to restart OH, because the marketplace entries are cached on runtime.
I can’t point the resource file to my myfiles repo, the link format for the installer is not supported.
So, I created a GitHub release in my code repo (e.g. blu_motion2 branch as of today). In the future I’ll create Beta release from time to time, when I have something stable (e.g. after a PR has merged). Check the release notes for the current one.
The might be merged PRs, which go into the next milestone build
I’ll provide beta versions (stable DEV versions)
And the myfiles repo holds the current development status (unstable)
I think most users should go with the release or beta version, but it you want to stay top of line (e.g. you need supported for new Shelly devices), then you could select the DEV build.
Hi,
I don’t know whether it is the right place for this topic. If not please advise …
On autodiscover of shellies (Shelly3EM in this case) with the shelly beta binding I have following issue: there is no differentiation between the separate meters of some items!
For example the electrical current for meter 1:
…for meter 2:
… and for meter 3:
They all have the same name. Do I have to change that manually to seperate between the different meters? Or did I a mistake?
I’ve posted a question about totalKWH on e Pro 3EM (here).
Should that be solved with the Beta Binding for Shelly?
Unfortunately, I wasn’t able to uninstall the official version yet. When trying to uninstall from the UI, I get errors in openhab.log [ERROR] [internal.handler.ScriptActionHandler] - Script execution of rule with UID 'washingmachine-5' failed: An error occurred during the script execution: Cannot invoke "org.openhab.core.model.rule.scoping.RulesClassCache.get(Object)" because "cache" is null in washingmachine
for seemingly unrelated items, the UI breaks (404) and I have to restart openhab completely.
What’s the right procedure to uninstall the official binding and switching to beta?
from my point of you, this has nothing to do with it binding. Exception shows problem in your rule. Try to simplify the to Nail down tissue.
Please post any questions or problems Related to the binding here:
This post also includes a link to the DEV build and READMEbeta shows how to install it. If you already install it the beta version Make sure to remove it
In this case As a users could also help or benefit from the discussion to solve issues
thx
I have 2 ShellyPro3EMs in use. One finds more items than the other. Temperature is missing, for example. Firmware is 1.3.2 on both. Do you happen to know what could be wrong? Binding version is 4.2.0.202403290805.
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.0.x and 3.4.x are outdated.
Any help is appreciated!
…
