Homebridge Be Wave

Homebridge plugin to control Be Wave virtual devices using TCP trigger messages.

This plugin allows you to trigger Be Wave zones, outputs, or virtual devices from Apple HomeKit.

Features

• Listen to TCP commands send by Be Wave upon switching virtual output
• Send TCP commands from HomeKit to Be Wave with CommandOn message
• Support for multiple devices
• Works with virtual zones and outputs
• Real-time feedback via incoming TCP messages
• Momentary / trigger-style behavior

Installation

npm install -g homebridge-bewave

Configuration

Add this to your Homebridge config.json:

{
  "platform": "BeWave",
  "name": "Be Wave",
  "host": "192.168.10.10",
  "devices": [
    {
      "id": 1,
      "name": "Virtual Device 1",
      "commandOn": "trigger_zone_1",
      "onMessage": "switch_on_1",
      "offMessage": "switch_off_1"
    },
    {
      "id": 2,
      "name": "Virtual Device 2",
      "commandOn": "trigger_zone_2",
      "onMessage": "switch_on_2",
      "offMessage": "switch_off_2"
    }
  ]
}

Configuration Options

Platform

| Key | Description | Required | | ------- | -------------------------------- | -------- | | host | IP address of the Be Wave system | Yes | | devices | List of devices | Yes |

Device

| Key | Description | Required | | ---------- | ------------------------------------------- | -------- | | id | Unique device ID | Yes | | name | Name shown in HomeKit | Yes | | commandOn | TCP message sent when triggered | Yes | | onMessage | Message received from Be Wave for ON state | No | | offMessage | Message received from Be Wave for OFF state | No |

Behavior

This plugin uses trigger-based switching:

• Every toggle in HomeKit sends a commandOn message
• commandOn is used to trigger a zone. Standard time 400ms
• Switch back controlled in Be Wave
• Be Wave controls the actual state
• If feedback is configured, HomeKit state is updated based on incoming messages

This makes the plugin ideal for:

• Alarm zones
• Virtual inputs
• Scene triggers
• Automation triggers

How It Works

HomeKit → Satel Be Wave

• Create a virtual device in Be Wave and configure according to manual
• When a switch is toggled (ON or OFF)
• The plugin sends the commandOn TCP message
• Create a routine in Be Wave to change the output state
• With every change of the switch from Homebridge the Be Wave output will change state

Be Wave → Homebridge

• Be Wave sends a TCP message upon change of output
• Plugin matches this with onMessage / offMessage
• HomeKit state is updated accordingly

Notes

• Each device must have a unique id
• commandOn is required
• If no feedback messages are configured, the switch behaves as a momentary trigger
• Make sure Be Wave is configured to send TCP messages back

Troubleshooting

Device does not respond

• Check IP address (host)
• Verify Be Wave TCP configuration
• Check Homebridge logs

Switch state incorrect

• Verify onMessage and offMessage
• Ensure Be Wave sends the exact same messages

Nothing happens on toggle

• Check logs for "trigger verstuurd"
• Verify TCP connectivity
• Be Wave listens on Port 5000
• Confirm Be Wave is able to listen to this port
• Check if the port is not used by others on your server

Development

npm install
npm run build

License

MIT License

Disclaimer

This plugin is not officially affiliated with Be Wave. Use at your own risk.