That was does work through the Abode HE internet integration. I was hoping to be able to do the entire thing local with HEs, then new, Homekit integration.
OK, may be some typos in your response so perhaps I misunderstood. But I think you have an interesting idea. There are these options:
-
HE Abode Integration -> Internet -> Abode servers:
Sends HE the Abode devices and their status via internet, allowing HE control of Abode modes (Standby, Home, Away) and HE automations based on Abode Device status. It does NOT allow HE only devices to trigger Abode alarms. -
HK Abode Integration -> Abode Hub:
Sends HK the Abode devices and their status (some say locally) allowing HK automations based on Abode Device status. (At least this is my understanding of it; I don't have this). I presume it also does not allow HK only devices to trigger Abode alarms. -
HE standard HK Integration:
Allows HE devices to be exposed to Homekit. I presume this is local but I'm not sure. I can see HE devices in the HK app on an Ipad and control them from the Ipad, so I presume they can also be controlled via HK automations. But devices first need to be in HE. -
HE new HK Integration:
I understand this works only on the C-8 pro, and allows everything the HE standard HK intergration allows, and also allows HK devices to be exposed to HE without first being in HE. I presume this is local but I'm not sure. Presumably these are devices first paired with HK, or brought into HK via integrations. Don't know if it allows HE to also control these devices or just see their status.
I think your post is saying you used 2. above to bring the Abode devices into HK, then tried to use 4 to bring the Abode devices from HK into HE, and you get only the hub (and presumably can set it's mode?), but not any of the Abode devices. So my question is whether the HE new HK integration allows child devices? Because I think maybe on the backend, that is what they are?
