[RFC] Native support for BT4200 / 4200IP / BT00909 alarm webserver (Port 61898)

[TheDarkWizard]

As mentioned in this thread, I am opening this discussion for the integration of the BT4200 alarm webserver.

It can be set to low priority if other issues are of higher importance at this stage, but we'd love to explore adding native support for it if developers/maintainers are available to test.

📋 Context & Technical Details

• Device / Model: BT4200 / 4200IP / BT00909 alarm webserver
• Port: Dedicated TCP port 61898 (instead of the standard OpenWebNet port 20000)
• Authentication: Uses specialized maintenance/user authentication.

💡 Proposal & Benefits

Currently, alternative integration solutions for this system seem to be available only as paid options.

Adding native, open-source support for the BT4200 alarm webserver could bring extensive benefits to anyone looking to integrate this specific alarm system into the MyHOME Integration.

Bus logs and connection specs can be provided upon request/collaboration. Feedback, thoughts, or availability for testing are very welcome!

[anotherjulien]

I am open to the idea, but the main question is "where?".
The scope of the integration is fairly narrowly defined around MyHOME_Up and OpenWebNet. (Even the ZigBee part still technically talks OWN, even if the bus is not SCS)

Does this webserver talk OpenWebNet?
If the answer is no, maybe another repository/integration hosted by the organization would be a better place?

[TheDarkWizard]

Hi @anotherjulien :)
The BT4200 systems are part of Ksenia Security and use their own proprietary and standard communication mechanisms rather than OpenWebNet over SCS.

Specifically, Ksenia systems rely on:

• Central Station & Alarm Monitoring:
  • SIA DC-09: The primary standard protocol used over IP to transmit encrypted alarm events, zone statuses, and system alerts to Central Monitoring Stations (CMS).
  • Contact-ID: Supported over IP / cellular paths for legacy monitoring software compatibility.

Given this, if developing a brand-new integration is out of scope at this stage, it would definitely be worth revisiting later once the current roadmap is completed.

Of course, this stems primarily from a personal use case/need for now, but if there is enough community interest down the line, we can certainly consider some time working on it.

[anotherjulien]

Thanks for the context 🙂
As I said I'm not opposed to supporting that, and even doing so under this Organization, I just don't feel it is within the scope of the current integration!
I'll let others voice their opinions as well! 🙂

[antonio-pier]

I am very interested in this integration.

[pale2684-spec]

Me too

[TheDarkWizard]

How to Integrate the BT4200 During This Phase of Missing Native Integration

Just to give a little context on how BT4200 can be integrated right now into Home Assistant:

BT4200 Scenarios's can be launched directly from Home Assistant. Although you cannot control the alarm status directly, these scenarios can be triggered as part of your automations.

For example:

"Arm the alarm when I leave the house" translates to running the CEN+XXX command, which activates the "Arm Alarm" scenario whenever you leave the defined home zone.

Key Takeaways

• Native Integration Bypass: You can leverage this workflow to keep the alarm functional and integrated within Home Assistant despite the current lack of direct native control.
• Automation-Friendly: Triggers and commands (like CEN+XXX) bridge the gap between Home Assistant state changes and alarm actions.
• Dedicated App Support: The dedicated alarm application takes care of the rest of the detailed management and status handling.

[antonio-pier]

I can confirm that's spot on! I tested this directly with my MyHomeServer1: if you create a scenario in Home + Project without assigning it to any command or button, the server doesn't generate any OpenWebNet messages on the SCS bus.
To fix this and allow Home Assistant to trigger it via a CEN command, you must assign the scenario to a command/button (even a virtual one). This way, MyHomeServer1 links the scenario to a precise address and control code, making the message finally appear on the bus and enabling Home Assistant automations to run it.