The building knows. Now the screens do too.
Home Assistant watches your sensors, meters, and devices. A rest_command in any automation POSTs that state to your Hangar.Media inbound webhook — temperature, occupancy, energy, air quality — turning signage into the building’s live status board.
From sensor state to standing display
Define a rest_command service once — method post, your webhook URL, the X-Webhook-Token header — and call it from any automation with a templated payload. State changes, schedules, and threshold triggers all become screen updates: the meeting-room board, the energy dashboard, the pool-temperature card.
What you can do with Now the screens do too.
Three capabilities that make this integration essential for your digital signage network.
rest_command is the bridge
Add a rest_command to configuration.yaml: method post, your inbound webhook URL, content type application/json, and the X-Webhook-Token header. Call it from any automation action with a templated payload of entity states.
Every sensor in the building can drive a pixel on the wall.
Templated payloads carry any entity states you choose
Trigger on state change, schedule, or threshold
Screens update within seconds of the push arriving
Shape the payload into screen content
Point display columns at payload fields with dot-notation paths, set defaults for missing fields, and apply per-column transforms — uppercase, lowercase, truncate, prefix, suffix. The same mapping engine powers every automation platform integration, so a recipe built once is portable across tools.
Your automation sends data; the mapping decides how it reads on screen.
Dot-notation paths reach nested payload fields
Defaults fill gaps so screens never show blanks
Transforms tidy values without touching the automation
Token-verified delivery
Your sending step includes the integration secret in the X-Webhook-Token header; Hangar.Media compares it in constant time, fail-closed, and rejects anything else with a 401.
Every push is authenticated before a pixel changes.
Constant-time secret comparison, fail-closed
One-click secret rotation
Unknown senders receive 401 and publish nothing
Four steps to connected screens.
From setup to live content in minutes, not days.
Connect the integration
Add the Home Assistant integration in Hangar.Media. Your unique inbound webhook URL and secret are generated instantly.
Define the rest_command
In configuration.yaml, add a rest_command: method post, your inbound webhook URL, content type application/json, a header X-Webhook-Token with your integration secret, and a templated JSON payload.
Map fields to the display
Choose Data Table, Content Cards, or KPI Metrics, then map payload fields to display columns with the field mapper. Defaults and transforms are optional.
Push and publish
Run the automation. The payload renders in the bound widget on your screens within seconds — enable Accumulate for a rolling board of recent pushes.
Built for every sector.
See how different industries use this integration to drive results.
Meeting-room climate boards
Automations push CO2, temperature, and occupancy per room to the facilities screen — stuffy rooms surface before complaints do.
HospitalityPool and spa status
Temperature and chlorination sensors update the leisure-area screen on every reading — guests see live conditions.
PublicEnergy transparency dashboards
Solar generation, grid draw, and consumption KPIs push to the lobby screen — the building’s footprint, live.
EducationCampus environment displays
Air-quality automations push classroom AQI tables to corridor screens, flagging rooms that need ventilation.
Common questions. Straight answers.
How is the webhook secured
The rest_command sends your integration secret in the X-Webhook-Token header; Hangar.Media compares it in constant time and rejects non-matching requests with a 401 — fail-closed, with no anonymous path.
What payload shape does Hangar.Media expect
Any JSON. A single object becomes one row or card; an array of objects becomes one row or card per record. With a field mapping configured, only the mapped fields are displayed; without one, the raw fields are shown as a key-value table.
Can one push update several screens
Yes. The push lands in the integration’s data feed; every design widget bound to that feed updates, wherever those designs are scheduled — one push can update one screen or the whole estate.
Does my Home Assistant need to be reachable from the internet
No. The push goes outbound from Home Assistant to Hangar.Media over HTTPS — no inbound port, tunnel, or cloud subscription required. Outbound events in the other direction need a reachable HA webhook URL (Nabu Casa or a reverse proxy).
One price. The whole platform.
That's how we think signage should work. Content editor, screen management, and 200+ app integrations — all included from day one.