HomeAssistant (ISY-> EISY migration)

[Mecheng70]

Curious if anyone has migrated the ISY/POLISY to the new EISY with the zwave dongle and what if anything changes on HomeAssistant.  Will we have to update all the renaming, etc?  

[asbril]

11 minutes ago, Mecheng70 said:

Curious if anyone has migrated the ISY/POLISY to the new EISY with the zwave dongle and what if anything changes on HomeAssistant.  Will we have to update all the renaming, etc?  

Not sure that this will answer your question but I added the ZMatter board to my eisy and added one Zwave device to make sure that Zwave is activated on eisy. I did NOT migrate yet. 

I added  the eisy to my Home Assistant and the 1 Zwave device does show up in my HA, together with all my Polisy devices.

Edited January 5, 2023 by asbril

[Mecheng70]

I think the scenario you have is a new eisy added to HA.  my current configuration is HA and ISY.  I curious if I have to update all my nodes with any special names and icons or if the ZWXX (XX - numbers) will come over with the new system.  

 

[asbril]

23 minutes ago, Mecheng70 said:

I think the scenario you have is a new eisy added to HA.  my current configuration is HA and ISY.  I curious if I have to update all my nodes with any special names and icons or if the ZWXX (XX - numbers) will come over with the new system.  

 

good question

[Mecheng70]

@shbatm Thoughts on this?

[shbatm]

2 Options for migrating from one device to another (assuming you're doing a backup > restore):

1. Easy, but you will have to update entity names and ids: remove the old integration and add the new.

2. Harder, but everything stays the same (just did this last week with my ISY>Polisy). You will need access to the files in the Home Assistant Config Folder (either Samba, SSH, VS Code Remote--Edge Addon Repo, my recommended, etc).

1. Stop Home Assistant
2. 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.
3. 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.
4. 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).
5. Save and restart Home Assistant.

Edited January 15, 2023 by shbatm

[Mecheng70]

I plan on replacing the ISY with the EISY (IP addresss, etc).  ISY will be pulled from service.

The instructions for option 2 look good for me (linux based system,etc).  

Thank you, this is exactly what I was looking for.  Will keep the wife factor at 1.0..

[brians]

Z-Wave on ZMatter changes the note prefix from ZW to ZY. Also nodes may change slightly due to differences in old implementation vs. the new APIs UDI is using for Z-Wave. You will probably have to manually fix a lot of things because the entities names will be different.

I just tried on my Polisy/ZMatter (which should be same as EISY/ZMatter) and had to do updates on test HA for it to work since have not used it for a long time.

After playing around with it for a bit I decided to delete it off HA again since I see no real use for it in my case and looks like a big opportunity for me to waste time on that I don't really wish to do now

 

Edited January 8, 2023 by brians

[asbril]

9 minutes ago, brians said:

Z-Wave on ZMatter changes the note prefix from ZW to ZY. Also nodes may change slightly due to differences in old implementation vs. the new APIs UDI is using for Z-Wave. You will probably have to manually fix a lot of things because the entities names will be different.

I just tried on my Polisy/ZMatter (which should be same as EISY/ZMatter) and had to do updates on test HA for it to work since have not used it for a long time.

After playing around with it for a bit I decided to delete it off HA again since I see no real use for it in my case and looks like a big opportunity for me to waste time on that I don't really wish to do now

 

I have some 80 Zwave devices on Polisy and right now just 2 on eisy. They all show up in HA.

However, with the different identity I expect that after the migration, I will have to manually update my "Cards" and "Automations".  I don't think that it will be huge task and I estimate that it will take me no more than 2 hours.

[shbatm]

ZMatter requires Home Assistant 2023.1.0 or later, and yes, because of the node number changes, those entity_id's will change in Home Assistant.

[Mecheng70]

Does this indicate that new entities would be affected? Or will the ZW change to ZY or the entire string? 

[asbril]

23 minutes ago, Mecheng70 said:

Does this indicate that new entities would be affected? Or will the ZW change to ZY or the entire string? 

I think that there is a difference between what you ask and what @shbatm writes.

• New entities are added to HA as always.
• According to @shbatmZMatter requires Home Assistant 2023.1.0. To a degree that is not yet relevant as ZMatter has not yet been implemented and will require a future firmware upgrade.
• Before 2023.1.0  I added a Zwave device to HA that is on my eisy with the ZMatter board. I only needed to add another ISY Integration for the eisy ISY.
• I expect that after migration to eisy-with-Zmatter the Zwave devices on HA may appear as not connected if the HA identification looks at the ZY instead of ZW.  In that case we may have to replace each device with its new ZY identification and it may, or may not, also impact HA Automations. However, it should not be a major task, even with my approx. 80 ZWave devices.

Edited January 8, 2023 by asbril

[Mecheng70]

Bullet 4 addresses my question. Thanks. 

 

Look like I may need to hone my find and replace skills. I have local copies of the 3 files @shbatm mentioned to update.  

[asbril]

10 minutes ago, Mecheng70 said:

Bullet 4 addresses my question. Thanks. 

 

Look like I may need to hone my find and replace skills. I have local copies of the 3 files @shbatm mentioned to update.  

It should  be easy. After the migration your Zwave devices should still have the same name as in ISY994 or Polisy. Let's say that you have Zwave device named Kitchen Light and you have that in a HA card named Kitchen.  After the migration  and a  reload of the eisy ISY Integration (I expect that) the Kitchen Light  should appear as not connected.  Then click on edit and replace the not connected Kitchen Light (ZW) with the connected Kitchen Light (ZY).  As they say in French, Simple comme Bonjour  

[shbatm]

@asbril's summary is accurate.

1. New devices added to the ZMatter Z-Wave board/dongle will be picked up in Home Assistant after an integration reload, or HA restart. There was a new family identifier added in the ISY for the new ZMatter boards (as well as the node address changing to ZY prefix) -- this was added in PyISY 3.0.10, which is now included in Home Assistant 2023.1.0.
2. If the device was previously migrated from ISY Z-Wave or a USB stick, the node address in the ISY/IoX console will have changed from ZW_0xx to ZY_0xx. This change means the Unique ID changes in Home Assistant (tied to the UUID of the ISY/IoX and the Node Address). You can do the same search/replace described above with the Node Address (ZW_xxx) and update it to the new ZY_xxx (xxx may have changed as well).
3. Devices that you migrated in the ISY, but did not search/replace in Home Assistant may need to be manually deleted in Home Assistant or they should go away after 7 days when the Restore State information expires. You can also try the `isy994.cleanup_entities` service in Home Assistant, but sometimes that doesn't catch everything.

Edited January 8, 2023 by shbatm

[shbatm]

Also - don't want to distract from this thread, but expect some more updates and breaking changes in Home Assistant 2023.2.0:

1. Network Resources will be added as "Button" entities (isy994.run_network_resource service goes away in 2023.5.0).
2. Query button entities will be added for each device (isy994.system_query service goes away in 2023.5.0).
3. Beep button entities will be added for each INSTEON device.
4. Groups/Scenes will now show under the ISY Hub device, unless they have only 1 controller node, then they'll be assigned to that device.
5. Variable Sensors will be removed and Variables will be available as Number entities (both value and init) that can be directly controlled (isy994.set_variable service goes away in 2023.5.0)
6. Devices disabled on the ISY will show an error if you try and control them from Home Assistant.
7. eisy should be auto-discovered.

And if I get to it:

1. INSTEON Ramp Rates will be available as a select menu entity.
2. INSTEON On Level will be available as number entity.
3. Node Server native sensor support (with correct sensor names and values)

Edited January 8, 2023 by shbatm

[asbril]

26 minutes ago, shbatm said:

the `isy994.cleanup_entities` service

where can I find this in HA ?

[shbatm]

Under Developer Tools (bottom left of sidebar, or type 'c' then Navigate Developer Tools) > Services Tab

Edited January 8, 2023 by shbatm

[MrBill]

1 hour ago, shbatm said:

Also - don't want to distract from this thread, but expect some more updates and breaking changes in Home Assistant 2023.2.0:

1. Network Resources will be added as "Button" entities (isy994.run_network_resource service goes away in 2023.5.0).
2. Query button entities will be added for each device (isy994.system_query service goes away in 2023.5.0).
3. Beep button entities will be added for each INSTEON device.
4. Groups/Scenes will now show under the ISY Hub device, unless they have only 1 controller node, then they'll be assigned to that device.
5. Variable Sensors will be removed and Variables will be available as Number entities (both value and init) that can be directly controlled (isy994.set_variable service goes away in 2023.5.0)
6. Devices disabled on the ISY will show an error if you try and control them from Home Assistant.
7. eisy should be auto-discovered.

And if I get to it:

1. INSTEON Ramp Rates will be available as a select menu entity.
2. INSTEON On Level will be available as number entity.
3. Node Server native sensor support (with correct sensor names and values)

These are some awesome updates!  Many thanks!

[Mecheng70]

2 hours ago, shbatm said:

Also - don't want to distract from this thread, but expect some more updates and breaking changes in Home Assistant 2023.2.0:

1. Network Resources will be added as "Button" entities (isy994.run_network_resource service goes away in 2023.5.0).
2. Query button entities will be added for each device (isy994.system_query service goes away in 2023.5.0).
3. Beep button entities will be added for each INSTEON device.
4. Groups/Scenes will now show under the ISY Hub device, unless they have only 1 controller node, then they'll be assigned to that device.
5. Variable Sensors will be removed and Variables will be available as Number entities (both value and init) that can be directly controlled (isy994.set_variable service goes away in 2023.5.0)
6. Devices disabled on the ISY will show an error if you try and control them from Home Assistant.
7. eisy should be auto-discovered.

And if I get to it:

1. INSTEON Ramp Rates will be available as a select menu entity.
2. INSTEON On Level will be available as number entity.
3. Node Server native sensor support (with correct sensor names and values)

 

Sweet. Awesome updates.  Once migrated, do you need help testing? 

[shbatm]

44 minutes ago, Mecheng70 said:

Once migrated, do you need help testing? 

These will go into the beta release towards the end of the month, so if you Join the Beta Channel in Home Assistant you can keep an eye out for it.

Or if you're eager to test, several of the changes are already merged and available in the 'dev' branch from GitHub.

[Mecheng70]

38 minutes ago, shbatm said:

These will go into the beta release towards the end of the month, so if you Join the Beta Channel in Home Assistant you can keep an eye out for it.

Or if you're eager to test, several of the changes are already merged and available in the 'dev' branch from GitHub.

I will once I get things migrated over, I will do that.  

[Mecheng70]

Getting an error when updating:  Do I need to put this on github?

 

Logger: homeassistant.config_entries
Source: components/isy994/__init__.py:180
First occurred: 15:11:34 (1 occurrences)
Last logged: 15:11:34

Error setting up entry Riften (172.16.5.251) for isy994
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 382, in async_setup
    result = await component.async_setup_entry(hass, self)
  File "/usr/src/homeassistant/homeassistant/components/isy994/__init__.py", line 180, in async_setup_entry
    await isy.initialize()
  File "/usr/local/lib/python3.10/site-packages/pyisy/isy.py", line 138, in initialize
    self.nodes = Nodes(self, xml=isy_setup_results[2])
  File "/usr/local/lib/python3.10/site-packages/pyisy/nodes/__init__.py", line 110, in __init__
    self.parse(xml)
  File "/usr/local/lib/python3.10/site-packages/pyisy/nodes/__init__.py", line 329, in parse
    feature.getElementsByTagName(TAG_DEVICE_TYPE)[0]
IndexError: list index out of range

 

 

[Mecheng70]

@shbatm I had the above error, uninstalled, rebooted and reinstalled the integration.  Still getting this error:

 

Logger: homeassistant.config_entries
Source: components/isy994/__init__.py:180
First occurred: 17:11:54 (2 occurrences)
Last logged: 17:12:41

Error setting up entry Riften (172.16.5.251) for isy994
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 382, in async_setup
    result = await component.async_setup_entry(hass, self)
  File "/usr/src/homeassistant/homeassistant/components/isy994/__init__.py", line 180, in async_setup_entry
    await isy.initialize()
  File "/usr/local/lib/python3.10/site-packages/pyisy/isy.py", line 138, in initialize
    self.nodes = Nodes(self, xml=isy_setup_results[2])
  File "/usr/local/lib/python3.10/site-packages/pyisy/nodes/__init__.py", line 110, in __init__
    self.parse(xml)
  File "/usr/local/lib/python3.10/site-packages/pyisy/nodes/__init__.py", line 329, in parse
    feature.getElementsByTagName(TAG_DEVICE_TYPE)[0]
IndexError: list index out of range

 

[shbatm]

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.

Edited January 14, 2023 by shbatm