[SOLVED]Z-Wave engine 3.0 lastWorkingRoute (?)

[SmartHomeEddy 1,005]

In the Z-Wave engine 2.0 we have lastWorkingRoute with device ID’s of the hops the Z-Wave network mesh uses to communicatie via other non battery operated Z-Wave devices to the HomeCenter. Like a route table. 
 

In the Z-Wave engine 3.0 the lastWorkingRoute seems to be empty? How does the Z-Wave mesh knows what route to take? 

[m.roszak 763]

This property only lists this in the server API, it is just an information. Routing table and mesh is written in Z-Wave chip.

This data is available on Z-Wave 3.0 engine API.


GET method // replace nodeId with the actual one
Neighbour list:

Please login or register to see this link.

Last working route:

Please login or register to see this link.

Please login or register to see this link.

Please login or register to see this link.

Please login or register to see this link.

In general you will find a lot of interesting things in Swagger

[SmartHomeEddy 1,005]

Thanks Michał

 

So in the 3.0 engine the route table comes from api/zwave/nodes/nodeId/last_working_route 

and

in the 2.0 engine the route table is in the device properties: devices.properties.lastWorkingRoute ?

 

6 minutes ago, m.roszak said:

In general you will find a lot of interesting things in Swagger

 

Browsing through the api 

 

 

[m.roszak 763]

Yes, in 3.0 it is in a different place.
In general, showing the neighbors by system devices IDs is not fully correct, so we moved this to Nodes, which is why it is on another API now. 
Maybe we will fill out old properties for backward compatibility but I think that more probable we will remove the old properties at some point.