iobroker.homeassistant-bridge
v0.8.7
Published
Emulates a minimal Home Assistant server so devices expecting a Home Assistant dashboard can display any custom web URL.
Downloads
875
Readme
ioBroker.homeassistant-bridge
Emulates a minimal Home Assistant server so that devices like the Shelly Wall Display XL can be redirected to any custom web URL — without running a real Home Assistant Core.
Features
- Home Assistant Emulation — minimal HA API compatible with Shelly Wall Display XL
- mDNS Discovery — automatic detection via Avahi (
_home-assistant._tcp) - OAuth2-like Auth Flow — full login flow emulation, optional credential validation
- Flexible Redirect — send the display to any ioBroker VIS, VIS-2, or custom web URL
- Modern Admin UI — JSON-Config for easy configuration
Requirements
- Node.js >= 20
- ioBroker js-controller >= 7.0.0
- ioBroker Admin >= 7.6.20
- Linux system with Avahi (for mDNS)
Ports
| Port | Protocol | Purpose | Configurable | |------|----------|---------|--------------| | 8123 | TCP/HTTP | Home Assistant emulation (Shelly requires exactly this port) | No — fixed |
Configuration
Configuration is done via the Admin UI (jsonConfig):
| Option | Description | Default | |--------|-------------|---------| | Bind to Interface | Network interface to listen on | 0.0.0.0 (all) | | Redirect URL | Target URL for the display (e.g., VIS) | must be set | | mDNS Enabled | Avahi Service Discovery | enabled | | Service Name | Name in the network | "ioBroker" | | Auth Required | Validate credentials | disabled | | Username | Login name (if auth enabled) | "admin" | | Password | Login password (stored encrypted) | - |
Important: Port 8123 is mandatory. The adapter always listens on port 8123 — this is hardcoded and cannot be changed. Shelly displays and other Home Assistant-compatible devices expect exactly this port. Make sure port 8123 is not already in use on your ioBroker server.
Important: The redirect URL must be a network-accessible address, e.g.:
http://192.168.1.100:8082/vis/index.htmllocalhost will not work because the display calls the URL!
Troubleshooting
Display cannot find the server (mDNS)
The adapter registers a _home-assistant._tcp service via Avahi. Automatic discovery did not work reliably in tests — manual configuration is more stable:
IP: <ioBroker-IP>
Port: 8123Check if Avahi is running:
systemctl status avahi-daemonCheck if the service is registered:
avahi-browse _home-assistant._tcp -r -tIf mDNS doesn't work, use manual configuration on the display with the ioBroker server's IP address.
Avahi Permission Error
sudo chown iobroker /etc/avahi/servicesHealth Check
The adapter provides a health endpoint:
http://<IP>:8123/healthChangelog
0.8.7 (2026-03-21)
- Fix repository URL format for Admin UI GitHub installation
0.8.6 (2026-03-19)
- Admin UI fully translated into all 11 languages; i18n refactored to use short semantic keys
0.8.5 (2026-03-19)
- Admin UI: interface selector moved before port; port field removed (fixed at 8123)
0.8.4 (2026-03-19)
- Logging cleanup: auth flow, redirect and config details moved to debug; remove redundant start/stop messages
0.8.3 (2026-03-18)
- Remove unused
info.clientsstate and dead code cleanup
0.8.2 (2026-03-17)
- Migrate to @alcalzone/release-script, enable npm Trusted Publishing
0.8.1 (2026-03-16)
- Fix automated release pipeline (remove legacy ci.yml and release.yml workflows)
0.8.0 (2026-03-16)
- ioBroker repository compliance: official testing actions, all translations, donation link
Older changelog: CHANGELOG.md
Support
If this adapter is useful to you, consider supporting its development via the PayPal badge at the top of this page.
License
MIT License - see LICENSE
Copyright (c) 2026 krobi [email protected]
Developed with assistance from Claude.ai
