iSG Home Assistant Add-ons Guide for Local Smart Homes
iSG becomes more useful when Home Assistant is not just installed, but organized. Add-ons such as MQTT, Zigbee2MQTT, Z-Wave JS UI, Matter Server, and Node-RED can turn one gateway into the control center for lights, sensors, IR appliances, dashboards, and local automations.
This guide explains how to plan iSG Home Assistant add-ons without making the system harder to maintain. It is designed for users choosing between iSG Box SE and iSG Display Max, or expanding an existing iSG setup with presence, IR, RF, cameras, and room dashboards.
Start with the Role of the iSG Gateway
Before installing more add-ons, decide what job the iSG device should perform. Some homes need a quiet local gateway that sits in a cabinet. Others need a visible room controller with a screen. The add-on plan changes depending on that role.
Local gateway
Run Home Assistant, MQTT, automations, and device integrations with fewer visible controls.
Room dashboard
Use iSG Display Max where family members need visible scene control, room status, and quick manual overrides.
Automation bridge
Connect presence sensors, IR appliances, RF devices, cameras, and Matter devices into one local workflow.
iSG Box SE vs iSG Display Max for Add-ons
| Use case | iSG Box SE | iSG Display Max | Best next step |
|---|---|---|---|
| Compact Home Assistant gateway | Best fit | Works, but screen may be unused | View iSG Box SE |
| Wall or room control surface | Needs a separate screen | Best fit | View iSG Display Max |
| Camera dashboard and room scenes | Good as gateway | Better for visible dashboard | Read the local camera dashboard guide |
| Presence, IR, RF room automation | Good local automation base | Good base plus room UI | Read the room automation blueprint |
Recommended Add-ons and What They Do
A healthy Home Assistant system does not install every add-on at once. Start with the services that match your devices, then add dashboard and automation layers after the basics are stable.
| Add-on or service | Typical role | Use when | Risk to avoid |
|---|---|---|---|
| MQTT Broker | Local message layer | You use MQTT devices, eRemote HA, Zigbee2MQTT, or automation bridges. | Do not lose credentials; document username, password, and broker address. |
| Zigbee2MQTT | Zigbee device bridge | You want local Zigbee sensors, buttons, plugs, or lighting inside Home Assistant. | Avoid changing coordinator ports without updating the add-on config. |
| Z-Wave JS UI | Z-Wave device bridge | You use Z-Wave locks, sensors, switches, or relays. | Back up keys and network settings before migration. |
| Matter Server | Matter device support | You want Matter-compatible devices to appear inside Home Assistant. | Keep network and IPv6 behavior consistent when troubleshooting. |
| Node-RED | Visual automation logic | You prefer flow-based rules for scenes, alerts, and multi-room logic. | Do not duplicate automations in both Node-RED and native Home Assistant unless needed. |
Practical rule: install fewer add-ons first, document the ports and credentials, then expand after backups and core automations are stable.
Access Add-ons Safely from the Local Network
Most iSG add-on work should happen from a browser on the same WLAN or LAN. Keep a small local reference table for the device IP address, Home Assistant URL, add-on URLs, and credentials. This is especially useful before firmware updates, router changes, or gateway migration.
| Item | Example local URL | What to record |
|---|---|---|
| Home Assistant | http://iSG-IP:8123 | Admin login, backup location, current version |
| iSG Web | http://iSG-IP:1688 | Device access method and network notes |
| Zigbee2MQTT | http://iSG-IP:8080 | Coordinator path, network key, MQTT settings |
| Z-Wave JS UI | http://iSG-IP:8091 | Z-Wave keys, controller details, device list |
| MQTT Broker | iSG-IP:1883 | Broker address, username, password, TLS notes |
Setup Order for a Cleaner iSG System
Create a backup first
Before enabling new services, create a Home Assistant backup and keep a copy outside the device. If you need a full recovery workflow, use the Home Assistant backup and restore guide for iSG.
Confirm the local IP and access path
Record the iSG IP address, Home Assistant URL, and add-on URLs. This saves time when a browser bookmark, router, or DHCP lease changes.
Add the message layer
If your plan includes MQTT devices, eRemote HA, Zigbee2MQTT, or bridges, configure MQTT before building complex automations.
Add device bridges one at a time
Enable Zigbee, Z-Wave, Matter, IR, or camera integrations separately. Test each layer before adding the next one.
Build room-level automations
After devices are stable, connect room scenes, presence, IR control, and dashboards. Start with one room before copying the same pattern to the whole home.
How iSG Add-ons Connect to LinknLink Products
| Product | Role in the system | Best add-on or integration path | Link |
|---|---|---|---|
| iSG Box SE | Compact Home Assistant gateway | Home Assistant core, MQTT, device bridges | iSG Box SE product page |
| iSG Display Max | Gateway plus visible dashboard | Home Assistant dashboard, scenes, camera and room controls | iSG Display Max product page |
| eRemote HA | Local IR control | MQTT and Home Assistant automation scenes | eRemote HA product page |
| eMotion Air | Flexible presence sensing | Home Assistant room presence and scene conditions | eMotion Air product page |
| eMotion Pro | Presence plus IR room control | Presence-based AC, TV, fan, and media scenes | eMotion Pro product page |
Example Local Automation Stack
Here is a practical stack for a local smart home that uses iSG as the base and LinknLink devices as room endpoints.
Gateway: iSG Box SE or iSG Display Max Core services: Home Assistant MQTT Broker Zigbee2MQTT or Z-Wave JS UI if needed Matter Server if Matter devices are used Room devices: eMotion Air for flexible presence eMotion Pro for presence plus IR control eRemote HA for dedicated AC, TV, projector, or fan control Automation layers: Native Home Assistant automations for simple rules Node-RED for multi-step room logic if needed Dashboard cards on iSG Display Max for manual override
When to Use Native Automations vs Node-RED
Native Home Assistant automations are usually enough for simple rules: if presence is detected, turn on a light; if the room is empty, turn off a device after a delay. Node-RED becomes useful when a flow has many branches, repeated conditions, or visual troubleshooting value.
| Automation type | Use native Home Assistant | Use Node-RED |
|---|---|---|
| Presence lighting | Yes, simple and readable | Only if multiple rooms share a complex flow |
| AC and TV IR scenes | Yes for fixed scenes | Useful when many conditions decide which IR command to send |
| Guest or sleep mode | Works for simple toggles | Useful for multi-step state logic |
| Debugging device bridges | Keep in native logs first | Use only after the core add-on is stable |
Related Guides for the Next Step
- Home Assistant backup and restore guide for iSG
- Home Assistant local camera dashboard with ONVIF, RTSP and iSG Display Max
- Local control smart home guide for Home Assistant
- Home Assistant room automation blueprint with mmWave, IR and RF
- Home Assistant AC automation with IR blaster and presence sensors
FAQ
Which iSG device is better for Home Assistant add-ons?
Use iSG Box SE when you want a compact Home Assistant gateway. Use iSG Display Max when you also want a visible dashboard and touch control surface in a room.
Do Home Assistant add-ons need cloud access on iSG?
Core add-ons such as MQTT, Zigbee2MQTT, Z-Wave JS UI, Matter Server, and Node-RED can support local smart home control when configured on the same LAN.
What should I check before enabling more iSG add-ons?
Create a backup, confirm the device IP address, document ports and credentials, and add only the services your automation plan needs.
How do iSG add-ons connect to presence, IR, and RF automation?
Use iSG as the local Home Assistant base, then connect presence sensors, eRemote HA IR control, and RF or Matter devices through the appropriate integrations and add-ons.
Maintenance note: add-on sprawl makes recovery harder. Keep a current backup and a short local document with URLs, ports, and credentials before changing routers, firmware, or device bridges.
Build a Local iSG Home Assistant Stack
Start with the right iSG gateway, add only the services your devices need, and connect room automations after the core add-ons are stable.