CasaSmart guide
How to keep local control and add voice control.
CasaSmart
Many homes in Moldova arrive at the same picture: under one roof there is an iPhone, a Yandex speaker with the Alice voice assistant, and a Home Assistant server that holds together lights, sockets, thermostats, blinds, and sensors from different brands. The natural question is how to control all of it without jumping between five apps. The practical answer is to make Home Assistant the hub and, on top of it, publish a chosen set of devices into two parallel voice ecosystems: Apple Home for family members on iPhone, iPad, or HomePod, and Yandex Alice for those who talk to a speaker in Russian. This guide shows exactly how, step by step, with a focus on what you expose, what stays private, and what depends on the internet. CasaSmart configures such mixed setups for clients regularly, because the reality here is not one clean brand but a blend that needs to be unified intelligently. You will see where everything stays fully local and where, by contrast, a cloud dependency appears that is worth knowing about in advance, so an outage brings no surprises.
Apple Home connects to Home Assistant through the HomeKit Bridge integration, which is native and runs directly on your own server. In effect, Home Assistant presents itself on the local network as a HomeKit bridge, and the iPhone discovers it and adds it via a pairing code, just like a certified device. The big advantage is that this bridge works on the local network, without passing through anyone's servers, as long as the phone and the server are in the same home. With Yandex Alice the story is different: Alice does not see your server on the local network and expects to talk to a public endpoint secured over HTTPS. That is why the Yandex integration requires an internet-reachable domain, a valid certificate, and a reverse proxy that routes requests to Home Assistant. Understanding this core difference — Apple local, Yandex over the internet — completely changes your network and security plan, so we treat it explicitly rather than hiding it behind buttons.
A third thread we keep in hand throughout is privacy. Exposing a device to a voice assistant is not free in data terms: room names, the device list, and the commands you give may pass through external services, especially with Yandex, where the voice stream is processed in the cloud. That is why our consistent advice is to publish only what you genuinely need to command by voice, not your entire inventory of entities. A smart lock, an alarm, or a camera deserves separate thought before being handed to an assistant. The guide shows how to filter exactly what enters each ecosystem, how to name rooms and scenes so a command sounds natural, and how to keep fine control in Home Assistant, which remains the source of truth. In the end you get a home where a short phrase in Romanian or Russian makes exactly what you planned happen, without giving up your privacy.
TL;DR
Use Home Assistant as the hub. For Apple Home, enable the HomeKit Bridge integration and add it on the iPhone with the pairing code — all local. For Yandex Alice you need a public domain, an HTTPS certificate, and a reverse proxy, because Alice works over the internet. Expose only the devices you genuinely need by voice, name rooms and scenes clearly, and remember the Yandex flow passes through the cloud.
Step 1
Before any integration, decide what you want to control by voice and by app: lights, sockets, thermostats, blinds, sensors. Do not expose everything — a home with hundreds of entities becomes hard to use in both Apple Home and Alice. Make sure the Home Assistant server runs stably, is updated to a recent version, and has a fixed local IP on the router so the bridge stays reachable. Check that mDNS works on the local network, since Apple Home discovers the bridge through it. For Alice you will additionally need a public domain and a valid HTTPS certificate. Note from the start which entities go to Apple only, Alice only, or both, to avoid duplicate commands and room confusion.
Step 2
In Home Assistant go to Settings, then Devices & Services, click Add Integration, and search for HomeKit Bridge. This integration is native, so you install nothing extra. During setup you are offered the option to include or exclude whole domains — for example light, switch, cover, climate — or to pick entities manually. We recommend starting with a small, easy-to-test selection and expanding it later. Once you confirm, Home Assistant creates a HomeKit bridge and generates a numeric pairing code, which you will see in the notification and on the integration page. Leave this window open, because you will need the code in the next step. If the server has multiple network interfaces, make sure the bridge listens on the correct local network.
Step 3
On the iPhone or iPad open the Home app, tap the plus in the corner, and choose Add Accessory. Scan the code shown by Home Assistant or enter it manually via the "more options" / "I don't have a code" path. The phone must be on the same local network as the server. Apple Home will warn that it is an uncertified accessory — this is normal for a HomeKit bridge created by Home Assistant, tap Add Anyway. After pairing, all exposed entities appear as accessories you can assign to rooms. Correct room assignment matters, because Siri uses the room name in commands, for example "turn off the light in the kitchen." If you later add new entities to the integration, they appear automatically, but you will need to assign them to the right rooms yourself.
Step 4
Now go back into Home Assistant and refine the list. In the HomeKit Bridge integration options you can switch between "include" and "exclude" mode and pick precisely what goes through. The practical recommendation is to include the types you use often via Siri — lights, sockets, blinds, thermostats — and leave out technical sensors, diagnostic entities, and anything that would clutter the Home app. Be careful with sensitive devices: a lock or camera reaches Apple Home with specific functions, and Apple treats them with extra security requirements. Consider whether you truly want them voice-controllable. After every change to the exposed set, restart the integration or Home Assistant so the bridge reflects the change. Check in Apple Home that unwanted entities are gone and only the useful ones remain.
Step 5
Unlike Apple, Yandex Alice does not see your local server and expects a public endpoint secured over HTTPS. You need an internet-reachable domain and a valid certificate. The cleanest options are a reverse proxy, such as Nginx Proxy Manager or Caddy, which obtains certificates automatically, or a Cloudflare Tunnel, which avoids opening ports directly on the router. Whichever path you take, expose only what is needed, keep Home Assistant authentication enabled, and do not publish the admin panel unprotected. Verify from outside your network that the address responds correctly over HTTPS and the certificate raises no warnings. This endpoint will be the foundation of the Yandex integration; if it goes down or the certificate expires, Alice can no longer command the devices, even if Home Assistant runs perfectly at home.
Step 6
To link Home Assistant to Alice you typically use a community Yandex Smart Home integration, installable via HACS, which presents your entities as the devices of a smart-home maker inside your Yandex account. This is not an official relationship but a bridge built through the public Yandex integrator interface. The process involves configuring the integration in Home Assistant, mapping entities to the types Alice understands — light, switch, blind, climate — and then, in the Yandex app, adding this provider and authenticating against your HTTPS endpoint. After pairing, the devices appear in the Yandex app and can be assigned to rooms. Read the documentation of whichever integration you choose, because the exact authorization steps differ. Test with a single bulb first, to confirm the chain works end to end.
Step 7
The real value appears when you move from individual devices to scenes. In Home Assistant create scenes or scripts — for example "Evening," which turns off ceiling lights, switches on warm lamps, and lowers the blinds. These scenes can be exposed to both Apple Home and Yandex so you trigger them with a single phrase. The key is naming: choose short names, without words that are easily confused and that recognize well. In Apple Home you can also create your own scenes, combining accessories from several bridges. For Alice, exposed scenes can be started by voice or through scenarios in the Yandex app. Test the real pronunciation: say the command aloud in Romanian and Russian and adjust the name if the assistant does not catch it. Keep the source of truth in Home Assistant so the logic is single, whichever assistant you trigger it from.
Step 8
Finally, review what you exposed and why. Remember the fundamental difference: the HomeKit bridge works locally between iPhone and server, whereas voice commands to Alice pass through Yandex cloud services, including room and device names. So do not expose sensitive things to Yandex — locks, alarms, or cameras — unless you consciously accept that trade-off. Plan also for an internet outage: Apple Home keeps working locally, but Alice does not. Set a maintenance routine — periodically check the HTTPS certificate expiry, Home Assistant and integration updates, and occasionally test a command on each ecosystem. If you want a robust configuration, with proper security and no data exposed needlessly, CasaSmart can design and install the whole chain in your home.
The most common mistakes: exposing all entities at once so the apps become chaos; forgetting to give the server a fixed IP, so the HomeKit bridge vanishes after a router reboot; opening ports directly on the router without a proxy or tunnel, leaving Home Assistant vulnerable; ignoring HTTPS certificate expiry, so Alice suddenly stops; and exposing locks or cameras to Yandex without considering that the flow passes through the cloud.
Yes. Home Assistant stays the hub, and you publish the same devices or scenes to both ecosystems in parallel. Family members on iPhone command via Siri and Apple Home, while those who talk to a Yandex speaker use Alice. The logic and source of truth remain in one place, in Home Assistant, which avoids duplicating automations and keeps behavior consistent.
The HomeKit bridge presents itself on your local network, and the iPhone talks to the server directly, without intermediaries, as long as you are in the same home. Yandex Alice, by contrast, is built as a cloud service that contacts a public endpoint; it does not see your server on the local network. That is why Alice needs a domain, HTTPS, and a reverse proxy or tunnel.
Generally, the device and room names, their state, and the commands you give. With Yandex, the voice stream and this information are processed in the cloud, since the integration goes over the internet. With Apple Home, communication stays mostly local between iPhone and server. That is why we recommend exposing only what you need to command by voice and avoiding, especially toward Yandex, sensitive devices such as locks or cameras.
Partly. Apple Home, through the HomeKit bridge, works on the local network, so commands from the home iPhone keep working even without internet. Yandex Alice, being a cloud service, cannot send commands when the connection drops. Local automations in Home Assistant keep running independently. For resilience, base important scenarios on local automations, not on voice alone.
Yes. CasaSmart is a turnkey smart-home integrator and regularly configures such mixed setups, with Home Assistant as the hub, a HomeKit bridge for Apple Home, and a secured connection to Yandex Alice. We can design the network, the HTTPS certificate, and the proxy, choose what to expose and what stays private, name the scenes for voice, and install it all correctly. The initial consultation is free; the on-site visit and detailed design are paid services.
● CasaSmart · Chișinău
CasaSmart can configure the Home Assistant automation and test it on real devices.