And then I found this;
k-the-hidden-hero/bticino_intercom: 
Bring Back bticino on netatmo API
No need to root, or install anything on the intercom. Just installed the integration using HACS, and it worked on my first try. 
That is indeed the integration I was talking about. Only works on 2.x firmware and works with the Netatmo api
This integration does not work for 1.x firmwares as this hardware does NOT use the netatmo api internally.
What surprised me is that I got the impression from our conversation that ācrackingā the 2.x FW would be virtually impossible due to the new Bticino encryption technology - and suddenly here comes a guy that solves the whole thing without as much as any mention of SSH or flashing or hacking. Just plain install! Way to go, if you ask me. And I wouldnāt be surprised if the same is fully doable for the 1.x FW as well if just someone with the right tools and knowledge decided to do it.
Itās always like that with āimpossibleā things. They remain impossible until someone comes along and does something completely different, and viola, itās not impossible any more.
(Itās called progress)
You are welcome to reverse engineer the protocols for the 1.x my friend. You make it sound I have not spent hours reversing binary files and trying to make sense of it all.
The 2.x implementation just uses the netatmo api as seen in the android app. It uses the endpoints as seen in the app.
The solution fquinto and me proposed predates all that stuff by at least 5 years and barely uses any public http apis (because there are none).
So please donāt pretend to know what you are comparing.
Nevertheless I am happy you found a working solution for your unit. No need to post anything anymore as I find your tone offensive and totally unrespectful, so I wonāt bother replying anymore.
1 Like
I get the clear impression that you knew all along that your ātechyā solution would never work on v2.x FW devices, and now you also say that you knew about the other solution that do work!
Then why didnāt you tell me (and others) about that and I could have saved myself days of impossible work trying to hack my unit to no avail.
So no need to be grumpy. I apologize if you felt me being offensive. That was not my intention.
Because it was added literally 3 days ago.
1 Like
Ok, by bad then. Sorry for my unfair comments to you. I stand corrected.
2 Likes
Privacy, trust, and the difference between open code and obscure clouds
Thereās a big difference between using a project that has no external dependencies and runs fully under your control, versus one that relies on external APIs, hidden dependencies, and corporate cloud infrastructure.
Take ākātheāhiddenāheroā as an example. Their project uses the Netatmo API, which means:
- You have no local control of your own device.
- You depend entirely on internet access and Netatmoās servers.
- Your data goes through external platforms you donāt own or audit.
This isnāt something you can easily compare with a minimal, transparent repository that runs locally and doesnāt phone home. Itās a completely different trust model.
And hereās the core issue:
- We donāt know who ākātheāhiddenāheroā is.
- Thereās no accountability, no real identity.
- The project depends on layers of third-party code, platforms, and opaque systems.
If you value privacy, transparency, and local control, the choice is obvious. Some of us prefer software we can actually inspect, understand, and trust.
If you trust people who spend their time building real, privacy-respecting tools, you can support them with a small donationāshowing real trust in open work.
If instead youāre okay depending on anonymous sources and obscure infrastructure, thatās your choice too.
But letās not pretend these two models are even remotely the same.
I see your point, but if one works and the other donāt, then I havenāt got much choice - do I ?
Of course, you always have a good option: take a deep breath and relax. Support community development, keep learning, contribute to the cause, and be patient while the issue is resolvedāwhether by others or by yourself. And above all, always show gratitude to those who help. It would be wonderful if your good deeds and contributions served as an inspiration for the entire community to follow.
Personally, I find the āfquintoā manual very difficult to followā¦ and on top of that, you lose the functionality of using the original app. Depending on your needs, it may or may not be interestingā¦ if you want to have everything locally, itās a good solution, but if you want to keep your cloud and add the HA option, itās not for youā¦
Iām not sure what you are saying is correct, I have a C300x with firmware 1.x.
I use the rooted firmware with fquintoās method and have the Door Entry app, Homekit and HomeAssistant all working at the same time.
Of course I cannot speak for people with 2.x firmwares.
I have a BTicino Classe 300 with firm 1.7.19, I currently use the BTicino Door Entry app. I think Iām in the same situation as you.
Does the Door Entry app work perfectly for you? Answering? Listening? Viewing? Opening the door?