BedroomStandingLamp_mode is a dummy and NOT linked to the actual mode channel.
Also definded is a string (BedroomStandingLamp_ColorString) that takes as input {red/green/blue/white/etc}
I also created the following rule
rule "BedroomStandingLamp_mode received command"
when
Item BedroomStandingLamp_mode received command
then
switch(receivedCommand) {
case ON : BedroomStandingLamp_ColorString.sendCommand("blue")
case OFF : BedroomStandingLamp_ColorString.sendCommand("white")
}
end
BedroomStandingLamp_mode controls the color/white through the rule
BedroomStandingLamp_Dimmer controls both the brightness of the white and the gain/brightness of the color through the Group
I even connected it to Google Assistant and I can say “Turn on/off color” to control the bulb.
Hope this helps
@markus7017, I have a question. The Shelly devices are updating quite frequently, especially the Pro 3EM. As a matter of fact, after some time, my OS switches the filesystem to read-only because of the excessive logging. This happens with openhabian on a Pi4.
Is there a way to restrict shelly logs to warnings or change the default log level to verbose to reduce the amount of events that are logged?
I’ve got a new Shelly Motion 2 but OH 3.4.4 and also OH 4.0.0.M3 does only discover a shellymotion (Gen1). There is no channel for the vibration-sensor available, and the motion-channel stays “off” when I move in front of the device (the Web UI shows a motion-alarm!).
If I try to create the thing manually, I can’t see any thing-type “shellymotion2” in the list as described in the OH-docs
you could go to the OH console and enter
log:set WARNING org.openhab.binding.shelly
There is also a way to filter log output, so you could suspress messages based on an regex expression. Search for log filter or stthg liked that. I know there is a post from me, but I didn’t bookmarked it. Let me know if you can’t find it
I updated calculation of consumption values for relays (Gen1+2) devices. In addition OH4 framework does stricter checking on the item unites and the binding has some issues in the channel definitions. Several other bugs has also been fixed (thanks @igi for testing).
I need help to verify that updating the relay energy channel works, show the correct values and units.
Please help!!
Gen 1: 1PM, 2.5, 4Pro, EM, 3EM
Gen 2: Plus 1PM, 2PM, Pro 1PM, Pro 2PM, Pro 3EM
Important: You need to delete and re-discover the things
I’ve tried the current DEV version (from yesterday) with a brand new OH 4.0.0.m3 installation, but there is no way to add a shelly-motion2. It is discovered as a shellymotion (gen1) and the motion-channel doesn’t change when I move in front of the device (the WebUI of the device shows a motion-alarm and the mqtt-state changes).
How do I add a shelly motion gen2 correctly?
I tested my 2.5 and it fits. 20 watts on channel 1 according to WebUI of the device, 20.41 watts in OH. Channel 2 is not in use atm but the accumulate watts value was 20.41 too.
I think the calculations for the totalkWh on Gen2 - I’m using a Plus 1PM - is wrong. Per API documentation the aenergy.total object is returning Watt-hours which matches my observations. So you may need to change the calculations from:
… ok, we are getting there. Now the item reports 1/1000th of what I’d expect. Might be a UoM thing, not sure where the gratuitous 1000 scaling is coming from.
Was a bit let down. The window sensor seems to be cool, but I’m not sure about the ZWave line…
I fear they try to get kind of a jack of all trades.
And I keep rooting for Matter and even more Thread.