I'm about to move from Android to iPhone. We have had alexa shut off for a while, but i would like to get at least limited voice control back. Is this something that would be possible?
What other things do I need to be aware of or address with iPhone?
Are you wanting to re-use the Amazon Echo devices you already have? If so, you can still manage Alexa via the iOS Alexa mobile phone app.
Or, are you wanting to use Apple's Siri for voice control? If so, one would either use Hubitat's new HomeKit integration to add Hubitat devices (with some known restrictions) to the Apple Homekit ecosystem. OR, use Homebridge with either one of the two community developed Homebridge Plugins for Hubitat.
You'd also probably want to have at least one modern AppleTV device OR Apple HomePod Mini device in your home. These devices will act as a "HomeKit Hub" for your house, allowing you to control devices via the "Home" app on your phone or iPad when away from your house. The HomeKit Hub will also run any HomeKit automations locally.
If you go all-in, the Apple Watch also has Siri functionality, which can be very convenient vs pulling out your phone.
Nope. "Hunches" caused drastic loss of WAF points. I no longer trust Alexa.
Yes. That is what I was thinking. With the Homekit support being fairly new is there a prefered way to go? Does Homebridge require xtra hardware, like a raspberry pi or anything?
I have no issue with picking up 2 or 3 home pods.
That is my intention, though that extent may be a few months off. I need to get my wife switched over first as well.
People's preferences differ, but there are a few things to consider about the native integration vs. Homebridge.
Homebridge runs on another device that has to be always-on, an RPi is a common option. But it's been in development for a lot longer than the native Hubitat HomeKit integration, which is still considered in beta. Check out the homebridge github wiki page for all the supported setup methods.
@bertabcd1234 put together a new page in the hub docs on the integration, which includes some details on the types of device that can't be supported, as the team is going for an official Apple certification (which Homebridge doesn't have, and never will).
Edit: Forgot to mention it's also possible to run both the native HomeKit integration and Homebridge at the same time. It doesn't have to be either/or. For example, if you really want door locks paired with Hubitat to be included, Homebridge is the only option. So you can have your door locks, or other unsupported devices (because of the restrictions Apple enforces), integrated through Homebridge, and most/all other devices integrated with the new, native Hubitat HomeKit app.
I personally run Homebridge on my always-on Windows 10 home server. Since that server is up 24x7, and also handles InfluxDB, Grafana, Node-RED, and Plex Media Server duties, I figured why not try to run it on the same system. I have been pleasantly surprised at how well and mature Homebridge is these days. As such, I really have not spent too much on Hubitat's new HomeKit integration. I figured I would wait a little while longer for it to mature. Also, some of my devices will not be supported by Hubitat's Official HomeKit integration. Thus, I will be patient.
As for other things you can use HomeKit for... one popular option is to use it for Geofencing based 'presence', instead of the other options available. I personally have been using Locative on my iPhone for a few years. It has also been very reliable for me, and thus I am not motivated to make a change at this time. YMMV, of course.
I also have Homebridge running in a docker container on a Windows NUC PC that's always on and have been pretty happy with it. So I'm similarly in no rush to switch over to the built-in HomeKit integration and will continue using Homebridge for the unsupported device types even after the native integration has matured.