[FR] Missing Routers #247
Comments
o0shojo0o
added
enhancement
|
Oh yes, I didn't know that, but it's definitely interesting. {
"data": {
"missing_routers": [
{
"friendly_name": "FL.Licht.Links",
"ieee_address": "0xb4e3f9fffea14f56"
},
{
"friendly_name": "FL.Licht.Decke Hinten",
"ieee_address": "0x0017880102a096e5"
},
{
"friendly_name": "KZ.Geraet.WorkStation",
"ieee_address": "0x00158d000356bb32"
},
{
"friendly_name": "FL.Licht.Rechts",
"ieee_address": "0xb4e3f9fffea3efbd"
},
{
"friendly_name": "FL.Licht.Garderobe",
"ieee_address": "0x00124b0022661ae6"
},
{
"friendly_name": "FL.Licht.Decke Vorne",
"ieee_address": "0x0017880102eebc0b"
},
{
"friendly_name": "BU.Licht.Schreibtisch",
"ieee_address": "0x842e14fffe26f649"
},
{
"friendly_name": "SZ.Licht.Bett",
"ieee_address": "0x588e81fffefea724"
}
]
},
"status": "ok"
} |
|
Please test the dev branch -> https://github.com/o0shojo0o/ioBroker.zigbee2mqtt/tree/Missing-Routers-%23247 |
Many thanks for picking it up. I stumbled upon this also by pure chance and was quite surprised and have implemented this check in my Iobroker Node-Red instance already. Of course, having it directly in your great adapter is very much appreciated. Unfortunately I have already fixed my devices but I will test nevertheless. I would consider this a quite serious health issue for a zigbee network so this might even warrant some warning messages at "info" level in the iobroker log. |
|
What does your JSON currently look like when it doesn't find missing_routers? |
|
Hmm, good point.
When clicking on the empty array. The GUI error page pops up:
In the browser's console: |
|
Please delete the data point and install again via this link :) -> https://github.com/o0shojo0o/ioBroker.zigbee2mqtt/tree/Missing-Routers-%23247 Then you also have this option: |
|
And I meant the JSON object you get back via MQTT |
|
The JSON object as returned by MQTT looks like: The error when clicking on the empty array is also solved 👍 Crontab seems to work as well. Great work! Many thanks |
|
Ok then I will create a PR, merge and create a new release :) |
- (o0shojo0o) added state `info.coordinator_check` ([#247](#247)) - (o0shojo0o) added state `info.missing_routers` ([#247](#247)) - (o0shojo0o) added state `info.missing_routers_count` ([#247](#247)) - (o0shojo0o) added option `Automatic check for missing routers in the coordinator memory` ([#247](#247))
What happened?
Apparently zigbee2mqtt or rather the firmware of TI based coordinators can "forget" that certain devices are routers.
To detect this, zigbee2mqtt has implemented a coordinator_check.
Sending:
zigbee2mqtt/bridge/request/coordinator_checkwill return on:
zigbee2mqtt/bridge/response/coordinator_checkwith an array of missing routers like:
{"missing_routers":[{"friendly_name":"LEDGarage","ieee_address":"0x04cd15fffe0ae5f7"}]}
It would be nice to have an option to check this regularly, e.g. every day at 3 in the night and populate some data points under:
zigbee2mqtt.0.infoWhat did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Adapter version
2.11.0
Log
No response
The text was updated successfully, but these errors were encountered: