Home Assistant isn't a commercial product. They have some revenue streams, but it's just not the same business model. Honestly, while I get your passion for the product (and to be clear that's why I worked with @cwwilson08 and Scott Kuester to test as much as we could to bring the Insteon Websocket server to fruition), the business case for a commercial product to support a currently dead product line (I'm not saying useless because it's certainly not, but unless the line is picked up, for which they claim to have already tried and failed, then it's not going to come back to life. End of story). Chris put in the lion's share of effort, developing three different versions of support on HE over time, for a system he didn't even own or use!
With the passing of time and little users responding to the efforts, we just could not keep testing and iterating. For myself and most, it does exactly what we set out to do, and with more responsive results than even the HA integration that they spent years working on. Contrast that with the efforts of Chris, building three different integrations over a single years time! I'm not dissing the HA Insteon integration. It may be slower, but FFS it works. What's to complain about there? And they have agreed to now integrate Tom Harris' excellent Insteon Panel too, giving back device configuration so you don't have to stand on one leg and go through complicated device button presses. They also claim they will be putting more development effort into it. So if that actually happens, what's not to like there? Setting up HA to run on an old computer with VirtualBox takes 10 minutes or less. Unless you're really savvy, setting up the node.js instance is going to take you a lot longer than that. But if you've got some time and patients. it's worth the effort.
Probably you can use Home Assistant Device Bridge to bring HA discovered Insteon devices back into HE. I did a quick test a week ago, and it didn't work. Might just need some updates or new device types to make that work properly. You can always. help in the community support efforts by setting up HA and testing that, but please post in that thread about Home Assistant Device Bridge issues, not here. I can test myself at some point, but since I already run the HE node.js setup and have for years, it's not a priority. Don't get me wrong, I want to help, but I can only afford to volunteer so much of my time for this. Bottom line is, there are already several viable solutions, so pick one.
