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.
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.
I did play around a while until I found a solution:
When I add a new point, and choose type dimmer, I get the values 0-100 for dimming lights, I can add then a new link for each shellydimmer2 and choose âHelligkeitâ
I did test it now with 10 dimmable garden lights and it works perfect.
Is there any possibility to specify the precision e.g. on the thing?
I handle this by specifying a JS profile when linking the channel to the item. I have a mini JS script that does what I need to do on the decimals. I hope this helps.
Yes, my pleasure, I could not do it yesterday as I was from my phoneâŠ
An example of a filterdecimal.js file. I have also other versions to filter the unit out if the binding reports the numbers with units⊠Let me know if youâd like to see it.
(function(i) {
var entier = Math.round(i*100)/100;
return (entier);
})(input)
And I use only the UI for the config of my items, so I canât really help on the .items file syntax. But there seem to be good examples here:
Just upgraded to openHAB 3.4.0.M3 from M2 and have a strange thing happening: My Shelly2 controllers (shelly2-roller) controllers display HANDLER_MISSING_ERROR. Other Shellies (eg shelly25-roller) seem to be fine. Any idea?
Updated to openHAB 3.4.0.M3 (docker alpine) (including shellyEnhancements13439 Add Plus/Pro support, some bugfixes)
Updated both of my Shelly Plus H&Ts
Still was not possible to find the devices via âScanâ button (despite the fact that they were in discovery mode)
But adding them manually via setting IP was possible
Now it seems like its basically working, but it also looks like the values never get updated
I know, that the update frequency of these devices is very low on purpose but at the moment i relly see only the very very first value from the discovering of the device
Ups, you are right. I removed shelly2-roller, because we thought the Shelly 2 doesnât support roller mode lacking the power meter. I can re-add the thing the next days.
Configuring them manually yesterday made me have all of them Online.
Looking at it today again, only the Shelly Plus H&Ts are back to âthe yellow stateâ again (which i do not see anymore because i deleted the things as you said.
This means my Shelly1 and the two Shelly2.5s work as expected after manual configuration â OK for me but also these do not get discovered
I have no idea how this works but at the bottom line, even if i manually configure the H&Ts manually and get them to Online, they never update values and stop working i think
Hi @markus7017 ,
i have a problem with the shelly binding. My shelly motion throws a exception on every update. I am using the milestone release 3.4 M3. Do you know this problem?
thanks for helping
Ralph
> 2022-10-12 19:37:01.258 [WARN ] [.californium.core.network.UdpMatcher] - error receiving response NON-2.05 MID= 10, Token=, OptionSet={"Uri-Path":["cit","d"], "Unknown (3332)":0x53484d4f532d3031233630413432333836463030322332}, "{"blk":[{"I":1,"D":"sens".. 472 bytes for Exchange[R2233]
> java.lang.NullPointerException: null
> at org.eclipse.californium.elements.UdpEndpointContextMatcher.isResponseRelatedToRequest(UdpEndpointContextMatcher.java:80) ~[bundleFile:?]
> at org.eclipse.californium.core.network.UdpMatcher$3.run(UdpMatcher.java:316) [bundleFile:?]
> at org.eclipse.californium.elements.util.SerialExecutor$1.run(SerialExecutor.java:289) [bundleFile:?]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) [?:?]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
> at java.lang.Thread.run(Thread.java:829) [?:?]