Looks like raszberry not correctly update its routing table, for device_1 all greee, but actualy node 4 is off.
Any clue?
Thanks
Routing table not correct
Routing table not correct
- Attachments
-
- Screenshot (4).png (106.9 KiB) Viewed 4238 times
Re: Routing table not correct
The routing table is how devices communicate with each other, and not the device status.
When you say off, do you mean off at the switch, or off at the breaker?
If it's been connected and you turn it off at the breaker you can re-run the routing table so that everything shows the connection to it as red (which everything already does except the controller). If you just want to see the status of the device after you switch off the switch go into control and update the status.
The routing table shows how a command can get from one device to another in a nice matrix view (it really is very helpful to make sure you have nice connections). So all green squares have direct connection for communication, light green (which you don't have) means 1 hop for communications, yellow > 1 hop, red no way of communicating.
More in depth detail can be found in the z-way manual.
When you say off, do you mean off at the switch, or off at the breaker?
If it's been connected and you turn it off at the breaker you can re-run the routing table so that everything shows the connection to it as red (which everything already does except the controller). If you just want to see the status of the device after you switch off the switch go into control and update the status.
The routing table shows how a command can get from one device to another in a nice matrix view (it really is very helpful to make sure you have nice connections). So all green squares have direct connection for communication, light green (which you don't have) means 1 hop for communications, yellow > 1 hop, red no way of communicating.
More in depth detail can be found in the z-way manual.
Re: Routing table not correct
In fact, in Z-Wave controller never updates its routing iteself (as it is almost useless). Instead it relies on answers from other nodes in the network (they also report connection to the controller).
In this table each line is "neighbours of a node". As you see, line 4 was not updated (since it is off). Line 1 was not updated (in terms of column 4), since there was no reply from 4. At some point the chip will mark device 4 as dead and next update of routes for 1 will report no connection between 1 and 4 (in line 1), but in line 4 it will remain as the full line is not updated.
In this table each line is "neighbours of a node". As you see, line 4 was not updated (since it is off). Line 1 was not updated (in terms of column 4), since there was no reply from 4. At some point the chip will mark device 4 as dead and next update of routes for 1 will report no connection between 1 and 4 (in line 1), but in line 4 it will remain as the full line is not updated.