I have installed new devices for Christmas. They have been in for a while and are visible in AltUI, controllable, and no issues. It’s just the Network Quality Graph is not updating and showing the new devices. What do I do?
I have been noting same for a while… Suspect nothing to do with AlUI but rather with the Z-Wave F/W upgrade that came with the most recent versions of Vera F/W: I noted that routing variables in devices are no longer updated or even present in newly configured devices… It could be the consequence of “Mios Routing” being dropped as a result of these upgrades ?
Neighbors and Polling variables on the other hand still are updated and the “zWave Network” matrix in AltUI still works.
[quote=“LV999, post:2, topic:190611”]I have been noting same for a while… Suspect nothing to do with AlUI but rather with the Z-Wave F/W upgrade that came with the most recent versions of Vera F/W: I noted that routing variables in devices are no longer updated or even present in newly configured devices… It could be the consequence of “Mios Routing” being dropped as a result of these upgrades ?
Neighbors and Polling variables on the other hand still are updated and the “zWave Network” matrix in AltUI still works.[/quote]
That is correct , I can’t do a lot about until we understand where to get this data from now with the new firmwares…
I’d certainly help poke around. If you have some info of how you got the original I’ll try and use that as a basis to work on finding the new stuff. 
network quality chart is implemented by the function UIManager.pageQuality()
it uses the variable “AutoRoute” or “ManualRoute” from the devices when they exists which contains route information and metrics.
ManualRoute was to enable the user to force the route if I remember well.
Both variable used syntax like this for instance. the quality metric is after the “-”. the x means route is failing.
"2-20x,7-59x,2.7-78"The color of the link is automatically given by the D3 library using a d3.scale.quantize() from red to green and the color selected will be based on how close the value is from the min or the max values of all the data set.
linkcolor = d3.scale.quantize()
.domain( [d3.max(data.links, function(d) {return d.quality;} ),d3.min(data.links, function(d) {return d.quality;} )] )
.range(["red","orange","yellow","green"]);
since recent firmware with no more user controllable healing, it seems these variable & metrics are not updated anymore and therefore the chart lost its validity to my knowledge
Looks like zwave routes has the same issue. I’m no coder by any means but I matched what was in j_altuimgr.js with all the variables and information presented to me and the missing variable as we know is LastHeal otherwise it all seems in order but I can’t find any “heal” references in j_altuimgr.js.
Perhaps removing any need for the heal information and use the AutoRoute directly which is a “scoring” feature to determine quality and linkage instead. If the heal report was giving scores, perhaps using the scoring method below instead would be the new alternative.
http://docs5.mios.com/doc.php?language=1&platform=3Lite&page=ManualRoute
The score is a measure of latency and accuracy,the lower number is better. The ‘x’ that follows means the last attempt to use it failed, so it won’t be used anymore.
The next route uses node #7, it scored worse, and also failed. The 3rd route uses node 2 & 7. It had the worst score (78), but it’s currently working (no x).
(I’m assuming 0 or 1 is the best and I “think” 99 or 100 is the worst)
[quote=“tomtcom, post:6, topic:190611”]Looks like zwave routes has the same issue. I’m no coder by any means but I matched what was in j_altuimgr.js with all the variables and information presented to me and the missing variable as we know is LastHeal otherwise it all seems in order but I can’t find any “heal” references in j_altuimgr.js.
Perhaps removing any need for the heal information and use the AutoRoute directly which is a “scoring” feature to determine quality and linkage instead. If the heal report was giving scores, perhaps using the scoring method below instead would be the new alternative.
http://docs5.mios.com/doc.php?language=1&platform=3Lite&page=ManualRoute
The score is a measure of latency and accuracy,the lower number is better. The ‘x’ that follows means the last attempt to use it failed, so it won’t be used anymore.
The next route uses node #7, it scored worse, and also failed. The 3rd route uses node 2 & 7. It had the worst score (78), but it’s currently working (no x).
(I’m assuming 0 or 1 is the best and I “think” 99 or 100 is the worst)[/quote]
in fact ALTUI is not using lastheal or things like that. it purely uses the AutoRoute and ManualRoute, as documented in this link indeed : http://docs5.mios.com/doc.php?language=1&platform=3Lite&page=ManualRoute
but that doc seems obsolete and AutoRoute and ManualRoute do not seem to be used any more
[quote=“amg0, post:7, topic:190611”][quote=“tomtcom, post:6, topic:190611”]Looks like zwave routes has the same issue. I’m no coder by any means but I matched what was in j_altuimgr.js with all the variables and information presented to me and the missing variable as we know is LastHeal otherwise it all seems in order but I can’t find any “heal” references in j_altuimgr.js.
Perhaps removing any need for the heal information and use the AutoRoute directly which is a “scoring” feature to determine quality and linkage instead. If the heal report was giving scores, perhaps using the scoring method below instead would be the new alternative.
http://docs5.mios.com/doc.php?language=1&platform=3Lite&page=ManualRoute
The score is a measure of latency and accuracy,the lower number is better. The ‘x’ that follows means the last attempt to use it failed, so it won’t be used anymore.
The next route uses node #7, it scored worse, and also failed. The 3rd route uses node 2 & 7. It had the worst score (78), but it’s currently working (no x).
(I’m assuming 0 or 1 is the best and I “think” 99 or 100 is the worst)[/quote]
in fact ALTUI is not using lastheal or things like that. it purely uses the AutoRoute and ManualRoute, as documented in this link indeed : http://docs5.mios.com/doc.php?language=1&platform=3Lite&page=ManualRoute
but that doc seems obsolete and AutoRoute and ManualRoute do not seem to be used any more[/quote]
You are right and I “believe” any devices currently with AutoRoute and ManualRoute are no longer used and new ones are not creating that variable. With the exception of a battery device, all the devices below with no routing are the newest ones I installed post the zwave firmware change where heal was disabled and so on.
2016-01-20 20:37:50 1453340270
Node: 16 Name: MiniMote has this route and performance:
Node: 17 Name: Alarm has this route and performance:
Node: 18 Name: Kitchen Lights has this route and performance:
Node: 19 Name: Back Lawn Lights has this route and performance:
Node: 3 Name: Living Room Light has this route and performance: 0-5,9-13,11-15,11.10-22
Node: 11 Name: Front Room Lamp has this route and performance: 0-5,9-13,3-15,4-15
Node: 12 Name: Patio Light has this route and performance: 0-5,13-13,4-15,3-15
Node: 13 Name: Stand Up Light has this route and performance: 0-5,3-13,12-15,9-15
Node: 4 Name: Thermostat has this route and performance: 0-5,13-15,11-15,9.11-23
Node: 8 Name: Front Door Lock has this route and performance: 4-15,11-15,12-15,9.11-23
Node: 15 Name: Back Bathroom Door has this route and performance:
Node: 9 Name: Spare Bedroom Light has this route and performance: 0-3,3-15,4-15,11.10-23
Node: 10 Name: Outside Foyer Light has this route and performance: 11-13,3-15,4-15,13-17
Node: 20 Name: Front Lawn Lights has this route and performance:
Sounds like the zwave quality monitoring has been designed by the Zwave chip manufacturer ( Gen5 or Wave+) only for some service providers based on this IMA toolkit
http://z-wave.sigmadesigns.com/docs/Z-Wave_Whats_IMA_Tool2.pdf
No more access to the network quality data from the UI or Luup
[quote=“gerardosamara, post:9, topic:190611”]Sounds like the zwave quality monitoring has been designed by the Zwave chip manufacturer ( Gen5 or Wave+) only for some service providers based on this IMA toolkit
http://z-wave.sigmadesigns.com/docs/Z-Wave_Whats_IMA_Tool2.pdf
No more access to the network quality data from the UI or Luup[/quote]
That’s too bad. I’m sure it costs a lot.