shbatm

Screenshots of changes: Variables: Network Resources:

Until 2023.2.0, you have to set the variable string in the config options to get them to show up as sensors Settings > Devices & Services > Integrations tab Click configure under Universal Devices ISY994 Next month they'll all come in as number entities. The only thing that setting will control is which get enabled by default. Sent from my SM-S908U using Tapatalk

Updated list of changes coming 2022.2.0 (bold=New feature) Add Insteon backlight control support to ISY994, bump PyISY to 3.1.7#85981 @MrBill Deprecate isy994.cleanup_entities service (#85931) Add enable switch for ISY994 devices, support availability (#85928) Add Insteon ramp rate select entities to ISY994 (#85895) Bump PyISY to 3.1.5 and fix bad Z-Wave properties from eisy (#85900) (may be pulled into 2023.1.x) Add On Level number entities to ISY994 Insteon Devices (#85798) Deprecate YAML configuration for ISY994 (#85797) Bump PyISY to 3.1.4 to fix dependency issues (#85825) Make use of str.removeprefix and .removesuffix (#85584) Move ISY994 data to dataclass and remove bad entities (#85744) Consolidate device info and clean-up ISY994 code base (#85657) Remove old migrate unique ID code from ISY994 (#85641) Add ISY994 variables as number entities (#85511) Add network resource button entities to ISY994 and bump PyISY to 3.0.12 (#85429) Add beep button entity to ISY994 Insteon devices (#85367) Add query button entities to ISY994 devices and hub (#85337) Use Platform enum and remove DOMAIN as X imports in ISY994 (#85341) Add additional device classes to ISY994 sensors and bump PyISY to 3.0.11 (#85315) Add additional device classes and units to ISY994 aux sensors (#85274) Restore low battery state on ISY994 Insteon heartbeat nodes (#85209) Assign ISY994 program entities to hub device, simplify device info (#85224) ISY994: Add dhcp support for eisy (#85083) Update ISY994 integration to be model agnostic (#85017) Change ISY994 group device assignments (#84933)

It's going to come down to testing, unless you're using some full size enterprise-grade servers. I don't see much overhead on the Hass box, which is an old ~6th Gen i5 HP ProDesk SFF. It's runs some other minor services, but just one VM (with hassos, zigbee2mqtt, zwavejs2mqtt, and some other addons). Frigate is running fine for me in docker, on the same Lenovo USFF 7th Gen i7 as plex (docker) and my media VM (for Linux isos). I pulled the wifi card and added a Coral mPCIe in the slot. It passes through to docker (or a VM) just fine. That box will run a Win10 VM too when needed. When I first started getting familiar with proxmox, virtualbox and VMs I saw the giant setups on full servers like in r/homelab on reddit. But the more I read into it, running a Linux VM on something that's not extremely demanding doesn't need a massive machine.

@Mecheng70 I'm very conscious of the venue I'm in; but if you're already using Home Assistant--you may want to check out Z-Wave JS with a Zooz stick.

I would also love to see IoX available as a generic service I can run on a VM--really it should even be able to run as a docker container. IoX as an add-on to Home Assistant would be a great combination. My personal setup is similar to @jlegault Home Assistant OS on a VM on a low-power device running Proxmox. It's an extra layer to potentially fail--but for the past 3 years it has been more of a benefit as an extra layer to allow troubleshooting--I don't usually have to go to the physical device (and usually don't have to be at home) and I have multiple layers of backups (HA backups, VM snapshots) and if the host dies, I can install proxmox and restore everything in ~30 min on a spare box.

@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

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

Please send me a message with your nodes.xml file: Use web browser to go to http://eisy.local:8080/rest/nodes Save page as nodes.xml Replace eisy.local with the IP address if link doesn't work.

service: logger.set_level data: homeassistant.components.isy994: debug pyisy: debug

Making progress:

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.

Perfect @asbril Got what I needed. Thanks!

All you need to do is find the node name of your Z-Wave dimmer device (ZW_xxx) and go to this address in a web browser and save (CTRL+S) what shows up as a .XML file and post here. http://your-isy-ip/rest/nodes/ZW_xxx Should be something like below: <?xml version="1.0" encoding="UTF-8"?> <nodeInfo> <node flag="128" nodeDefId="DimmerLampSwitch_ADV"> <address>2E BA CA 1</address> <name>Game Room Christmas Tree</name> <parent type="3">63777</parent> <type>1.14.67.0</type> <enabled>false</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>2E BA CA 1</pnode> <property id="ST" value="" formatted=" " uom="0" /> </node> <properties> <property id="OL" value="" formatted=" " uom="0" /> <property id="RR" value="" formatted=" " uom="0" /> <property id="ST" value="" formatted=" " uom="0" /> </properties> </nodeInfo>

@MrBill@Mecheng70@asbril12 or any others using: ISY + Z-Wave (or Z-Matter) + Home Assistant: I need someone to please share an XML result for a Z-Wave Dimmer for testing some upcoming changes: http://your-isy-ip/rest/nodes/ZW_xxx

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.

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

Expect some upcoming changes to the ISY/IoX Integration in Home Assistant, some will be picked up in the 2023.1.x releases, but most will be coming next month (2023.2.0): Edit: Screenshots here: Network Resources will be added as "Button" entities (isy994.run_network_resource service goes away in 2023.5.0). Query button entities will be added for each device (isy994.system_query service goes away in 2023.5.0). Beep button entities will be added for each INSTEON device. 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. 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) Devices disabled on the ISY will show an error if you try and control them from Home Assistant. eisy should be auto-discovered. And if I get to it: INSTEON Ramp Rates will be available as a select menu entity. INSTEON On Level will be available as number entity. Node Server native sensor support (with correct sensor names and values)

Also - don't want to distract from this thread, but expect some more updates and breaking changes in Home Assistant 2023.2.0: Network Resources will be added as "Button" entities (isy994.run_network_resource service goes away in 2023.5.0). Query button entities will be added for each device (isy994.system_query service goes away in 2023.5.0). Beep button entities will be added for each INSTEON device. 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. 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) Devices disabled on the ISY will show an error if you try and control them from Home Assistant. eisy should be auto-discovered. And if I get to it: INSTEON Ramp Rates will be available as a select menu entity. INSTEON On Level will be available as number entity. Node Server native sensor support (with correct sensor names and values)

@asbril's summary is accurate. 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. 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). 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.

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.

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

@indomitableMan Sorry it's taken so long for me to test, but I was able to recreate your error. I think it boils down to something very simple-- You must reload the Home Assistant ISY994 Integration after you make changes in the ISY Admin Console, such as creating or renaming variables. Only states and values are updated on-the-fly by Home Assistant, any changes to the "definitions" of the nodes, variables, and programs--such as creating, renaming, or deleting--are only updated on initial loading or broken connections.

@Javi Thanks for the leads! This will help. I didn't see anything about the family code for the primary node endpoints (e.g. /rest/nodes and /rest/node/ZY_xxx) <family>12</family> Just want to confirm if Matter/Zigbee is going to be 12 as well or if it will use 11 (or something else)? Thanks!

To the UDI team, maybe @Michel Kohanim can answer this (Sorry to tag you directly but I don't think that this is going to be public knowledge, so I'm coming to the source...) I am trying to update the PyISY python package to support the new ZMatter board after a user reported getting errors loading Home Assistant here. I can trace it back to how HA is differentiating Z-Wave vs Insteon nodes via the family code in the rest results. I see that Z-Wave on the new board is using a Family code of 12 instead of 4. Is that just for Z-Wave on the new board? Is Zigbee/Matter using anything different (e.g 11)? Has anything else changed on the REST side for the new board or Node structure? Asking so I can build in as much support as I can now without just being reactive to users running into errors. Thanks!