With the new private build everything seems ok, no error in the log and the wifi signal now it’s ok
Thanks a lot!.
ok, then it seems that OH 2.4 doesn’t support that unit. good to know.
Could you spend 5 mon on searching in the community? I’m pretty sure that other people experienced the same. Maybe we could copy the gson jar directly to the addons folder an then stays.
Yes I’ve found others around suggesting to copy the jar in the add-on folder, I can test it tomorrow and let you know if it survives a clean cache.
Good job! and Good night!
appriciate ![]()
It seems that the milliwatt fix also resolved the roller control value…could it be related?
With the latest private build the position gets updated correctly after a stop during the run.
hmm, mostly not, but…
could you do some intense testing with the rollercontrol + rollerpos channel making sure that slider works, percent gets updated properly, slider is adjusted when roller is stopping
Played a while with roller control and rollerpos, everything is working as exptected.
Every change to one item gets reflected to the other after the stop. ![]()
perfect, thx
I can confirm that copying the gson-2.8.5.jar in the addon folder makes everything survive a clean-cache in my OH 2.4 env.
ok, that makes way more sense than the bundle:install
I’ll add that to READMEbeta.md
Hi,
upfront, thanks for this great binding. I am using shellys just a few weeks now but I think they are really great and from the price perspective one of the best things to make a non-smart home really smart ![]()
Just one thing I would like to ask you for support even its a general “blind-topic” maybe.
I have following usecase for the blinds. A Widget with 3 buttons.
[UP] [Home] [DOWN)
UP = blind up to 0%
DOWN = blind down to 100%
they are straight forward but
Home = Blind down but open a little bit - maybe like down to 100%, wait for finishing this and afterwards up again for about 3%?
or is there another way?
So 2 topics here:
1.: Can someone share his implementation to reach this? Rules or is there another way?
2.: Does someone has a nice widget as I am too bad in html/css coding ![]()
This is my current implementation: Maybe this could be bind in one Widget instead of 4 items in dashboard ![]()
Thanks in advance for your help.
Stef
This is nothing the binding can or should implement.
You can achieve this by using a virtual item with mappings and a rule triggered by this item.
You will find many examples searching the community…
You can calibrate your Shelly roller-Switch and then set the position to a dedicated value.
Like set the ‘Roller Position’-Channel to e.g. 75% or 34%
Take a look at settings → Positioning Controls in your Shelly-WebUI
Hello everybody,
Please excuse my bad english, the google translator will do his best.
Now my question:
Is it possible that the values of the Shelly1 PM in the KWh range are displayed by a factor of 1000 too high?
Is it possible that the last shelly update provides Wh not kWh?
Somehow the values did not match since the update to org.openhab.binding.shelly-2.5.0-SNAPSHOT.jar 04-Dec-2019 01:16 677.51 KB. and Firmware version of Shelly device 20191127-095910/v1.5.
OH is the version
openHAB 2.5.0 ~ M6-1 (Milestone Build).
The whole is instaliert on a Pi 4.
hmm, I checked the code
- device reports Wh (total)
- will be converted by the binding (/1000 = kw/h)
- and then mapped to the channel
Do you use firmware version 1.5.0 ? maybe try 1.5.6.
please check what’s reported when opening /status
should be the same value excep *1000
Hello Markus, thanks for your quick reply. ![]()
My Shelly 1PM works with the firmware 1.5.6.
The status value is actually the displayed value without / 1000.
I found here “https://shelly-api-docs.shelly.cloud/#shelly1-1pm-status” that the status is not in watts hours but in watts minutes. Could that be the mistake?
If that were so, you would not have to divide by 1000 but by 60000.
That would come closer to real values.
It is definetly like this. I am using the Shellies via MQTT and use a JS transformation to transform the Wartt minutes to KWh. I also first made the mistake to divide by 1000 and now get correct values with /60000.
all good, you are right, try this one:
https://github.com/markus7017/myfiles/blob/master/org.openhab.binding.shelly-2.5.0-SNAPSHOT.jar
fyi: deadline for 2.5 is 12/8, I would appreciate more testing and feedback (even if you see no issues).



