wmcneil Posted April 6, 2020 Posted April 6, 2020 I am unable to add a new Zwave device using my ISY. When I select "add/include a zwave device" the "adding" window does not appear, and I am unable to add any new devices. From the event viewer, I see the following: Sun 04/05/2020 06:52:34 PM : Z-Wave device detected, retrieving info 7 Sun 04/05/2020 06:54:26 PM : [ZWAVE-TX-NR ] [0105004A85EBDE] REQ ZW_ADD_NODE_TO_NETWORK Sun 04/05/2020 06:54:26 PM : [ZWAVE-TX-NR ] [0105004B05EC58] REQ ZW_REMOVE_NODE_FROM_NETWORK FUNCID=5 STATUS=236 UID=88 Sun 04/05/2020 06:54:26 PM : [ZWAVE-TX-NR ] [0105004D05ED5F] REQ ZW_CONTROLLER_CHANGE Sun 04/05/2020 06:54:26 PM : [ZWAVE-TX-NR ] [0105005000EE44] REQ ZW_SET_LEARN_MODE Sun 04/05/2020 06:54:26 PM : [ZWAVE-TX ] [01030020DC] REQ MEMORY_GET_ID Sun 04/05/2020 06:54:26 PM : [ZWAVE-TX ] [01030002FE] REQ SERIAL_API_GET_INIT_DATA Sun 04/05/2020 06:54:26 PM : [ZWAVE-TX ] [01030005F9] REQ ZW_GET_CONTROLLER_CAPABILITIES Sun 04/05/2020 06:54:27 PM : [ZWAVE-TX-NR ] [0105004A85EFDA] REQ ZW_ADD_NODE_TO_NETWORK Sun 04/05/2020 06:54:27 PM : [ZWAVE-TX ] [01030020DC] REQ MEMORY_GET_ID Sun 04/05/2020 06:54:27 PM : [ZWAVE-TX ] [01030002FE] REQ SERIAL_API_GET_INIT_DATA Sun 04/05/2020 06:54:27 PM : [ZWAVE-TX ] [01030005F9] REQ ZW_GET_CONTROLLER_CAPABILITIES I have tried all of the following: heal zwave network, repair links, synchronize all. I still get the same behavior. Reading this thread , it seems likely that the problem is that I unintentionally made another Zwave controller primary. The other controller is a Trane XL824 thermostat. It has no option to "shift Primary Control to another device". (In fact, it seems to be intentionally designed not to play well with others.) Is there really no way to forcibly make the ISY the primary controller? Is my only option to rebuild the zwave network from scratch? If so, how can this be an acceptable architecture?
Mecheng70 Posted April 6, 2020 Posted April 6, 2020 Did you try try excluding the Trane? Did you ty rebooting like the second poster did? Also, try commenting on that thread and see if someone there may have solved the issue. What firmware are you on?
wmcneil Posted April 6, 2020 Author Posted April 6, 2020 9 hours ago, Mecheng70 said: Did you try try excluding the Trane? Did you ty rebooting like the second poster did? Also, try commenting on that thread and see if someone there may have solved the issue. What firmware are you on? I'm on 5.0.16C . Yes, I have tried (repeatedly) to exclude the Trane XL824. Yes I have repeatedly rebooted the ISY. @Michel Kohanim , can you comment on this please? If the ISY can be placed into a state where it is not possible to return it to being the primary zwave controller without completely rebuilding the zwave network from scratch, do you not agree that this is a serious problem that needs to be addressed? Since either poor implementation or outright malicious intent of another controller can create the situation, this makes the problem all the more troubling.
lilyoyo1 Posted April 6, 2020 Posted April 6, 2020 9 hours ago, wmcneil said: I am unable to add a new Zwave device using my ISY. When I select "add/include a zwave device" the "adding" window does not appear, and I am unable to add any new devices. From the event viewer, I see the following: Sun 04/05/2020 06:52:34 PM : Z-Wave device detected, retrieving info 7 Sun 04/05/2020 06:54:26 PM : [ZWAVE-TX-NR ] [0105004A85EBDE] REQ ZW_ADD_NODE_TO_NETWORK Sun 04/05/2020 06:54:26 PM : [ZWAVE-TX-NR ] [0105004B05EC58] REQ ZW_REMOVE_NODE_FROM_NETWORK FUNCID=5 STATUS=236 UID=88 Sun 04/05/2020 06:54:26 PM : [ZWAVE-TX-NR ] [0105004D05ED5F] REQ ZW_CONTROLLER_CHANGE Sun 04/05/2020 06:54:26 PM : [ZWAVE-TX-NR ] [0105005000EE44] REQ ZW_SET_LEARN_MODE Sun 04/05/2020 06:54:26 PM : [ZWAVE-TX ] [01030020DC] REQ MEMORY_GET_ID Sun 04/05/2020 06:54:26 PM : [ZWAVE-TX ] [01030002FE] REQ SERIAL_API_GET_INIT_DATA Sun 04/05/2020 06:54:26 PM : [ZWAVE-TX ] [01030005F9] REQ ZW_GET_CONTROLLER_CAPABILITIES Sun 04/05/2020 06:54:27 PM : [ZWAVE-TX-NR ] [0105004A85EFDA] REQ ZW_ADD_NODE_TO_NETWORK Sun 04/05/2020 06:54:27 PM : [ZWAVE-TX ] [01030020DC] REQ MEMORY_GET_ID Sun 04/05/2020 06:54:27 PM : [ZWAVE-TX ] [01030002FE] REQ SERIAL_API_GET_INIT_DATA Sun 04/05/2020 06:54:27 PM : [ZWAVE-TX ] [01030005F9] REQ ZW_GET_CONTROLLER_CAPABILITIES I have tried all of the following: heal zwave network, repair links, synchronize all. I still get the same behavior. Reading this thread , it seems likely that the problem is that I unintentionally made another Zwave controller primary. The other controller is a Trane XL824 thermostat. It has no option to "shift Primary Control to another device". (In fact, it seems to be intentionally designed not to play well with others.) Is there really no way to forcibly make the ISY the primary controller? Is my only option to rebuild the zwave network from scratch? If so, how can this be an acceptable architecture? This is a zwave issue not an isy issue. Technically it's not even an issue. It's only an issue since (in your case) you want it to do something that it's not designed to do. Since Trane doesn't allow swapping someone can't simply tap into your network and screw with it. Controllers in general don't play well with others as their primary design is to be the boss and control devices. It's like being a company. The controller is a boss and the devices are employees. Another boss (that's equal) can't simply walk up to an employee and say you work for me now. The same thing applies to the isy. The Trane is the controller. The isy can't simply take control of something else from it. Especially if the current controller doesnt allow it.
wmcneil Posted April 8, 2020 Author Posted April 8, 2020 I submitted a ticket to universal devices, and Michel and Chris helped me work through the issues. (Thanks guys!) I was able to get things straightened out without having to rebuild my zwave network. Here are the important take-aways: * If you are unable to exclude a zwave device via normal means: In the admin console, you can do right click / zwave / remove failed node (A couple of scenarios where you would be unable to exclude the device: the device is malfunctioning, or you are no longer in physical possession of the device.) * Before attempting to include any device to your zwave network that you have reason to believe may not play well: In the admin console: do zwave/ tools /backup followed by file / backup isy * If you want your ISY to remain the primary controller of your zwave network, do not attempt to include any of the newest Trane zwave thermostats (that have the built in Nexia bridge). These thermostats are not capable of any zwave role other than primary controller, and attempting to include them may remove your ability to include zwave devices using the ISY.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.