asbril Posted January 14, 2023 Posted January 14, 2023 2 hours ago, shbatm said: Turn on debug logging and reload the integration: Developer Tools > Services Logger: Set Logging Level YAML mode data: - homeassistant.components.isy994: debug pyisy: debug - 'C' key > Reload Universal Devices ISY994 If you do that and look at the actual log file (home-assistant.log in your config directory) that should tell you the node it's trying to load and is having problems with right before the error. Post that info as an issue on github. This is as far as I got :
Mecheng70 Posted January 14, 2023 Author Posted January 14, 2023 17 minutes ago, asbril said: This is as far as I got : Now I believe you go to the integration and reload it.
shbatm Posted January 14, 2023 Posted January 14, 2023 3 hours ago, asbril said: This is as far as I got : service: logger.set_level data: homeassistant.components.isy994: debug pyisy: debug
shbatm Posted January 14, 2023 Posted January 14, 2023 @Mecheng70 I'm assuming you're hitting the same issue as @asbril: the node structure changed / is missing some information for some of the Z-Wave nodes on the Z-Matter Board. They're not reporting the "<devtype>" tag on some nodes (see difference below). The fix on my side will require a patch of PyISY, update to Home Assistant, then they will need to release the changes (hopefully in one of the 2023.1.x releases, if not 2023.2.0 in a couple weeks). <node flag="128" nodeDefId="ZY016_1"> <address>ZY016_1</address> <name>4. Guest Closet</name> <family>12</family> <parent type="3">36247</parent> <type>4.16.1.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZY016_1</pnode> <rpnode>ZY016_1</rpnode> <sgid>1</sgid> <custom flags="0" val1="0" /> <devtype> <gen>4.16.1</gen> <mfg>99.21079.13619</mfg> <cat>121</cat> </devtype> </node> <node flag="128" nodeDefId="ZY017_1"> <address>ZY017_1</address> <name>Battery Lobby Sensor 2</name> <family>12</family> <parent type="3">4304</parent> <type>4.7.1.0</type> <enabled>false</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZY017_1</pnode> </node>
Mecheng70 Posted January 14, 2023 Author Posted January 14, 2023 @shbatm thanks. I am still struggling to get the eisy up and running. Decided to factory reset everything and start over about 30 minutes ago.
asbril Posted January 14, 2023 Posted January 14, 2023 2 hours ago, shbatm said: @Mecheng70 I'm assuming you're hitting the same issue as @asbril: the node structure changed / is missing some information for some of the Z-Wave nodes on the Z-Matter Board. They're not reporting the "<devtype>" tag on some nodes (see difference below). The fix on my side will require a patch of PyISY, update to Home Assistant, then they will need to release the changes (hopefully in one of the 2023.1.x releases, if not 2023.2.0 in a couple weeks). <node flag="128" nodeDefId="ZY016_1"> <address>ZY016_1</address> <name>4. Guest Closet</name> <family>12</family> <parent type="3">36247</parent> <type>4.16.1.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZY016_1</pnode> <rpnode>ZY016_1</rpnode> <sgid>1</sgid> <custom flags="0" val1="0" /> <devtype> <gen>4.16.1</gen> <mfg>99.21079.13619</mfg> <cat>121</cat> </devtype> </node> <node flag="128" nodeDefId="ZY017_1"> <address>ZY017_1</address> <name>Battery Lobby Sensor 2</name> <family>12</family> <parent type="3">4304</parent> <type>4.7.1.0</type> <enabled>false</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZY017_1</pnode> </node> As I asked you in our PM, if this is only the 2 devices would it make sense to exclude and include these ?
MRinehart Posted January 14, 2023 Posted January 14, 2023 For clarity, assuming you're asking about swapping out your ISY994i for an EISY, and how to swap them in HA as easy as possible. After some tinkering, i was delighted to learn this was pretty easy, and I didnt need to set everything up in HA again. 1. assuming you've already replaced your ISY994i with EISY using the ISY configuration consol and backup method, and it's configured (talking to your PLM and controlling things) 2. do a full backup of your HA configuration (just in case) 3. Delete your Universal Devices integration in HA 4. Make sure the devices and entities are gone. You cards should all have yellow errors where the devices used to be. 5. Perform 'add integration' for Universal Devices. 6. Once executed, HA shoudl see all the devices again, assuming they are all the same names and IDs I just did this and was suprised this wasn't on this forum.
asbril Posted January 14, 2023 Posted January 14, 2023 31 minutes ago, MRinehart said: For clarity, assuming you're asking about swapping out your ISY994i for an EISY, and how to swap them in HA as easy as possible. After some tinkering, i was delighted to learn this was pretty easy, and I didnt need to set everything up in HA again. 1. assuming you've already replaced your ISY994i with EISY using the ISY configuration consol and backup method, and it's configured (talking to your PLM and controlling things) 2. do a full backup of your HA configuration (just in case) 3. Delete your Universal Devices integration in HA 4. Make sure the devices and entities are gone. You cards should all have yellow errors where the devices used to be. 5. Perform 'add integration' for Universal Devices. 6. Once executed, HA shoudl see all the devices again, assuming they are all the same names and IDs I just did this and was suprised this wasn't on this forum. That was the first thing I did and actually 3 times. It did not resolve the problem. @shbatm identified the problem and I hope that it can be resolved soon.
shbatm Posted January 14, 2023 Posted January 14, 2023 1 hour ago, MRinehart said: For clarity, assuming you're asking about swapping out your ISY994i for an EISY, and how to swap them in HA as easy as possible. After some tinkering, i was delighted to learn this was pretty easy, and I didnt need to set everything up in HA again. 1. assuming you've already replaced your ISY994i with EISY using the ISY configuration consol and backup method, and it's configured (talking to your PLM and controlling things) 2. do a full backup of your HA configuration (just in case) 3. Delete your Universal Devices integration in HA 4. Make sure the devices and entities are gone. You cards should all have yellow errors where the devices used to be. 5. Perform 'add integration' for Universal Devices. 6. Once executed, HA shoudl see all the devices again, assuming they are all the same names and IDs I just did this and was suprised this wasn't on this forum. @MRinehart - That's the spelled out version of what I intended by #1 here: Main issue is that if you've renamed entities or devices on the Home Assistant side, or set custom icons, you will lose that information. The issue @asbril and @Mecheng70 are hitting is an error in the python module / eisy XML schema and is being fixed here: https://github.com/home-assistant/core/pull/85900 1
asbril Posted January 14, 2023 Posted January 14, 2023 2 minutes ago, shbatm said: @MRinehart - That's the spelled out version of what I intended by #1 here: Main issue is that if you've renamed entities or devices on the Home Assistant side, or set custom icons, you will lose that information. The issue @asbril and @Mecheng70 are hitting is an error in the python module / eisy XML schema and is being fixed here: https://github.com/home-assistant/core/pull/85900 Thanks @shbatm
oatflake Posted January 19, 2023 Posted January 19, 2023 On 1/6/2023 at 3:37 AM, shbatm said: Stop Home Assistant Make a backup copy of your `config/.storage` folder, you will be changing `core.config_entries`, `core.device_registry`, and `core.entity_registry`. EDIT: these don't have file extensions, but are all JSON text files. Find and replace the IP address of the old device with the new in the 3 files above. If going from ISY to eisy or Polisy, you will also need to update the url to add the port `:8080` (or HTTPS if using that)--should be listed in the config entry, and for each device in device registry under configuration url. Find and replace the MAC address/UUID of the old device with the new (should be a lot of replacements, one for each entity, device and config entry). Save and restart Home Assistant. I can confirm this worked for me. I was replacing an ISY994i with a new eisy and I did the above steps. I ssh'd into the Home Assistant server, cd /config/.ssh/storage and then used "vi" to edit the 3 files using the search/replace feature. If you want to make sure you've found everything, you can do a "grep" on the mac address of your old ISY994i and IP address to confirm you didn't miss anything. Since I am running Home Assistant OS via VirtualBox, there wasn't a way for me to stop Home Assistant, so I did the edits while it was running, then rebooted the Home Assistant box after editing the files; it worked just fine.
asbril Posted January 19, 2023 Posted January 19, 2023 41 minutes ago, oatflake said: I can confirm this worked for me. I was replacing an ISY994i with a new eisy and I did the above steps. I ssh'd into the Home Assistant server, cd /config/.ssh/storage and then used "vi" to edit the 3 files using the search/replace feature. If you want to make sure you've found everything, you can do a "grep" on the mac address of your old ISY994i and IP address to confirm you didn't miss anything. Since I am running Home Assistant OS via VirtualBox, there wasn't a way for me to stop Home Assistant, so I did the edits while it was running, then rebooted the Home Assistant box after editing the files; it worked just fine. I wish I coud do the same but with some 80 Zwave devices changing the URL etc would take too long. I changed my HA settings to Beta and hopefully a new beta version comes out soon that will allow me to link my eisy to HA.
MrBill Posted January 19, 2023 Posted January 19, 2023 3 hours ago, oatflake said: Since I am running Home Assistant OS via VirtualBox, there wasn't a way for me to stop Home Assistant, so I did the edits while it was running, then rebooted the Home Assistant box after editing the files; it worked just fine. Developer Tools > Services > Home Assistant Core Integration: Stop (or homeassistant.stop)
Recommended Posts