It includes some significant updates to the version in HA that have not been merged yet. The long term plan is to get these included, but I haven’t made it that far yet.
For me, it actually worked the way it’s supposed to. My scenes and devices under the native integration took 5 seconds to react to commands. When I switched to the HACS version, it started working right away. Plus the developer of the integration has more control of releases.
Do I have to use HACS to get proper heartbeat monitoring from water sensors and low-battery monitoring from motion sensors? I’m on mainline 0.103.6 and I’m getting a lot of “unknown” from these devices. I tried writing some new binary_sensors to deal with that, but they seem to be ignoring the history of the heartbeat before the HA restart. My ISY is 5.0.16C.
This is one of the things that should be fixed in the HACS version.
I am using the HACS version 1.0.11, is there any way to support more than one ISY994?
Not tested yet, but here’s what I suggested to someone else asking the same thing:
Here’s a rough work-around I would recommend trying:
isy994 folder in your custom_components folder. Name it something like isy994_2const.py if using my version; somewhere in __init__.py if using the built-in).DOMAIN = "isy994"
ISY994_NODES = "isy994_nodes" --> "isy994_2_nodes"
ISY994_WEATHER = "isy994_weather" --> "isy994_2_weather"
ISY994_PROGRAMS = "isy994_programs" --> "isy994_2_programs"
ISY994_VARIABLES = "isy994_variables" --> "isy994_2_variables" # Only in mine
isy994_2).manifest.json for the line: "domain": "isy994",# Example configuration.yaml entry
isy994_2:
host: ISY_ADDRESS
username: ISY_USERNAME
password: ISY_PASSWORD
shbatm…That worked very well!
I am using the isy994 for the house and isy994_2 for the shop. As development evolves for the isy994 I will update and if needed copy to the isy994_2 making the necessary edits as required.
Thank you for the suggestion.
Glad it’s working. @simplextech, did you get yours working as well?
Since this is something more than one person is asking for, I’ll take a look when I get a chance and see how difficult it will be to allow multiple host entries in the HACS version.
I haven’t tried it yet. I’ve been off playing in RTI land.
A big thanks to @bdraco for the help: you can now configure an ISY from the Integrations page:
You can still use your configuration.yaml settings (and still need to if configuring variables). This will also populate the Device Registry:
And collect child nodes together:
I just tried to update to v1.2.0, but lose all variables. Tried full reboot with no joy. I see no errors anywhere or even warnings. Anyone else seeing this? Went back to 1.1.2 and all is fine again.
I am fully up to date on all other components of the HA system.
Thanks for the ongoing terrific work on this plugin!!
@Blueman2 - Did you reconfigure the ISY through Integrations or just leave your config the same in configuration.yaml?
I left the config as it was. Note that switches, etc worked. Just not variables. My guess in pilot error on my part, but I did not spend a lot of time diagnosing it. I just reverted back to earlier version.
Let me try once again to see if I have any better luck.
I just did a re-upgrade to 1.2.0. It looks like the variables are there in Integrations. They are all listed under “Entities without devices”. But when I look at my Lovelace interface, the values all show up as “unavailable”.
OK, I think I see what is going on. My variables are all renamed with “_2” at the end. That is why my interface does not see them. It must think they are from a 2nd ISY?
Gotcha. A couple of things changed with this update that affects the unique_id assigned to each entity. For all of the other devices, the transition should be seamless, but not with variables.
Long story short: Home Assistant has a memory of the old entities, which don’t exist any more (because the unique_id changed) and also created duplicates (_2 is Home Assistant’s way of managing duplicate names).
To Fix: Delete the old entities from the Entity Registry manager, then rename each of the new ones by removing the _2 from the entity_id and all of your displays should start working again.
Very cool. I was just reading about the ability to have 2 ISYs, which I just happen to have! So I will be looking forward to seeing how this works.
Cheers!
Bob
@shbatm, I was able to resolve the unique_id issue pretty easily. I did the update in HACs, but before rebooting I deleted the core.entity_registry file. It took 2 reboots to clean everything up, but now I have everything working with minimal effort on my part. Now running 1.2.1 and very happy.
BTW, for anyone else using the HACS interface and running HASSIO on a Raspberry Pi, do not use the system restart in HACS after doing an upgrade. For Hassio/Pi, you need to do a full reboot. Otherwise you will have errors on restart.
Congratulations on the integration of your work into the main release! I know this took a lot of effort and time from you. But I think this is a huge step forward in terms of long term support of the ISY integration. Well done, sir!
