Shelly Binding

Add-ons Bindings
,
2786

I expect that OH 3.3 comes with Californium 2.0, whereas 3.4 milestone build has switched to 2.7

I added the jar build to the Community Market Place, The binding does not yet show up, you need to enable the market place and previews (both options in Settings:Community Marketplace)

  • remove the files from the addons folder
  • Go to Settings:Bindings and search for “Shelly Beta with Plus/Pro support”
  • install the binding
2787

Hi Markus,

thanks again, I see the binding in the marketplace but when I install it nothing happens. No binding/bundle ist listed in karaf console, nothing in the logfiles. A little crazy, would at least expect some logfile entries about the install or a failure…

2788

try again, I changed the url

as always: If something has changed it might require adjustments. When installing the binding from the UI the loader automatically resolves dependencies like we have with Coap/Californium, but if you copy the jar to the addons folder you need to do the prep yourself. Obviously the included Coap version has changed + the bundle now requires more files then 2.0.

thanks for helping

2789

Hi Markus,

nothing to thank for, I have to thank for your work and kind support!

I tried again to install but get an error in the UI when trying to install:

grafik

Sadly nothing in the logfiles to further indicate what went wrong.

2790

:crazy_face:

I think something is wrong with definition of openhab-transport-coap in 3.4M2. It installed version 2.0.0, whereas the build environment references 2.7.3. I setup a test environment and need to investigate.

Does somebody else has 3.4 M2+ with the binding running?

2791

I found this PR

and this one

That could cause the situation that 3.3/3.4M2 needs Californium 2.0, whereas new builds require 2.7.3

2792

for now try the previous build: https://github.com/markus7017/myfiles/blob/a12594a9967f98f5c4fac54f668fd406664f5b16/shelly/org.openhab.binding.shelly-3.4.0-SNAPSHOT.jar?raw=true

1 Like
2793

Hi Markus,

thanks for the link to the older jar, this one works like a charm for my shelly 1 plus. Thanks a lot and hopefully the binding with gen2 support will come with 3.4 :slight_smile:

Thanks for your work, great support and kind regards,
Daniel

2794

With the previous build you linked to i can see all channels for dimmer2.
So now everything is working.

1 Like
2795

Me too,
i was not seeing the channel Power2 of a Shelly 2.5 with the previous build is ok.

2796

Hello @markus7017 ,

now I had the time to test again.

I just copied latest build from you into my add-on folder. Shelly2pm+ is now found and working (in Switch mode).
I didn’t use californium 2.7!

Thx, I’m very happy with this!! :slight_smile:

CU Frank

2797

Status is as follows

  • OH 3.3…3.4M2 bringt Californium 2.0
  • 2 weeks ago they bumped the version to 2.7.3
  • a new build of the binding will be build with this dependency
  • 3.4M3 will bringt Californium 2.7.3
  • it doesn’t work if the dependency in the binding jar doesn’t match the OH platform
  • at the moment I’m looking for a way to build a new 3.3 version
2 Likes
2798

I think I found a solution

  • 3.4.0-M2 build, which also serves 3.3.0
  • 3.4.0-M3 build, which runs on the current SNAPSHOT build of the Distro and M3+

Please help testing, I have on the 3.4-SNAPSHOT environment. When copying the jar to the addons folder make sure to delete the existing one (different name). Use bundle:list to see status, the new builds show up as “Shelly Binding for Gen1+2”.

2799

Hi markus,

I did test your 3.4.0-M2 on my OH 3.3.0 regarding the shelly 1 plus device but I only get status Offline with error message: unexpected error: WebSocket connection closed abnormal. Older devices like shelly1 and shellyswitch25 are working fine.

In openhab.log I do not get an error message, I just found “Added new thing ‘shelly:shellyplus1:3c610572ed5c’ to inbox.” there.

Under Bundle:List I have the follwoing entry:

257 │ Active │ 80 │ 3.4.0.202210071549 │ openHAB Add-ons :: Bundles :: Sh

2800

I fixed a JSON parsing problem and improved logging in this situation, please try again

2801

Many thanks Markus, Problem solved :slight_smile: I will do some further testing soon.

2802

When I try to add a link to a point (category lightbulp and semantic call point), I can choose the thing (e.g. shelly 1 plus) but the thing will not be added to the point and I see no channels. This happens when I use Google Chrome.

With Microsoft Edge Browser, I can add the thing and link the channel successfully.

2803

I have no clue why, if so it’s a UI issue. I not on Windows :slight_smile:

Good news,
PR #13439 has been merged, so Plus/Pro support will be included with the next milestone build / 3.4 final.

I updated the build:

  • 3.4.0-M2 build, which also serves 3.2.0 and 3.3.0, but not current dist snapshot/nightly

It includes another fix: When roller was moving and reached open or close state the position was not updated (0/100%).

1 Like
2804

Hi Markus,

I might have a feature request for the “shelly dimmer 2”, cause I did not found a solution to solve my problem.

I plan to install 10 dimmable lights across a wall, which will usually be powered on or off in parallel. I did not found a solution to dimm the 10 lights in parallel. I have to do it for each dimmer itself which is quite uncomfortable,

Usually I set the dimmer function via Model/Shellydimmer2/Item/Helligkeit, where I can set a value between 0-100. Do you see a chance to set the dimmer value 0-100 for multiple “shelly dimmer 2” actors in parallel? The idea is then, that all 10 lights have allways the same brightness.

2805

Why dont you put your 10 Dimmers into a group and send the brifhtness command to the group?