Ezlo Plus - Philips Hue devices duplicates in MSR
-
I PM'd you a like to upload your
ezlo_inventory.json
file (inlogs
). I can see there if anything is published that would lead to that action, or if it's "special knowledge" (i.e. kludge) in Ezlo's Reactor clone. -
OK thanks I uploaded the requested file. All my rules are still in MSR so could be handy if I could use this blink feature on the Hue lights, but not mission critical.
I did look under the AltHue plugin on the Vera Plus but could not find "alert" and a forum post I read suggested it was never added by that dev.
-
I PM'd you a like to upload your
ezlo_inventory.json
file (inlogs
). I can see there if anything is published that would lead to that action, or if it's "special knowledge" (i.e. kludge) in Ezlo's Reactor clone.Damn looks like I won't be able to upgrade MSR anytime soon. I can no longer login to the Debian box MSR runs on for some reason. Not sure what happened and went wrong.
https://smarthome.community/topic/1015/help-please-cannot-login-to-debian-msr-box
EDIT: I've managed to fix my login problems now.
-
Couple of nice updates there for me !
VeraController: Ensure x_vera_device.failed and .configured are null if Vera fails to provide state for these values.
EzloController: Dead-marking and automatic removal (after delay) of entities for Ezlo devices/rooms/scenes that no longer exist (functional parity with other hub Controller objects).I am going to update MSR now.
Thanks
-
@cw-kid said in Ezlo Plus - Philips Hue devices duplicates in MSR:
So after 24 hours it would auto remove them from MSR right.
Or I can just manually remove them now.Yes.
For the alert, use the
x_ezlo_device.set_item_value
action with the item name and desired value: -
@cw-kid said in Ezlo Plus - Philips Hue devices duplicates in MSR:
So after 24 hours it would auto remove them from MSR right.
Or I can just manually remove them now.Yes.
For the alert, use the
x_ezlo_device.set_item_value
action with the item name and desired value:Even better thanks. I will give the alert a try.
-
A bit of background here. Unlike Vera, which had actions separate from values (state variables) to make things happen, the Ezlo firmware uses the Z-Wave approach of modifying values as a way of stimulating action. It's not surprising they would use this model, as Z-Wave is the philosophical core of their system. There is therefore no need for separate actions, which on Vera was the byproduct of attempting to implement UPnP (and didn't quite get there).
Since actions on Ezlo are actually just item value changes, using
x_ezlo_device.set_item_value
, you can set the value of any item associated with a device, even if the value isn't mapped to one of Reactor's capabilities or attributes, and whatever action that may stimulate either in the firmware or on the device itself will occur. -
A bit of background here. Unlike Vera, which had actions separate from values (state variables) to make things happen, the Ezlo firmware uses the Z-Wave approach of modifying values as a way of stimulating action. It's not surprising they would use this model, as Z-Wave is the philosophical core of their system. There is therefore no need for separate actions, which on Vera was the byproduct of attempting to implement UPnP (and didn't quite get there).
Since actions on Ezlo are actually just item value changes, using
x_ezlo_device.set_item_value
, you can set the value of any item associated with a device, even if the value isn't mapped to one of Reactor's capabilities or attributes, and whatever action that may stimulate either in the firmware or on the device itself will occur.Thanks for the additional information, that is certainly good to know about.
-
T toggledbits locked this topic on