Bring sensor states, API responses and business measures into Denframe, or share selected Denframe actions and summaries with Home Assistant.
Choose whether to bring data into Denframe or share Denframe entities with Home Assistant. These guides describe builds with the new connection setup; check your installed build if a choice is missing. Examples use synthetic values and placeholder endpoints.
Have your screens say when a door is open, a leak is detected or a battery is low, and turn chosen lights and switches on and off from Denframe.7 steps →
Export chosen Denframe scenes, speaker mute switches and short summaries to Home Assistant through MQTT, then use them there and in its official car apps.8 steps →
Operate approved lights and switches from Denframe, and start dashboards or mute speakers from Apple Home and Siri, with Home Assistant between them.7 steps →
Connect Denframe to a broker you already run, read one exact state topic, and show live temperature and battery readings with clear freshness and availability.8 steps →
Discover a compatible MCP server, approve one fixed read and map its JSON result to dashboard values.7 steps →
Which connection should I choose?
Home sensor values: start with the native Home Assistant connection.
Denframe scenes, mute controls or summaries in Home Assistant: use the opt-in Home Assistant export guide, including Companion automotive favorites.
Lights from Denframe, or Denframe in Apple Home: see the experimental Apple Home guide.
Power BI with an existing organization flow: use Power Automate and a webhook. Without an approved inbound delivery route, consider direct Power BI sign-in.
A conventional JSON API: use HTTP GET or a fixed read-only POST.
An existing MQTT broker and exact state topics: use MQTT readings. For sensors already in Home Assistant, keep the native Home Assistant connection.
A producer that sends HTTP updates: use a webhook.
A compatible MCP server with a reviewed read operation: use the advanced MCP connection. Denframe is an MCP client: it connects outbound to an MCP server you run and reads reviewed, read-only data. It is not an MCP server, and it offers no cloud or public API for agents to control a household; its own interfaces require the household's credentials and are reachable beyond the home network only through a route its owner sets up.
Already have data and need a screen? See the casting guide.