Classe 300EOS (BNCX) – API exposure and third-party integration roadmap

Hello,

I am investigating integration possibilities for a BTicino Classe 300EOS with Netatmo in a third-party automation environment and would like to clarify the current API status and future roadmap.

Context

•Device: Classe 300EOS with Netatmo

•Account successfully linked through Netatmo Cloud

•Integration tested using the official Netatmo API via Home Assistant (pyatmo library)

•Authentication and scopes are correctly granted

From the diagnostic data returned by the API, the following modules are visible:

•type: BNCX (bridge)

•type: BNEU (bridged module)

•type: BNDL (bridged module)

This indicates that the device is present at the API level. However, no functional entities are exposed (no camera, doorbell, lock, or event endpoints), meaning that the current public API does not provide usable control or state access for these modules.

Observed behavior

Within the official Netatmo / Legrand applications it is possible to:

•receive doorbell calls

•access video stream

•trigger door unlock

•receive activity events

but none of these capabilities appear to be available through the public API endpoints currently used by third-party integrations.

Questions

1.Are BNCX/BNEU/BNDL device types intentionally excluded from the public Netatmo API?

2.Is there any planned API exposure for door entry systems (even limited to non-video functions such as unlock action or call events)?

3.Is there a recommended integration path for local or third-party controllers (Home Assistant, Control4, etc.) without relying on proprietary gateways?

From a developer perspective, even minimal access (event notifications and door unlock command) would enable meaningful integrations while keeping video and audio streams private.

Any clarification regarding long-term API strategy for door entry products would be greatly appreciated.

Thank you.

Marco