Auch verfügbar in:
DE Deutsch
Home Assistant
Inhalt
Mesh-to-HA integration via REST API + Long-Lived Access Token.
What the integration can do
- Smart Home widget with person status, energy consumption, issues
- HA health indicator in the Command Overview banner (shows updates + unresolved issues)
- Z2M auto-discovery via the HA template API (see Zigbee2MQTT)
- ESP auto-discovery when ESP devices are connected via HA
Prerequisites
- Home Assistant 2024.x or newer
- Long-Lived Access Token from the HA profile (Profile → Security → Long-Lived Access Tokens → "Create Token")
- HA must be reachable from the Mesh container (network check:
curl -H "Authorization: Bearer $TOKEN" https://home.example.com/api/)
Setup in Mesh
- Admin → Integrations → Home Assistant
- Fields:
baseUrl— e.g.https://homeassistant.local(no trailing slash)token— the long-lived tokenesphomeGroupEntity(optional) — if you use legacy ESP via HA groupzigbee2mqttGroupEntity(optional) — if Z2M is inhamode
- Save → connection is tested immediately
Using the widget
Admin → Content → Widgets → "Home Assistant" or "Smart Home".
homeassistant— compact sensor list with person status and energysmartHome— larger overview with KPIs (lights on, temperature, consumption)
Troubleshooting
- Token invalid → regenerate from HA profile; old tokens are invalidated on password reset
- CORS error in browser console — Mesh calls HA from the server (container), should never be CORS. If it is: check reverse proxy headers
esphomeGroupEntityshows nothing — the group must exist AND contain devices. Test in HA: Developer Tools → Templates →{{ states.group.esphome.attributes.entity_id }}
API endpoints (for debugging)
| Endpoint | Purpose |
|---|---|
GET /api/ |
Connection probe (auth check) |
GET /api/states |
All entity states |
POST /api/template |
Template rendering (auto-discovery) |
GET /api/config |
HA version + components |
GET /api/events |
Event stream (not used by Mesh) |