Hel
Many (All) of my Fibaro Devices sent all 10 minutes an
- Heat alarm
- Powermanagement Alarm
What can I do ?
Thanks
Fibaro Heat alaram
Fibaro Heat alaram
Greetings from germany
Jörg
Raspi 4(Buster), Zwave Version 4.1.1 Raz 7 Pro, Serial API Version:07.38(SDK 7.20)
Jörg
Raspi 4(Buster), Zwave Version 4.1.1 Raz 7 Pro, Serial API Version:07.38(SDK 7.20)
-
- Posts: 177
- Joined: 02 Mar 2020 22:41
Re: Fibaro Heat alaram
A couple of suggestions...
1. To understand what's being sent by your Fibaro device, point your browser to: http://[IP Address of Z-Way controller]:8083/expert/#/installer/history
2. Look at the Z-Way controller log file (nominally /var/log/z-way-server.log) to see how Z-Way is processing the Fibaro messages
3. Power-cycle the Fibaro device by removing and re-installing the battery - that should update its routing table
A likely explanation is that the Z-Way controller is sending an ACK message back to the Fibaro device, but the Fibaro device is not receiving the ACK message so it's re-transmitting the alarm messages. Issues related to weak RF signals can be difficult to troubleshoot because the conditions are frequently intermittent. The RSSI data in the Zniffer history can be useful.
Note that if you've done a secure inclusion for the Fibaro device, the Z-Wave protocol requires multiple messages. If that's the case, you may want to exclude the Fibaro device and re-include it without security as that will reduce the number of Z-Wave messages and improve battery life.
1. To understand what's being sent by your Fibaro device, point your browser to: http://[IP Address of Z-Way controller]:8083/expert/#/installer/history
2. Look at the Z-Way controller log file (nominally /var/log/z-way-server.log) to see how Z-Way is processing the Fibaro messages
3. Power-cycle the Fibaro device by removing and re-installing the battery - that should update its routing table
A likely explanation is that the Z-Way controller is sending an ACK message back to the Fibaro device, but the Fibaro device is not receiving the ACK message so it's re-transmitting the alarm messages. Issues related to weak RF signals can be difficult to troubleshoot because the conditions are frequently intermittent. The RSSI data in the Zniffer history can be useful.
Note that if you've done a secure inclusion for the Fibaro device, the Z-Wave protocol requires multiple messages. If that's the case, you may want to exclude the Fibaro device and re-include it without security as that will reduce the number of Z-Wave messages and improve battery life.
Re: Fibaro Heat alaram
If you are on v3.2.2, use the newest Packet Statistics to see for duplicates and other problems with device 17
Re: Fibaro Heat alaram
Hello,
thanks for your Reply.
Do you need further more Infos ?
thanks for your Reply.
Do you need further more Infos ?
Greetings from germany
Jörg
Raspi 4(Buster), Zwave Version 4.1.1 Raz 7 Pro, Serial API Version:07.38(SDK 7.20)
Jörg
Raspi 4(Buster), Zwave Version 4.1.1 Raz 7 Pro, Serial API Version:07.38(SDK 7.20)
Re: Fibaro Heat alaram
There is a clear routing issue here:
- up to 2 and even 8 seconds to reach the device! (804 * 10ms) in timing info
- a lot of duplicates with Nonce Reports with same values
- big duplicates level
check route map (switch to ingress packets by pressing "I") and see real routes. If they are crazy, assign manual routes and add repeaters
- up to 2 and even 8 seconds to reach the device! (804 * 10ms) in timing info
- a lot of duplicates with Nonce Reports with same values
- big duplicates level
check route map (switch to ingress packets by pressing "I") and see real routes. If they are crazy, assign manual routes and add repeaters
Re: Fibaro Heat alaram
Hello,
thanks fpr your Reply.
This is Route map for Device 34 .
There was an Bold Line Direktly to the Controler. But in there was no Link to Controler...
Can you explain it ?
thanks fpr your Reply.
This is Route map for Device 34 .
There was an Bold Line Direktly to the Controler. But in there was no Link to Controler...
Can you explain it ?
Greetings from germany
Jörg
Raspi 4(Buster), Zwave Version 4.1.1 Raz 7 Pro, Serial API Version:07.38(SDK 7.20)
Jörg
Raspi 4(Buster), Zwave Version 4.1.1 Raz 7 Pro, Serial API Version:07.38(SDK 7.20)
Re: Fibaro Heat alaram
wow! what a mess. So many routes are a sign of very bate routing and reception.
I would suggest uploading a floor map, placing devices on it, and then seeing where is the weak point. All the dashed lines are links with losses.
I would suggest uploading a floor map, placing devices on it, and then seeing where is the weak point. All the dashed lines are links with losses.
Re: Fibaro Heat alaram
Hallo, thanks for Your Support
Is there Any Reason why the Routes are Duplikate ?
Must im set all routes manuel ?
Why is there an Route in the Route map direct To Controller but in neighbour map no link ?
Greetings
Jörg
Is there Any Reason why the Routes are Duplikate ?
Must im set all routes manuel ?
Why is there an Route in the Route map direct To Controller but in neighbour map no link ?
Greetings
Jörg
Greetings from germany
Jörg
Raspi 4(Buster), Zwave Version 4.1.1 Raz 7 Pro, Serial API Version:07.38(SDK 7.20)
Jörg
Raspi 4(Buster), Zwave Version 4.1.1 Raz 7 Pro, Serial API Version:07.38(SDK 7.20)
Re: Fibaro Heat alaram
Neighbours map shows a known routing table based on the last node neighbours update. But devices still tries to use the direct route - it is allowed. As a result, you can see them in the Route Map. Route Map shows REAL routes used in the last few hours, while Routing Table shows the state from the last neighbour update.
Re: Fibaro Heat alaram
Hello PoltoS,
Thank you for your explanation
If an Manuel Route is defined - ist that than the Only Used Route ?
Thank you for your explanation
If an Manuel Route is defined - ist that than the Only Used Route ?
Greetings from germany
Jörg
Raspi 4(Buster), Zwave Version 4.1.1 Raz 7 Pro, Serial API Version:07.38(SDK 7.20)
Jörg
Raspi 4(Buster), Zwave Version 4.1.1 Raz 7 Pro, Serial API Version:07.38(SDK 7.20)