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
Commenti
3 commenti
Hello Marco,
In a nutshell, the C300EOS is unfortunately "pretty locked" when it deals with 3rd party management
We don't plan to open features currently locked to 3rd parties in the future. UPDATE : I re-opened the subject with both Netatmo and Bticino teams. I can't promise anything, but we will discuss it
Concerning integrations, I found out there is an HomeKit integration : https://connecthomekit.com/how-to-connect-bticino-to-homekit/. But I can't tell if it really works
Have a good day,
Leslie - Community Manager
Hello,
Thank you for your previous response and for the clarification regarding third-party API access for the EOS 300. I understand the security limitations that prevent lock opening and video streaming via public APIs.
Given this architectural decision, I have a follow-up question regarding native Apple Home (HAP) support:
Specifically:
A HomeKit integration via HAP would enable the EOS 300 to appear directly in Apple Home without relying on cloud API access or third-party bridges.
It would provide native HomeKit device representation for things such as call events or door state (even if video and opening remain restricted).
I am aware that the current API limitations are related to security concerns, but HAP support is handled locally and securely according to Apple’s architecture. Many other devices (e.g., Netatmo cameras) support HomeKit natively via HAP without exposing the same level of control externally.
Could you please clarify:
Whether HomeKit/HAP support for EOS 300 is being considered for future firmware?
If not, could you share the main technical or security reasons preventing this?
Thank you!
Hi Marco,
Unfortunately, it will not be possible. The C300EOS doesn't match with Apple's requirements concerning video screen quality (because of limitations of our 2-wires system). So, they refused to allow us to make it HK compatible
Have a good day,
Leslie - Community Manager
Accedi per aggiungere un commento.