Is every powered z-Wave device a repeater?

Community Playground General Discussions
1

I am just wondering if every z-Wave device that is mains powered is a repeater (I know the battery powered devices don’t repeat messages to conserve energy).

I have 10 of these EverSpring On/Off switches and I am not convinced that they are recognised by the Vera as routing data. I recently added a Horstmann Actuator and it is notable that the nightly heals look like this (node 49 is the new actuator) and all the rest are EverSpring On/Off switches. Why do I not see possible routes showing up that include something other than the Horstmann?

Thanks in advance for any info.

=======EDGE NODE PROFILE=======

Node: 3
Edge node: 0 score: 12 route: 1->0.0.0.0->3 num hops: 0 Latency avg: 103 max: 636 success 10 of 10

Node: 4
Edge node: 0 score: 47 route: 1->0.0.0.0->4 num hops: 0 Latency avg: 115 max: 327 success 8 of 10
Edge node: 49 score: 96 route: 1->49.0.0.0->4 num hops: 1 Latency avg: 110 max: 561 success 6 of 10

Node: 6
Edge node: 0 score: 5 route: 1->0.0.0.0->6 num hops: 0 Latency avg: 98 max: 190 success 10 of 10
Edge node: 49 score: 9 route: 1->49.0.0.0->6 num hops: 1 Latency avg: 101 max: 123 success 10 of 10

Node: 7
Edge node: 0 score: 5 route: 1->0.0.0.0->7 num hops: 0 Latency avg: 98 max: 190 success 10 of 10
Edge node: 49 score: 10 route: 1->49.0.0.0->7 num hops: 1 Latency avg: 100 max: 213 success 10 of 10

Node: 9
Edge node: 0 score: 5 route: 1->0.0.0.0->9 num hops: 0 Latency avg: 98 max: 190 success 10 of 10
Edge node: 49 score: 9 route: 1->49.0.0.0->9 num hops: 1 Latency avg: 99 max: 124 success 10 of 10

Node: 10
Edge node: 0 score: 5 route: 1->0.0.0.0->10 num hops: 0 Latency avg: 98 max: 190 success 10 of 10
Edge node: 49 score: 8 route: 1->49.0.0.0->10 num hops: 1 Latency avg: 100 max: 114 success 10 of 10

Node: 11
Edge node: 49 score: 8 route: 1->49.0.0.0->11 num hops: 1 Latency avg: 99 max: 102 success 10 of 10

Node: 12
Edge node: 0 score: 47 route: 1->0.0.0.0->12 num hops: 0 Latency avg: 311 max: 2420 success 10 of 10
Edge node: 49 score: 8 route: 1->49.0.0.0->12 num hops: 1 Latency avg: 99 max: 102 success 10 of 10

Node: 49
Edge node: 0 score: 3 route: 1->0.0.0.0->49 num hops: 0 Latency avg: 95 max: 102 success 10 of 10

2

According to the z-wave specification, there are controllers, portable controllers, slaves, and routing slaves.

It says

The slave is the simplest node available in a Z-Wave network. The slave node is unable to initiate
transmission of data to other nodes in a Z-Wave network unless it is as a response to a request. A slave
can only be mains powered. …
The slave has the ability to act as router when a source node tries to reach a destination node out of
direct range.

For Routing Slave it says :

The routing slave has the same Z-Wave protocol functionality as a slave, but in addition the node can initiate transmission of data to a limited number of other nodes in the Z-Wave network.

So even a non-routing slave must be able to route transmissions for other nodes.

HTH.

3

So it looks like MiOS ignores slaves when creating its routing table, although it appears that in theory MiOS could ask those slaves to send data on.

Routing slaves on the other hand are specifically included in the routing table.

Perhaps I am missing something here, but wouldn’t it make sense for the Vera to try to build a routing table that includes non-routing slaves even if it has to initiate that communication?