Calling all ISY994 users!

[shbatm]

@Blueman2 Make sure you follow this topic too:

Multiple ISY994's

I am new to Home Assistant with very little coding experience but I now have a Raspberry Pi 4B running hassio 0.105.3. I have two ISY994’s, one in my home and one in my detached shop. I have the one in my home working with hassio and would like to add the second but keep running into errors. Here is what I have in my configuration.yaml # Universal Devices ISY994 (House) isy994: host: !secret isy_house_url username: !secret isy_house_username password: !secret isy_house_password # Unive…

[Blueman2]

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

[Blueman2]

@shbatm,

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!

[tendiian]

I just updated to .110 and saw that the ISY integration had gone through some major upgrades so I decided to pull my ISY out of storage and try it again with my Insteon devices. Everything went swimmingly except that my two Insteon Micro open/close modules that I’m using with some roller shades are populating as sensors.

The modules are 2444-222 and I’m hoping that it’s just something I missed in setting things up.

I noticed in the release notes that the on/off control had changed from a switch to a sensor. So maybe they won’t work as open close anymore.

I’ve also tried creating the program like the documentation discusses for HA.cover but that does not seem to be picked up by the integration anymore. Even though I’ve tried several times removing and recreating the integration hoping to pick up the program “device”.

Any suggestions or thoughts would be great.
Thanks

[shbatm]

Thanks for giving it a try and reporting back!

@tendiian

The modules are 2444-222 and I’m hoping that it’s just something I missed in setting things up.

Can you please use a web browser to go to “http://your-isy-ip/rest/nodes/INSTEON-ADDRESS-OF-MICRO” and post the XML file here? That will help me tweak the sorting. Also, what firmware version is your ISY? Is it 4.x.x or 5.0.x?

Side note: even if they are picked up as sensors and we can’t get the sorting to work, you can still use the isy994.send_raw_node_command service to send DON (on) and DOF (off) commands to a sensor. A Home Assistant Template Switch would allow you to assign these as the regular on/off commands.

@tendiian

I’ve also tried creating the program like the documentation discusses for HA.cover but that does not seem to be picked up by the integration anymore. Even though I’ve tried several times removing and recreating the integration hoping to pick up the program “device”.

This is definitely still supported (it’s how I use my garage door IOLinc). Are you seeing any errors in your Home Assistant log? If it’s finding them but refusing to add them you should see something like:

"WARNING Program cover entity 'SOME NAME' not loaded, invalid/missing status program."

Just for clarity, you should have a folder called HA.cover, inside of that a folder called MyCover or whatever, and in that folder you should have two programs; one named actions and one named status.

[tendiian]

Firmware is 5.0.16C

Both modules report similar XML just changes for the different names and such.

<?xml version="1.0" encoding="UTF-8"?>
<nodeInfo>
   <node flag="128" nodeDefId="DimmerMotorSwitch_ADV">
      <address>20 1C 52 1</address>
      <name>Master Bedroom Window</name>
      <type>14.1.67.0</type>
      <enabled>true</enabled>
      <deviceClass>0</deviceClass>
      <wattage>0</wattage>
      <dcPeriod>0</dcPeriod>
      <startDelay>0</startDelay>
      <endDelay>0</endDelay>
      <pnode>20 1C 52 1</pnode>
      <ELK_ID>C03</ELK_ID>
      <property id="ST" value="0" formatted="Off" uom="100" />
   </node>
   <properties>
      <property id="DUR" value="163" formatted="16.3 seconds" uom="58" prec="1" />
      <property id="OL" value="255" formatted="100%" uom="100" />
      <property id="RR" value="28" formatted="28" uom="25" />
      <property id="ST" value="0" formatted="Off" uom="100" />
   </properties>
</nodeInfo>

The HA.cover issue was me. As usual when I’m creating ISY programs I missed hitting the save button at some point in the process…

Thanks!

[pashdown (Pete Ashdown)]

Now that the excellent work by @shbatm is mainline, should we still be using the HACS version? Is there ay advantage in doing so?

[shbatm]

@tendiian – I can have this added as a cover (changes already staged here). Question for you though since this thread got me nowhere… Can you send a particular open % to this device, or is it just ON/OFF?

For example – does the REST command below command it to go to 50% or full open?
http://your-isy-ip/rest/nodes/20 1C 52 1/set/DON/128

@pashdown: Short answer: No, you don’t need the HACS version**. See original response here:

ISY994 HACS Version with PyISY-Beta

My plan is to update it to match these changes in Core, but I would recommend once you update to 0.110, you remove the custom component. I still have some plans for testing a few improvements in speed, as well as better support for ISY NodeServers, however, the base case will be to progress these changes in the Core code and the HACS version will not be maintained or updated unless there is a significant change to be made and tested. This HACS component was necessary because of the significant…

**If you want to continue testing, the next “phase” is to move the PyISY module to asynchronous code to try and speed up the communications. That is available on the 2.0.0b1 beta HACS release right now, but as soon as it’s stable it’ll be merged to Core as well. That will likely be my last major HACS update since that’s the end of the roadmap laid out for PyISY updates, anything else will be pushed to Core (including @tendiian’s micro open/close support).

[Blueman2]

@shbatm,

I finally updated to the newest HA and ISY944 Integration. A couple issues worth noting:

1. None of my HA.binary_sensor or HA.lock programs came across. I had them working just fine before upgrading to 0.110.3 but none of the binary sensors are created after upgrade. I checked and see no errors. I will increase logging to see if I can tell what is going on.

2. Most of my variable icons defaulting to “mdi:counter”, but easily fixed in customizations. I am guessing that is normal behavior.

Home Assistant 0.110.3

[shbatm]

@Blueman2

None of my HA.binary_sensor or HA.lock programs came across. I had them working just fine before upgrading to 0.110.3 but none of the binary sensors are created after upgrade. I checked and see no errors. I will increase logging to see if I can tell what is going on.

Try restarting HA one more time… Someone else mentioned this but they showed up after a restart. I just confirmed that all of my programs are loading (ISY 5.0.16C, HA 0.110.1) and functioning correctly.

@Blueman2

Most of my variable icons defaulting to “mdi:counter”, but easily fixed in customizations. I am guessing that is normal behavior.

This is the default behavior now. There are different default icons for Groups/Scenes, Variables, and Programs to semi-mimic the ISY’s UI; they should all be customizable within Home Assistant.

[Blueman2]

@shbatm,

Still no joy. I have tried numerous reboots, even restarting the ISY a couple times, and for some reason Home Assistant no longer reads the Binary sensors from ISY Programs. I did not change anything at the ISY side, just the upgrade to 0.110.3

I am not seeing any warning or error messages in the Log.

[shbatm]

Confirm you’ve checked the States page too just to make sure the name didn’t change to something else?

[Blueman2]

Correct, I have checked all devices to make sure it was not a name change. All 8 of the Binary Sensors that were being created by HA.binary_sensor programs have disappeared. Also, the 2 HA.lock programs are missing in HA as well.

[shbatm]

Can you PM me your /rest/programs?subfolders=true XML file?

[tendiian]

@shbatm
Sorry I got tied up with work just tested this now and it worked perfectly.

http://your-isy-ip/rest/nodes/20 1C 52 1/set/DON/128
<RestResponse succeeded="true">
<status>200</status>
<reason code="0"/>
</RestResponse>

[Blueman2]

@shbatm,

I tried pretty much everything. I wiped my entire config and started from scratch with a new 0.110.3 system, and still no ability to get HA.binary_sensor to work from ISY. I reverted back to 0.109.4, and everything works just fine with HA.binary_sensor. So that sort of rules out issues with the ISY since it works fine with no changes there. I am going to stay at 0.109.4 for a few days until I have the time to really debug.

I did set my log level to Info while in 0.110.3 and saw where the ISY program data was being requested, and there were no errors there that I saw. So the data is being ingested it appears, but not interpreted by HA.

[shbatm]

Add support for Insteon 2444-222 to ISY994

[Blueman2]

@shbatm solved my migration issues. Here is what worked for me:

1. start with 0.109.4 and ISY 1.3.7
2. Remove HACS version & remove ISY994 from your configuration.yaml (completely–it should persist in your integrations page).
3. upgrade to 0.110.3 - reboot
4. Adjust any options for ISY994 in the Integrations page (this also forces a reload).
5. If you have any “extra” entities after changing options, you can run the cleanup service.

[shbatm]

Glad you got it working! I’ll take a look at the HACS version and see why it’s not loading programs.

[Blueman2]

Quick update after my move to 0.110.3 and new ISY994 integration. After overcoming my poor migration path with the help of @shbatm, I am really loving this upgrade. First, I notice a much faster start of HA. I am doing alot of adjustments that require changes to my configuration.yaml. Using the Configuration=>Server Controls=>Server Management=>Restart, I am able to reboot the HA instance in about 30 seconds or so. Used to take much, much longer. Nice!

Also, being able to use the new ISY services like Reload and Cleanup Entities is a godsend.

Thanks so very, very much @shbatm for your hard work on all of this. The HA/ISY integration has been the biggest factor in improving my home automation setup in years.