wuench
Senior Member
ChrisCicc said:wuench, since you mention that, I have a question for you if you don't mind. In order to prevent the issues you described, CastleOS bypasses the INSTEON scene/group functionality, and sends direct commands to each light in a software defined scene, verifying and retrying as needed, and guaranteeing all devices in a scene are activated as needed. We've heard from some users that they want us to implement normal INSTEON scene functionality, what are your thoughts about this?
A long time ago in a galaxy far far away, I wrote my own VB app for Insteon. This was right after it came out. And I never released it, because I was never quite happy with it. So I appreciate how difficult it is to do correctly. The programming of linking is slow and a lot of validation is required by the developer. Implementing control is much easier, in comparison. And I think most of your competitors just do control.
Personally I think even doing native control isn't the sweet spot. I think supporting devices like the ISY and Vera are. The ISY supports linking, etc, but they add some additional intelligence to make all the hassles of linking transparent to the users. They do additional linking and programming so that no matter what the user sees a single scene. (I think Powerhome does something similar.) And their API is much easier to deal with than the PLM. And I hear they are even doing single scenes for ZWave/Insteon which is pretty cool.
So I would take a look at your competitors and see what they are doing and how well they are doing it. If you want to support linking you have to do more than just the plain old Insteon way to do it right. And it will take a lot of your time to do and then support in the future.
CQC I know just does control, and I think most users are using the ISY vs. the native PLM driver....