Home Assistant and local smart-home control for NYC homes and buildings

What local control means, and why it matters

Most consumer smart-home products depend on a chain of links: the device, a hub, the vendor's servers and a phone app. If any link fails, control can stop. A local system removes the vendor's servers from the chain. The controller sits in your network closet, talks to devices over your own Wi-Fi, Zigbee, Z-Wave or Thread radios, and runs automations without an internet connection.

Recent vendor shutdowns and changes show where the risk lies. In each case, features that relied on the vendor's cloud stopped, while devices with a local path continued to work.

The lesson is not that every vendor will fail. It is that a home should keep basic functions when one does, and that even local features can change with a firmware update.

What Home Assistant is

Home Assistant is open-source home automation software that runs on a small computer inside the home. It offers thousands of integrations, provides dashboards and automations, and keeps its data on your own hardware. The project is maintained under the Open Home Foundation, and Nabu Casa, its commercial sponsor, sells the Home Assistant Green controller, the Connect radios and an optional Home Assistant Cloud subscription.

Every Home Assistant integration declares an IoT class, which is shown on its documentation page. This label is the most useful check before buying any device.

• Local Push: the device reports changes over your network immediately. This is the best case.
• Local Polling: Home Assistant asks the device for its status on a schedule over your network. It is fully local and slightly slower.
• Cloud Push or Cloud Polling: Home Assistant communicates through the vendor's servers. It works only while the internet and the vendor's service are available.
• Assumed State: Home Assistant cannot read the device's state back, as with some one-way radio devices.

Many inexpensive Wi-Fi plugs and switches built on the Tuya platform connect through the Tuya integration, which is Cloud Push. Owners who prioritize privacy should prefer devices with a local integration or a Zigbee, Z-Wave or Matter version.

Home Assistant compared with other platforms

Home Assistant is not the only local option. The table summarizes the main platforms as described by their publishers in October 2026. Prices are manufacturer list prices in US dollars before tax.

Hubitat and Homey are closed-source local hubs. LG acquired a majority stake in Athom, the maker of Homey, in 2024. openHAB is maintained by the openHAB Foundation and, like Home Assistant, is open source.

Controller hardware and radios

• Home Assistant Green ($199): the simplest dedicated controller, with a quad-core processor, 4 GB of memory, 32 GB of storage and gigabit Ethernet. It has no built-in Zigbee, Thread, Z-Wave or Bluetooth radio.
• Connect ZBT-2 ($49): a Zigbee or Thread adapter. It cannot run both at the same time, so a home that needs both uses two.
• Connect ZWA-2 ($69): an 800-series Z-Wave adapter that runs a standard Z-Wave mesh and Z-Wave Long Range at the same time on US frequencies.
• Home Assistant Yellow: production ended on October 15, 2025, and the project states it will continue to receive software support. Existing units keep working.
• Mini PC: a small x86-64 computer offers more headroom for camera recording, voice processing and large installations.
• Raspberry Pi 4 or 5: workable, though we prefer SSD or eMMC storage over memory cards for long-term reliability.
• Virtual machine or NAS: suitable for owners with IT support. A Container installation does not include apps (add-ons), so Thread and Z-Wave need extra setup.

We place the controller on a battery backup (UPS) together with the router and network switch. Home Assistant can monitor the UPS through its NUT integration and shut down cleanly during a long outage. Radio adapters go on a shielded USB 2.0 extension cable, away from Wi-Fi access points, so the Zigbee network is not affected by interference.

Remote access and voice control

Remote access should not expose the house to the internet. The two sound approaches are the optional Home Assistant Cloud subscription from Nabu Casa, or a VPN such as WireGuard or Tailscale that connects your phone to the home network. Opening a router port directly to Home Assistant is not recommended.

Alexa and Google Assistant integrations require their vendors' clouds. Home Assistant also includes its own voice assistant, Assist, which can run locally; its quality depends on the hardware and the language, so we review it with each owner before relying on it.

Limits to plan for

• Setup time: pairing, naming, dashboards and automations take from several hours for a few rooms to several weeks for a full house.
• Updates: Home Assistant releases updates frequently, and some include breaking changes. Each update should follow a backup, and backups should be stored off the controller.
• Support: Home Assistant is community-supported, with no vendor hotline. Ongoing care comes from an owner who enjoys the work, a service agreement, or a deliberately simple configuration.
• Everyday use: every wall switch must still work as a switch when the controller is off. We design to this rule.
• Cloud-only products: some devices have no local path, including Ring and Blink cameras, several Wi-Fi lock apps and Tesla vehicle control.
• Vendor firmware: a manufacturer can reduce local features in an update, as Enphase did with battery controls.

Small residential buildings and the Tenant Data Privacy Law

NYC's Tenant Data Privacy Law (Local Law 63 of 2021) applies to owners of class A multiple dwellings that use smart access systems, such as key fobs, RFID cards, phone apps or biometrics, for the building, common areas or units. According to HPD, owners must:

• Provide tenants with a data retention and privacy policy.
• Obtain express consent, in writing or in the app, before collecting reference data.
• Collect only the minimum data needed, such as name, unit, doors, contact method, lease information and the time and method of access for security.
• Destroy authentication data within 90 days unless it is anonymized.
• Not sell or share data without consent or a legal requirement, not track tenants outside the building, and not use the data to harass or evict.
• Not require tenants to use a smart access system to enter their own unit, so a key option for unit doors must remain.

A locally hosted access system keeps the data on a building server rather than a vendor cloud, which makes retention limits and deletion easier to demonstrate. This is a summary, not legal advice; owners should review their obligations with counsel and HPD. We also separate the owner's building network from tenant networks.

How we plan and install a local system

We start with your floor plan and the devices you already own, and we mark which ones can run locally, which need a hub, and which depend on a vendor cloud. We then plan the controller location, radios, network closet and cabling as one low-voltage scope. Smart switches and other line-voltage work are installed by our licensed partner electricians.

At handover, you receive the device list, the configuration, backups and all administrator credentials in your own name. Because Home Assistant is open source and uses standard radios, another qualified professional can maintain the system later if needed.