Integrations
Home Assistant integration
Install the SpacePC integration, discover local devices and troubleshoot their connection to Home Assistant.
What the integration does
The SpacePC integration connects compatible firmware directly to Home Assistant over the local network. Devices advertise _spacepc._tcp.local. over mDNS and expose the versioned SpacePC Local API. A cloud account and MQTT broker are not required. MQTT can still be enabled independently when another system needs it.
One integration supports different SpacePC projects. Home Assistant creates entities from the capabilities reported by each device, including sensors, binary sensors, switches, lights, fans, diagnostics and firmware updates where the firmware provides them.
Requirements
Home Assistant 2026.5 or newer
SpacePC integration 0.1.3 or newer
SpacePC firmware with Local API v1 and mDNS discovery
Home Assistant and the device on a network that permits local HTTP and mDNS traffic
Completed Wi-Fi setup on the SpacePC device
Install with HACS
Open HACS in Home Assistant.
Add https://github.com/spacepc-de/home-assistant-spacepc as a custom repository in the Integration category, or open https://my.home-assistant.io/redirect/hacs_repository/?owner=spacepc-de&repository=home-assistant-spacepc&category=integration.
Install the newest stable SpacePC version.
Restart Home Assistant when HACS requests it.
Open Settings → Devices & services and confirm the discovered device.
Manual installation
Copy custom_components/spacepc from the repository into config/custom_components/spacepc and restart Home Assistant. Then open Settings → Devices & services → Add integration → SpacePC. HACS is recommended because it reports integration updates. Do not install both methods at the same time.
Prepare and discover a device
Install compatible SpacePC firmware from the browser flasher.
Complete the device Wi-Fi setup and wait for its restart.
Keep the device and Home Assistant on a network that permits local HTTP and mDNS.
Confirm the discovered SpacePC device under Settings → Devices & services.
The integration stores the stable mDNS hostname. When DHCP assigns a new IP address, discovery updates the connection and the local API client is rebuilt.
Manual setup
Choose Add integration → SpacePC and enter the device hostname or current IP address. Use the hostname when possible. Manual setup still requires the SpacePC Local API to be reachable.
Entities and device page
Entities depend on firmware capabilities. The DS18B20 project creates one temperature entity per enabled probe. Compatible projects can expose binary sensors, switches, lights, fans, diagnostics and firmware updates. The device page includes its current IP address and a link to the local SpacePC web interface when supplied by firmware.
Local operation and MQTT
The native integration requires neither cloud access nor a broker. MQTT remains optional for other systems. Avoid duplicate MQTT Discovery entities unless both integration paths are deliberately required.
Updates
Install integration updates through HACS and restart Home Assistant when requested. Firmware remains project- and hardware-specific; select the correct ESP32 family and review whether settings are erased.
Troubleshooting
Device is not discovered
Confirm setup is complete and mDNS is permitted. Guest networks, client isolation and some VLAN rules block multicast discovery.
Manual setup cannot connect
Open the local device UI from the same network, verify its current IP in the router and allow local HTTP traffic. A successful ping alone does not prove the Local API is available.
Device is unavailable after an IP change
Use the current integration release and ensure mDNS works across the network segment. Discovery updates stale connection information automatically.
A sensor entity is unavailable
Check the GPIO and physical sensor in the local device UI. For DS18B20 probes, verify VDD, GND, DATA and the external 4.7 kΩ pull-up. Missing sensors are intentionally reported as unavailable.
Remove or reinstall
Remove the SpacePC entry under Settings → Devices & services and add it again through discovery or manual setup. Restart Home Assistant after removing or reinstalling the HACS package.