This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Unable to zwave devices anymore
Today I tried to add a fgs-222 device from Fibaro to my configuration.
The initial device interview was aborted and I resetted the ZWave network next.
Now the device was succesfully included and worked, but re-including any other Fibaro Zwave device failed.
Next I resetted the zwave network again and tried to include a fibaro motionsensor (non Plus version), but the inclusion mode was not recognised by homey. Adding a Eversping Zwave also failed.
Bottonmline: No zwave device can be included anymore!
Next, I pulled the plug for 15 minutes, which didn't solve the problem either.
Has anyone else seen such behavior?
I'm on Homey experimental 1.22
The zwave log for device inclusion is below.
The initial device interview was aborted and I resetted the ZWave network next.
Now the device was succesfully included and worked, but re-including any other Fibaro Zwave device failed.
Next I resetted the zwave network again and tried to include a fibaro motionsensor (non Plus version), but the inclusion mode was not recognised by homey. Adding a Eversping Zwave also failed.
Bottonmline: No zwave device can be included anymore!
Next, I pulled the plug for 15 minutes, which didn't solve the problem either.
Has anyone else seen such behavior?
I'm on Homey experimental 1.22
The zwave log for device inclusion is below.
[2017-04-20T14:31:32.535Z] Command[1] start: addNode
[2017-04-20T14:31:32.637Z] Command[1] status: addNode, status: ADD_NODE_STATUS_LEARN_READY
[2017-04-20T14:32:02.671Z] Command[1] status: addNode, status: ADD_NODE_STATUS_DONE
[2017-04-20T14:32:02.677Z] ProcessAddNode[2]: Error: timeout
[2017-04-20T14:32:02.690Z] Command[1] end: addNode
[2017-04-20T14:32:05.380Z] Command[2] start: addNodeAbort
[2017-04-20T14:32:05.385Z] Command[2] end: addNodeAbort
[2017-04-20T14:32:29.800Z] Command[3] start: addNode
[2017-04-20T14:32:29.878Z] Command[3] status: addNode, status: ADD_NODE_STATUS_LEARN_READY
[2017-04-20T14:32:59.886Z] Command[3] status: addNode, status: ADD_NODE_STATUS_DONE
[2017-04-20T14:32:59.887Z] ProcessAddNode[3]: Error: timeout
[2017-04-20T14:32:59.891Z] Command[3] end: addNode
[2017-04-20T14:33:02.784Z] Command[4] start: addNodeAbort
[2017-04-20T14:33:02.790Z] Command[4] end: addNodeAbort
[2017-04-20T14:33:14.740Z] Command[5] start: getNetworkTopology
[2017-04-20T14:33:14.740Z] Command[5] start: getNetworkTopology
[2017-04-20T14:33:14.843Z] Command[5] end: getNetworkTopology
The Zwave state information:
{"zw_state":{"ver":5,"capabilities":{"api":"controller","timerSupported":false,"controllerType":"primary"},"nodes":[1],"chip_type":5,"chip_version":0,"homeId":3541521839,"nodeId":1,"nvr":[1,5,0,21,13,27,120,32,1,0,32,0,64,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,22,17,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,71,63],"CONTROLLER_IS_SECONDARY":false,"CONTROLLER_ON_OTHER_NETWORK":false,"CONTROLLER_NODEID_SERVER_PRESENT":true,"CONTROLLER_IS_REAL_PRIMARY":true,"CONTROLLER_IS_SUC":true,"NO_NODES_INCUDED":true,"sucId":1,"powerLevel":0,"version":"Z-Wave 3.99","networkKey":"820be4b4fc65edb72a091a4a2ede8694","methodsAsync":["factoryReset","addNodeAbort","removeNodeAbort","replaceFailedNodeAbort","sendData","isFailedNode","getFailedNodes","ping"]},"zw_ready":true,"_stateTimestamp":1492699106829}
The Zwave state information:
{"zw_state":{"ver":5,"capabilities":{"api":"controller","timerSupported":false,"controllerType":"primary"},"nodes":[1],"chip_type":5,"chip_version":0,"homeId":3541521839,"nodeId":1,"nvr":[1,5,0,21,13,27,120,32,1,0,32,0,64,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,22,17,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,71,63],"CONTROLLER_IS_SECONDARY":false,"CONTROLLER_ON_OTHER_NETWORK":false,"CONTROLLER_NODEID_SERVER_PRESENT":true,"CONTROLLER_IS_REAL_PRIMARY":true,"CONTROLLER_IS_SUC":true,"NO_NODES_INCUDED":true,"sucId":1,"powerLevel":0,"version":"Z-Wave 3.99","networkKey":"820be4b4fc65edb72a091a4a2ede8694","methodsAsync":["factoryReset","addNodeAbort","removeNodeAbort","replaceFailedNodeAbort","sendData","isFailedNode","getFailedNodes","ping"]},"zw_ready":true,"_stateTimestamp":1492699106829}
Comments
I had to reset homey back to defauilt settings (wiping all data) before I could add zwave devices again.
Off course that was only possible after resetting each device before including them in the Z-Wave network again.
Hopefully that won't happen again as it caused me a lot of work fixing all flows, luckily I saved all my flows before making any changess. Thanks to the Flow Backup app, kudos Serge!