BTicino Door Entry for CLASSE300X13E

Feature Requests
104

Hi Skatboy,
I am unable to follow the fifth step to modify the firmware and gain SSH access to the 300X. But I understand that if you follow that tutorial, you lose the functionality of the original door entry app. Is that correct?

105

No that is not correct, it runs completely alongside it.

106

Could you explain the modification process in more detail? I don’t understand the fquinto’s manual.

107

Have a look a the telegram channel listed in this thread if you are looking for more support on the firmware creation process.

I don’t want to offend, but if you have doubts on what you are doing, then maybe you shouldn’s, messing with custom firmwares is alwaysj a risk that you brick your device.

So I guess I do recommend that you understand what the script (and you) are doing.

108

Hello,

I tried following this tutorial

where in step 1. Prepare and create firmware via Python script there is a video. The video does not resemble what I am seeing at all… This is the step where I am having difficulty; I believe I would have no problem with the rest of the steps. Several questions are asked that are not addressed in the video…

Best regards

109

I’m also on firmware 1.7.19 …
So if i understand correctly, my device needs a new V2 firmware?
Is this firmware gonna be pushed to my device, because it states it is on the latest one?
There is no way to force to get this V2 firmware?

1 Like
110

I have the same, it is called Classe 300EOS, which is apparently a newer model with Alexa, however I am unsure whether all this is applicable. Can anyone confirm? I am available for testing, if needed.

111

To follow fquinto’s procedure fquinto/bticinoClasse300x: BTicino Classe 300X13E and C100X , you must be on firmware 1.x.x because it is not compatible with the new door entry units running on firmware 2.x.x

113

I have a BTicino Classe 300 with firm 1.7.19, I currently use the BTicino Door Entry app.
But I don’t understand the first step of preparing the firmware to load onto the device. The video isn’t clear, since nowadays there are more steps than those documented in the video. Isn’t there a modified firmware that you can just load and you’re done?

114

Does it also work wit firmware 1.7.19 ( 300 version?) If no Can i just downgrade with the modded firmware 1.5.x?

Thanks

115

no you have to put your own personal mqtt server data in the firmware

117

I have a 363911, is it compatible?
Purchased on 04/11/22
I would like to integrate it with HA
:wink:

118

Hi everyone,
I have a Classe300x with V2.0.2 with DoorEntry-App. Is it possible to flash an old 1.7.9 from fquinto on this device?
Thanks in advance.
Hendrik

119

BTicino Intercom v2.0 — Live Video, Two-Way Audio, and Call History

Hey everyone!

I’ve been working on a major update for the BTicino Intercom integration and I’m happy to share that v2.0 is now in release candidate stage and ready for beta testing.

This is a big one — the integration now supports live WebRTC video streaming directly from your intercom, two-way audio (talk back to visitors), and persistent call history with snapshots. All of this was built by reverse-engineering the Netatmo cloud protocol from the official app.

What’s new in v2.0

Live video streaming
On-demand WebRTC video from your intercom cameras, right in the HA dashboard. No go2rtc, no RTSP, no local video server needed — it goes through the Netatmo cloud signaling, same as the official app. One camera entity per external unit, so if you have multiple entrances, each gets its own camera.

Two-way audio
Hear the visitor and talk back through the intercom microphone. This requires a custom Lovelace card because HA’s built-in camera player mutes audio by design.

Call history
Incoming call snapshots and vignettes are downloaded and saved locally as soon as the doorbell rings. The cloud URLs expire within minutes, but your images stay forever. Browsable from the HA Media Browser. Configurable retention (default: 30 days, 500 events).

Doorbell event entity
A proper EventDeviceClass.DOORBELL entity for automations, alongside the existing binary sensor for backwards compatibility.

Automation blueprints
Ready-to-use blueprints you can import with one click:

  • Actionable Doorbell Notification — snapshot preview + unlock buttons, rings even on silent mode (alarm stream)
  • Auto-Open on Schedule — automatic unlock during a time window (great for deliveries)
  • Missed Call Log — get notified when a call goes unanswered
  • And more in the blueprints folder

How to join the beta

You need two components:

1. The integration

Via HACS:

  1. Go to HACS → BTicino Intercom → three-dot menu → Redownload
  2. Enable “Show beta versions” and select v2.0.0-rc10 (latest RC)
  3. Restart HA

Manual:
Download from Releases and replace the custom_components/bticino_intercom/ folder.

2. The custom card (for video + audio)

Install BTicino Intercom Card — also available via HACS (Frontend category).

Add it to your dashboard:

type: custom:bticino-intercom-card
intercoms:
  - name: Front Door
    camera: camera.bticino_intercom_front_door
    actions:
      - entity: lock.front_gate
        service: lock.unlock

The card features: compact idle state, live video with audio, microphone toggle for two-way audio, multi-intercom tabs, call history viewer, and incoming call overlay with ringtone.

Browser compatibility

Live video requires Chrome or Chromium-based browsers (Chrome, Edge, HA Companion on Android). This is a device firmware limitation — the BTicino hardware uses Chrome-specific RTP payload types regardless of SDP negotiation. Firefox and Safari/iOS are not supported for live video. All other features (locks, sensors, automations, call history) work on any browser.

Full technical details in the browser compatibility investigation.

Compatible devices

  • BTicino Classe 100X (BNC1)
  • BTicino Classe 300X (BNC1)
  • Must be connected to the Netatmo cloud (Home + Security app)
  • Devices using the old “BTicino Door Entry” app are not compatible

Feedback & issues

This is a beta — bugs are expected! If you run into something:

  1. Enable debug logging:
    logger:
  logs:
    custom_components.bticino_intercom: debug
    pybticino: debug
  2. Reproduce the issue
  3. Download the full log from Settings → System → Logs
  4. Open an issue on GitHub with your HA version, device model, browser, and the log file attached

The entire protocol was reverse-engineered from scratch — the pybticino library, the integration, and the custom card are all open source. Contributions and feedback are very welcome!

1 Like