Please help!
Answered
I have a problem...
Have a Fibaro Door/window Sensor with temperature connected to my ZipaBox
Today I saw that the battery level for it was down to 32% (was only weeks since installed)
When I look in the Events Panel for the device I see that it for some reason CONSTANTLY switches OPEN/CLOSE (see picture)
Ofcourse that is the reason the battery is drained!
But what can I do to stop it???!!!
Can I turn off the door sensor in it... I can live without it for some time.
But I very much need that readings from the temperature sensor!!!!
I have 400km car trip to manualy fix it, so how to stop this battery drain remotly?
What can I do???
I was thinking that the battery should live for a year or two.
The same question You can't vote. Please authorize!
You can't vote. Please authorize!
You can't vote. Please authorize!
You can't vote. Please authorize!
You can't vote. Please authorize!
No connection
Real-time notifications may not work
Strange! I do have the same sensor wo this problem.
Sometimes i have experienced multipel open states But not
continuously like yours. Did this start now after firmware update?
Have you tried to re-apply the descriptors?
Strange! I do have the same sensor wo this problem.
Sometimes i have experienced multipel open states But not
continuously like yours. Did this start now after firmware update?
Have you tried to re-apply the descriptors?
Solved! (for this time)
First tried re-apply... didn't help :-/
Then changed the configuration from NORMAL_CLOSED to NORMAL_OPEN and did a SYNC, then it stoped! :-)
Changed back to NORMAL_CLOSED, and the problem is gone.
(at least not flooding events)
Must have been that sensor that got some (in swedish) "tuppjuck"
I have the new firmware, but this must have been something in the Fibaro sensor, don't think it is Zipatos fault!
Solved! (for this time)
First tried re-apply... didn't help :-/
Then changed the configuration from NORMAL_CLOSED to NORMAL_OPEN and did a SYNC, then it stoped! :-)
Changed back to NORMAL_CLOSED, and the problem is gone.
(at least not flooding events)
Must have been that sensor that got some (in swedish) "tuppjuck"
I have the new firmware, but this must have been something in the Fibaro sensor, don't think it is Zipatos fault!
I always hate when things gets "tuppjuck"... ;)
I always hate when things gets "tuppjuck"... ;)
Replies have been locked on this page!