Scene controllers such as the Futurehome Modeswitch/Modusbryter (a Z-Wave device) only ever emit `evt.scene.report` on a button press and never appear in the periodic Vinculum state poll. Their address therefore never got an entry in the HA state cache, so live scene events were dropped by the `if (!payload[addr]) continue` guard in haUpdateStateValueReport, leaving the "Scene" entity permanently 'unknown'. - Register an address -> state-topic mapping from the device config so live events can be routed even when the service is absent from the state poll. - Seed the cache entry from that mapping when a report arrives for an otherwise-unknown address. - Preserve previously known values across state polls so a scene value set by a live event is not wiped by a later poll that omits the service. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BRMavpbsGAcY2ctkKvcoNR
Futurehome Home Assistant add-on
Futurehome add-on for Home Assistant. Designed to be a complete drop-in replacement for the official Futurehome app, with support for all device types compatible with the Futurehome hub. See the FAQ for more details.
Watch the official add-on demo video
Features
This add-on:
- Fetches all device metadata from the Futurehome hub and maps them to Home Assistant devices/entities.
- Fetches and updates device states and availability in real time.
- Supports interaction with devices comparable to the official Futurehome app.
- Supports pairing and unpairing devices.
Installation Guide
See the full Installation Guide for step-by-step setup instructions.
Futurehome Device Services Compatibility Chart
This chart lists all services supported by the Futurehome hub, along with their current implementation status.
Devices commonly consist of multiple services: for example, a presence sensor might expose a sensor_presence service with a presence (true/false) value, and also a battery service if it is battery-powered.
Some services are more common than others; some are deprecated entirely.
Implemented system services
| Name | Service | Implementation status | Home Assistant entity |
|---|---|---|---|
| Fall-back Z-wave 'basic' service | basic | ✅ | Number |
| Reboot device | dev_sys | ✅ | Button |
| Identify device | indicator_ctrl | ✅ | Button |
| Advanced configuration of a device | parameters | ✅ | Button, Sensor, Number, Select, Text |
Other system, meta, unused, or not essential services
| Service | Description |
|---|---|
| association | Virtual association between devices. Easily reproducible using Home Assistant's built-in configuration. |
| battery_charge_ctrl | No devices or hub support this stub service. |
| diagnostic | Diagnostic (logging, etc) |
| inverter_consumer_conn | No devices or hub support this stub service. |
| inverter_grid_conn | No devices or hub support this stub service. |
| inverter_solar_conn | No devices or hub support this stub service. |
| ota | Managing OTA updates of devices |
| power_regulator | Automation. Easily reproducible using Home Assistant's built-in configuration. |
| schedule | No devices or hub support this stub service. |
| technology_specific | Should be covered by other services |
| time | Z-wave service for setting and reading time |
| time_parameters | Z-wave service for setting and reading time |
| version | Device hardware and software versions. Exposed through other means. |
| virtual_meter_elec | A virtual electricity meter that estimates energy usage by multiplying the device's configured average power consumption with its operating duration. Easily reproducible using Home Assistant's built-in configuration. |
FAQ
Q: But I thought Futurehome was going to disable the local API after a short grace period, as stated in the Subscription FAQ. What gives?
While that was initially stated, the latest hub firmware keeps the local API open indefinitely. There is currently no built-in mechanism in the firmware to disable it after a certain period, unless you update to a newer firmware. This has also been confirmed in the updated Subscription FAQ.
By using both public and reverse-engineered local APIs, this add-on is able to fully replicate the functionality of the Futurehome app.


