Bring a mixed-vendor smart home into one FrontierStack view

Published 2026-08-20

A home automation setup rarely stays with one vendor. The first smart plug comes with its own app; the lights use Zigbee; a few scenes live in Apple Home; Home Assistant ties together everything that does not quite fit. Before long, the useful settings are scattered across browser bookmarks, notes and several phone apps.

FrontierStack gives that mixed setup an operational home on your Mac. It keeps connection details together, stores secrets in Keychain and puts devices into physical Places such as Home, Garage and Workshop. It does not replace every vendor app or copy their private databases. Pairing, firmware updates and account management still belong with the platform that owns them.

Start with the shape of your home

Open Setups and choose Home Automation. This trims the sidebar to the services that matter here: home automation, IoT, MQTT, cameras, networking and remote hosts. It changes the workspace, not the underlying devices; you can switch setups without losing configuration.

Next, open Places and create locations that match how you think about the property. A simple house may need Home, Garage and Garden. A larger setup may use Main House, Workshop and Holiday Cabin. Avoid starting with every room; broad locations are easier to maintain, and you can split them later when the board becomes crowded.

Places is deliberately vendor-neutral. A SwitchBot plug, Zigbee sensor, camera, UPS and discovered network device can sit beside one another because they serve the same location. The board answers a practical question: what is installed here, and is it reachable?

Connect each platform once

FrontierStack keeps ordinary connection settings, such as a local host, port or entity ID, in its local configuration. Tokens, API secrets and passwords go into the Mac's Keychain. That gives you one place to update a changed credential without putting secrets in a spreadsheet or a note.

• SwitchBot: save the cloud token and secret once; FrontierStack verifies the account, lists physical and infrared devices, and offers the controls each device supports.
• Zigbee2MQTT: save the MQTT broker address, port and optional username; the broker password stays in Keychain.
• deCONZ or Phoscon: save the gateway address and port; keep the API key in Keychain.
• Home Assistant: save one base URL and one long-lived access token; individual outlets then need only their entity IDs.
• Apple Home: no HomeKit database is copied. FrontierStack lists Apple Shortcuts that contain Home actions and runs the scene or accessory action through macOS.

1. Add SwitchBot devices

In the SwitchBot app, open Preferences → About, tap the app version and open Developer Options. Copy the token and secret into FrontierStack's SwitchBot pane, then choose Save & Verify.

FrontierStack will list plugs, Bots, curtains, locks, sensors, hubs and the infrared remotes exposed by a Hub. Test one harmless action first: turn on a lamp plug or press a Bot. Cloud commands require a SwitchBot Hub for BLE-only devices; if you want a fully local route, expose those devices through Home Assistant's SwitchBot integration instead.

Pin the devices you want on the Places board. If this account is dedicated to the property, Automatically pin new devices saves work as the system grows. FrontierStack checks the account for newly added devices about once a day.

2. Bring in Zigbee

Open Zigbee and choose the bridge that already runs your network: Zigbee2MQTT or deCONZ/Phoscon. Enter the broker or gateway address, its port and the credential. Refresh the device list; switches and lights receive an on/off control.

If you are building the Zigbee network from scratch, connect a supported coordinator such as a Sonoff Zigbee Dongle, Home Assistant Connect ZBT-1 or ConBee/RaspBee to the machine running the bridge. Allow Devices to Join opens a 120-second pairing window. Pair one room at a time, give each device a useful name at the bridge, then pin it to the right Place.

On a Mac, do not assume a coordinator plugged into the computer will automatically appear inside Docker Desktop. USB passthrough is the awkward part. Run Zigbee2MQTT directly on the Mac, or run it on a Linux machine or Raspberry Pi and point FrontierStack at that broker.

3. Use Home Assistant as the common power adapter

Home Assistant is useful when a plug is already exposed there, including a Zigbee plug managed by ZHA or Zigbee2MQTT. In Power Control, enter the Home Assistant base URL and create a long-lived token from your Home Assistant profile. Add each outlet with an entity ID such as switch.nas_plug.

The same Power Control pane can also hold local Shelly and Tasmota plugs, private on/off HTTP endpoints and monitored UPS units. This is where separate vendor platforms become one practical control surface: the NAS plug can come from Home Assistant, the workshop relay can be Shelly, and the rack PDU can use a local HTTP endpoint.

Keep the first pass manual. Confirm that status, On, Off and Cycle target the correct physical outlet. A clean name such as Office: NAS power is safer than Plug 7, especially when someone else has to use it six months later.

4. Add Apple Home scenes without pretending to own HomeKit

Apple does not expose the HomeKit homes, rooms and accessory database to a normal macOS app. FrontierStack therefore uses a smaller, dependable bridge: Apple Shortcuts.

Create a Shortcut containing a Home action, such as Set Good Night scene or Turn off downstairs lights. Open Apple Home in FrontierStack and refresh; the Shortcut appears with a Run button. The Home app remains the place for pairing accessories, changing rooms, managing family access and commissioning Matter devices.

5. Organize by place, not logo

Return to Places after each platform is connected. Pin the devices worth watching, then assign them to Home, Garage, Workshop or another saved location. Cameras added through AV Feeds and UPS units from Power Control can join the same board as SwitchBot and Zigbee devices.

Use names that combine location and purpose: Garage: side-door sensor, Office: desk plug, Workshop: camera north. Vendor model numbers belong in the detail view; the board should be readable at a glance.

Add automation only after the map is trustworthy

A tidy inventory makes later automation safer. Link a smart outlet to the host it powers, select a ping, TCP or HTTP health check, and test a manual power cycle. If you later enable automatic recovery, FrontierStack waits for repeated failures, observes a cooldown and stops after three attempts. Use that for equipment you can safely hard-reboot; do not attach it casually to storage that may be writing data.

If Home Assistant is your household dashboard, FrontierStack can also publish its Mac, server, router and agent health to an MQTT broker and create matching Home Assistant discovery entries. This sends operational health into Home Assistant; it does not duplicate every vendor device.

What stays in the vendor platforms

One place for settings does not mean one app owns everything. Keep device pairing and firmware updates in SwitchBot, Zigbee2MQTT, Phoscon or Home Assistant. Keep HomeKit rooms, family permissions and Matter commissioning in Apple Home. Use FrontierStack for the connection registry, secure credentials, cross-vendor status, Places board and recovery controls.

That division ages well. You can replace a plug vendor or move Zigbee to another bridge without redrawing the whole property. Update the connection in FrontierStack, check the affected devices, and keep the same location model.

A short setup checklist

1. Select the Home Automation setup.
2. Create a few broad Places.
3. Connect SwitchBot and verify one safe command.
4. Connect Zigbee2MQTT or deCONZ; pair and name devices room by room.
5. Add the Home Assistant URL and token; register only the outlets you need.
6. Create Apple Home Shortcuts for the scenes worth running from the Mac.
7. Pin cameras, UPS units and important devices to Places.
8. Test every control manually before enabling recovery automation.
9. Record which tasks still belong in each vendor app.

The result is not a mythical universal smart-home app. It is something more useful: one maintained map of the property, one secure place for platform connections and one screen for the controls you use when something needs attention.

Continue with the home lab overview, getting started guide and automation guide.