Version 0.6.0 adds automatic MQTT device discovery directly inside the BE WAVE integration. No virtual IP devices are needed for supported physical-device telemetry and on/off control. Uses Home Assistant’s existing MQTT connection and groups devices as children of a BE WAVE hub. Requires Home Assistant 2026.10.0 or newer.
Nederlandse installatiehandleiding, schakelen en IP-adres wijzigen
- Copy
custom_components/bewaveto your Home Assistant configuration and restart. - Configure Home Assistant’s MQTT integration.
- Add BE WAVE → MQTT. Enter base topic
bewavefor messages onbewave/devices/16/tx. - Devices and supported fields appear when telemetry arrives.
MQTT supports temperature, battery, contacts, detection and other statuses, plus on/off control for components reporting on_off. Set the command base topic to match BE WAVE’s Subscribe topic, for example bewave/command. State changes follow actual status feedback. Alarm-group commands and dimmer brightness are not included. Existing TCP installations are preserved. TCP hub addresses can be changed through Configure → Hub IP-adres wijzigen or Reconfigure, without changing entity IDs. Change the MQTT broker IP through the MQTT integration’s own Reconfigure action.
See the changelog and test suite. Automated tests run with Home Assistant, including a round-trip test through a real local MQTT broker and simulated BE WAVE device. A live hardware test is still required.
The instructions below apply to the existing TCP mode, selected via BE WAVE → TCP.
This custom integration models each configured BeWave zone as up to two Home Assistant entities:
- a Button entity that sends the configured trigger command to BeWave
- a Binary Sensor entity that reflects the latest feedback status from BeWave
For each zone, configure:
- Name: friendly zone name
- HTTP command to BeWave: exact trigger text to send when the button is pressed
- HTTP output on request: feedback text that means the zone is ON
- HTTP output off request: feedback text that means the zone is OFF
- Listen port: TCP port Home Assistant listens on for BeWave feedback
The integration still uses raw TCP under the hood, matching the original Homebridge plugin behavior:
- outgoing command to
<host>:5000 - push feedback from BeWave back into Home Assistant
- Copy
custom_components/bewaveinto your Home Assistant config folder. - Restart Home Assistant.
- Add the BeWave integration via Settings > Devices & Services.
- Configure one or more zones.
- If the feedback fields are left empty, only the trigger button will be created.
- Existing old switch entities from earlier builds may remain in the entity registry and can be removed manually.
Enter the IP address of the Hub.
First, configure the first zone:
1: Zone name
2: Command to send to the Bewave hub
3: Status (ON) – used to receive the ON state from the Bewave hub
5: Status (OFF) – used to receive the OFF state from the Bewave hub
1: To add an new zone
2: to save the zone