This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Comments
On thing about the battery. When you remove/insert it again, it's set at 100%.
But doesn't it measure the voltage, so it will very quickly drop to a more realistic percentage?
As far as I know, that's how most devices measure battery power?
For the main reason that not all batteries have the same voltage from the start (even at 100%)
You can try to leave out the battery for a few hours, this will let the battery slowly rise its voltage to -"maximum" and then add it to the smoke sensor, then the voltage should fall quickly/quicker to a more realistic value.
Disclaimer though, does not work for all batteries.
(yet)
Homey 1.3.2
Fibaro app 1.5.3
I re-added them 2 weeks ago (after the 1.5.3 update) but after approx 1 week only temperature was showing
Is this still a known problem or should I report at Github?
but the fibaro smoke sensors just won't send its current state when it wakes up (every 6 hours), only on force wake up (3 times click of the button)
we can't change anything of course in the smoke sensor itself so it does report its states.
so it is now just a device issue, not an homey issue.
The only thing i could do is give a false sense of security by setting the state of the smoke sensor to False/Off by default, but that won't change anything in the workings, it will still trigger on smoke like it should... just the current state in homey is null (no current state available) instead of a fake false..
so the fibaro smoke sensors are useless with Homey?
except as a temperature sensor.
Or is there some setting in the sensor that could do the trick?
how does it work with the Fibaro controller or other brands?
let me quote the most important sentence, but also combine/enhance it a little:
So is it useless?
no, it just gives no current state, which again is 99.9% of the time "False/Alarm off" anyway.
The difference between homey and other controllers like fibaro: they just give you that False Sense of Security, by just always giving False as a value, even if they don't know the Real value.
I can live with that but it would be nice to see the battery status as an empty smoke sensor doesn't work anymore
there is only 1 fibaro device (that i know of) that actually measures the battery level, and that is the keyfob.
so even if you knew the battery level of the smoke sensor it will most likely give you 100%, even if the battery is not 100%.
How i know this? because i have 2 of them, and have NEVER seen another level then 100% come from the smoke sensor.
i have seen it from the motion sensor (73%), but after a reset of the device, it was nicely on 100% again...
advice?
just test the smoke sensor once in a while, like those nice and old (non smart) smoke sensors.
or feel lucky and it will start beeping when the battery voltage gets too low (i have had this with one of my smoke sensors now)
If the battery is dead, then no smoke sensor in existence can do that for you.
If the battery is not dead, and you made a flow for it... Then it will nicely activate that flow for you.
Go blame to fibaro for not measuring the battery level actively, only passively
i just installed two of the fibaro smoke sensors, i can live with it not giving a false "no" but the temperature reading also has a dash -. This happens after a day or so. Has anything changed? Does it give the temp reading every 6 hours too? or more often. Thanks for the answer.
by default the temperature only reports if the change is bigger then 1 full degree celcius from the previous time it was send, the interval/threshold is way lower, only 10 seconds need to at least have past
Ok i understand that. So if the temp does not change the fibaro will report null? and homey shows a dash? Shouldnt it just report the current temp anyway? The temp change report is set to 0,1 on my smoke sensor. So if the temp changes it will send the new temp even though the wakeup interval is set to 21600seconds?
there are 5 big separate ways to send the information for battery devices:
1. on interval when threshold is surpassed
2. threshold when timeout was surpassed
3. on interval or threshold
4. only threshold
5. only interval (though haven't seen a case for this one yet)
so no, it does not need to wake up until it is send.
if nothing changes (or enough change) then nothing will be send.
homey will then use old information, if you reboot and the value is older then 30 minutes, then it is flagged "too old" and is not used anymore, so displaying a "none" ( - ).