I noticed this too and finally realized that unlike before the upgrade I could simply change the temp but now I have to change the temp then hit the associated button. I may be wrong but I don't remember having to do that before the upgrade...

Ex. change temp then hit "cool setpoint"

Try this

Edited August 12, 20205 yr by drprm1

1 hour ago, drprm1 said:

I noticed this too and finally realized that unlike before the upgrade I could simply change the temp but now I have to change the temp then hit the associated button. I may be wrong but I don't remember having to do that before the upgrade...

Ex. change temp then hit "cool setpoint"

Try this

From the release announcement (first post of this thread):

Quote

-      New – Some changes to the Admin Console

o   You now have to press the button when issuing a command for a node on the device page (rather than just change a parameter for the command to automatically be submitted)

 

Missed that

I just upgraded from 5.0.16C to 5.1.0.  I did a synchronize on just 1 z-wave device, and it moved it into the root the folder and renamed it to default name.  It was not in any scenes, but was in a few programs.  It remained in those programs just fine.  So all I had to do was just fix the name.  No biggie.  

I also noticed the 2 programs were in yellow, indicating an issue.  Easy to find my doing an 'expand all' in programs view.  Both programs turned out to be phantoms that were not there before the upgrade.  I think they were very old programs I had deleted long ago that for some reason showed up again.  I just deleted them.  

More to come as I find it.  Thanks Chris for the continued development!!!!

EDIT:  As a follow up, I decided to do a synchronize on my z-wave pool controller.  Unfortunately, most of the nodes went away and did not come back after the synchronize.  I physically turned on/off some of the pool switches to see if that might cause them to be discovered, but no joy.  Any ideas on how to retrieve the missing nodes?   

EDIT 2: Well, things are not going well for me.  I could not get my pool controller to work at all under 5.1.0.  I went back to 5.0.16C, and did a restore from just before the upgrade, but still my z-wave pool controller was messed up.  So I tried to do a z-wave restore (I had done a backup of z-wave before I did the ISY backup before the upgrade) but I get an error message that z-wave cannot be restored.  My pool controller is still non-operational.  

 

.  

 

Bob

 

Edited August 12, 20205 yr by blueman2

I could not restore my z-wave dongle and could not talk to any z-wave devices.  Finally, I looked in Task Manager in Windows, and found that I had several java sessions running in background processes. Once I cleared those out, I was finally able to do a restore to my z-wave dongle.  I have never had this happen before, so I suggest anyone having odd problems restoring backups to ISY or zwave to check for extra java processes running.  

Even with that cleared up, only about 1 in 10 attempts to restore the z-wave backup will work.  The other 9 times I get "Cannot enter programming mode".  This is with the 300 series dongle.  

I ended up having to revert back to 5.0.16C in order to get my system somewhat stable from a z-wave perspective.   I plan to stay there until I have an entire weekend to devote to this.

EDIT: I am still having massive problems with z-wave system stability after attempting this upgrade, even after reverting back to 5.0.16C.  My system has been rock solid for over a year before this.  Big mistake trying out this new software.  I have also learned that backups are not to be relied upon.  Even with regular backups of the ISY and the z-wave dongle, being able to restore to that state I had before attempting to upgrade has failed.  My system just does not work well any more.  Only about 1/3 of my z-wave devices are communicating well.  Other 2/3 give me incessant "communication failure" messages.  So many that it is impossible to type anything on the ISY because I am constantly being interrupted by the pop ups that prevent typing.  

Really, really wish I had not done this 5.1.0 upgrade attempt.  

Edited August 14, 20205 yr by blueman2

I have two ISY-994i PRO units. I migrated the z-wave devices that would not function on a ISY-994i Pro unit with firmware version 5.1.0 to my second ISY-994i Pro unit running version 5.0.15A. The migrated z-wave devices now seem to be functioning.

I have one exception. I received a new z-wave ZooZ outdoor motion sensor, ZSE29 version 2.0, which does function from either of the firmware versions mentioned above but I can not set any z-wave configuration parameters.

Wed 08/12/2020 19:06:07 : [UZW-CMD 51      ] [ZWCMD cmd.51]
Wed 08/12/2020 19:06:16 : [UZW-CMD 51      ] [ZWCMD cmd.51]
Wed 08/12/2020 19:06:24 : [ZWAVE-TE        ] [70/05] CC=0x70 cmd=0x05 [05] ACK,AUTO,EXPLORE To=0x10
Wed 08/12/2020 19:06:24 : [ZWAVE-TX ZW016_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE To=0x10
Wed 08/12/2020 19:06:28 : [ZW-TX-FAILED] enc=Fail uid=16.0 cmd=0x70.05 CONFIGURATION
Wed 08/12/2020 19:06:28 : [ZWAVE-TX-E      ] ZWAVE-WAIT Waiting for retry 1 of 2
Wed 08/12/2020 19:06:29 : [ZWAVE-TE        ] [70/05] CC=0x70 cmd=0x05 [05] ACK,AUTO,EXPLORE To=0x10
Wed 08/12/2020 19:06:29 : [ZWAVE-TX ZW016_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE To=0x10
Wed 08/12/2020 19:06:29 : [ZWAVE-RX-ST     ] No Device Ack
Wed 08/12/2020 19:06:29 : [D2D EVENT   ] Event [ZW016_1] [ERR] [1] uom=0 prec=-1
Wed 08/12/2020 19:06:29 : [     ZW016_1]      ERR   1
Wed 08/12/2020 19:06:29 : [ZW-TX-FAILED] enc=Fail uid=16.0 cmd=0x70.05 CONFIGURATION
Wed 08/12/2020 19:06:29 : [ZWAVE-TX-E      ] ZWAVE-WAIT Waiting for retry 2 of 2
Wed 08/12/2020 19:06:30 : [ZWAVE-TE        ] [70/05] CC=0x70 cmd=0x05 [05] ACK,AUTO,EXPLORE To=0x10
Wed 08/12/2020 19:06:30 : [ZWAVE-TX ZW016_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE To=0x10
Wed 08/12/2020 19:06:34 : [ZWAVE-RX-ST     ] No Device Ack
Wed 08/12/2020 19:06:34 : [ZW-TX-FAILED] enc=Fail uid=16.0 cmd=0x70.05 CONFIGURATION
Wed 08/12/2020 19:06:34 : [UZW-CMD 28 ERR  ] Query Config : ZW016_118 param 5

Final update for this totally wasted day:  none of my z-wave devices are functioning now, even after returning to 5.0.16C after doing restore.  Something in this update total screwed my z-wave dongle.  It no longer accepts communications of any type.  It will not do z-wave restore, will not do z-wave backup, will not talk to any z-wave devices.   Only thing it will do is factory reset for z-wave dongle. 

It was working perfectly before the update, and after the update is useless.   This is with the 300 series dongle.   Power down reboot does not help, tried 3 different PCs to make sure that was not the problem.  Cleared Java cache.  Nothing helps.  

And I gave one more attempt to use the 500 series dongle that never gave very good range so I stopped using.  It also is showing the same failure.  It will reset, but will not take any restore.  

My ISY is now a boat anchor.  

Edited August 13, 20205 yr by blueman2

Day 2 of my nightmare upgrade attempt.  What I am finding is that the z-wave restore process is broken.  Not sure when that happened, but I cannot do restore reliably.  And of course, step 1 of a restore is to wipe the existing records.  So every time I try to do a restore, I end up with either no z-wave items on my dongle.  I was able to go back to very old back up from February, and found one that does restore sometimes.  But so much has changed since then, it does not really help me.  This issue is with both the 500 series and 300 series dongle.  500 series works a bit better in being able to do a restore sometimes, but only with very old backups from 9 months ago.  Anything recent fails.  But the 500 series dongle is terrible and does not provide reliable communications, whereas the 300 has always been much better.  And I cannot get the 300 series do take ANY restores.  

So if the new 5.1.0 release requires that we rely on doing z-wave back ups and restores, I am not sure how to proceed.  

My system is now working in a crippled state with the 500 series dongle.  It only talks to about 70% of my devices, and even those are VERY unreliable with constant 'cannot communicate' messages.  Queries mostly give error messages of cannot communicate.  Sometimes they work.

 

I did miss the note about having to press the button after making the parameter change to cause transmission to the device. Thanks for pointing it out.

However, when starting the Admin console, the status for the 2441V thermostat adapter does not show actual status of the adapter until I click on one of the buttons (one of the Setpoints, Mode, Fan Mode).  Also, the parameter settings are not accurate as to current mode settings until I click on one of the buttons.  Clicking Query doesn't seem to update device status in the UI.

 

I was lucky enough that I was able to restore 5.0.16 after experiencing serious Zwave issues with 5.1.0 . I believe that UDI is working on an update. 

I have the system working on 5.1.0 but very poorly.

• Every secure device had to be brought within 3' of the ISY.  In comparison Homeseer required zero moving around (50' and a wall were no problem).
• 2 LS100 leak sensors just give "1010", other 2 work fine.
• Communication is crazy slow.  I have a Z-Wave wall switch that triggers a Z-Wave plug-in switch (programs, not association).  After hitting the wall switch it takes about 6-8 seconds for the plug-in to turn on, in Homeseer this is about 0.5 seconds.

Remind me to never buy a Z-Wave device.

 

UPDATE:

Well, I am mostly back in business again.  There were a couple issues I had to overcome:

1) Z-wave backups saved on 5.0.16B and 5.0.16C were not able to be used for 300 series dongles due to a bug in the code.  And since the first thing the ISY does in a restore is to delete the existing config, before it tried and failed to restore, I was left with no network at all.  And no backup to restore from.  Well, not if I wanted to continue to use my 300 dongle.  Good news is that the restore did work on a spare 500 series dongle I had, since the bug only impacts 300 series restores.  If you are still using a 300 series dongle, and want to stay on it, DO NOT RELY ON YOUR Z-Wave BACKUP!!!!!!  Either move to the 500 series dongle (which is what I did), or make damn sure you do not reset or try to recover your z-wave dongle backup saved from B and C of 5.0.16.  

2) The second issue was just getting everything to work well with the 500 series dongle.  This required 3 steps:

1. I had to re-sync each device, one by one.  (use the synchronize command by left clicking each device).  For many of them, I had to move them within 3 feet of the ISY to make it work.  A real PITA, but had to be done.  I recommend against anyone else doing this on 5.0.16C, but rather wait for 5.1.x release.  No need for you to do it twice, since I think doing these syncs will be needed for the new code due to lots of z-wave changes needed for for z-wave certification.  
2. I had to put the ISY on it's side.  Seriously, that made a HUGE difference in coverage.  Something about the antenna I guess.
3. I put a Gen 5 z-wave switch about 1 foot away from my ISY in order to ensure signals could be repeated by a strong device.  With those 3 things in place, I was able to get my system working almost as well as it was on the 300 series dongle.

Chris is working on a new drop of the code hopefully within the next week.  I am sitting on 5.0.16C for now.  Only bad news is that I am unable to make a backup of my 500 series dongle on my 5.0.16C setup.  Not sure if that is a bug or an issue with my hardware.  But without a backup of the z-wave network, moving to 5.1 will definitely be sphincter clinching.  

Big thanks for Chris for hand holding me through some of this!!

EDIT: After using my system with the new Series 500 dongle for the past several hours, it appears to be even more stable in terms of z-wave communications than ever.  Past attempts to use the 500 dongle left me with poor communications so I always went back to the 300.  But doing the 3 steps above solved it.  I am very happy now with the 500 series dongle.  This is good, since I think UDI might be dropping support for the 300 series dongle before long.  So if you have not upgraded your system to the 500, now might be the time.  

Edited August 14, 20205 yr by blueman2

2 hours ago, blueman2 said:

I am unable to make a backup of my 500 series dongle on my 5.0.16C setup.  Not sure if that is a bug or an issue with my hardware.  But without a backup of the z-wave network, moving to 5.1 will definitely be sphincter clinching.  

I have had the 500 dongle for a while, and I am still on 5.0.16,  and regularly perform a dongle backup without a problem. In fact the dongle backup is done in about a minute.

I may be missing something, but can you not make a backup to your computer, File, Backup ISY ?  I backup my ISY to my computer every time I change  a device or make a significant change in a program.

15 minutes ago, asbril said:

I have had the 500 dongle for a while, and I am still on 5.0.16,  and regularly perform a dongle backup without a problem. In fact the dongle backup is done in about a minute.

I may be missing something, but can you not make a backup to your computer, File, Backup ISY ?  I backup my ISY to my computer every time I change  a device or make a significant change in a program.

I can back up and restore the ISY just fine.  It is the z-wave dongle that I cannot backup.  It took over a dozen tries and I was finally able to make it do a backup, but I have not been able to replicate doing a backup for the last 10 times.  Here is what I get:

 

dongle backup attempt.txt

Edited August 14, 20205 yr by blueman2

9 minutes ago, blueman2 said:

I can back up and restore the ISY just fine.  It is the z-wave dongle that I cannot backup.  It took over a dozen tries and I was finally able to make it do a backup, but I have not been able to replicate doing a backup for the last 10 times.  Here is what I get:

 

dongle backup attempt.txt 11.78 kB · 1 download

I know that you are more expert than I am, but what is the difference between a dongle and ISY backup ? If my ISY would be damaged by my 4 year old grandson and, for argument sake the dongle survived, would there be a difference in restoring from the dongle or from the computer ?

1 hour ago, asbril said:

I know that you are more expert than I am, but what is the difference between a dongle and ISY backup ? If my ISY would be damaged by my 4 year old grandson and, for argument sake the dongle survived, would there be a difference in restoring from the dongle or from the computer ?

The dongle is what contains your z-wave network.  The dongle knows how to talk to each device and how to manage them.  The ISY says "Dongle, tell switch ZW022 to turn on".  The dongle takes care of all the details of how to communicate with it and do error checking, etc.  If your dongle dies for some reason, and you do not have a backup, you will have to go through the long process of re-including each device all over again. This will also require you to rebuild all the programs and scenes that reference use these devices since the reference IDs will probably have changed. 

So every once in a while, especially after I add alot of z-wave devices or change their configuration, I will tell the ISY to do a Z-Wave => Tools => Backup, which will make a copy of the z-wave network.  THEN, you also need to do a File => ISY Backup in order to save both the z-wave and ISY onto your PC.  The ISY backup file contains a copy of the z-wave dongle backup file.    

If, in your example, your dongle survives, then it really does not matter much.  But the dongle does not know the names you have given your devices.  So you would, at a minimum, need to rename everything again.   And no, I am no expert at all on this.  I just like to pretend I do to make me feel useful in retirement. 

Edited August 14, 20205 yr by blueman2

If we "old guys" stick together, we only need to remember how part of this system works  ?

8 hours ago, gviliunas said:

If we "old guys" stick together, we only need to remember how part of this system works  ?

You mean, we each remember something, so that collectively we know it all ? That goes directly against what my wife tells me, calling me a know-it-all who remembers nothing !

1 hour ago, asbril said:

You mean, we each remember something, so that collectively we know it all ? That goes directly against what my wife tells me, calling me a know-it-all who remembers nothing !

Maybe somebody will write a better NS to control spouses? I don't think the protocol quite matches.
When I Dim the lights, she wants to go "Out" and keeps disconnecting. Maybe the handshake isn't working?

Edited August 14, 20205 yr by larryllix

PSA for anyone still on 300 series dongle:

I know this is perhaps more of a 500 vs 300 series dongle topic than a 5.1.X topic, but I think the two topics are related for anyone still on Series 300 z-wave dongles/controllers.  I had tried multiple times in the past to move from the 300 controller to the 500 series controller, but each time it created a lot of problems in terms of communications with my z-wave devices, so each time I bravely retreated back to series 300.  But now, after following the steps I outlined above, I am FINALLY seeing much more reliable communications using the 500 series dongle than the 300.  Pretty much all my z-wave issues are gone now.  My theory is that doing a re-sync of each device is what helped the most.  From what I have read, all newer Gen 5 devices will go into legacy mode when they see a 300 series controller.  When moving to the 500 series controller in the ISY, the devices need to be re-sync'ed in order to realize they can now go into Gen 5 mode.  I had never done that before.  Also, if you have any older (non-zwave+) devices in the chain of communications from the ISY to an end device, everything in that chain has to revert back to legacy mode so you lose all the benefits of Gen 5.  So removing legacy z-wave devices as much as you can, especially if they are very close to the ISY, I think also helped me.  Finally, once you are mostly using Gen 5 devices in your mesh, you can take advantage of the automatic routing used in Gen 5.  Gen 5 remembers the last several successful routes used to get to a device.  It will always use the last one that worked first, then if that fails, go back to another prior path that worked and mark that new path as the primary one.  The result is much faster communications from ISY to end device.  And if the existing path fails (for example, you remove or change a repeating device in the path), the network will automatically 'heal' itself and update with the new working path.  I am not even sure if network heals are needed anymore, but I did one at first just in case.        

Bottom line is that I am MUCH happier now on the 500 series dongle than on the 300 series.  And since the path I took (lots of re-syncs) may be required anyway in the move to 5.1.X firmware, might as well make the move to 500 series dongle now if you have not already.  

 

Edited August 14, 20205 yr by blueman2
add link to prior post for clarity

When I first saw release notes for 5.1.0, I feel certain it said that toggle to external antenna had been re-enabled. Two questions:

1. Is that true since not finding that note now?

2. Does 500 series board have external antenna connector? My ISY is in an RF intense area so getting zwave antenna away is a must which I did with 300 series board. I also do this with an extension cord for PLM.

26 minutes ago, hart2hart said:

When I first saw release notes for 5.1.0, I feel certain it said that toggle to external antenna had been re-enabled. Two questions:

1. Is that true since not finding that note now?

2. Does 500 series board have external antenna connector? My ISY is in an RF intense area so getting zwave antenna away is a must which I did with 300 series board. I also do this with an extension cord for PLM.

The 500 series does not have the external antenna.  Only internal.  Frankly, for me anyway, the external antenna never worked as well as the internal on the old 300 series, but YMMV.  

When you do go to 500 series, I just recommend you put the ISY into a vertical orientation (not flat on the table, but rather on it's side with z-wave module at top).  For some reason, that helps a lot for the 500 series.  And place a Gen 5 device/repeater within about 5-10 feet of the ISY so that it can be used to relay the ISY signal better.  

As for comparisons with the 300 series, that is becoming a moot point quickly as support for the 300 series appears to be going away pretty soon.  I know it is a PITA to make the conversion, but I recommend doing it.  

Post deleted by author.

For Homeseer WD200+ Users,    ISY v5.1.0 creates a new "Basic" node if you synchronize this device. 

The Basic node and the Dimmer nodes appear to operate similarly but status back on the Basic node  does not update properly:

1. If you switch-On or Switch-Off this device from the local switch, The Admin Console status will not change. (1st problem)

2. If you switch-On or Switch-Off from the Admin Console, the Status will rise or fall but will not end-up at the correct value. i.e. Turn-On and expect to see 35% but instead see random values from 16-22% (Incorrect) If you query this node, the status value jumps to 35% (Correct). Turn-off and expect to see 0% but instead see 16-9% (Incorrect) Again, if you manually query the node, the status will be correct 0% (2nd problem)

I tried changing the "Automatically sends status update" setting but this did not fix status reporting for the Basic node of the WD200+

The Dimmer node seems to report status properly both when controlled locally and via the AC - I recommend that you use this node in your programs and scenes

Event viewer L3 data attached.

 

Basic Node Turn ZW072 On and Off from AC.txt

Edited August 15, 20205 yr by gviliunas