MR60BHA2 Breath-Heartbeat Sensor with Home Assistant | Seeed Studio Wiki

[giscus[bot]]

MR60BHA2 Breath-Heartbeat Sensor with Home Assistant | Seeed Studio Wiki

MR60BHA2 Heartbeat mmWave Sensor with Home Assistant

https://wiki.seeedstudio.com/ha_with_mr60bha2/

[camilogz]

Hi everyone,

I’ve successfully added the MR60BHA2 to Home Assistant, and the integration is working fine—I can see the device and its entities. However, when I go to the ESPHome page, the device does not appear in the list, so I can’t edit its YAML configuration.

Has anyone else experienced this issue? How can I access the ESPHome configuration for this device? Any help would be greatly appreciated!

Thanks!

[nfs0619]

Thanks for the clarification! Since you're trying to add a BMP280 sensor, please refer to the source code repository below. It contains the ESPHome external components used for this device:
https://github.com/limengdu/MR60BHA2_ESPHome_external_components

You may need to update the configuration based on this repo in order to add your sensor.

If the issue persists, I recommend contacting our technical support team at techsupport@seeed.io. They will be able to provide more detailed and faster assistance.

[rotilho]

@camilogz did you manage to flash it? I have a similar problem, I can't import it to esphome nor flash it through OTA.

My computer is not able recognise it either when plugged.

[hyacin75]

@camilogz did you manage to flash it? I have a similar problem, I can't import it to esphome nor flash it through OTA.

My computer is not able recognise it either when plugged.

Just got mine, 100% same. Can't add to ESPHome Builder as C6 isn't supported (even though the docs I found on GitHub make it sound like you should just be able to add it in there) - no option for OTA update, and does not show up as a serial port on my computer using a known good USB-C cable that I literally just used two days ago to serial connect to a Home Assistant Yellow box.

@rotilho , @camilogz - did you get any further with this? My device shipped with 2.0 and constantly shows a distance of 0.0m to the 'target', between fixing that, additional people detection, etc., I'd really like to bring it up to 3.5.

@nfs0619 Any chance you could provide some feedback here rather than directing us to email you in silos? Multiple people having the same issue, and more are sure to come along. Putting the answers here makes a lot more sense.

Edit: As I had ordered three, I just took a brand new one out of the box to see if it made any difference if the device was in a fresh/reset state - but exact same, it does not show up as a serial port in Windows.

Edit2: Tried a few more cables just to be sure, and tried basically every USB3 port on this device (which, I'll remind, was doing serial over USB to a Home Assistant Yellow just two days ago) - nada. This device is 100% NOT exposing a serial port over USB.

Edit3: Popped the case open and tried "connecting while holding down the [only button I could see, presumably the 'boot' button]" as I kept seeing everywhere. Nada. Then I tried connecting to the OTHER USB-C port that is within the case, and voila, I had a serial port. Trying to update now with their online tools and they keep failing (advising me to hold down the button while pressing install, which isn't helping), but I'm a big step closer, so fingers crossed.

Edit4: Ok, so from this page, the "Web Tool" did not work. I also found an OTA tool somewhere that did not work. The "ESPHome Web" combined with the 'factory' bin file from the repo seems to have worked though. I've added the 'new' one, it's not showing any devices or entities yet though - iirc this took some time with the first one too. I flashed the first one with the OTA image hoping it wouldn't blow away my settings, and now HA isn't seeing it at all, so I think I may need to crack it back open, 'prepare for first use', flash the factory image, and then connect to the WiFi to get it reconnected to my network.

Edit5: Device "2" finally produced a 'device' and entities, and confirmed, it's running 3.5 -

Edit6: Connecting device "1" to the PC to reflash it, the serial device keeps appearing and disappearing - I think it's in a bootloop. So I would not advise trying to use the OTA firmware to avoid redoing the config! I'm unscrewing it from the bottom case now to do a 'hold the button and power on', and hopefully then it will be stable and I can start fresh.

Edit7: Device "2" was working for a few minutes after a reboot but is just randomly going and staying unavailable. And I can't seem to get device "1" out of what looks like a bootloop no matter how long I hold the button or at what point ... so at this point, I'd say "live with the 2.0 firmware it shipped with if you can, or put the device on a shelf for a few weeks or months to avoid bricking it" 😞

Edit8: Now I'm not even getting a disappearing serial port from device "1", just nothing - so I'll again reiterate, be very careful going down this path, or do not go down it at all without guidance (and replacement justification if things go sideways) from Seeed.

Edit9: Ok, so what I thought was a reset button on the large board, I guess was not a reset button. There are two tiny little metal circles to the left and right of the USB-C port that is on the ESP32C6 board (the small one you have to open the case to see) ... one has a small B, and one a small R. These are in fact buttons, just very difficult to operate ones. The B, is the 'boot' button. Holding that down with the tip of a tiny screwdriver, and then applying power to the ESP32C6 board directly (with what was also a console cable as the other end was my PC) enabled a stable serial port, and I was able to 'prepare for first use' and then 'install' the 3.5 image. I doubt it will be any more stable than the other board I flashed with 3.5, but I'm happy it doesn't seem to be in a boot loop anymore.

Edit10 (day 2): so I have, like, all the sensors here, two types of Seeed mmWave, three types of Screek mmWave sensors ... I'd intended to cannibalize/convert some of the older 24 GHz Seeed ones I have to 60 GHz but that didn't work out. What I was able to steal from them though, is WiFi antennas! They do seem to be plentiful and cheap on Amazon, but I figured if I've got some here, already of roughly the right length, and doing nothing, why not try them out? So I've gone back to the 3.5 firmware that seems to have bigger WiFi issues than the 2.0 firmware, but with an antenna now. So far, so good. It's also added "person information" (detected/not) and "target number" (presumably number of people detected) which 2.0 didn't have. "Distance to detection object" is still showing as unknown. Fingers crossed the antenna improves what looks a lot like connectivity issues (sensors all going 'unknown', frequently, and for extended periods of time).

Edit11: For anyone going down the same road with the antenna, it seems the connector is U.FL/IPEX/MHF1 (not IPEX4 or MHF4)

Edit12 (day 3): IPEX / "IPEX G1" confirmed, I ordered these and it snapped on np. Generally though, these running 3.5 is "WOW bad" ... two of them sitting ~1.5' from me, with the antenna, frequent disconnects from HA, and now they're saying "yep, there is a person there" and they're connected, I can turn the light on and off, but they show no heart rate or breathing. And I do have them at different angles so as to not conflict. I'm going to try a longer test with them even more spread out (basically 0, 50 and 110 degrees or so), one with the original 2.0 and the new antenna, one 3.5 old/kit antenna, one 3.5 no antenna, and see if I can find anything that is stable.

Edit13: I hope all this info is useful for someone at some point in the future, lol! Upon opening and connecting my 3rd unit without touching the firmware, it seems firmware 2.0 does in fact have the additional items I thought it did not - maybe they just weren't discovered yet or something when I added the cards to a dashboard last time. All three show the same available data though -

Edit14: 3.5 firmware with the antenna from the "presence detection kit" flatlined first, and quick ... I haven't moved, the other two are still tracking my heartrate fine, but it's gone to 0 and past experience says it will stay there until a restart -

Edit15: The only one that seems to pick back up and carry on after I leave and come back is the 2.0 unit -

They're all still connected, I can toggle their lights - but the two 3.5 units will not register any vitals. I'll swap positions and/or antennas (in case they're causing any kind of interference, primarily) and see if anything changes.

[nfs0619]

Hi @hyacin75 ，

Thanks so much for taking the time to document your process in such detail—this kind of real-world testing and feedback is incredibly valuable!

We welcome you to share your experience on our community forum: https://forum.seeedstudio.com/. There, you'll find more users who enjoy discussing topics like this, and it’s a great place to dive deeper into troubleshooting and share updates.

Really appreciate your effort and hope things continue to improve with your setup!

[hyacin75]

Hi @hyacin75 ，

Thanks so much for taking the time to document your process in such detail—this kind of real-world testing and feedback is incredibly valuable!

We welcome you to share your experience on our community forum: https://forum.seeedstudio.com/. There, you'll find more users who enjoy discussing topics like this, and it’s a great place to dive deeper into troubleshooting and share updates.

Really appreciate your effort and hope things continue to improve with your setup!

Oh, amazing, I am able to create threads there now! Initially I was not and joined in an existing thread to ask about it where other users with the same issue were doing the same. It seems I am able to now though, so that's great, I'll see what I can find there! Thanks!! 😄

[corgan2222]

HA 2025.6.1
ESPHome: 2025.6.1

will crash and boot loop because of problems with i2c.
Add "scan: false" to i2c

full working code:

esphome:
  name: seeedstudio-mr60bha2-kit-8549b0
  friendly_name: seeedstudio-mr60bha2-kit-8549b0
  # project:
  #   name: "seeedstudio.mr60bha2_kit"
  #   version: "3.5"
  platformio_options:
    board_upload.maximum_size: 4194304
  min_version: "2025.6.1" # Fix logger compile error on ESP32-C6 esphome#6323


esp32:
  board: esp32-c6-devkitc-1
  variant: esp32c6
  flash_size: 4MB # upload.flash_size
  framework:
    type: esp-idf

external_components:
  - source:
      type: git
      url: https://github.com/limengdu/MR60BHA2_ESPHome_external_components
      ref: main
    components: [ seeed_mr60bha2 ]
    refresh: 0s

# Enable logging
logger:
  hardware_uart: USB_SERIAL_JTAG
  level: DEBUG

# Enable Home Assistant API
api:
  encryption:
    key: "xxx"

ota:
  - platform: esphome
    password: "yyy"
    
packages:
  wifi: !include common/wifi.yaml
  device_base: !include common/device_base.yaml    

i2c:
  - id: bus_a
    sda: GPIO22
    scl: GPIO23
    scan: false 

uart:
  id: uart_bus
  baud_rate: 115200
  rx_pin: 17
  tx_pin: 16
  parity: NONE
  stop_bits: 1  

seeed_mr60bha2:
  id: my_seeed_mr60bha2
  uart_id: uart_bus


binary_sensor:
  - platform: seeed_mr60bha2
    has_target:
      name: "Person Information" 

sensor:
  - platform: bh1750
    name: "Illuminance"
    address: 0x23
    update_interval: 1s  
  - platform: seeed_mr60bha2
    breath_rate:
      name: "Real-time respiratory rate"
    heart_rate:
      name: "Real-time heart rate"
    distance:
      name: "Distance to detection object"
    num_targets:
      name: "Target number"      

packages:
wifi: !include common/wifi.yaml

wifi:
  networks:
  - ssid: "ssid"
    password: "!!!!"
    
  reboot_timeout: 2min      

packages:
device_base: !include common/device_base.yaml

debug:
  update_interval: 30s

logger:  
  level: DEBUG

sensor:
  - platform: debug
    free:
      name: "Heap Free"
    loop_time:
      name: "Loop Time"

  - platform: wifi_signal # Reports the WiFi signal strength/RSSI in dB
    name: "WiFi Signal dB"
    id: wifi_signal_db
    update_interval: 60s
    entity_category: "diagnostic"

  - platform: copy # Reports the WiFi signal strength in %
    source_id: wifi_signal_db
    name: "WiFi Signal Percent"
    filters:
      - lambda: return min(max(2 * (x + 100.0), 0.0), 100.0);
    unit_of_measurement: "%"
    entity_category: "diagnostic"
    device_class: ""  

  - platform: uptime
    name: "Uptime Sensor"   


time:
  - platform: homeassistant
    id: homeassistant_time


binary_sensor:
  - platform: status
    name: "Status"  

text_sensor:
  - platform: wifi_info
    ip_address:
      name: "IP"
    ssid:
      name: "SSID"
    bssid:
      name: "BSSID"    
  - platform: version
    name: "Version"   
  - platform: debug
    reset_reason:
      name: "Reset Reason"       

button:
  - platform: restart
    name: "Restart"         

[nfs0619]

Thank you for your feedback! We are arranging to verify this issue, and if confirmed, we will update the documentation accordingly.

[Nekkit]

I have the same problem as the person before mentioned, I get very unreliable readings. i specifically set the sensor as directed (45 angle, pointing at chest on the sleeping person) and the readings work for a bit and then flat line. I get "detected" person target number: 1, but 0 hartbeat. then it jumps back to normal then flat lines respiratory rate, or detection distance drops to 0., and so on.

Device is working by testing I can control the LED, so its not a connection problem. If its this unrealiable the it wont work for my proyect :(. Context is i need to alarm when health condition of a child (heart rate or respiratory rate) have severe changes that point to a possible health problem. Just need to roughly detect changes, no need for medical precision, but at least i needed continous readins :(

Could anyone confirm they have the same problem? and or if they solved it?

Im using the stock configuration, device and firmware are as received, conected to ESP home (2025.10.1 version) on a Home Assistant (20253.10.3 core version).

Device is powered by samsung super charge v2 wall charcher to usbc power the device directly and there is no interference from extrernal factors. distance to router is about 4m.

Diagnostics show: (not that i understand, it was supposed to be plug and play :)
"storage_data": {
"device_info": {
"uses_password":
"name": "seeedstudio-mr60bha2-kit-8e87c0",
"friendly_name": "Seeed Studio MR60BHA2 Kit 8e87c0",
"mac_address":
"compilation_time": "Feb 5 2025, 07:12:25",
"model": "esp32-c6-devkitc-1",
"manufacturer": "Espressif",
"has_deep_sleep": false,
"esphome_version": "2024.12.2",
"project_name": "seeedstudio.mr60bha2_kit",
"project_version": "3.5",
"webserver_port": 0,
"legacy_voice_assistant_version": 0,
"voice_assistant_feature_flags": 0,
"legacy_bluetooth_proxy_version": 0,
"bluetooth_proxy_feature_flags": 0,
"zwave_proxy_feature_flags": 0,
"zwave_home_id": 0,
"suggested_area": "",
"bluetooth_mac_address": "",
"api_encryption_supported": false,
"devices": [],
"areas": [],
"area": {
"area_id": 0,
"name": ""
}
},
"services": [],
"api_version": {
"major": 1,
"minor": 10
},
"binary_sensor": [
{
"object_id": "person_information",
"key": 807585817,
"name": "Person Information",
"disabled_by_default": false,
"icon": "mdi:motion-sensor",
"entity_category": 0,
"device_id": 0,
"device_class": "occupancy",
"is_status_binary_sensor": false
}
],
"light": [
{
"object_id": "seeed_mr60bha2_rgb_light",
"key": 421767625,
"name": "Seeed MR60BHA2 RGB Light",
"disabled_by_default": false,
"icon": "",
"entity_category": 0,
"device_id": 0,
"supported_color_modes": [
35
],
"min_mireds": 0.0,
"max_mireds": 0.0,
"effects": [],
"legacy_supports_brightness": true,
"legacy_supports_rgb": true,
"legacy_supports_white_value": false,
"legacy_supports_color_temperature": false
}
],
"update": [],
"sensor": [
{
"object_id": "seeed_mr60bha2_illuminance",
"key": 387687418,
"name": "Seeed MR60BHA2 Illuminance",
"disabled_by_default": false,
"icon": "",
"entity_category": 0,
"device_id": 0,
"device_class": "illuminance",
"unit_of_measurement": "lx",
"accuracy_decimals": 1,
"force_update": false,
"state_class": 1,
"legacy_last_reset_type": 0
},
{
"object_id": "real-time_respiratory_rate",
"key": 3149911513,
"name": "Real-time respiratory rate",
"disabled_by_default": false,
"icon": "mdi:pulse",
"entity_category": 0,
"device_id": 0,
"device_class": "",
"unit_of_measurement": "",
"accuracy_decimals": 0,
"force_update": false,
"state_class": 1,
"legacy_last_reset_type": 0
},
{
"object_id": "real-time_heart_rate",
"key": 1733026013,
"name": "Real-time heart rate",
"disabled_by_default": false,
"icon": "mdi:heart-pulse",
"entity_category": 0,
"device_id": 0,
"device_class": "",
"unit_of_measurement": "bpm",
"accuracy_decimals": 0,
"force_update": false,
"state_class": 1,
"legacy_last_reset_type": 0
},
{
"object_id": "distance_to_detection_object",
"key": 1827072686,
"name": "Distance to detection object",
"disabled_by_default": false,
"icon": "mdi:signal-distance-variant",
"entity_category": 0,
"device_id": 0,
"device_class": "distance",
"unit_of_measurement": "cm",
"accuracy_decimals": 2,
"force_update": false,
"state_class": 1,
"legacy_last_reset_type": 0
},
{
"object_id": "target_number",
"key": 222526658,
"name": "Target Number",
"disabled_by_default": false,
"icon": "mdi:counter",
"entity_category": 0,
"device_id": 0,
"device_class": "",
"unit_of_measurement": "",
"accuracy_decimals": 0,
"force_update": false,
"state_class": 0,
"legacy_last_reset_type": 0
}
],
"text_sensor": []
},
"dashboard": {
"configured": true,
"supports_update": true,
"last_update_success": true,
"last_exception": null,
"addon": "5c53de3b_esphome",
"has_matching_name": false
}
},
"issues": []

thanks

[nfs0619]

Thanks for reaching out and sharing the details! Could you please check which firmware version your radar module is currently using? The latest version is v1.6.12 — updating to this version may help improve stability.

You can follow the steps in this video and guide to update the firmware:

• YouTube Tutorial
• Firmware Upgrade Guide

If the issue still persists, please feel free to contact our technical support team at techsupport@seeed.io and share the related information — they can provide more detailed and faster assistance.

[hyacin75]

Thanks for reaching out and sharing the details! Could you please check which firmware version your radar module is currently using? The latest version is v1.6.12 — updating to this version may help improve stability.

You can follow the steps in this video and guide to update the firmware:

• YouTube Tutorial
• Firmware Upgrade Guide

If the issue still persists, please feel free to contact our technical support team at techsupport@seeed.io and share the related information — they can provide more detailed and faster assistance.

Hi. I'm on 1.6.5 so I'm trying this update too. Multiple devices get connected to the Seeed studio OTA app no problem and start spewing out their data, but clicking "Request Update" does nothing. I've tried multiple cables in multiple ports, but I can't believe that has anything to do with it as I am getting a stream of data from the device. Please advise.

Edit: Ok, I checked out the video and see the Arduino IDE part is not an alternate method of doing it or anything - it's a mandatory step. I've not ever used the Arduino IDE ever for any of my smarthome and automation stuff, but I did get it installed, and after a few searches and hitting a few other seeedstudio wiki pages, got it working, did that part, and was able to flash to 1.6.12.