Looks like there might a bug in how PLEG evaluates the light sensor value on the EZMultiPli (HSM200) (or in the EZ itself), the Scale in the Advanced tab is shows it as a 1, I am not sure what that means, but the EZMultiPli expresses light as a percentage from 0-99 (even though the Vera UI shows it as LUX).
The Light Trigger works great for the Fibaro Motion Sensor Light Sensor which uses Scale type 2 and expresses the value in LUX (actual LUX), but for the EZMultiPli I can’t figure out what it is doing, usually the value will show as false until with a brightnest higher than 95, unless the values get below 60 or so than they go true. I can’t figure it out.
I am guessing PLEG is doing a conversion of the value wrong based on the Scale Type.
I have attached the Advanced Tab of EZ light sensor, the Fibaro Light sensor (just to show scale type), and the Status report on the triggers.
Also attached a snippet from the EXManual, maybe a hex conversion problem
The trigger use the the live value for “Sensor Value”.
Note: the Advanced tab is not the CURRENT value … it is the value at the time you loaded the browser.
You need to refresh the browser to see the current value.
No, I don’t think that is it. In attached example The room has been dark for hours. The Device UI propperly shows 0 LUX. The Advanced Tab shows 1.
The PLE trigger shows True for the value being greater than 95.
I refreshed the browser. The sensor updates every 10 minutes.
Something isn’t right. Particularly if you look at the last false value and true values, they don’t make sense.
Note here is the status as of this morning. As you can see the trigger hasn’t been in a False state for over 2 days, even though the sensor is in a darkened hallway over night, with the sensor reporting either 0 or 1 as the brightness.
Most of the day this sensor reports below 95 except for late in the afternoon when it is in full son, but trigger seems to almost be an inverse of what it is looking for.
Thanks Richard, you will want to configure variable 3 to 5 using 1 byte Dec (or something similar). Variable 3 is how often the light sensor reports back to Vera in Minutes. The default is 60 minutes, why they set that to 60 minutes on a plug in device is beyond me. I have mine set to 10 minutes.
Hey Richard, any Luck with the EZMultiply light sensor? Since we live in the Seattle area, controlling lights by just time can be super unrealiable because it is so often overcast and dark in the day would love to be able to use this for only disabling automatic lights when it is truly bright from the sun in the house.
@shallowearth,
Were you able to confirm if this is a device or PLEG issue and is there a solution to this problem (I too have one of these sensors in my kitchen) thanxs Mike
No, PLEG seems to have trouble reading the light level percentage value correctly particularly when the value is zero it is seeing it as something higher than 96, I haven’t been able to figure it out.
I have worked arround it by creating a virtual switch, then I just use a basic scene to turn on when the light level is above 90, and another scene to turn it off when the light level is below 90. I then use the virtual switch in PLEG input conditions instead of trying to read the light level directly.
I have noticed that I cannot leave the LED light on all the time on atleast one of my EZMultiPli if I want to use the light sensor as the LED light seems to actually impact the light sensor, have you noticed that?
@shallowearth, thanxs for the comeback, I do use the EZMultiPli utility to change colors between motion and no motion as a quick visual and have yet to use the light sensor in earnest (will check) but it makes sense that when you turn on the LED, it would impact the light sensor. Mike
Best Home Automation shopping experience. Shop at Ezlo!