User Profile

I have an electric "garage door", but it's not an "overhead" door that opens upwards, as seems to be common in the US. This is a motorized sliding gate. It can be told to open fully for a car to cross, or stopped anywhere in the middle, for example for a person to go out.I want to make a HomeKit bridge for it, and looking at the non-commercial HAP spec, I'm struggling to see how it fits into the predefined HomeKit services.The "Garage Door Opener" service has a "Current door state" characteristic, which can report the door is open, closed, opening, closing, or stopped while not fully open or closed. This seems great for my use case. However, the "Target door state" characteristic can only be used to "open" or "close". This is more problematic; I don't see a way to tell it to stop it while it's moving, before it reached the end state.In the "Door" service, there is a "Hold Position" optional characteristic, which "causes the service such as door or window covering to stop at its current position". That, too, sounds great for me. However, the Door service has required "Current Position" and "Target Position" characteristics, but I can't know what's the exact position of the gate, and I can't tell the gate to move from its current position to another exact one, I can only tell it to "open" or "close". So it seems the "Door" service is unsuitable for this kind of electric gate.What's the appropriate configuration for this? Can I use the Hold Position characteristic in the Garage Door Opener service? Does the Home app support it? Or should I use the Door service?

Is there an API for an app running on arm64 to know whether Rosetta is available? Currently that's always "yes", if you're on arm64 then Rosetta is always available and x86_64 apps can run on it. But I'm sure in future OS versions Rosetta may go away. What is the future-proof for an arm64 app to know if x86_64 is supported before it starts an x86_64 subprocess?