Rule activated by lumination sensor

I think it is perhaps because your time intervall spans over midnight.....

Try to minimize the Suze if the rule by removing different if statements and if works slowly add piece by piece. Use push messaging to test the rule always

If you are using a luminosity sensor I don't see the point of using the schedule puzzle. I use the following rule and works perfect.

I had a similar problem once and I think I solved it by replacing the "ANY" from the WHEN condition to "MOTION"

basically

When "sensor as "motion" then...

ANY wasn't working very well and my best guess is due to the fact that my motion sensor "Fibaro Eye" has temperature and luminance sensors as well and I'm not sure if the ANY isn't related to these last two instead of the motion...

FP

Hi Hans,

I had a similar challenge, but for another use - turning indoor ambient lights on when the light went below a certain level. (I have to admit that it was much easier with the Fibaro than the zipato 4-in-1, because the Fibaro Luminance device is seen as a sensor, not as a meter). For some reason my rule seemed to work in reverse, so using that logic, I reversed the rule :)

See my rule - instead of setting it to turn on when the light went below a certain level, it worked for me if it was on by default, and I'm turning it off, when it goes above a certain threshold.

This is working great for me.

I´m very interested to hear if someone from Zipato has any clues to why this rule wont work in lumination settings. The multisensor seems to work/report as it should in Zipabox.

Hi Hans...its really simple, but a bit tricky until you wrap your head around the fact that the rules are event driven.

Your condition in the middle of the rule (luminance <100) will not work since that is not a event that is triggered when you want it to happen. In order to solve this you need to put the luminance level in a variable (separate rule) when it changes....and then use that variable value in your rule.

Say for instance that the last reported luminance was 0 at 15:30 (gets dark early in Sweden at wintertime) then the value will not be reported again until it changes and therefore will not trigger your rule.

Hope I did not make you even more confused. :)

/Erik

Thanks Erik,

Yes, now I´m confused :-)

Actually i have been looking at variable but not tested yet, will do so.

For the moment I get the lamp started in a timeperiod and with the lumination sensor <=80. My problem now is that I don´t get it to go off in a certain time (in my case 01.00 at night). I`ll attach an example later this evening.

Hi Hans,

I had another look at this one, as I was getting some strange results. (Even now I'm getting some strange results, but its a lot more predictable) As Erik suggested, I also ended up with a similar rule. This is what I am now using, and I'm also attaching some history so you can see its working

Since the Luminance is reported correctly as you say, the trick was to trigger an event. so:

If Luminance is between value_A and value_B (% based on the Zipato 4-in-1, or Lux value in Fibaro)

If the time is between Time_A and Time_B (maybe overkill, but I'm using this as it suits my needs)

Perform an Action

I've lined up the graphs for the sensor reading and the status of the stairs lights so you can see the relationship between the two in the Results image attached.

btw - I'm not sure I understand why youre using the join (FORENA) command - wouldnt that prevent it from happening again?

Also check if its switching the first device only (your Kok Fonster), not the others. Some of the randomness I'm seeing if you look at my rule is that the stairs lights are working fine, but the Ambient LED strips are not always coming on, yet both are on the same rule.

Hope that helps