Modules don't see neighbors, only Vera

Community Playground General Discussions
1

Although everything is functional in my network, I am puzzled that there is no mesh despite all machinations and contortions I can think of. At present, each module can see Vera, and Vera can see each module, but that is the extent of it. This has been the case since I first set this Vera system up. There was one instance shortly after installing a new humidity/temp module that a nice collection of neighbors appeared for each module, but after the next heal they were gone again and each module only shows Vera, “1”, as a neighbor. Any ideas?

I’ve had a ticket in twice, but they were not successful in resolving this issue, although they apparently tried.

Here is my last repair log:

12-06-11 9:51:59 report for HealNetwork. Successful: Y Updated net: N mr_only:0 Job ID: job#6 :heal network (0x7ca7b8) P:71 S:5

=======NEIGHBOR NODE UPDATES=======
Node 2 Device 15 Entry Light neighbor nodes updated 2 times (incomplete 0 in a row 2), woke up 0 times configured: YES
Node 3 Device 4 Keyless Entry Lockset neighbor nodes updated 2 times (incomplete 0 in a row 2), woke up 0 times configured: YES
Node 4 Device 5 Trane Thermostat neighbor nodes updated 2 times (incomplete 0 in a row 2), woke up 0 times configured: YES
Node 7 Device 9 Entryway Outlet neighbor nodes updated 2 times (incomplete 1 in a row 2), woke up 0 times configured: YES
Node 8 Device 10 Floor Lamp neighbor nodes updated 0 times (incomplete 5 in a row 0), woke up 0 times configured: NO
Node 9 Device 11 Water Heater neighbor nodes updated 2 times (incomplete 0 in a row 2), woke up 0 times configured: YES
Node 10 Device 17 _Temp Humidity Sensor neighbor nodes updated 0 times (incomplete 1 in a row 0), woke up 0 times configured: NO
Node 13 Device 21 _3-in-1 sensor neighbor nodes updated 2 times (incomplete 0 in a row 2), woke up 0 times configured: YES

=======STRESS TEST RESULT=======
Node 4 Device 5 Trane Thermostat
Test: NOP Sent 2 test frames and 2 succeeded (100%) with average of 0.092746 seconds and maximum of 0.092799 seconds
Test: Basic_Get Sent 2 test frames and 2 succeeded (100%) with average of 0.162744 seconds and maximum of 0.162776 seconds
Test: Get Node Info Sent 2 test frames and 2 succeeded (100%) with average of 0.161451 seconds and maximum of 0.166419 seconds
–HEALTH SCORE: 5–
Node 7 Device 9 Entryway Outlet
Test: NOP Sent 2 test frames and 2 succeeded (100%) with average of 0.112842 seconds and maximum of 0.112842 seconds
Test: Basic_Get Sent 2 test frames and 2 succeeded (100%) with average of 0.172680 seconds and maximum of 0.172702 seconds
Test: Get Node Info Sent 2 test frames and 2 succeeded (100%) with average of 0.166176 seconds and maximum of 0.166263 seconds
–HEALTH SCORE: 5–
Node 8 Device 10 Floor Lamp
Test: NOP Sent 2 test frames and 0 succeeded (0%) with average of 0.000000 seconds and maximum of 0.000000 seconds
Test: Basic_Get Sent 2 test frames and 0 succeeded (0%) with average of 0.000000 seconds and maximum of 0.000000 seconds
Test: Get Node Info Sent 2 test frames and 0 succeeded (0%) with average of 0.000000 seconds and maximum of 0.000000 seconds
–HEALTH SCORE: 0–
Node 2 Device 15 Entry Light
Test: NOP Sent 2 test frames and 2 succeeded (100%) with average of 0.092953 seconds and maximum of 0.092972 seconds
Test: Basic_Get Sent 2 test frames and 2 succeeded (100%) with average of 0.163018 seconds and maximum of 0.165004 seconds
Test: Get Node Info Sent 2 test frames and 2 succeeded (100%) with average of 0.162224 seconds and maximum of 0.167164 seconds
–HEALTH SCORE: 5–
Node 9 Device 11 Water Heater
Test: NOP Sent 2 test frames and 2 succeeded (100%) with average of 0.115101 seconds and maximum of 0.117476 seconds
Test: Basic_Get Sent 2 test frames and 2 succeeded (100%) with average of 0.157619 seconds and maximum of 0.172829 seconds
Test: Get Node Info Sent 2 test frames and 2 succeeded (100%) with average of 0.140086 seconds and maximum of 0.144106 seconds
–HEALTH SCORE: 5–
Node 3 Device 4 Keyless Entry Lockset
Test: NOP Sent 2 test frames and 2 succeeded (100%) with average of 1.820326 seconds and maximum of 2.437792 seconds
Test: Basic_Get Sent 2 test frames and 2 succeeded (100%) with average of 3.897721 seconds and maximum of 3.920101 seconds
Test: Secure Sent 2 test frames and 2 succeeded (100%) with average of 6.027354 seconds and maximum of 6.701922 seconds
Test: Get Node Info Sent 2 test frames and 2 succeeded (100%) with average of 1.290980 seconds and maximum of 1.337703 seconds
–HEALTH SCORE: 3–

=======NEIGHBOR NODE RESULT=======
Node 10 Device 17 _Temp Humidity Sensor took 0.36267000 seconds to report neighbors:
Node 4 Device 5 Trane Thermostat took 0.38582000 seconds to report neighbors: 1,
Node 7 Device 9 Entryway Outlet took 0.34575000 seconds to report neighbors: 1,
Node 8 Device 10 Floor Lamp took 0.36143000 seconds to report neighbors:
Node 2 Device 15 Entry Light took 0.60771000 seconds to report neighbors: 1,
Node 9 Device 11 Water Heater took 0.37116000 seconds to report neighbors: 1,
Node 13 Device 21 _3-in-1 sensor took 0.36095000 seconds to report neighbors: 1,
Node 3 Device 4 Keyless Entry Lockset took 0.36946000 seconds to report neighbors: 1,

Inversely:
Node 4 Device 5 Trane Thermostat is seen by: 1,
Node 7 Device 9 Entryway Outlet is seen by: 1,
Node 2 Device 15 Entry Light is seen by: 1,
Node 9 Device 11 Water Heater is seen by: 1,
Node 13 Device 21 _3-in-1 sensor is seen by: 1,
Node 3 Device 4 Keyless Entry Lockset is seen by: 1,

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

Node: 2
Edge node: 0 score: 5 route: 1->0.0.0.0->2 num hops: 0 Latency avg: 98 max: 196 success 10 of 10
Edge node: 4 score: 10 route: 1->4.0.0.0->2 num hops: 1 Latency avg: 95 max: 181 success 10 of 10
Edge node: 7 score: 70 route: 1->4.7.0.0->2 num hops: 2 Latency avg: 119 max: 192 success 7 of 10
Edge node: 9 score: 34 route: 1->9.0.0.0->2 num hops: 1 Latency avg: 162 max: 303 success 9 of 10

Node: 3
Edge node: 0 score: 139 route: 1->0.0.0.0->3 num hops: 0 Latency avg: 2399 max: 4857 success 10 of 10
Edge node: 4 score: 75 route: 1->4.0.0.0->3 num hops: 1 Latency avg: 1218 max: 2431 success 10 of 10
Edge node: 7 score: 102 route: 1->4.7.0.0->3 num hops: 2 Latency avg: 1255 max: 2507 success 9 of 10

Node: 4
Edge node: 0 score: 6 route: 1->0.0.0.0->4 num hops: 0 Latency avg: 95 max: 266 success 10 of 10
Edge node: 7 score: 9 route: 1->7.0.0.0->4 num hops: 1 Latency avg: 101 max: 123 success 10 of 10
Edge node: 9 score: 34 route: 1->9.0.0.0->4 num hops: 1 Latency avg: 160 max: 312 success 9 of 10

Node: 7
Edge node: 0 score: 25 route: 1->0.0.0.0->7 num hops: 0 Latency avg: 100 max: 197 success 9 of 10
Edge node: 4 score: 10 route: 1->4.0.0.0->7 num hops: 1 Latency avg: 97 max: 181 success 10 of 10
Edge node: 9 score: 173 route: 1->9.0.0.0->7 num hops: 1 Latency avg: 151 max: 302 success 2 of 10

Node: 9
Edge node: 0 score: 4 route: 1->0.0.0.0->9 num hops: 0 Latency avg: 96 max: 173 success 10 of 10
Edge node: 4 score: 10 route: 1->4.0.0.0->9 num hops: 1 Latency avg: 158 max: 174 success 10 of 10

=======DETAILED LOG=======
–Stage #1 started: 12-06-11 9:52:01 completed: 12-06-11 9:52:01 successful: N
—12-06-11 9:37:50 Job unknown
–Stage #2 started: 12-06-11 9:37:50 completed: 12-06-11 9:52:01 successful: Y
—12-06-11 9:37:50 Pass 0/5 Updating neighbors for node 2
—12-06-11 9:37:50 Job job#7 :heal_neighbor_node 2 (0x7c9cd0) P:70 S:4 was Successful
—12-06-11 9:37:50 Pass 0/5 Updating neighbors for node 3
—12-06-11 9:37:53 Job job#8 :heal_neighbor_node 3 (0x762110) P:70 S:4 was Successful
—12-06-11 9:37:53 Pass 0/5 Updating neighbors for node 4
—12-06-11 9:37:54 Job job#9 :heal_neighbor_node 4 (0x813de8) P:70 S:4 was Successful
—12-06-11 9:37:54 Pass 0/5 Updating neighbors for node 7
—12-06-11 9:37:55 Job job#10 :heal_neighbor_node 7 (0x7d2778) P:70 S:4 was Successful
—12-06-11 9:37:55 Pass 0/5 Updating neighbors for node 8
—12-06-11 9:38:03 Job job#11 :heal_neighbor_node 8 (0x75b250) P:70 S:4 was Successful
—12-06-11 9:38:03 Pass 0/5 Updating neighbors for node 9
—12-06-11 9:38:04 Job job#12 :heal_neighbor_node 9 (0x7d2ad8) P:70 S:4 was Successful
—12-06-11 9:38:04 Pass 0/5 Updating neighbors for node 10
—12-06-11 9:38:12 Job job#13 :heal_neighbor_node 10 (0x7cd2a8) P:70 S:4 was Successful
—12-06-11 9:38:12 Pass 0/5 Updating neighbors for node 13
—12-06-11 9:38:12 Job job#14 :heal_neighbor_node 13 (0x7d2238) P:70 S:4 was Successful
—12-06-11 9:38:12 Pass 1/5 Updating neighbors for node 2
—12-06-11 9:38:13 Job job#15 :heal_neighbor_node 2 (0x7f79d0) P:70 S:4 was Successful
—12-06-11 9:38:13 Pass 1/5 Updating neighbors for node 3
—12-06-11 9:38:16 Job job#16 :heal_neighbor_node 3 (0x7cab58) P:70 S:4 was Successful
—12-06-11 9:38:16 Pass 1/5 Updating neighbors for node 4
—12-06-11 9:38:16 Job job#17 :heal_neighbor_node 4 (0x763f90) P:70 S:4 was Successful
—12-06-11 9:38:16 Pass 1/5 Updating neighbors for node 7
—12-06-11 9:38:16 Job job#18 :heal_neighbor_node 7 (0x8471e8) P:70 S:4 was Successful
—12-06-11 9:38:16 Pass 1/5 Updating neighbors for node 8
—12-06-11 9:38:25 Job job#19 :heal_neighbor_node 8 (0x7c8b30) P:70 S:4 was Successful
—12-06-11 9:38:25 Pass 1/5 Updating neighbors for node 9
—12-06-11 9:38:26 Job job#20 :heal_neighbor_node 9 (0x847498) P:70 S:4 was Successful
—12-06-11 9:38:26 Pass 1/5 Updating neighbors for node 13
—12-06-11 9:38:26 Job job#21 :heal_neighbor_node 13 (0x81b440) P:70 S:4 was Successful
—12-06-11 9:38:26 Pass 2/5 Updating neighbors for node 7
—12-06-11 9:38:27 Job job#22 :heal_neighbor_node 7 (0x7cdbd8) P:70 S:4 was Successful
—12-06-11 9:38:27 Pass 2/5 Updating neighbors for node 8
—12-06-11 9:38:35 Job job#23 :heal_neighbor_node 8 (0x84a448) P:70 S:4 was Successful
—12-06-11 9:38:35 Pass 3/5 Updating neighbors for node 8
—12-06-11 9:38:44 Job job#24 :heal_neighbor_node 8 (0x8101d0) P:70 S:4 was Successful
—12-06-11 9:38:44 Pass 4/5 Updating neighbors for node 8
—12-06-11 9:38:52 Job job#25 :heal_neighbor_node 8 (0x805c60) P:70 S:4 was Successful
—12-06-11 9:38:52 Neighbor Update Done
–Stage #3 started: 12-06-11 9:38:52 completed: 12-06-11 9:52:01 successful: Y
—12-06-11 9:38:52 Routing update node 2
—12-06-11 9:38:52 Job job#26 :heal_routing_node 2 (0x760368) P:70 S:4 was Successful
—12-06-11 9:38:52 Routing update node 3
—12-06-11 9:38:52 Job job#27 :heal_routing_node 3 (0x8c8b88) P:70 S:4 was Successful
—12-06-11 9:38:52 Routing update node 4
—12-06-11 9:38:52 Job job#28 :heal_routing_node 4 (0x75fc58) P:70 S:4 was Successful
—12-06-11 9:38:53 Routing update node 7
—12-06-11 9:38:53 Job job#29 :heal_routing_node 7 (0x814120) P:70 S:4 was Successful
—12-06-11 9:38:53 Routing update node 8
—12-06-11 9:38:53 Job job#30 :heal_routing_node 8 (0x7c2130) P:70 S:4 was Successful
—12-06-11 9:38:53 Routing update node 9
—12-06-11 9:38:53 Job job#31 :heal_routing_node 9 (0x848ce8) P:70 S:4 was Successful
—12-06-11 9:38:53 Routing update node 10
—12-06-11 9:38:53 Job job#32 :heal_routing_node 10 (0x80cb68) P:70 S:4 was Successful
—12-06-11 9:38:53 Routing update node 13
—12-06-11 9:38:53 Job job#33 :heal_routing_node 13 (0x845028) P:70 S:4 was Successful
—12-06-11 9:38:53 Routing update done
–Stage #4 started: 12-06-11 9:52:01 completed: 12-06-11 9:52:01 successful: Y
—12-06-11 9:40:16 Calculate Routes Done
–Stage #5 started: 12-06-11 9:40:16 completed: 12-06-11 9:52:01 successful: Y
—12-06-11 9:40:16 Configure node 2
—12-06-11 9:40:17 Job job#36 :conf_jh#2 (0x7fb050) P:70 S:4 was Successful: Node Successfully Configured
—12-06-11 9:40:18 Configure node 3
—12-06-11 9:42:38 Job job#42 :conf_jh#3 (0x7f71a0) P:70 S:4 was Successful: Node Successfully Configured
—12-06-11 9:42:38 Configure node 4
—12-06-11 9:42:41 Job job#61 :conf_jh#4 (0x7c9cd0) P:70 S:4 was Successful: Node Successfully Configured
—12-06-11 9:42:41 Configure node 7
—12-06-11 9:42:42 Job job#73 :conf_jh#7 (0x762110) P:70 S:4 was Successful: Node Successfully Configured
—12-06-11 9:42:42 Configure node 8
—12-06-11 9:42:53 Job job#80 :conf_jh#8 (0x8152f8) P:70 S:3 was Aborted: Unable to get any information on node
—12-06-11 9:42:53 Configure node 9
—12-06-11 9:42:57 Job job#82 :conf_jh#9 (0x7c3d98) P:70 S:4 was Successful: Node Successfully Configured
—12-06-11 9:42:57 Configure node 10
—12-06-11 9:43:08 Job job#96 :conf_jh#10 (0x7d19a8) P:70 S:3 was Aborted: Unable to get any information on node
—12-06-11 9:43:08 Configure node 13
—12-06-11 9:43:12 Job job#98 :conf_jh#13 (0x7c48c8) P:70 S:4 was Successful: Node Successfully Configured
—12-06-11 9:43:12 Configure Done
–Stage #6 started: 12-06-11 9:52:01 completed: 12-06-11 9:52:01 successful: Y
—12-06-11 9:49:12 Battery Done
–Stage #7 started: 12-06-11 9:50:12 completed: 12-06-11 9:52:01 successful: Y
—12-06-11 9:50:16 Node Details heal 2
—12-06-11 9:50:22 Node Details heal 2
—12-06-11 9:50:35 Node Details heal 3
—12-06-11 9:50:50 Node Details heal 3
—12-06-11 9:50:56 Node Details heal 4
—12-06-11 9:51:02 Node Details heal 4
—12-06-11 9:51:08 Node Details heal 7
—12-06-11 9:51:15 Node Details heal 7
—12-06-11 9:51:21 Node Details heal 8
—12-06-11 9:51:35 Node Details heal 8
—12-06-11 9:51:50 Node Details heal 9
—12-06-11 9:51:56 Node Details heal 9
—12-06-11 9:51:58 Stress test Done

2

If you look at the “EDGE NODE PROFILE” part, you can see a couple devices have hops in their routing, those devices at least should show their neighbors. More than likely this is a FW bug and not related to anything other than a displaying neighbors issue.
Check again in a few days and see if they show up again.

What Mios build are you running?

3

I had this problem awhile back and couldn’t fix it no matter what I did. Everything still worked but all my devices had only 1 neighbor like you are talking about.

I finally added a new device and then all of a sudden all my devices had neighbors again. I removed the new device later because I didn’t need it.
As @Jod says, maybe a firmware bug ?

Worth a try…

4

Adding a new module did once bring neighbor lists back but then they disappeared again. Vera has been healing every night with no return of neighbors. I’ll have to try excluding and including a module to see what happens.

What is the edge node profile officially?

Thanks
Chip

5
What is the edge node profile officially?
Only MCV could give you an official answer. IMHO, edge nodes connect internal nodes to external nodes.

Example below from your heal report:

Node: 2 Edge node: 0 score: 5 route: 1->0.0.0.0->2 num hops: 0 Latency avg: 98 max: 196 success 10 of 10 Edge node: 4 score: 10 route: 1->4.0.0.0->2 num hops: 1 Latency avg: 95 max: 181 success 10 of 10
Node 1 (Vera) is trying to communicate with node 2 (route: 1->0.0.0.0->2) in the frist of several tests Vera can communiacte directly and there is no need for an edge node and reports (num hops: 0)

The 2nd test Vera (1) uses node #4 (route: 1->4.0.0.0->2) to communicate with #2 (num hops: 1)
Notice how the latency was reduced “Latency avg: 95 max” by using a hop vs going direct.

What route actually gets used in practice? I have no idea; but it’s all worked out in MCV’s algorithm.

6

AFAIK, the route with the lowest score (that is working).

7

Hi,
If you look at the “EDGE NODE PROFILE” part you will see that all your nodes are there,
I (sometimes) have the same issue where the field “neighbors” does not seem to be working properly.

I do believe that this is a fw bug etc.

Dont worry, your nodes are fine.

Flo

8

Help!

All my devices have started showing neighbour as “1” (presumably Vera). I see that others have experienced this problem also.

System is more or less working except for one 3-in-1 sensor that fails to poll much of the time with the result that the temperature does not update.

Suggestion is that it is a FW problem (I’m on 1.5.408).

Since it’s been a while since there was any contribution to this thread I thought I’d check for progress before issuing a ticket.