a) The release implementation follows the standard OH paradigm
- brightess = 0 sets also device OFF
- brightness > 0 automatically turns on the device
b) The DEV build includes a new thing config option to disable the Auto-ON so you could set brightness without turning ON the device
Brightness and state could be controlled by linking 2 items(Switch for ON/OFF, Number for brightness-%) to the same brightness channel.
i have a lamp and a motion detector on a shelly 2.5. basically the control works, but i have a problem with the reaction time.
the motion detector is supposed to switch on the lamp immediately. but the lamp is only switched on up to 8s after the motion detector has been switched on.
am i the only one with this problem, or has anyone else noticed it?
rule "Licht Haustuer ein"
when
Item Eg_Haustuer_Bewegungsmelder changed to ON
then
sendCommand(Eg_Haustuer_Licht, ON)
end
logfile
2019-12-28 22:01:33.225 [vent.ChannelTriggeredEvent] - shelly:shelly25-relay:690a17:relay1#button triggered LONG_PRESSED
2019-12-28 22:01:37.941 [vent.ItemStateChangedEvent] - Eg_Haustuer_Bewegungsmelder changed from OFF to ON
2019-12-28 22:01:37.992 [ome.event.ItemCommandEvent] - Item 'Eg_Haustuer_Licht' received command ON
2019-12-28 22:01:38.003 [nt.ItemStatePredictedEvent] - Eg_Haustuer_Licht predicted to become ON
2019-12-28 22:01:38.032 [vent.ItemStateChangedEvent] - Eg_Haustuer_Licht changed from OFF to ON
clear the push action url in the Shelly Web App (this is not yet automatically done by the binding)
Maybe the push event url overwrites the button event url = when the push urls are set the device doesn’t provide the regular button urls
Problem behind: Shelly does not provide up-to-date documentation, so the exact behavior is not specified
You could also try to enable CoIoT for the device. Send me a PM with the TRACE log and I check what we can do.
i have implemented the advice. currently it takes 1.5-5 seconds from switching the motion detector to switching the relay for the light. in my opinion this time is still much too high.
rule "Licht Haustuer ein"
when
Item Eg_Haustuer_Bewegungsmelder changed to ON
then
if(Astro_Daylight_On.state != ON)
{
sendCommand(Eg_Haustuer_Licht, ON)
}
end
I may change the binding to register push events only in momentary switch mode and otherwise register button events. However, this might remove flexibility, because you loose full control, which event types to register (e.g. having a momentary switch in detached mode). What do you think?
fyi: Together with @dilisi we identified a problem that sensor things (e.g. HT) stay in status UNKNOWN after a OH restart when a thing was added manually in PaperUI or defined in a .things file.
Thanks Markus! I’m a bit novice to try the DEV build i think! I currently have 2 items defined for each channel on the RGBW2 (power channel - switch ON/OFF and Brightness channel - dimmer %), but the power channel still changes to ON when brightness channel is changed.
Looking forward to the thing config to disable the Auto-ON I will hold off reconfiguring back to MQTT for now! Cheers!
This is already implemenrted. Go to the thing configuration there is a Switch “Brightness Auto-ON”, set this to OFF. Make sure you deleted the thing and re-discovered (Item linkage will be restored)
A user has the problem that the channels get the values, but some of them don’t show the unit. I check channel definition and code, which looks good and even more strange meter1 shows the V on voltage, but meter 2 doesn’t even it uses exactly the same channel definition.
I will hold off reconfiguring back to MQTT for now! Cheers!