Thermopro TP357 Integration

New to HomeAssistant so thanks for the help.

Have installed haos_ova (8.5 or 9.0,dev) on an VM in an Unraid server with an attached XDO USB bluetooth radio extender, with the hopes of gathering temp and humidity data from a Thermopro TP357. HA seems to see the bluetooth radio (comes up as an integration), but I’m not sure what to do from here.

I think that TP357 is BLE (which I think means passive scanning is needed). I found this page on ble monitoring which seems to indicate newer versions of HA might be able integrate with the TP357 automatically? (…or maybe for now I can install some extra software to get it integrated?)

Not sure what to try next, I feel like I may be missing something. Any pointers welcome.

Cheers.

I got it working.

  • Install the latest HA instance in a VM (I used a qcow2 image)
  • get into the underlying OS in HA (i.e. type login at the CLI)
  • make sure there is a /mnt/data/supervisor/homeassistant/ directory
  • on a different system, clone this project
  • somehow get the directory custom_components from that other system into the HA instance directory /mnt/data/supervisor/homeassistant/ (I used scp from the HA instance)
  • On the HA instance, you should now have the dir /mnt/data/supervisor/homeassistant/custom_components/ble_monitor with all the code you cloned from github
  • reboot HA and now there should be an integration called “Bluetooth Low Energy Monitor”
  • long press the button on the back of the sensor (it will show the bluetooth logo on the front) and it should show up as a device in HA and display entity values for temp and humidity.
  • I checked the “Use active scan in stead of passive scan (affects battery)” on the BLE config panel. No idea if I needed it.

I think this will all become unnecessary after ble_monitor becomes a standard part of HA in the near future.

so 4th bullet - on a different system, are you saying another instance of HA? i have my ble tracker up and running - currently pulling one of the other device stats. wanted to add the TP357. i found on there it referenced a bind key but the model looks off a bit. did you run into this? i tried adding bind key and it still does not ingest into the system. i do see it come up in the scan logs though.
thanks

Did you manage ?

Is it possible to log on daily / hourly base ?

As of Dec 2023, TP357 was discovered by HA automatically immediately after batteries were inserted into TP357. I could add it to an area and start saving data.

In the screenshots below, ATC xxxx are Xiaomi Mijia LYWSD03MMC thermometer-hygrometers.


However, I checked history in HA after a few hours, and I see that while both temperature and humidity monitoring seem to work in general, the graph jumps to hundreds or thousands of degress temperature and hundreds of percent humidity. I wonder if this is a HA issue with decoding TP357 data, or the device sends invalid data.


Opened ticket TP357 values sporadically jump to meaningless values · Issue #113003 · home-assistant/core · GitHub.