I created a new scene on my ISY994i. How do I get it to show up in HA?
The Universal Devices ISY/IoX integration documentation
When I first installed the integration all of the my scenes (along with devices, etc) showed up. I tried nuclear option:
- delete the integration
- reboot HA
- Install the integration
but only the items that were there before the removal showed up, no new ones.
How do I get the new ISY scenes to show up in HA?
I may have a convoluted work-around which involves creating programs in ISY, using the isy994 send_program_command and a variable that was already integrated into HA
I also have some questions about Creating Custom Devices using ISY Programs, but I suspect that the custom devices have to be created before the first time installing the integration. This would be a ridiculously bad assumption on the part of the integration designer so I must assume that a way to get changes from the ISY994i to show up in HA. How is this done?
I don’t have this integration, but for the Insteon Integration and Yolink integration, I have to pick Reload under the 3 dot menu for the Intengration to discover new devices. I think they eventually find things on their own but typically I’m ready to finish what I’m doing.
Edit: One of the reasons I suggested this way vs nuclear is that recently I blew away my Matter and Thread integrations and reinstalled, and then re-set up devices. Some of the old info for the devices came back so it appears there can be memory of previous incarnations.
I had tried that but it didn’t seem to do anything, but the reload worked this time. 
Alas, now I’m seeing some strange things though.
My old scene was EnrtryChandelier
My new scene is “EntryChandelierISYscene”
The old scene still appears in Settings–>DeveloperTools–>States but deleted from the ISY. The new scene appears here, too.
Neither scene appears in Settings–>" Universal Devices ISY/IoX >"–>ISY (Controls box) but other scenes do
Using switch.entrychandelierisyscene in automations works as hoped.
Since it is working. I’m not going to try to fix these mysteries.
Thanks for the tip.
It seems like a lot of ISY Integration users ask questions on the UDI forum but not the HA forum about things like this. Now I get why… there’s about 500 active ISY integration users (About 1200 Insteon Integration users) and they aren’t that talkative here, or it gets lost with so much else going on here and hundreds of thousands of community members and myriad topics.
I guess I’m suggesting posting this back on the HA part of the UDI forums and someone there probably has an idea.
I logged into the UD forum and my first search item described my problem. That person ended up using the nuclear options: wipe HA, start with a clean slate and install the integration. This is not a good option.
It is without question in my mind that the author of the integration knows of this issue and has a better work around, even if it is editing configuration files.
I really like Insteon devices because they work. Sure, they cut corners in the manufacturing. The problem is their controller which, to put it mildly, has never lived up to expectations. That’s where UD comes in. My ISY994i has been working flawlessly ever since I figured out my Insteon Hub was useless. Then UD ceased support for the ISY994i and expected its users to plunk down another chunk of cash. My thought was that this was going to be a recurring theme where one had to replace the controller every couple years. Then I found my way to HA and the UD integration. I moved all my Z-Wave devices to HA and ran HA and the ISY994i loosely tied in parallel.
I was finding delays with the communication between the two which sometimes caused a positive feedback loop. I thought that using the HA Insteon integration and dropping the ISY994i completely would solve that. Not really and lost some nice Insteon functionality.
So now I’m here, trying to tighten the communication between HA and the ISY994i via the UD integration.
For me the opportunity cost in choosing the Insteon Integration was losing double-tap and configuring fade up / dim level in scenes. These might/could be added by the integration owner. There is active development and I opened a git feature request for the latter.
I wouldn’t be sure what to expect if both integrations were used at the same time since there is one (USB) serial connection to the PLM from HA, not sure of what would have ownership of that connection or how that would be managed.
However Insteon performance remains the same from HA - PLM - Device, or the other way. I think we discussed elsewhere that the back-to-back serial line speed comms of device to PLM, and PLM to HA (or 994) are the long pole in the tent. Nothing will change that.
I think the serial connection from any controller to PLM is 19.2k baud, but Insteon devices max at I think 14k baud rf. Depending where you read, the effective Thread throughput is probably closer to 125k baud - let’s round up and call it 10x faster OTA. My limited experiments with Matter/Thread devices “feel” faster when switching on a device anywhere on the mesh from HA