Update routes fails

Discussions about Z-Way software and Z-Wave technology in general
pz1
Posts: 2053
Joined: 08 Apr 2012 13:44

Update routes fails

Post by pz1 »

Under menu Network/Routing Table the commmand update routes fails with the warning:
Command execution failed due to some error on the server: Command not found: /ZWaveAPI/Run/devices%5B10%5D.RequestNodeNeighborUpdate().

The log file says:
2012-08-09 14:43:12,077 WebSrv.ERROR Bad request /ZWaveAPI/Run/devices%5B10%5D.RequestNodeNeighborUpdate(): Command not found: /ZWaveAPI/Run/devices%5B10%5D.RequestNodeNeighborUpdate()
2012-08-09 14:43:12,076 Except.CRITICAL Error handling web request: /ZWaveAPI/Run/devices%5B10%5D.RequestNodeNeighborUpdate()
2012-08-09 14:43:12,076 Except.CRITICAL AttributeError: Device instance has no attribute 'RequestNodeNeighborUpdate'
2012-08-09 14:43:12,076 Except.CRITICAL File "", line 1, in
2012-08-09 14:43:12,076 Except.CRITICAL File "/var/pyzw/pyzw/WebServer.py", line 178, in do_POST
2012-08-09 14:43:12,076 Except.CRITICAL Traceback (most recent call last):
2012-08-09 14:43:11,964 WebSrv.ERROR Bad request /ZWaveAPI/Run/devices%5B9%5D.RequestNodeNeighborUpdate(): Command not found: /ZWaveAPI/Run/devices%5B9%5D.RequestNodeNeighborUpdate()
2012-08-09 14:43:11,963 Except.CRITICAL Error handling web request: /ZWaveAPI/Run/devices%5B9%5D.RequestNodeNeighborUpdate()
2012-08-09 14:43:11,963 Except.CRITICAL AttributeError: Device instance has no attribute 'RequestNodeNeighborUpdate'
2012-08-09 14:43:11,963 Except.CRITICAL File "", line 1, in
2012-08-09 14:43:11,963 Except.CRITICAL File "/var/pyzw/pyzw/WebServer.py", line 178, in do_POST
2012-08-09 14:43:11,961 Except.CRITICAL Traceback (most recent call last):
2012-08-09 14:43:11,929 WebSrv.ERROR Bad request /ZWaveAPI/Run/devices%5B7%5D.RequestNodeNeighborUpdate(): Command not found: /ZWaveAPI/Run/devices%5B7%5D.RequestNodeNeighborUpdate()
2012-08-09 14:43:11,928 WebSrv.ERROR Bad request /ZWaveAPI/Run/devices%5B8%5D.RequestNodeNeighborUpdate(): Command not found: /ZWaveAPI/Run/devices%5B8%5D.RequestNodeNeighborUpdate()
2012-08-09 14:43:11,928 Except.CRITICAL Error handling web request: /ZWaveAPI/Run/devices%5B7%5D.RequestNodeNeighborUpdate()
2012-08-09 14:43:11,927 Except.CRITICAL Error handling web request: /ZWaveAPI/Run/devices%5B8%5D.RequestNodeNeighborUpdate()
2012-08-09 14:43:11,927 Except.CRITICAL AttributeError: Device instance has no attribute 'RequestNodeNeighborUpdate'
2012-08-09 14:43:11,927 Except.CRITICAL AttributeError: Device instance has no attribute 'RequestNodeNeighborUpdate'
2012-08-09 14:43:11,926 Except.CRITICAL File "", line 1, in
2012-08-09 14:43:11,926 Except.CRITICAL File "", line 1, in
2012-08-09 14:43:11,924 Except.CRITICAL File "/var/pyzw/pyzw/WebServer.py", line 178, in do_POST
2012-08-09 14:43:11,923 Except.CRITICAL File "/var/pyzw/pyzw/WebServer.py", line 178, in do_POST
2012-08-09 14:43:11,922 Except.CRITICAL Traceback (most recent call last):
2012-08-09 14:43:11,921 Except.CRITICAL Traceback (most recent call last):
2012-08-09 14:43:11,795 WebSrv.ERROR Bad request /ZWaveAPI/Run/devices%5B5%5D.RequestNodeNeighborUpdate(): Command not found: /ZWaveAPI/Run/devices%5B5%5D.RequestNodeNeighborUpdate()
2012-08-09 14:43:11,794 Except.CRITICAL Error handling web request: /ZWaveAPI/Run/devices%5B5%5D.RequestNodeNeighborUpdate()
2012-08-09 14:43:11,794 Except.CRITICAL AttributeError: Device instance has no attribute 'RequestNodeNeighborUpdate'
2012-08-09 14:43:11,794 Except.CRITICAL File "", line 1, in
2012-08-09 14:43:11,794 Except.CRITICAL File "/var/pyzw/pyzw/WebServer.py", line 178, in do_POST
2012-08-09 14:43:11,793 Except.CRITICAL Traceback (most recent call last):
2012-08-09 14:43:11,734 WebSrv.ERROR Bad request /ZWaveAPI/Run/devices%5B4%5D.RequestNodeNeighborUpdate(): Command not found: /ZWaveAPI/Run/devices%5B4%5D.RequestNodeNeighborUpdate()
2012-08-09 14:43:11,734 Except.CRITICAL Error handling web request: /ZWaveAPI/Run/devices%5B4%5D.RequestNodeNeighborUpdate()
2012-08-09 14:43:11,733 Except.CRITICAL AttributeError: Device instance has no attribute 'RequestNodeNeighborUpdate'
2012-08-09 14:43:11,733 Except.CRITICAL File "", line 1, in
2012-08-09 14:43:11,733 Except.CRITICAL File "/var/pyzw/pyzw/WebServer.py", line 178, in do_POST
2012-08-09 14:43:11,732 Except.CRITICAL Traceback (most recent call last):
2012-08-09 14:43:11,390 WebSrv.ERROR Bad request /ZWaveAPI/Run/devices%5B1%5D.RequestNodeNeighborUpdate(): Command not found: /ZWaveAPI/Run/devices%5B1%5D.RequestNodeNeighborUpdate()
2012-08-09 14:43:11,390 Except.CRITICAL Error handling web request: /ZWaveAPI/Run/devices%5B1%5D.RequestNodeNeighborUpdate()
2012-08-09 14:43:11,390 Except.CRITICAL AttributeError: Device instance has no attribute 'RequestNodeNeighborUpdate'
2012-08-09 14:43:11,389 Except.CRITICAL File "", line 1, in
2012-08-09 14:43:11,389 Except.CRITICAL File "/var/pyzw/pyzw/WebServer.py", line 178, in do_POST
2012-08-09 14:43:11,388 Except.CRITICAL Traceback (most recent call last):
2012-08-09 14:43:02,506 Rules.INFO Event: from 10:0 to 1:0, Report, value: [37, 0]
2012-08-09 14:43:02,454 Z-Wave.INFO Send to device 10, instance 0, switch binary get: Delivered
2012-08-09 14:43:02,391 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-08-09 14:43:02,204 Rules.INFO Event: from 9:0 to 1:0, Report, value: [37, 0]


Is this due to something wrong in my settings, or is something wrong in the central server? I am investigating this, because after placinf one more Zwave.me binary switch, my system behaves strange. The network matrix has many more red and yellow fields.

By the way, in the colored blocks I did see number combinations like 3/2. I could not find the meaning of those numbers in the manual.

Edit: In addition the communications timing statistics table does have three % colums. Can you tell what the SOSO column means?
Since 29-12-2016 I am no longer a moderator for this forum
User avatar
PoltoS
Posts: 7565
Joined: 26 Jan 2011 19:36

Great! Someone is using geek stuff in Z-Cloud ;)

Post by PoltoS »

We did partial update of our server for technical reasons and this screwed up some functions in GUI. We have already fixed this issue.

We hoped no one will notice these minor issues, but we are surprised to have advanced users among our cutomers ;)

The numbers in expert mode in routing tables are ammount of one hope routes / ammount of two hop routes.
As for SOSO column, it means the timing is "so-so". Not good, but still not bad.
pz1
Posts: 2053
Joined: 08 Apr 2012 13:44

Working after restart

Post by pz1 »

After a restart of z-agent the update routes is working again. Thanks for the quick fix of this problem.
A first observation is that the result of a manual update routes produces a more stable (=more dark green) result than the matrix produced immediately after the restart.
For the "so-so" column I noticed very high percentages there (ranging from 83-100%). Even a Zwave.me switch which is about one meter away in direct sight of the Z-stick has a 93% "so-so" level, and only 6% was OK. The Danfoss LC noted 66% OK and 33% Fail, but "so-so" was 0%. How must I interpret these data? Does this mean that the Aeon Z-stick S2 is not functioning correctly?
Since 29-12-2016 I am no longer a moderator for this forum
User avatar
PoltoS
Posts: 7565
Joined: 26 Jan 2011 19:36

Usually so-so means that routing occurs

Post by PoltoS »

The exact timeing (on the right) can even give and idea about how many hops are involved. No, that does not certinly means Aeon labs stick has something wrong. These data are not easy to interpret - usually we use them in conjunction with other data like routing table and actual user experience.

33% of failure for DLC is normal, since sometimes packets are sent then devices is already sleeping, so packets fails.
pz1
Posts: 2053
Joined: 08 Apr 2012 13:44

Automatic Updates?

Post by pz1 »

In the standard setup you provided a Scene call Request Network Update which is called via a schedule every friday mid night. The command in this scene is defined as:
if ZWaveAPI.controller.data.SUCNodeId.value not in (0, ZWaveAPI.controller.data.nodeId.value):
ZWaveAPI.RequestNetworkUpdate()


I thought this performed an update routes just like Network/Routing Table/Update routs. But if Iactivate that scene nothing happens.
What do I miss?
Since 29-12-2016 I am no longer a moderator for this forum
User avatar
PoltoS
Posts: 7565
Joined: 26 Jan 2011 19:36

This script should be used when Z-Cloud is secondary controller

Post by PoltoS »

This script should be used when Z-Cloud is secondary controller. It will get updates from primary SUC/SIS controller.In your case Z-Way is primary.To update routes of devices you need another script: ZWaveAPI.NetworkHealing()  You can also directly run: for nodeId in self.devices.keys():
if nodeId not in (self.NODE_BROADCAST, self.controller.data.nodeId.value) and not self.devices[nodeId].data.basicType.value == 1:
self.devices[nodeId].RequestNodeNeighbourUpdate()  
pz1
Posts: 2053
Joined: 08 Apr 2012 13:44

Thanks

Post by pz1 »

Thank you for this very helpful comment. Unfortunately I can't save the modified Scene. I get this error:
Can not write Rules.xml: File Not Found: ./config/Rules.xml,
Error response
Error code 404.
Message: File Not Found: ./config/Rules.xml.
I do get the same error if I try to save a device from which the position has changed.
update: From my WEB interface I can open ./config/Rules.xml
Since 29-12-2016 I am no longer a moderator for this forum
User avatar
PoltoS
Posts: 7565
Joined: 26 Jan 2011 19:36

Fixed. Was a problem with filesystem

Post by PoltoS »

Save it again
pz1
Posts: 2053
Joined: 08 Apr 2012 13:44

Thanks for the quick fix

Post by pz1 »

Thanks. I got it working with the first solution in the scene:
ZWaveAPI.NetworkHealing()

If I put in the second solution the system complained about "self" not existing or so. I put that code in a scene and activated the scene.
Since 29-12-2016 I am no longer a moderator for this forum
User avatar
PoltoS
Posts: 7565
Joined: 26 Jan 2011 19:36

Oops ;)

Post by PoltoS »

Indeed! Substitute self by ZWaveAPI. It's a copy from internal code of Z-Way, where self is ZWaveAPI...
Post Reply