asbril Posted August 26, 2020 Posted August 26, 2020 11 minutes ago, hart2hart said: s there a guide here that shows how to move from 300 to 500 series board? I remember that when I received the 500 dongle, it came with instructions.
lilyoyo1 Posted August 26, 2020 Posted August 26, 2020 (edited) 31 minutes ago, hart2hart said: Thanks it is battery operated so if I understand you that makes it a receiver only so not part of the mesh. Thanks. Whew! Bullet. dodged. Lol Is there a guide here that shows how to move from 300 to 500 series board? I’ve had a mini note since I first installed zwave board. As I recall I have to transfer control over to it to start process but that’s about all and that may be dated information. You're welcome it's pretty simple. Make a back up of the zwave board (it's separate from the isy back up). Then restore it to the new one https://wiki.universal-devices.com/index.php?title=Z-Wave_500_Series_Beta The transfer I believe was to update the zwave board itself (if memory is correct) Edited August 26, 2020 by lilyoyo1
blueman2 Posted August 27, 2020 Posted August 27, 2020 1 hour ago, danbutter said: Ok so thanks to all that answered my question about a mixed zwave network. I do have the 500 series board in my ISY so I took a chance and upgraded to 5.2.0. So far it seems like no zwave device knows about any other device. Do I have to run that Update Neighbors on every zwave device I have since the "Heal" is gone now? The other thing I have noticed is that my Kwikset locks don't like this version much. If I manually operate the locks they show up in the AC, but after that ISY doesn't seem to know they are there anymore and there is no battery level displayed like there always has been before now. Saw this in the event viewer when running a query on one of them: Wed 08/26/2020 06:15:32 PM : [ZW-TX-FAILED] enc=Fail uid=29.0 cmd=0x80.02 BATTERY Thoughts? Did you do a synchronize on any of the devices yet? I would start with the devices that are closest to the ISY or can be brought near the ISY. Do the synchronize one by one so that you can more easily deal with issues as they arise.
jwagner010 Posted August 27, 2020 Posted August 27, 2020 (edited) On 8/25/2020 at 11:32 AM, asbril said: Chris, I apologize for my ignorance but I am not sure to understand what a button press is and what it is supposed to do. @Chris JahnI too would be interested to understand exactly what this is. Is there documentation describing what this actual is / does? Much thanks. “Optional Basic and Button Press/Sensor Detection nodes for Z-Wave devices (See Z-Wave node level menu in the Admin Console)” Edited August 27, 2020 by jwagner010
hart2hart Posted August 27, 2020 Posted August 27, 2020 This is way in the weeds about zwave plus but my Schlage BE469 deadbolts are version prior to the BE469ZP versions. Any issues with them on 500 series board? Any reason to consider replacing them? They are the only two Zwave devices I need to have stay near 100% reliable.
TexMike Posted August 27, 2020 Posted August 27, 2020 19 hours ago, hart2hart said: Is there a guide here that shows how to move from 300 to 500 series board? Same question from me. Specifically, can you restore a Z-Wave backup or some other method of migration or will I need to manually exclude/include every Z-Wave device after upgrading to the 500?
danbutter Posted August 27, 2020 Posted August 27, 2020 (edited) 20 hours ago, blueman2 said: Did you do a synchronize on any of the devices yet? I would start with the devices that are closest to the ISY or can be brought near the ISY. Do the synchronize one by one so that you can more easily deal with issues as they arise. Well I was a bit leary of the synchronize because the last time I tried I never got the node back, but I have a backup so I tried again, but now with 5.2.0. So before doing the sync I did the show all and this is what I got: Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] ---------------------------------------------- Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] Mudroom_Outlet Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] ZW020_1 uid=20 security=None type=4.16.1 mid=99 tid=18770 pid=12337 Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] - x25 V1 SWITCH_BINARY Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] - x27 V1 SWITCH_ALL Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] - x75 V1 PROTECTION Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] - x73 V1 POWERLEVEL Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] - x70 V1 CONFIGURATION Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] - x86 V1 VERSION Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] - x72 V1 MANUFACTURER_SPECIFIC Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] - x77 V1 NODE_NAMING Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] - Secure Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] Last working route from ISY to Node 20 - Mudroom_Outlet Thu 08/27/2020 04:07:59 PM : [ZWAVE-TX ] [01040092147D] REQ ZW_GET_LAST_WORKING_ROUTE Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] - Node 22 - UnstableZ Thu 08/27/2020 04:07:59 PM : [ZW-SHOW ] Thu 08/27/2020 04:08:00 PM : [ZWAVE-TX ] [01070080140000FE92] REQ ZW_GET_ROUTING_INFO Thu 08/27/2020 04:08:00 PM : [ZWAVE-TX ] [01070080140100FF92] REQ ZW_GET_ROUTING_INFO Thu 08/27/2020 04:08:00 PM : [ZWAVE-TX ] [01070080140001EB86] REQ ZW_GET_ROUTING_INFO Thu 08/27/2020 04:08:00 PM : [ZW-SHOW ] Node 20 - Mudroom_Outlet has the following neighbors Thu 08/27/2020 04:08:00 PM : [ZW-SHOW ] No Neighbors Thu 08/27/2020 04:08:00 PM : [ZW-SHOW ] Thu 08/27/2020 04:08:00 PM : [ZW-SHOW ] Node 20 - Mudroom_Outlet does not support associations Thu 08/27/2020 04:08:00 PM : [ZW-SHOW ] Thu 08/27/2020 04:08:00 PM : [ZW-SHOW ] ---------------------------------------------- It is a (non plus) GE outlet. Notice how it has no neighbors, but had to go through another node to get to it??? So I did the synchronize and it disappeared and didn't get added back. This is what the event viewer showed for that: Thu 08/27/2020 04:08:21 PM : [ZWAVE-NODE-SYNC] [DS1] sync [ZW020_1] request Thu 08/27/2020 04:08:21 PM : [ZWAVE-TX ] [01030002FE] REQ SERIAL_API_GET_INIT_DATA Thu 08/27/2020 04:08:21 PM : [ZWAVE-NODE-SYNC] ---- Start Processing Z-Wave Node 20 (0x14) ---- QT1 Thu 08/27/2020 04:08:21 PM : [0046 15] Statement 1, line in 'Then' reset for node [ZW020_1] Thu 08/27/2020 04:08:21 PM : [0045 15] Statement 1, line in 'Then' reset for node [ZW020_1] Thu 08/27/2020 04:08:21 PM : All program references removed for node [ZW020_1] Mudroom_Outlet Thu 08/27/2020 04:08:21 PM : [ZWAVE-NODE-SYNC] Z-Wave node 1 (0x14) does not exist, removed 20 associated ISY node(s) Thu 08/27/2020 04:08:21 PM : [ZWAVE-TX ] [01030056AA] REQ ZW_GET_SUC_NODE_ID Thu 08/27/2020 04:08:21 PM : [UZW-CMD 45 ERR ] Get NodeDef : ZW020_1 Thu 08/27/2020 04:08:22 PM : [ZWAVE-TX ] [01030020DC] REQ MEMORY_GET_ID Thu 08/27/2020 04:08:22 PM : [ZWAVE-TX ] [01030056AA] REQ ZW_GET_SUC_NODE_ID Thu 08/27/2020 04:08:22 PM : [ZWAVE-TX ] [01030002FE] REQ SERIAL_API_GET_INIT_DATA Thu 08/27/2020 04:08:22 PM : [ZWAVE-TX ] [01030005F9] REQ ZW_GET_CONTROLLER_CAPABILITIES Thu 08/27/2020 04:08:22 PM : [ZWAVE-NODE-SYNC] -- Finished -- ISY/Z-Wave Node Sync -- So now it is just gone. So I went and hit the button on the outlet after it was no longer in the ISY and got this: Thu 08/27/2020 04:25:51 PM : [ZWAVE-TX-NR ] [0105004A85FECB] REQ ZW_ADD_NODE_TO_NETWORK Thu 08/27/2020 04:25:51 PM : [ZWAVE-TX-NR ] [0105004B05FF4B] REQ ZW_REMOVE_NODE_FROM_NETWORK FUNCID=5 STATUS=255 UID=75 Thu 08/27/2020 04:25:51 PM : [ZWAVE-TX-NR ] [0105004D05EB59] REQ ZW_CONTROLLER_CHANGE Thu 08/27/2020 04:25:51 PM : [ZWAVE-TX-NR ] [0105005000EC46] REQ ZW_SET_LEARN_MODE Thu 08/27/2020 04:25:51 PM : [ZWAVE-TX ] [01030020DC] REQ MEMORY_GET_ID Thu 08/27/2020 04:25:51 PM : [ZWAVE-RX ] CAN Thu 08/27/2020 04:25:51 PM : [ZWAVE-WAIT ] Waiting 5 ticks for retry 1 of 3 Thu 08/27/2020 04:25:52 PM : [ZWAVE-TX ] [01030020DC] REQ MEMORY_GET_ID Thu 08/27/2020 04:25:52 PM : [ZWAVE-TX ] [01030056AA] REQ ZW_GET_SUC_NODE_ID Thu 08/27/2020 04:25:52 PM : [ZWAVE-TX ] [01030002FE] REQ SERIAL_API_GET_INIT_DATA Thu 08/27/2020 04:25:52 PM : [ZWAVE-TX ] [01030005F9] REQ ZW_GET_CONTROLLER_CAPABILITIES Thu 08/27/2020 04:25:52 PM : [ZWAVE-TX ] [01030020DC] REQ MEMORY_GET_ID Thu 08/27/2020 04:25:52 PM : [ZWAVE-TX ] [01030056AA] REQ ZW_GET_SUC_NODE_ID Thu 08/27/2020 04:25:53 PM : [ZWAVE-TX ] [01030002FE] REQ SERIAL_API_GET_INIT_DATA Thu 08/27/2020 04:25:53 PM : [ZWAVE-TX ] [01030005F9] REQ ZW_GET_CONTROLLER_CAPABILITIES Still not in the ISY though. Anybody else have their zwave nodes just disappear when doing a synchronize on them? Edited August 27, 2020 by danbutter adding info
thruster999 Posted August 27, 2020 Posted August 27, 2020 (edited) Has anyone else run into any of these? When I installed 5.2.0(RC3) a number of problems arose making my ISY dead in the water: 1) Alexa can no longer communicate with my portal "The hub that device ... is connected to is not responding". 2) Polyglot no longer sees my ISY " Requested ISY not online" 3) Almost all of my Motion Controlled Responders (not the motion sensor but the device being controlled) are in a "1011" state. And its continuously writing to these devices and failing - putting my ISY into a constant busy state. 4) I receive several errors after a few hours "can't communicate with devices" BUT, As soon as I go back to 5.0.16 - everything is good again. I've installed 5.2.0 three times now - with the same results. Have had to back an reload 5.0.16 each time. Thanks Edited August 28, 2020 by thruster999
gviliunas Posted August 27, 2020 Posted August 27, 2020 @TexMike @hart2hart Here are the instructions we followed when beta testing the 500 dongle (I suspect any FW 5.0.13+ will work): Note backup of the 300 board is very slow (40 min- 1 hr) and may fail and need to be repeated. You must be running 5.0.13 You must backup your Z-Wave dongle (Z-Wave | Tools | Backup) … this is going to take a LONG time so, if you decide to go for this beta, it's best to backup now Disable query at restart Replace the dongle Restore your Z-Wave dongle by doing Z-Wave | Tools | Restore … this is going to be pretty fast Test communications, Heal the network, backup, and range (should be a little better) 3 1
io_guy Posted August 27, 2020 Posted August 27, 2020 5 hours ago, hart2hart said: This is way in the weeds about zwave plus but my Schlage BE469 deadbolts are version prior to the BE469ZP versions. Any issues with them on 500 series board? Any reason to consider replacing them? They are the only two Zwave devices I need to have stay near 100% reliable. I had two 469s that we're bulletproof with my old 300. I had a GE plug-in outlet next to each for beaming. It was almost 100% reliable. Once I switched to the 500 they were unusable. I then purchased 4 ZW+ range extenders to replace the plug-ins which made everything but the locks ZW+. At that point they were about 80% reliable. I've since moved and my new locks are the 469ZP. These work much better with the 500. 1
astar Posted August 27, 2020 Posted August 27, 2020 (edited) 27 minutes ago, io_guy said: I had two 469s that we're bulletproof with my old 300. I had a GE plug-in outlet next to each for beaming. It was almost 100% reliable. Once I switched to the 500 they were unusable. I then purchased 4 ZW+ range extenders to replace the plug-ins which made everything but the locks ZW+. At that point they were about 80% reliable. I've since moved and my new locks are the 469ZP. These work much better with the 500. I've just upgrade my 300 z-wave board to a 500. I only have 2 Schlage BE469NX locks but I'm unable to add them... I did place an Aeotec Range Extender 7 (ZW189) very close to the ISY and this one added without any problem to the ISY.. I'm running 5.2.0 (I upgrade from 5.1.0 and i'm not experiencing any of the issues that @thruster999 is experiencing - Polyglot is working fine) Both my locks are ~ 20 feet from the ISY/Range Extender. Any suggestions? Are they too far away? Locks too old? (I assume they are not ZW+ , but they worked with my 300 board) Edited August 27, 2020 by AStarink
blueman2 Posted August 27, 2020 Posted August 27, 2020 4 minutes ago, AStarink said: I've just upgrade my 300 z-wave board to a 500. I only have 2 Schlage BE469NX locks but I'm unable to add them... I did place an Aeotec Range Extender 7 (ZW189) very close to the ISY and this one added without any problem to the IS.. Both my locks are ~ 20 feet from the ISY/Range Extender. Any suggestions? Are they too far away? Is your ISY on it's side as recommenced? For some reason, laying flat give no signal to me, but on it's side works great.
blueman2 Posted August 27, 2020 Posted August 27, 2020 2 hours ago, danbutter said: Well I was a bit leary of the synchronize because the last time I tried I never got the node back, but I have a backup so I tried again, but now with 5.2.0. ....... So now it is just gone. Thu 08/27/2020 04:25:51 PM : [ZWAVE-TX-NR ] [0105004A85FECB] REQ ZW_ADD_NODE_TO_NETWORK Thu 08/27/2020 04:25:51 PM : [ZWAVE-TX-NR ] [0105004B05FF4B] REQ ZW_REMOVE_NODE_FROM_NETWORK FUNCID=5 STATUS=255 UID=75 Thu 08/27/2020 04:25:51 PM : [ZWAVE-TX-NR ] [0105004D05EB59] REQ ZW_CONTROLLER_CHANGE Thu 08/27/2020 04:25:51 PM : [ZWAVE-TX-NR ] [0105005000EC46] REQ ZW_SET_LEARN_MODE Thu 08/27/2020 04:25:51 PM : [ZWAVE-TX ] [01030020DC] REQ MEMORY_GET_ID Thu 08/27/2020 04:25:51 PM : [ZWAVE-RX ] CAN Thu 08/27/2020 04:25:51 PM : [ZWAVE-WAIT ] Waiting 5 ticks for retry 1 of 3 Thu 08/27/2020 04:25:52 PM : [ZWAVE-TX ] [01030020DC] REQ MEMORY_GET_ID Thu 08/27/2020 04:25:52 PM : [ZWAVE-TX ] [01030056AA] REQ ZW_GET_SUC_NODE_ID Thu 08/27/2020 04:25:52 PM : [ZWAVE-TX ] [01030002FE] REQ SERIAL_API_GET_INIT_DATA Thu 08/27/2020 04:25:52 PM : [ZWAVE-TX ] [01030005F9] REQ ZW_GET_CONTROLLER_CAPABILITIES Thu 08/27/2020 04:25:52 PM : [ZWAVE-TX ] [01030020DC] REQ MEMORY_GET_ID Thu 08/27/2020 04:25:52 PM : [ZWAVE-TX ] [01030056AA] REQ ZW_GET_SUC_NODE_ID Thu 08/27/2020 04:25:53 PM : [ZWAVE-TX ] [01030002FE] REQ SERIAL_API_GET_INIT_DATA Thu 08/27/2020 04:25:53 PM : [ZWAVE-TX ] [01030005F9] REQ ZW_GET_CONTROLLER_CAPABILITIES Still not in the ISY though. Anybody else have their zwave nodes just disappear when doing a synchronize on them? I did not have this happen with any of my 30 or so z-wave devices I did a synchronize on. What brand is that device?
beninsteon Posted August 27, 2020 Posted August 27, 2020 I do not have a zwave board or zwave devices. I am currently running 5.0.16C. Is my ISY compatible with this firmware? Is there any advantage to me updating? I see there are also some Insteon updates in 5.1 and 5.2 Thanks
astar Posted August 28, 2020 Posted August 28, 2020 57 minutes ago, blueman2 said: Is your ISY on it's side as recommenced? For some reason, laying flat give no signal to me, but on it's side works great. It's actually hanging on the wall - but the Z-wave ranger extender is like 1ft away from it - i was hoping this would solve have connectivity issues...
astar Posted August 28, 2020 Posted August 28, 2020 48 minutes ago, beninsteon said: I do not have a zwave board or zwave devices. I am currently running 5.0.16C. Is my ISY compatible with this firmware? Is there any advantage to me updating? I see there are also some Insteon updates in 5.1 and 5.2 Thanks you should 5.0.16C is RC1 (Release Candidate 1) and instead of 5.0.17 and 5.0.18 it seems they named it 5.1.0 and 5.2.0
lilyoyo1 Posted August 28, 2020 Posted August 28, 2020 1 hour ago, beninsteon said: I do not have a zwave board or zwave devices. I am currently running 5.0.16C. Is my ISY compatible with this firmware? Is there any advantage to me updating? I see there are also some Insteon updates in 5.1 and 5.2 Thanks It's only advantageous if you need what it offers. Outside of that you have nothing to gain by upgrading
lilyoyo1 Posted August 28, 2020 Posted August 28, 2020 1 hour ago, AStarink said: I've just upgrade my 300 z-wave board to a 500. I only have 2 Schlage BE469NX locks but I'm unable to add them... I did place an Aeotec Range Extender 7 (ZW189) very close to the ISY and this one added without any problem to the ISY.. I'm running 5.2.0 (I upgrade from 5.1.0 and i'm not experiencing any of the issues that @thruster999 is experiencing - Polyglot is working fine) Both my locks are ~ 20 feet from the ISY/Range Extender. Any suggestions? Are they too far away? Locks too old? (I assume they are not ZW+ , but they worked with my 300 board) Your locks are not zwave plus so they don't have any of the benefits of plus which means they need to be close to the isy in order to add
danbutter Posted August 28, 2020 Posted August 28, 2020 1 hour ago, blueman2 said: I did not have this happen with any of my 30 or so z-wave devices I did a synchronize on. What brand is that device? GE/jasco outlet. Not a plus model. I don't really use it much outside of winter so I picked it to try this on. I just tried on a zwave plus switch that I don't have installed yet...just on a pigtail and wirenuts and the sync worked ok. Added a new node that has zero controls though...strange. I hope to have a bit of time this weekend to mess around and will try on some non-plus devices to see if they all disappear like last time I tried to sync.
asbril Posted August 28, 2020 Posted August 28, 2020 15 minutes ago, danbutter said: Added a new node that has zero controls though I have a ton of these and I moved them to a folders that I named "phantom nodes"
io_guy Posted August 28, 2020 Posted August 28, 2020 3 hours ago, lilyoyo1 said: Your locks are not zwave plus so they don't have any of the benefits of plus which means they need to be close to the isy in order to add There's no benefit of plus with the ISY anyway. Every one of my devices are plus and they had to be within a couple feet to pair. Pretty sure NWI doesn't work.
lilyoyo1 Posted August 28, 2020 Posted August 28, 2020 5 hours ago, io_guy said: There's no benefit of plus with the ISY anyway. Every one of my devices are plus and they had to be within a couple feet to pair. Pretty sure NWI doesn't work. Was it turned on
cactus Posted August 28, 2020 Posted August 28, 2020 1. So how about someone actually ANSWERING the question "how do I find out what zwave module I have?"? Someone asked and rather than saying how to find out the reply was that THAT PERSON'S Zwave is 300. So now I have to ask also, how do I check? (HINT: MAYBE PUT THIS IN THE UPGRADE INSTRUCTIONS SINCE THIS IS APPARENTLY IMPORTANT!) Mine says "Z-Wave: 21100" in the about box. 2. If I have a 300 module, does this mean upgrading to RC3 will render my Zwave devices inoperable? After waiting YEARS FOR A FINAL 5.0 RELEASE?? Ugh. 3. If I have a 300 module, does this mean I am limited to running RC2 until I upgrade Zwave dongle and live with the Elk bugs in that version? 4. If I upgrade to the 500 module and RC3, will my existing Zwave devices still work (many of which I assume to be 300 since I've had many for over 3 years)? I am thankful that after YEARS OF WAITING a final version 5 release is on the horizon, assuming of course that the release candidate stage doesn't also go on for several years also...
hart2hart Posted August 28, 2020 Posted August 28, 2020 1. So how about someone actually ANSWERING the question "how do I find out what zwave module I have?"? Someone asked and rather than saying how to find out the reply was that THAT PERSON'S Zwave is 300. So now I have to ask also, how do I check? (HINT: MAYBE PUT THIS IN THE UPGRADE INSTRUCTIONS SINCE THIS IS APPARENTLY IMPORTANT!) Mine says "Z-Wave: 21100" in the about box. 2. If I have a 300 module, does this mean upgrading to RC3 will render my Zwave devices inoperable? After waiting YEARS FOR A FINAL 5.0 RELEASE?? Ugh. 3. If I have a 300 module, does this mean I am limited to running RC2 until I upgrade Zwave dongle and live with the Elk bugs in that version? 4. If I upgrade to the 500 module and RC3, will my existing Zwave devices still work (many of which I assume to be 300 since I've had many for over 3 years)? I am thankful that after YEARS OF WAITING a final version 5 release is on the horizon, assuming of course that the release candidate stage doesn't also go on for several years also... 1. 300 series Zwave board has a blue led on back of case. You can also look at AC under zwave and their is a number that tells you. 2. You should stay with 5.0.16 rc1 until you upgrade board to 500 series3. See above, 5.1 RC2 and 5.2 RC3 are not recommend with 300 series board. Many people had terrible migration issues issues from 5.0.x versions. 4. You should upgrade to 500 series board before you move to 5.1 or 5.2
Recommended Posts