Daikin Madoka BRC1H bluetooth custom component

Petapton · August 25, 2024, 5:23pm

Yes, of course, data is always welcome. I myself have two Daikin units, but more is better.

steve_r29 · August 25, 2024, 6:50pm

This probably will just amuse me, but I missed your reply last year and struggled on with a bluetooth dongle and it constantly dropping out until a few months ago when I started googling again out of frustration.

I’d totally forgot about your esp implementation and re-discovered it… still not remembering it. But my hopes were ruined when I was getting some weird authentication error, but after some short googling I found someone with the exact same problem… me!

Anyway, this has been super stable, so thanks very much for all your work on it. It’s made the A/C actually usable in HA for me!

Out of interest do you plan to get it merged into the main repo?

Petapton · August 28, 2024, 9:16pm

Thank you. I’m glad you find it useful.
Yes, actually there’s a pending PR on the esphome github project. But - don’t ask me why - nobody even reviewed it.
Luckily it’s no big deal, since you can use it right away from my repository with just few more lines of config.

Frank802 · September 10, 2024, 9:50pm

Hello everyone! I am having trouble with my VAM (ventilation) unit. Am I the only one experiencing the same problem?

Thanks

ivovangastel · September 18, 2024, 9:32am

i gave your PR a like, maybe it helps to get attention. i see your PR has a label “needs tests”. is there some automated testing needed before it will be reviewed?

Petapton · October 4, 2024, 8:13am

Yes. I think it’s because of tests missing. Let’s give it a try

mario-tux · October 28, 2024, 9:45pm

Hi @Petapton. I’ve found the time to test recent changes on your component on my 4 remotes. I had, in order to make them to work well, to split them on two different esp32 boards (two remotes for each board). It is known the limit of 3 connected devices for esphome but I got problems with 3.

My main issue is with the new fans support. I can’t spot any fan-related options on the HA climate devices (just HAVC modes and temperatures). It there something I have to enable? Can I provide some kind of logs to inspect the values reported by my remotes?

Thanks!

UPDATE: I did a clean rebuild and now the fan controls appeared…

comdinet · October 29, 2024, 7:49am

This seems to be hit and miss. I added 1 unit and it worked, except temperature settings are unreliable. Pressing -1 sometimes increases and sometimes decreases, setting temp also does this. Mostly when decreasing temps it goes ‘bad’.
Then I deleted everything and added 2 units. Unit that previously worked started to show only on/off and mode… removing and adding back couple times (whole integration) got it back to that mode. Had 1 unit showing up correctly, did a reload of integration and it went into this mode too.
Added just one unit to see if I can catch something wrong with temperature decrease, after playing with it, device went offline. Reloading integration didn’t help while I did see in bluetoothctl the device connected.
When device goes to this mode name changes in integration to - UE878 RF MODULE
This happened with master and slave madokas.
I’ve deleted everything from HA and bluetoothctl. Rebooted instance/HA and still same issues.

rotman253 · November 8, 2024, 7:38pm

I have the integration installed on HA container running on RPI 3b.
climate control can control my Madoka unit pretty instantly, but it doesn’t get an update when I change things on the Madoka unit itself.
In logs I can see this:

Logger: homeassistant.components.climate
Source: helpers/entity_platform.py:1020
integration: Climate (documentation, issues)
First occurred: November 4, 2024 at 11:19:10 PM (5337 occurrences)
Last logged: 9:31:21 PM

Updating daikin_madoka climate took longer than the scheduled update interval 0:01:00

This seems to happen every minute on the exact same time, for example:

2024-11-08 21:33:21.889 WARNING (MainThread) [homeassistant.components.climate] Updating daikin_madoka climate took longer than the scheduled update interval 0:01:00
2024-11-08 21:34:21.892 WARNING (MainThread) [homeassistant.components.climate] Updating daikin_madoka climate took longer than the scheduled update interval 0:01:00
2024-11-08 21:35:21.894 WARNING (MainThread) [homeassistant.components.climate] Updating daikin_madoka climate took longer than the scheduled update interval 0:01:00
2024-11-08 21:36:21.896 WARNING (MainThread) [homeassistant.components.climate] Updating daikin_madoka climate took longer than the scheduled update interval 0:01:00
2024-11-08 21:37:21.897 WARNING (MainThread) [homeassistant.components.climate] Updating daikin_madoka climate took longer than the scheduled update interval 0:01:00
2024-11-08 21:38:21.898 WARNING (MainThread) [homeassistant.components.climate] Updating daikin_madoka climate took longer than the scheduled update interval 0:01:00
2024-11-08 21:39:21.899 WARNING (MainThread) [homeassistant.components.climate] Updating daikin_madoka climate took longer than the scheduled update interval 0:01:00

cfoucher · November 15, 2024, 6:00am

@jeremykeen did you ever get this to work. I’m getting the same results.

0000vt · November 29, 2024, 12:21pm

Is there no other way to debug the bluetooth? My daikin has a lot of options in the app. I’d like to reverse engineer them to pymadoka but I dont have a Mac with XCODE or an android device. Any other ways to do it?

rotman253 · December 31, 2024, 2:23pm

Complete ESP32 noob here.
Is there a guide I can follow for how to install this on a brand-new ESP32 device and add it to my containerized HA?

Thanks very much

jonasdig · January 1, 2025, 7:43pm

I have a Altherma 3M 8kw with Madoka BRC1H HDAW. I tied the app before setting up Home Assistant but it shows very limited information. Have anyone seen this before? Any solutions for enabling more information. Google gives no hits on the error.

rotman253 · January 2, 2025, 9:51pm

How would you connect another Madoka controller to this configuration?

rotman253 · January 3, 2025, 9:15am

Moved to ESP32, looks like a promising option…

rotman253 · January 8, 2025, 7:44am

Hey @Petapton I will appreciate your help.
Using your driver and loving it!
My issues is most of the time, my control is in a weird state where it looks like it’s connected but it’s actually isn’t.
This is how it looks:

and this is the log that get to this state:

[09:37:03][D][madoka:189]: Got update request...
[09:37:03][W][component:237]: Component madoka.climate took a long time for an operation (259 ms).
[09:37:03][W][component:238]: Components should block for at most 30 ms.
[09:37:03][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_WRITE_CHAR_EVT
[09:37:03][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_WRITE_CHAR_EVT
[09:37:03][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_WRITE_CHAR_EVT
[09:37:03][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_WRITE_CHAR_EVT
[09:37:03][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_WRITE_CHAR_EVT
[09:37:07][D][esp32_ble_client:172]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_DISCONNECT_EVT, reason 8
[09:37:07][D][climate:396]: 'Living airconditioner' - Sending state:
[09:37:07][D][climate:399]:   Mode: HEAT
[09:37:07][D][climate:404]:   Fan Mode: AUTO
[09:37:07][D][climate:419]:   Current Temperature: nan°C
[09:37:07][D][climate:423]:   Target Temperature: Low: nan°C High: 23.00°C
[09:37:08][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_CLOSE_EVT
[09:37:08][D][sensor:094]: 'Living AC RSSI': Sending state nan dBm with 0 decimals of accuracy
[09:37:10][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] Found device
[09:37:10][D][esp32_ble_tracker:677]: Found device 00:CC:3F:EF:69:F7 RSSI=-77
[09:37:10][D][esp32_ble_tracker:698]:   Address Type: PUBLIC
[09:37:10][D][esp32_ble_tracker:700]:   Name: 'Living room '
[09:37:10][D][esp32_ble_tracker:222]: Pausing scan to make connection...
[09:37:10][D][esp32_ble_tracker:222]: Pausing scan to make connection...
[09:37:10][I][esp32_ble_client:067]: [0] [00:CC:3F:EF:69:F7] 0x00 Attempting BLE connection
[09:37:11][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_CONNECT_EVT
[09:37:11][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_OPEN_EVT
[09:37:11][D][esp32_ble_tracker:273]: Starting scan...
[09:37:15][D][esp32_ble_client:306]: [0] [00:CC:3F:EF:69:F7] Event 46
[09:37:16][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_SEARCH_CMPL_EVT
[09:37:16][I][esp32_ble_client:227]: [0] [00:CC:3F:EF:69:F7] Connected
[09:37:16][D][main:379]: Connected
[09:37:16][D][esp32_ble_client:188]: [0] [00:CC:3F:EF:69:F7] cfg_mtu status 0, mtu 23
[09:37:16][I][esp32_ble_client:333]: [0] [00:CC:3F:EF:69:F7] auth complete. remote BD_ADDR: 00cc3fef69f7
[09:37:16][D][esp32_ble_client:341]: [0] [00:CC:3F:EF:69:F7] auth success. address type = 0 auth mode = 13
[09:37:16][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_REG_FOR_NOTIFY_EVT
[09:37:16][D][esp32_ble_client:296]: Wrote notify descriptor 1, properties=16
[09:37:16][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_WRITE_DESCR_EVT

When it is really connected, this is how it looks:

and this is the log that get to this state:

[09:38:18][D][madoka:189]: Got update request...
[09:38:18][W][component:237]: Component madoka.climate took a long time for an operation (259 ms).
[09:38:18][W][component:238]: Components should block for at most 30 ms.
[09:38:18][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_WRITE_CHAR_EVT
[09:38:18][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_WRITE_CHAR_EVT
[09:38:18][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_WRITE_CHAR_EVT
[09:38:18][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_WRITE_CHAR_EVT
[09:38:19][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_WRITE_CHAR_EVT
[09:38:19][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_NOTIFY_EVT
[09:38:19][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_NOTIFY_EVT
[09:38:19][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_NOTIFY_EVT
[09:38:19][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_NOTIFY_EVT
[09:38:19][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_NOTIFY_EVT
[09:38:19][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_NOTIFY_EVT
[09:38:19][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_NOTIFY_EVT
[09:38:19][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_NOTIFY_EVT
[09:38:19][W][component:237]: Component esp32_ble took a long time for an operation (103 ms).
[09:38:19][W][component:238]: Components should block for at most 30 ms.
[09:38:19][D][climate:396]: 'Living airconditioner' - Sending state:
[09:38:19][D][climate:399]:   Mode: HEAT
[09:38:19][D][climate:404]:   Fan Mode: AUTO
[09:38:19][D][climate:419]:   Current Temperature: nan°C
[09:38:19][D][climate:423]:   Target Temperature: Low: nan°C High: 23.00°C
[09:38:19][D][climate:404]:   Fan Mode: AUTO
[09:38:19][D][climate:423]:   Target Temperature: Low: 23.00°C High: 23.00°C
[09:38:19][D][esp32_ble_client:110]: [0] [00:CC:3F:EF:69:F7] ESP_GATTC_NOTIFY_EVT
[09:38:19][D][climate:396]: 'Living airconditioner' - Sending state:
[09:38:19][D][climate:399]:   Mode: HEAT
[09:38:19][D][climate:404]:   Fan Mode: AUTO
[09:38:19][D][climate:419]:   Current Temperature: 23.00°C
[09:38:19][D][climate:423]:   Target Temperature: Low: 23.00°C High: 23.00°C

Would really appreciate the help here, how can I make it connected 100% of the time?
BTW, I’ve added a code that restarts the ESP32 every 60 minutes.

Petapton · March 6, 2025, 8:13pm

In the first snippet you posted, I see just the pairing process going on. Once it succeeds, it should always automatically connect to the esp. In more than three years of usage, this never happened to me.
Could you share your configuration? Maybe you got issues on that side.

madmad · March 14, 2025, 9:57pm

Hi,

Thanks @Petapton and @Blafois.

I changed my Madoka unit to operate with dual setpoint as in theory this offers better control.
To get what I wanted (HA independent control), I have edited/forked code, added yaml control, and customised esphome>web_sever_.js so that:

Heat and cool fan speeds now separately update and changeable in all modes including Auto mode directly (also with HA, which before was not so for auto mode). Commented out all but high and low fan mode as that’s all my setup support, but you can remove the comments to bring them back).
Added clear filter notification option so that it can be cleared without the app.
Added Madoka graphic, multi-device (due to esphom ble 3 connection limit) via single web page with linked theme adjustment and default to full width (double clicking device name tabs reveals logs). You can use yaml and js as a template to add more devices/pages, and change iframe ip addresses to mdns but its not android supported. Maybe someone could add mdns fallback code)
Added esp32 led status indicator and similar to error logs.

esphome/esphome/components/madoka at madoka · rawframe/esphome · GitHub (The yaml and js files are added to the fork)

Here is a screenshot of the webpage:

miskor · March 26, 2025, 6:48pm

Hi community,

I would really appreciate your support as summer is coming and it will be unbearable in my apartment without remote A/C control…

So, I was a happy user of this custom integration, running on rPi 4 with ASUS BT dongle (yes I know it is not reliable but in my case it was working quite fine).

Then, few months ago something happened and after one of the HA updates I was not able to regain control of my two MADOKA devices.

I though few reboots will help but no avail.

Yesterday I decided to redo complete installation, delete pairing and custom integration. Now I have them parired and integration is loaded but no devices/entities are detected, see below picture:

I can see some errors in the log related to MADOKA but I do not know if they are fatal or what…

Debug log can be found here (I’ve opened issue on the git as well but it seems relatively quiet there):

“https://github.com/user-attachments/files/19438148/home-assistant_daikin_madoka_2025-03-24T21-02-47.931Z.log”

Is anyone here running this integration sucesfully with HA 2025.3.4?

Any suggestions where should I look?

Thanks!

miskor · March 29, 2025, 2:18pm

SUCCESS!

Thanks to “amnsharif” from github for his work and support in this

Here is what I did:

delete MADOKA custom integration using the web interface
login to your HA
cd /homeassistant/custom_components/daikin_madoka/
if you want you can backup content of that folder: “tar tzf madoka_old.tar.gz” then “mv madoka_old.tar.gz /root”
erase the content of that folder: “rm -rf *”
wget https://github.com/amnsharif/daikin_madoka/archive/refs/heads/patch-1.zip
unzip patch-1.zip
restart HA and add MADOKA custom integration

and it should detect already attached MADOKA controllers…