None of my nodes have any neighbours!?!

Community Playground General Discussions
1

Hi everyone,

searching for the reason, why my z-wave network sometimes has a lag of 3-30 seconds I just saw, that none of my nodes have any neighbours in the advanced view.
Is this a flaw in the firmware (UI2 1.0.985) that simply doesn’t show them or is there something wrong with my network?

Cheers
Umtauscher

2

I get disappearing neighbors over time without making system changes, it does seem to only occur with my 3 in 1 sensors though, been waiting 3 weeks after submitting to tech support as requested, other than a forum comment that they would look at it I’ve had no reply, I know they’ve been busy with the new UI debacle but would be nice to hear something

3

Never had any neighbors on any of my devices and everything worked perfectly fine. Having few seconds lag is normal, but not 30 sec, unless you have dead nodes and some messages are stuck in the queue…

4

I gotta ask- you have ~20 devices and NONE of them have neighbors? That seems awfully odd that the only route your devices ever get is directly to/from the vera- doesn’t it? Sounds like something isn’t right.

do you regularly get lags of a few seconds or just sometimes? On rare occaisions I get a lag of a few seconds. But as a general rule I click a button and the action just happens.

5

Yes, I don’t have 20 but 6 nodes in the same floor. I normally get lags of 2-3 sec. the maximum seems to be about 30 sec.

I have to say that I am pretty unsatisfied with that performance. I am just setting neighbour ID’s by hand and see if that makes any difference. Nevertheless i think vera is the device that eats up the time.

We’ll see…

6

I’d try the repair nextwork function. My understanding is that kicks the crap out of the network for a while looking for ways to optimize it. so in theory that would fix it for you.

7

Hi Michael,

I am now pretty shure the “repair network” function does NOTHING.
Yesterday I ran it and it changed nothing. No neighbours…
Then I entered the neigbours by hand. In every node there now were 1 or two neighbours.
After that I ran the repair function again. Afterwards everything I entered manually was unchanged.

So either way the repair function didn’t change anything. Since both runs didn’t lead to any change I’m pretty sure, there is something messed up in Vera - again. >:(

Thanks anway for your suggestions.

Umtauscher

8

so the question : is there any point of adding nodes by hand. Just curious

regards

9

Well I seriously don’t know. I just used It to try to esablish if “repair my network” does do anything. In any case there should be changes after running it, but there are none. So this at least is broken. I am wondering what is not!

I am still hunting the lag…

10

Would you mind posting your Z-Wave routing matrix (http://forum.micasaverde.com/index.php?topic=2099.msg8292#msg8292)?

11

done, thanks.

12

Ok, thanks for all your input.

I solved the problem. I updated my z-wave dongle from 2.40 L:1 to 2.78 L:1
Now every node has 4-5 neighbours. Even after inclusion of a new node, the neighbours get updated automatically.

I find it quite strange, that this information is nowhere on the forum. At least MCV should know of any major changes in the dongles firmware and publish it.

Time will tell, if the lag will be gone.

Cheers
Umtauscher

13

@umtauscher,
Ah, that may explain it - I have 2.40 dongle.

@michaelk,
Yes, all my devices work fine, the delay is usually a second or two on average. I used to see some neighbors with older firmware prior to Luup. With new firmware I see no neighbors and everything works fine. Could be because of the old dongle, as umtauscher said…

14

HI:

I am having the same issue. None of my nodes have neighbours, I have Vera 2 with Z-wave 3.2 L:1

Here is my repair report:
11-10-03 2:07:14 report for HealNetwork. Successful: Y Updated net: N mr_only:1 Job ID: job#2238 :heal network auto (0x78fac0) P:50 S:5

=======NEIGHBOR NODE UPDATES=======
Node 4 Device 43 Living 2 neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: YES
Node 33 Device 119 Closet neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: YES
Node 36 Device 123 Terraza neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: YES
Node 39 Device 130 Term Salita_T1 neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: YES
Node 40 Device 134 _Home Energy Monitor neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: NO
Node 42 Device 152 Piscina neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: YES
Node 43 Device 217 Pieza Principal neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: YES
Node 44 Device 219 Pieza Principal 1 neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: YES
Node 46 Device 231 Escritorio 1 neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: YES
Node 47 Device 232 Salita 2 neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: YES
Node 48 Device 262 Baño Niños neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: YES
Node 49 Device 234 Pieza Niños neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: YES
Node 50 Device 235 Pieza 2 neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: YES
Node 51 Device 236 Entrada neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: YES
Node 52 Device 237 Baño Visitas neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: YES
Node 53 Device 238 Salita neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: YES
Node 54 Device 239 Lavadero neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: YES
Node 55 Device 240 Living neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: YES
Node 56 Device 264 Baño Ducha neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: YES
Node 57 Device 242 Baño Principal neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: YES
Node 58 Device 243 Baño ppal espejos neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: YES
Node 59 Device 266 Pieza Milu neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: YES
Node 60 Device 267 Pasillo Living neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: YES
Node 62 Device 279 Acceso neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: YES
Node 63 Device 280 Comedor neighbor nodes updated 0 times (incomplete 0 in a row 0), woke up 0 times configured: YES

=======STRESS TEST RESULT=======

=======NEIGHBOR NODE RESULT=======

Inversely:

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

Node: 4
Edge node: 0 score: 106 route: 1->0.0.0.0->4 num hops: 0 Latency avg: 150 max: 235 success 5 of 10

Node: 33
Edge node: 0 score: 26 route: 1->0.0.0.0->33 num hops: 0 Latency avg: 211 max: 1273 success 10 of 10

Node: 36
Edge node: 0 score: 5 route: 1->0.0.0.0->36 num hops: 0 Latency avg: 100 max: 183 success 10 of 10

Node: 39
Edge node: 0 score: 48 route: 1->0.0.0.0->39 num hops: 0 Latency avg: 1190 max: 1199 success 10 of 10

Node: 40
Edge node: 33 score: 118 route: 1->33.0.0.0->40 num hops: 1 Latency avg: 1338 max: 2430 success 8 of 10
Edge node: 57 score: 188 route: 1->57.0.0.0->40 num hops: 1 Latency avg: 1368 max: 5398 success 7 of 10

Node: 42
Edge node: 0 score: 4 route: 1->0.0.0.0->42 num hops: 0 Latency avg: 102 max: 130 success 10 of 10

Node: 43
Edge node: 33 score: 8 route: 1->33.0.0.0->43 num hops: 1 Latency avg: 100 max: 112 success 10 of 10
Edge node: 44 score: 30 route: 1->44.0.0.0->43 num hops: 1 Latency avg: 97 max: 185 success 9 of 10
Edge node: 46 score: 10 route: 1->46.0.0.0->43 num hops: 1 Latency avg: 103 max: 191 success 10 of 10
Edge node: 49 score: 10 route: 1->49.0.0.0->43 num hops: 1 Latency avg: 98 max: 191 success 10 of 10
Edge node: 50 score: 50 route: 1->50.0.0.0->43 num hops: 1 Latency avg: 106 max: 191 success 8 of 10
Edge node: 52 score: 70 route: 1->52.0.0.0->43 num hops: 1 Latency avg: 104 max: 186 success 7 of 10
Edge node: 56 score: 15 route: 1->44.56.0.0->43 num hops: 2 Latency avg: 97 max: 181 success 10 of 10
Edge node: 57 score: 10 route: 1->57.0.0.0->43 num hops: 1 Latency avg: 98 max: 191 success 10 of 10
Edge node: 58 score: 172 route: 1->58.0.0.0->43 num hops: 1 Latency avg: 145 max: 290 success 2 of 10
Edge node: 62 score: 10 route: 1->62.0.0.0->43 num hops: 1 Latency avg: 98 max: 191 success 10 of 10

Node: 44
Edge node: 0 score: 5 route: 1->0.0.0.0->44 num hops: 0 Latency avg: 98 max: 189 success 10 of 10

Node: 46
Edge node: 0 score: 5 route: 1->0.0.0.0->46 num hops: 0 Latency avg: 97 max: 187 success 10 of 10

Node: 47
Edge node: 0 score: 3 route: 1->0.0.0.0->47 num hops: 0 Latency avg: 99 max: 105 success 10 of 10

Node: 49
Edge node: 0 score: 5 route: 1->0.0.0.0->49 num hops: 0 Latency avg: 97 max: 189 success 10 of 10

Node: 50
Edge node: 0 score: 5 route: 1->0.0.0.0->50 num hops: 0 Latency avg: 97 max: 187 success 10 of 10

Node: 51
Edge node: 0 score: 3 route: 1->0.0.0.0->51 num hops: 0 Latency avg: 100 max: 115 success 10 of 10

Node: 52
Edge node: 0 score: 5 route: 1->0.0.0.0->52 num hops: 0 Latency avg: 97 max: 187 success 10 of 10

Node: 53
Edge node: 0 score: 25 route: 1->0.0.0.0->53 num hops: 0 Latency avg: 202 max: 1228 success 10 of 10

Node: 54
Edge node: 0 score: 5 route: 1->0.0.0.0->54 num hops: 0 Latency avg: 97 max: 187 success 10 of 10

Node: 55
Edge node: 0 score: 4 route: 1->0.0.0.0->55 num hops: 0 Latency avg: 104 max: 149 success 10 of 10

Node: 56
Edge node: 33 score: 20 route: 1->33.0.0.0->56 num hops: 1 Latency avg: 103 max: 827 success 10 of 10
Edge node: 43 score: 15 route: 1->33.43.0.0->56 num hops: 2 Latency avg: 98 max: 191 success 10 of 10
Edge node: 44 score: 10 route: 1->44.0.0.0->56 num hops: 1 Latency avg: 98 max: 190 success 10 of 10
Edge node: 46 score: 130 route: 1->46.0.0.0->56 num hops: 1 Latency avg: 108 max: 227 success 4 of 10
Edge node: 49 score: 10 route: 1->49.0.0.0->56 num hops: 1 Latency avg: 98 max: 191 success 10 of 10
Edge node: 57 score: 96 route: 1->57.0.0.0->56 num hops: 1 Latency avg: 109 max: 560 success 6 of 10

Node: 57
Edge node: 0 score: 5 route: 1->0.0.0.0->57 num hops: 0 Latency avg: 98 max: 188 success 10 of 10

Node: 58
Edge node: 0 score: 49 route: 1->0.0.0.0->58 num hops: 0 Latency avg: 111 max: 466 success 8 of 10

Node: 59
Edge node: 0 score: 5 route: 1->0.0.0.0->59 num hops: 0 Latency avg: 97 max: 188 success 10 of 10

Node: 60
Edge node: 0 score: 5 route: 1->0.0.0.0->60 num hops: 0 Latency avg: 103 max: 188 success 10 of 10

Node: 62
Edge node: 0 score: 5 route: 1->0.0.0.0->62 num hops: 0 Latency avg: 97 max: 188 success 10 of 10

Node: 63
Edge node: 4 score: 116 route: 1->4.0.0.0->63 num hops: 1 Latency avg: 202 max: 413 success 5 of 10
Edge node: 36 score: 10 route: 1->36.0.0.0->63 num hops: 1 Latency avg: 98 max: 191 success 10 of 10
Edge node: 42 score: 10 route: 1->42.0.0.0->63 num hops: 1 Latency avg: 100 max: 190 success 10 of 10
Edge node: 46 score: 8 route: 1->46.0.0.0->63 num hops: 1 Latency avg: 95 max: 102 success 10 of 10
Edge node: 51 score: 10 route: 1->51.0.0.0->63 num hops: 1 Latency avg: 98 max: 191 success 10 of 10
Edge node: 54 score: 29 route: 1->54.0.0.0->63 num hops: 1 Latency avg: 109 max: 156 success 9 of 10
Edge node: 55 score: 24 route: 1->55.0.0.0->63 num hops: 1 Latency avg: 116 max: 1069 success 10 of 10
Edge node: 59 score: 51 route: 1->59.0.0.0->63 num hops: 1 Latency avg: 121 max: 222 success 8 of 10
Edge node: 62 score: 10 route: 1->62.0.0.0->63 num hops: 1 Latency avg: 98 max: 191 success 10 of 10

=======DETAILED LOG=======