blueman2

@gregkinney, this is a VERY good point. I have moved mostly to Energizer Lithium AA batteries and was wondering why most of those devices continue to show 100% after so long. More research shows you are generally correct, in that the ramp down is very slow in voltage during first part of life, then rapid at end of life. Thanks for pointing this out.

I am currently running insteon/z-wave on an ISY994i with Nodeserver V2 running on a Raspberry Pi. I see that the Nodeserver forums have been split into V1, V2 and V3. I see no place on those forms to ask general questions (only questions related to a specific Nodeserver) so will ask here. What is the difference between the versions?

Either Jandy or Pentair will work fine. I have experience with Pentair and use Home Assistant plug in that controls that. It works great. Other thoughts: 1. Pentair is overall a better product than Jandy (my personal view) and is more widely installed. I think Pentair is a bit more expensive though(?) 2. Home Assistant is the way to go for any ISY user going forward . The Home Assistant platform is exploding in popularity. And the good news is that Home Assistant integrates into ISY extremely well. Long story short, you will need to go to Home Assistant at some time, so might as well do it now. You will never look back in terms of user interface.

Not sure this is something added in this build, but I have noticed I am now able to query battery status on pretty much all of my devices that are wireless and rely on 'query when awake'. In the past, battery percentage on all of my monoprice z-wave door sensors would not populate. Now it does. I just have to do nightly queries to get the data, but that is a simple program.

Yup, that fixed it for my Schlage locks, but not for a couple other devices that are wired/always on. For example, an Intermatic pool controller.

Upgraded from 5.3.2 to 5.3.3 no issues. I continue to have the Green "1011" tags on a few of my items, but understand that issue is still an open item.

@Chris Jahn, Thanks for the latest test release. This resolved the "Green Tag" on my locks, but the Green Tag remains on a couple of my devices. I tried to do a forced write and repair links, but still nothing seems to get rid of the Green Tag. Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] ---------------------------------------------- Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] Need to write the following for [ZW044_1] - ZW 044.01 Chlorinator Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] ---------------------------------------------- Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] Need to write the following for [ZW044_003_1] - ZW 044.03 Oscar Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] - Control Links Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] ---------------------------------------------- Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] ZW 044 Heat=Pool Cool=Spa Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] ZW044_140 uid=44 security=None type=4.16.1 mid=5 tid=20549 pid=1619 Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] ZW044_1 - Primary Isy Node Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] - x20 V1 BASIC Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] - x91 V1 MANUFACTURER_PROPRIETARY Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] - x73 V1 POWERLEVEL Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] - x72 V1 MANUFACTURER_SPECIFIC Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] - x86 V1 VERSION Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] - x81 V1 CLOCK Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] - x60 V2 MULTI_CHANNEL Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] - x70 V1 CONFIGURATION Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] - x85 V1 ASSOCIATION Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] - x25 V1 SWITCH_BINARY Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] - x27 V1 SWITCH_ALL Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] - x43 V1 THERMOSTAT_SETPOINT Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] - x31 V1 SENSOR_MULTILEVEL Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] - x30 V1 SENSOR_BINARY Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] - xEF V0 MARK Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] - Secure Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] Wed 01/27/2021 03:59:13 PM : [ZW-SHOW ] ----------------------------------------------

Did you try updating the association with the ISY by doing Z-wave | Repair Links? I had to do that with several older z-wave devices I had.

@Chris Jahn, I installed without issue. However, my devices that had the "GREEN 1011" label continue to have this label even after forcing writes. Example here is a Schlage BE469. It still thinks it has associations that are not written. Same with 2 other z-wave devices I have, not all of them locks. Events log attached. events.txt

I am having problems doing an Insteon Replace for an 8 button keypad. I added the replacement keypad, put both the replacement and the original in the root folder, then selected on the orginal "Replace with" and selected the replacement. All seems to go well (it does the writes and deletes each of the 8 keys on the replacement device, and then stops. I then close the window and open it again, but the old device with the old device Insteon 6 digit code is still there. And the new device is completely gone. So I tried again, starting by adding the new device. Since it does allow it to be added, that proves that it was removed, so that shows something definitely failed. And when I try to do the replacement again, same thing happens as above. Anyone else tried to do a device replacement, particularly with a KPL, using 5.3.0?? EDIT: Finally today after doing another system reboot, the replacement process for the KPL worked. Not sure why it failed numerous times yesterday, but all is well.

If you are seeing flickering in your bulbs, it is due to them being either not dimmable or very cheap. I had this same experience with super cheap bulbs. Switched over to better dimmables, and all flickering went away.

For me, shows up on all of my 2476D dimmers. Nothing else. It is merely cosmetic though and does not impact usability in any way.

Yup, I am seeing this too.

Yes, this can be confusing. Typically, we use threads like this to ask questions to see if issues we are having have solutions, or if they might be true bugs. If we strongly suspect there is a bug based on other people reporting the same issue, one (or more) of us will open a ticket with UDI so that they can log the bug. https://www.universal-devices.com/my-tickets

If you have only minimal z-wave devices and do not plan to buy any more devices in the near term, you definitely could stay on 4.x for a while. Only things you will lose are Polyglot and some new features and device support. But what you have now should continue to work just fine. But if you have any z-wave, or if you want to start looking a broader device support and Polyglot, I would upgrade to 5.0.16C and get that stable. 5.0.16C will at least get you to 5.x, but will avoid the need to upgrade your z-wave module (if you have one). This upgrade will probably require you to adjust some programs and maybe re-discover some devices, so set aside an hour or so to get everything working just right after the upgrade. Then the later upgrade to 5.3 and above will be pretty much trivial assuming you have the new 500 series z-wave dongle.

Correct. That is a 300 series board. Need to upgrade.

Try doing z-wave | update links. It might have a bad association, which will cause the lock not to send data to the ISY by itself. But Query will still work.

Thanks @Chris Jahn and @Michel Kohanim for updating the guides too. I had not noticed these until now.

Congratulations on z-wave certification and on 5.x Official Release.

@shbatm, I talked to @Michel Kohanim and this behavior is actually intentional. Since a device can only be controller for 1 scene, ISY does go ahead and change the device's parameters for Ramp Rate and On Level to be whatever that scene is. So not a bug, but more the way ISY handles the controller for a scene. I tried to come up with a plausible scenario where this might cause issues and could not.

@shbatm, yes, I confirm what you are seeing. Adding a device as a CONTROLLER to a scene does indeed appear to reset the device to 100% On Level and 0.1 sec ramp rate. Nice find!!! I missed this because I had been adding devices to scenes only as RESPONDER, and that does not appear to trigger this bug. @Chris Jahn, can you log this bug? And while we have @shbatm here, I want to add a note of recognition and thanks for everything he has been doing to better integrate the ISY with the Home Assistant project. I am using Home Assistant as my main user interface to the ISY, and it is just fantastic. @shbatm has been one of the leaders in creating the links between the ISY and Home Assistant. Bravo, sir!

@Craigb, I am seeing the same issue with all of my Schlage locks. They worked fine at first, then started having this issue. @Chris Jahn and @Michel Kohanim are aware of this. Fri 10/02/2020 01:34:09 PM : [ZW-SHOW ] ---------------------------------------------- Fri 10/02/2020 01:34:15 PM : [ZW-TX-FAILED] enc=Ok uid=46.0 cmd=0x85.05 ASSOCIATION Fri 10/02/2020 01:34:22 PM : [ZW-TX-FAILED] enc=Ok uid=46.0 cmd=0x85.05 ASSOCIATION Fri 10/02/2020 01:34:30 PM : [ZW-TX-FAILED] enc=Ok uid=46.0 cmd=0x85.05 ASSOCIATION Fri 10/02/2020 01:34:30 PM : [ZW-SHOW ] Node 46 - ZW 046 Den Door to Garage cannot retrieve association groups Fri 10/02/2020 01:34:30 PM : [ZW-SHOW ] Fri 10/02/2020 01:34:30 PM : [ZW-SHOW ] ----------------------------------------------

One of the issues I found after moving to 5.2.0 was that several of my devices lost their "association" with my ISY. While they sort of still worked, they were unreliable. To solve this: Right click the z-wave device in the Admin Console select Zwave => Repair Links

Congratulations Chris and Michel!!!! Long road from 5.0 alpha to today, and much more work than anyone thought. ???

Agreed.