I don’t disagree with you about the lack of standardization - that’s what’s attractive about Ignition to me, the fact that you can connect to a wide array of devices using just a TCP driver, MQTT, or web dev endpoints. In my head, if Ignition can’t connect to a device, it’s not the fault of Ignition for not supporting some novel or legacy protocol, it’s the backward thinking of the device manufacturer / designer.
I understand what you’re saying that it’s more difficult than I’m making it seem, but man, a commercial license for home automation would be so nice. Even if it was Ignition Maker exactly (except suitable for revenue-generating use) and no technical support, I would still pay for this license. Even for non-profit use - a use-case that has nothing to do with automation but that can leverage the fast development Perspective provides.