Hey @OverloadUT, thanks for the good work that you have done on the ISY 994 integration. My installation is large and mostly done using Insteon devices, but I also have ZWave devices connected to the ISY994. I was running the V4.62 firmware on the ISY and felt that the ISY - Hassio (under a RPi3) was rock solid.
I had to use a strange hack to get the ISY and Hass to work fast. In order to be able to trigger Hass scenes from a few Keypad Lincs, instead of detecting the button press Inside HASS, I wrote some ISY Programs that on a button press invoke a network resources on the ISY to call a scene via the HASS rest api. I had to do this to ensure that key presses in the Keypad lincs were immediately processed, as detecting the key presses in Hass sometimes takes up to 10 seconds. Maybe something is wrong on my Hassio environment, but it was taking that much. In this very moment I’m stuck on Hass version .72, as a lot of the weaker TLS ciphers were removed (see bug #12871) in 0.73, which prevents me from upgrading to 0.75.3 (at this moment is the latest Hass). The call from the ISY to Hass does not work under Hass 0.73 and upwards, as it cannot negotiate a common high strength cipher. If the button press event was raised quicker in Hass (< 1 sec), it would allow me to process the button presses in Hass, and that would be a big thing for usability.
On a separate thing, I’ve noticed that the state of devices on the ISY can sometimes take too long to be updated on Hass, which again deters from actively using Hass code to quickly detect events in the ISY.
Eventhough the previous two funny things are not trivial, all considered, this integration has allowed me to really move all the home automation processing logic to Hass, so I really like it a lot. I received the last batch of enhancements with a smile, because it made using sensors much more elegant.