It appears HS does not read Everspring units correctly!
Having struggled for almost a year now to get z-wave to work reliably without a great deal of success and now taking the bull by the horns I have managed to track down what I think is the basis of my problem. Everspring plug-in modules.
The Everspring module has been confirmed by independent sources as being a z-wave repeater, now I am assuming that is the same as a router, yet HS does not recognise it as that. It reports that it is a slave, not a routing slave.
Or, have I missed something in setting up the mesh as a lot of my z-wave statuses go to Unknown on a regular basis.
My log is full of this:
The Everspring module has been confirmed by independent sources as being a z-wave repeater, now I am assuming that is the same as a router, yet HS does not recognise it as that. It reports that it is a slave, not a routing slave.
Or, have I missed something in setting up the mesh as a lot of my z-wave statuses go to Unknown on a regular basis.
My log is full of this:
10/11/2013 20:28:31 Z-Wave Z-Wave WakeUp 'No More Info' Notification sent to Node 21
10/11/2013 20:29:31 Warning Aborting Z-Wave send, taking too long to send command to node 25 waited 2 seconds
10/11/2013 20:29:35 ERROR Timeout waiting for send abort to complete
10/11/2013 20:29:36 Z-Wave Z-Wave WakeUp 'No More Info' Notification sent to Node 25
10/11/2013 20:29:31 Warning Aborting Z-Wave send, taking too long to send command to node 25 waited 2 seconds
10/11/2013 20:29:35 ERROR Timeout waiting for send abort to complete
10/11/2013 20:29:36 Z-Wave Z-Wave WakeUp 'No More Info' Notification sent to Node 25