BONeil

@gzahar That worked!! Thank you

EISY 5.8.3, I recently reset my zwave network and dongle. Everything is back and good, locks respond fast and a heal takes under 2 minutes without any retries or comm problems in Event Viewer. Connection speed is good and nodes seem well placed. However, my two Schlage BE469ZP no longer notify the EISY when they are manually unlocked, so their state in the ISY never changes when it is manually unlocked. This did work prior to the reset, but I have no idea how to get it working again since for all intents and purposes, Zwave is working well and fast with little latency. I tried exclude\include, zwave compatability mode, heal the world, update neighbors, update with interview, detect button presses on\off. The locks both read as S2 access. Also, I did add a ULock zwave recently which shows up as S2 Access [S0] if the secure inclusion parameters matter in this instance. The ULock DOES notify the EISY when it is unlocked, so not a problem with the overall Zwave network as far as I can tell. One concerning thing is I see is that they show up as 'Interview Not done' and I have interviewed them numerous times. In X-Ray -> [DH All Devices]: Devices list: 1 Interview Not done --> assuming EISY radio since other devices 2 Interview done --> GE Enbrighten 3 Interview done --> GE Enbrighten 4 Interview done --> GE Enbrighten 5 Interview done --> ULock 6 Interview done --> GE Enbrighten 10 Interview Not done --> Schlage1 14 Interview Not done --> Schlage2 Lastly, the locks were paried next to the ISY and moved to their location after paring which was the conventional wisdom a few years back, not sure that is still the case. Let me know your thoughts on anything I've missed and any ideas to further troubleshoot.

It seems all of my programs have been disabled after upgrade. Kind of a surprise to see. Now I need to remember which ones were intentionally disabled.... Update: I enabled the ones I need, rebooted and they are all disabled again. Please advise.

Got to the bottom of this one while I was eating lunch, but figured I'd document if anyone else runs into it. Nothing to do with the PG3 module what so ever. Originally, I was using homebridge to access Elk through the ISYMaker add-in. When I migrated to the EISY, I had to change the service on Homebridge to the dedicated Elk add-in. Turned off homebridge and now it's working as expected. Something with the Elk module on Homebridge caused it to go awry. I migrated my HomeKit to Home Assistant and that seems to play much better with Elk along with the EISY.

Before I upgraded to EISY\PG3, I had an Elk automation that would wake my PC with Networking WOL when the Elk motion sensor was triggered in my office. I added the new WOL Polyglot and that seems to be working fine independent of the automation. After upgrading and adopting PG3, I noticed, 2 of my 3 motion sensors are no longer sending violated events. Anyone else see this?

Thank you. While not ideal, that should work for my use case!

I'd like to filter some devices and node servers from showing up in Home Assistant via the ISY integration module. Example, I'm using the Elk polyglot node on the ISY and the Elk integration module in HA, so I see two alarm panels. Probably a few other use cases too with other node servers. I see the integration allows a filter for a string, but only seems to honor one string and not multiple. Wildcard or specific node server would be great. Is this possible?

I found that pressing the pair button 3 times in quick succession adds the Aeotec Energy Meter to the EISY properly. One press added a single useless node.

Thanks Mr Bill, a reboot is fine. Not looking for full continuity of uptime. Just make my reference of the old system easier. Actually, to add to this, I'd like to find a way to keep the ISY around after step 4 in case I need to refer back to a program of variable.

Getting ready to flip the switch here. I have quite a few devices both insteon and zwave, along with a ton of Elk sensors and automation that is going to break. Ideally, I would like to have both systems online at the same time to compare the programs against each platform. My hopeful process is outlined below, but would like to understand caveats with the bridges (insteon PLM, Zwave, Elk etc) while they are in an 'offline' or disconnected state during comparison. This is based on the migration guide. 1. Assign unique IP addresses for EISY and ISY 2. Restore backup on EISY, keep PLM on ISY, do not attach zwave\matter radio to EISY yet 3. Do the compare, fix the programs and variables with two admin consoles 4. Decomission ISY 4.a Power down ISY 4.b attach PLM and Zwave radio to EISY 4.c Configure settings in EISY to begin using PLM and ZWAVE 4.d Remove ISY from portal

That's reassuring, thank you. I can deal with some temporary pain and can fix most problems, but lingering problems on critical systems (locks, alarm, etc) are a non-starter for the near term. I've had HA for 15ish years and my wife and I have grown to be somewhat uncomfortable without it. I am hearing a lot of Polisy to Eisy migrations, but I think those are far less impact from 994i -> Eisy since the architecture changes a bit. In particular, I am still trying to figure out how I will revisit my extensive library of Elk automations (it appears Elk moved to PG3) so I will have to touch each automation. Just time I didn't allocate for this weekend and probably explore a way to incrementally migrate instead of ripping a band-aid off. Possibly using Homeassistant as an abstraction to make the transition seamless.

To be honest, I got a bit gun-shy. I have a pretty complicated setup (~100 insteon devices, ~60 zwaves, ~60 Elk sensors and a bunch of Polyglot 3 nodes). Tons of programming that works very well. I've seen a bunch of posts about the reliability and getting door locks working and that has me worried.

I decided to roll back from a 994i to Eisy migration (not meeting WAF). I did not change anything on either system. I read in the users guide: In the migration I followed the procedure where I backed up the Z-Wave network before I did the ISY Backup. Then I used the ISY backup to restore on the EISY. Since some Z-Wave operations are one way, I want to make sure I understand this clearly as my action back on the 994i; Can I just use the Z-Wave -> Restore tool, or do I have to restore the entire ISY via File -> Restore ISY, File -> Restore Devices? Thank you