Bticino C300X working on Homekit and via scrypted

slyoldfox · December 22, 2022, 6:38pm

Hi,

I want to let everyone know that I managed to connect to the Bticino C300X to received audio/video as well as open door controls (together with guys that modified the firmware on Telegram).

I will put together some resources below:

Modify the official firmware and flash it to your device:

As I focussed on researching the audio/video part (not the door openings), you can find my first research here:

Further research aimed at being able to actually make a SIP call with the device and see the video (via X11):

gist.github.com

https://gist.github.com/slyoldfox/822bc31447f800f074448055f5848169

c300-sip.md

# SIP communication between c300x and baresip

The following document will help to explain the different components that are used to setup
a two-way audio and video call to the intercom to hear/talk and view the external camera.

Thank you @R for being my monkey and test things a lot.

## Todo/Not working yet

* Receiving calls from the intercom seems broken on `baresip` 2.9.0 (although working on 0.5.10)

This file has been truncated. show original

Someone was working on a SIP plugin for scrypted, the discussion can be found on github:

github.com/koush/scrypted

New plugin for SIP video doorbell - concept question

opened 11:17AM - 13 Nov 22 UTC

closed 04:23PM - 28 Nov 22 UTC

nanosonde

Hi @koush, I am planning to develop a new plugin which connects to my SIP vid…eo doorbell. The SIP video doorbell exposes the video stream via RTSP without any audio. However, to get the two-way audio streams it is required to call the the doorbell via SIP. In the past I already had a [PoC](https://github.com/Sunoo/homebridge-camera-ffmpeg/pull/1253) running based on the homebridge-camera-ffmpeg plugin. Now I would like to move completely to scrypted and use it for my Homekit camera setup. I need some advice on the right concept for this plugin as I am not familiar with the internal scrypted concepts and architecture in general. What would I like to achieve? 1. Homekit: use the RTSP video stream without audio (so only one stream), but with prebuffering and HK Secure Video. Recording also without audio 2. Homekit: when starting the live-streaming in the app, the new plugin shall call the video doorbell and setup two-way audio streaming. Note: As a SIP video doorbell is likely to be also integrated in some other SIP environment, it is required that the SIP call does not last indefinitly so that other SIP PBX participants can call the camera as well if nobody picks up via Homekit. As you can see in my PoC above, I have used a direct SIP INVITE to get the SDP and just wait for the OK response with SDP from the video doorbell. This is also based on [kirm/sip.js](https://github.com/kirm/sip.js/) that was used by the ring plugin before the [SIP API was removed](https://github.com/dgreif/ring/commit/7aeae37e6e93b68747e14983cea9c0a9229faec6). It boils down to this: ```typescript this.sipRemoteRtpDescription = await this.sipCall?.invite({ audio: { port: sipIncomingAudioPort, rtcpPort: sipIncomingAudioRtcpPort, ssrc: sipAudioSSRC }}); ``` So it basically something similiar that you are using here: https://github.com/koush/scrypted/blob/72333348981cffd2431256c4b3f614543636790b/plugins/ring/src/main.ts#L206 What I see from your ring plugin is that you seem to create a local RTSP server on demand and push the video and audio streams to it: https://github.com/koush/scrypted/blob/72333348981cffd2431256c4b3f614543636790b/plugins/ring/src/main.ts#L240 https://github.com/koush/scrypted/blob/72333348981cffd2431256c4b3f614543636790b/plugins/ring/src/main.ts#L298 While I think that I roughly know how to handle two-way audio based on the ring plugin, I am unsure how to handlle the complete separate video stream of the doorbell. It is itself negotiated via RTSP (and not via SIP). So the SIP plugin would also have to act like a RTSP client and push the stream to the new local on-demand RTSP-server. What do you propose here?

I ported and modified the code to make this work with the Bticino C300X:
GitHub - slyoldfox/scrypted: Scrypted is a high performance home video integration and automation platform for HomeKit, Google Home, Alexa, and more. (plugins/bticino) directory

Since scrypted has a Homekit integration it was pretty easy to view/hear through the Homekit interface.
I didn’t get to the point to import it as a seperate camera in home assistant at this point, I am just fine how it is at the moment. But it’s detected as a Homekit Controller and I’m sure it would work.

Good luck with this extra information.

javi_fly · November 26, 2023, 10:46pm

If I flash my Bticino 300X13E with this firmware I lose the original functionality to work with the “door entry” app?

javi_fly · December 9, 2023, 11:22am

more info:

slyoldfox · December 13, 2023, 4:13pm

No you don’t

Mattes83 · January 18, 2024, 10:24am

Great work, thanks for your efforts!

I guess I got most of it working, but I am not sure about the settings for the camera in scrypted. Are those fields auo populated and i do not need to adjust them? I am especially curious about the “sip FROM: uri” field as it does not match the user I created on the intercom.

Nevertheless it seems to work.

javi_fly · January 26, 2024, 10:50pm

more info here: https://community.home-assistant.io/t/bticino-door-entry-for-classe300x13e

Mandyy · July 24, 2024, 8:59am

setting up bticino to homekit via the home assistant is what i prefer , adding the integration and configuration operfectly , Then that is all you need to do.But on the other note, i also wonder the the Living now is homekit compatible , then Bticino make more homekit compatible products .But anways HA Integration works well.

slyoldfox · September 27, 2024, 10:46am

I am happy that is working for you. This guide is specifically for people without a MyHome server and only a C100X or C300X unit in house.

Meanwhile I have ported full RTSP/Homekit functionality into GitHub - slyoldfox/c300x-controller (without the need for scrypted)

Viking · December 28, 2024, 6:46pm

@slyoldfox - Is there any chance of getting your fine work on the C300X working on the Class100X16E Intercom as well?
Home - HS

slyoldfox · April 1, 2025, 9:01am

It works for the C100X as well.

Viking · April 1, 2025, 8:42pm

Hi, and many thanks for your reply.
Based on my brief examination of your repository, it appears your c300x-controller SW does include a front-end UI component (?)
Does this allow users to interact with the C300X devices in an intuitive way, rather than just through command-line interactions?

Can you share som screens shots of your UI ‘in-action’?.

Without more details from the repository, I’m unable to understand exactly what technology the UI is built with (web-based, desktop application, etc.) or how comprehensive its features are.

Or, if all this can be found somewhere else, please point me in the right direction.

Rgds
Oyvind

slyoldfox · April 3, 2025, 6:59am

It exposes a HTTP server on port 8080 where you can execute/view several types of things (like unlocking doors).
It also exposes an RTSP server on port 6554 which you can use for integration in HA with webrtc.
Additionally if you choose the Homekit bundle, it has an embedded Homekit bridge so you can use Homekit directly (without needing scrypted for it).
Note that the Homekit bundle might stress your intercom as it’s also doing ffmpeg transcoding for the audio on-device.

Viking · April 3, 2025, 12:12pm

Many thanks for your reply.
My main objective is simply to be able to view video from my Class100X16E intercom in a Lovelace Card in my Home Assistant Front End, as well as being able to select camera, open door and maybe also conduct a two-way conversation.

slyoldfox · April 3, 2025, 12:52pm

It does that as explained on GitHub - slyoldfox/c300x-controller

Viking · April 10, 2025, 3:19pm

Sorry for my questions (and many thanks for your replies).
I began looking at it now, and to me it appears as this is written/adopted to run only on an ARM7 platform. Is that correct?

slyoldfox · April 10, 2025, 3:37pm

The controller runs on the intercom itself, so yes it’s meant to run via node on that ARM cpu.

Viking · April 11, 2025, 9:12am

I am a bit confused. Please explain the difference between these two repositories:

slyoldfox · April 11, 2025, 4:34pm

fquinto repo is to flash a rooted firmware onto your intercom so you can access it via SSH for example.

My repo installs node and the controller on this intercom (and it requires the rooted firmware or ssh access).

So you need the first to make the second work.

Viking · April 11, 2025, 7:16pm

Ok, thanks. Now I get it.
I have a lot of questions, that I’m sure you have had many times before, and that you have answered, perhaps in the Telegram feed. But I couldn’t find a useful way to search through the feed to locate specific keywords or topics (?)
And I hate to bother you more that absolutely necessary. What is your advise in this regard?

And here comes the first question; When creating the firmware using the Python Script, it aks me for the version number of my current C100X firmware, which is v2.3.1

But when I enter that, it responds; “Wrong version”

slyoldfox · April 17, 2025, 10:11pm

The rooted firmware only works for 1.x versions (and hardware).

Check the telegram feed as they posted a new HA integration past days that works for 2.x firmwares.