Hi,
I recently bought the fibaro multi sensor to automate my sun screen under my porch. It does work, but sometimes it suddenly stops registering lux and goes from 15.000 to 0. And then stays at 0 for a while.
Since my flow is setup to close the sunscreen when the lux hit 12.000 for 3 minutes, this isn’t working a lot of the time. Does anyone know the solution? It is certainly 16.000 lux at the moment. It hangs outside under the porch.
Thanks a lot.
What’s the distance between the sensor and the nearest mains-powered Z-Wave device?
About 12 meters, its my automatic door lock. My router and homey are in the middle at around 5 meters tho
Not sure if it would help, but perhaps change the temperature measure and rapporting interval. Every second seems like real overkill imho. And drain the battery.
Perhaps that many reports are to much to handle and are causing interference?
I have about 15 of those sensors in my house (all inside btw) and I have never seen a invalid lux value.
Ive changed those, thank you. I was just fiddling with settings to see if that made anything different. It doesn’t. It’s 15.00 now, and 10 minutes ago it went straight back to 0 lux, even tho it’s sunny as hell outside.
One weird thing I noticed: When I manually activate one of my flows, the Lux immediately go back up. Right now that means I have to activate it manually when the time kicks in it should be automated.
Are you saying then when you run a flow which uses the lux value, the actual value of the lux on the device changes?
Yes, that’s exactly what I say. Lux went straight to 0 when it should have been 12000 lux at least, for several minutes.
my flow is easy: When the lux is 12.000 for 2 minutes, close the sunscreen.
When it is time to actually start the flow, it changes the lux to 0. When I manually activate that said flow the lux changes from 0 to 1800 (it hangs in the shade then, so that’s normal)
I am not sure how the Fibaro sensor works (or should work), but if I look at my Aqara motion sensor (that also measure brightness), the lux value only changes after it detects motion.
So the brightness sensor itself is inactive until the motion sensor detects motion. I assume to preserve battery and the main sensor in this case is motion, not brightness.
So I cannot use that sensor to monitor brightness on a continuous basis. Maybe your Fibaro sensors uses a similar approach. Of course this is just an assumption 
.
Thank you, I initially thought that too, but even when I go there to have motion, it just stays at 0 for 10 minutes+. So that really can’t be it.
No, lux is not related to motion on the Fibaro motion sensor.
Yeah, mine hangs inside. I have lux outside alswel, which are around 2k also (but those are not fibaro).
But it’s very strange that the value on the Device changes when a certain flow is triggered. I know of no way of that happening.
You said that you trigger things when the value is x for x minutes. Could you show the flow? Which flowcard are you using for it? The build in on, or mine from the Device Capabilities app?
Jep, those are buildin-ones yeah.
If you check your insights for the lux, does it show the 0 also for a moment?
Right now (after starting the 12.000 lux automation manually) the lux has been showing consistently, never going to 0.
But it did the exact same yesterday, and the day before. Tomorrow when it’s time to start the automation it will probably go to 0 again, until I manually start. I can’t get my head around that, but it’s been happing for 3 days now.
Also noting that restarting the Fibaro app, or my Homey in general did have no effect whatsoever.
But does it show the lux going to 0 in the insights?
2 things you could do:
Disable those flows using those flowcards, and see if the value then also goes to 0. Of not, the flows are responsible and perhaps there is a bug in those flowcards.
Other thing is, at least temporary, use my flowcard from the DC app. If that one works, again, there is an issue with the flowcards you are using.
The Device Capabilities app.
It has kinda the same flowcard.
Or just disable your flows tomorrow and see if the value drops to 0. If not, those flow(card)s are the issue.
