This object is in archive!
Fibaro Door-Window sensor shows inverted status..??
In Progress
Anybody can explain this weired behaviour:?
Includning the sensor, no problem.
But, senor status shows "Open" when door is closed and status changes to "Closed" when door opens...??
Tamper switches are shown OK, tried to exclude and reinclude but still same inverted status.
Any idea?
Best regards
Torbjorn
The same problem 
No connection
Real-time notifications may not work
I would try to exclude from network, reset the device and re-include. See below procedure for reset;
2. Resetting the Fibaro Door/Window Sensor
There is one way to reset the Fibaro Door/Window Sensor. The
procedure cleans its EPROM memory, including the main controller
and Z-Wave network data.
To reset the Fibaro Door/Window Sensor please follow below
instructions:
1) Take off the Sensor's cover and remove battery. Make sure the
TMP button is intact.
2) Touch the Sensor's body with a magnet,
3) Insert the battery,
4) Remove the magnet from the Sensor's body,
5) Remove the battery
6) Re-install the battery,
7) Reset will be confirmed by double LED blink.
I would try to exclude from network, reset the device and re-include. See below procedure for reset;
2. Resetting the Fibaro Door/Window Sensor
There is one way to reset the Fibaro Door/Window Sensor. The
procedure cleans its EPROM memory, including the main controller
and Z-Wave network data.
To reset the Fibaro Door/Window Sensor please follow below
instructions:
1) Take off the Sensor's cover and remove battery. Make sure the
TMP button is intact.
2) Touch the Sensor's body with a magnet,
3) Insert the battery,
4) Remove the magnet from the Sensor's body,
5) Remove the battery
6) Re-install the battery,
7) Reset will be confirmed by double LED blink.
Dear Alberto,
Thanks for your help, it worked out !
Torbjorn
Dear Alberto,
Thanks for your help, it worked out !
Torbjorn
Unfortunately this does work and then it doesn't... After reset and inclusion the sensor works as it should....until first wake-up event when the state gets inverted and then stays that way.
Unfortunately this does work and then it doesn't... After reset and inclusion the sensor works as it should....until first wake-up event when the state gets inverted and then stays that way.
I have the same problem here.
Zipato GW FW 1.0.17
Fibaro Door/Window Sensor FGK-101 FW 3.2
I have the same problem here.
Zipato GW FW 1.0.17
Fibaro Door/Window Sensor FGK-101 FW 3.2
Dear All,
Our team is working on this issue and we will do our best to resolve this issue as soon as possible.
We will keep you informed about the progress through this topic.
Thank you for your patience.
Best regards,
Pero Zovkic
Dear All,
Our team is working on this issue and we will do our best to resolve this issue as soon as possible.
We will keep you informed about the progress through this topic.
Thank you for your patience.
Best regards,
Pero Zovkic
Thanks for the reply and confirmation. :-)
Thanks for the reply and confirmation. :-)
Looks like this is an issue with the newer firmwares (either zipabox or device's), I have 5 of these sensors and they have never done that at all, I added them a long time ago and never had issues on that regard with it. I actually have a ticket opened for zipato MS4 which my old ones work just fine but, after upgraded with beta firmware (above 1.0.17) these sensors show up in zipabox without door sensor end points.
Looks like this is an issue with the newer firmwares (either zipabox or device's), I have 5 of these sensors and they have never done that at all, I added them a long time ago and never had issues on that regard with it. I actually have a ticket opened for zipato MS4 which my old ones work just fine but, after upgraded with beta firmware (above 1.0.17) these sensors show up in zipabox without door sensor end points.
Things might look brighter under this thread. I received the following response from an open ticket I have regarding this topic:
"Dear Thomas,
We are very sorry for the delay in resolving this issue.
Our team has created a totally new driver for this device and now they are testing it. So this issue will be resolved and closed in next day or two.
We are sorry for the caused inconvenience and thank you for sending us required information.
Best regards,
Pero Zovkic
"
Things might look brighter under this thread. I received the following response from an open ticket I have regarding this topic:
"Dear Thomas,
We are very sorry for the delay in resolving this issue.
Our team has created a totally new driver for this device and now they are testing it. So this issue will be resolved and closed in next day or two.
We are sorry for the caused inconvenience and thank you for sending us required information.
Best regards,
Pero Zovkic
"
Excellent news!
Does this mean that it will be corrected in the next stable Firmware?
Excellent news!
Does this mean that it will be corrected in the next stable Firmware?
Replies have been locked on this page!