-
-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Buderus CX100 support #415
Comments
I guess it's uses different uri's than heating modules; you'd need find main uri |
Is there any good way/method to scan for them? |
I decrypted apk back in the days and sniff http communication of the module |
Hello there i've got same issue/need with a MX300 gateway for a kb195i heating system - they are used to reach home system through myBuderus app but despite it seems same hardware/protocol than supported bosch devices, i can't configure it though bosch-custom-component. i'm new here but i think we should convert this issue into developper request |
Hi, same here, also with MX300. bosch-custom-component seems to get some kind of connection but fails to identify devices. |
Reached out to the manufacturer about this. API access is limited to MyBuderus App and MyEnergyManager and there are no plans for opening. The MyEnergyManager however uses the Bosch Smarthome Hub. Maybe there is a way. Will try to dig into this. |
I have exactly the same problem with an CX100 and would also be very interested in a solution 👍 |
@CeeEll any success with your research? I might need a solution for Buderus devices soon. |
Unfortunately not. Was able to connect heatpump to Bosch Hub but unable to control or see anything outside the manufacturer apps. |
Are there any news about the new CX100 IP Gateway? Thanks for your answer |
I gave up on integrating and startet using ems-esp. |
There is a solution of controlling CX100 with ems-esp? Can you give more info how it works? |
Hi there, I have the same problem you have.... |
Hi, As the esp connects directly to the ems bus there is no need for a networking module like the CX100 or MX300. @Ohhhja Documentation can be found here: https://docs.emsesp.org/ |
Thank you, I will try thatAm 02.01.2025 14:07 schrieb Christian Löer ***@***.***>:
Hi,
As the esp connects directly to the ems bus there is no need for a networking module like the CX100 or MX300.
I am very happy with the solution, integration into HA via MQTT was easy.
@Ohhhja Documentation can be found here: https://docs.emsesp.org/
There are a lot of tutorials on the internet as well
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
If you see the following warning in the logs:
You can suppress this warning by adding the following line to your logger:
logs:
slixmpp.stringprep: error This will hide warnings from the |
Is your feature request related to a problem? Please describe.
The CX100 is a USB Wifi module for AC climate systems.
Originally it can be used through the MyBuderus application on the phone and nothing else.
Describe the solution you'd like
if possible, add support for the Buderus CX100 dongle
Describe alternatives you've considered
I did not found any alternatives for Buderus support into HA.
Additional context
I found that this HomeAssistant integration works with some of the Buderus devices and gave it a shot. The device was connected but not recognized in HA.

This is the CX100 sticker

I went through a debug/raw scan where I had some (actually none) success with HTTP IVT communication
with the output
The text was updated successfully, but these errors were encountered: