blueman2

Thanks, @shbatm. And thanks for all the work you do and the leadership you have shown in this area. It does make things easier in a way to not store "native" scene info on the devices. Ensuring that the native records and the local HA records stay in sync can be an issue. And I can always edit the ALDB or using the UI or doing service calls in HA to write the links directly to the devices. The issue really comes up though where I have 3-way switches and I want the switches to control each other. Or where I have an "all outside devices" scene that I want controller by a switch.

@vbPhil, glad you posted this. I am seeing the exact same thing. HA does not create a scene the same way as ISY does. It appears the ISY creates native Insteon links between all the devices in a scene, so that even if the PLM is removed, the devices still talk to each other. HA on the other hand just creates a link between the devices in the scene to the PLM, and gives it a group # for use in HA. So if the PLM is disconnected for any reason, the scenes no longer work. I like the way ISY does it much more, since I want my house to still work when the PLM is dead for some reason. Maybe we can ask the Insteon plug-in leader in HA to add the creation of native links in the Insteon devices when HA creates scenes.

I also agree with MrBill. I have had some powerline noise that caused even dual band switches to become completely non-communicative. There is defintely something going on where powerline noise kills the ability to use RF.

@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.

Great comments and help by everyone here. This is what is so unique about this ISY community. People are willing to help others, we have experts here who can go as deep as you need in order to really understand something, all while not being demeaning or dismissive of anyone asking basic questions. But I still want to get back to the OP's original point. We should have a Pinned post, always kept as the very top post in this subforum, that is titled something like "Current firmware". That post should list the most recent firmware that we suggest people use (e.g. 5.3.4), along with the pros and cons of other potential firmware options. It should be a closed post without discussion.

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.