Feature request: HOBO bluetooth sensors

Devices not yet supported
1

Feature request: HOBO bluetooth sensors
https://www.onsetcomp.com/products/data-loggers/mx2001

2

Hi @mortenx,

This looks interesting, I didn’t find any information on the HOBO site about the devices’ BLE advertisement data so far though.Would you be willing in finding out together if and how the advertisment data of the HOBO devices you have could be decoded?

Fir that you would need to turn on advertisement and advanced data on your BLE OpenMQTTGateway and monitor and copy and paste the information the HOBO devices braodcast, along with their relevant data at the same time.

3

I am usung esp32 and home assistant, where to i insert this command?
“mosquitto_pub -t home/OpenMQTTGateway/commands/MQTTtoBT/config -m ‘{“pubadvdata”:true}’”

4

The easiest is to use MQTT Explorer. In the Publish section there you enter
home/OpenMQTTGateway/commands/MQTTtoBT/config
as the Topic, and
{“pubadvdata”:true}
as the payload in json format.

6

You can also activate it from the HA interface, Settings->Devices

image
image346×748 32.1 KB

7

data from logger , every ~65 seconds

{
“id”: “E9:8E:6C:E6:48:10”,
“mac_type”: 1,
“adv_type”: 0,
“manufacturerdata”: “c500075aa4410106240000000800523c029900dd9739”,
“rssi”: -45,
“txpower”: 0,
“distance”: 0.06662
}

{
“id”: “E9:8E:6C:E6:48:10”,
“mac_type”: 1,
“adv_type”: 0,
“manufacturerdata”: “c500075aa4410106240000000800123c029940d6e73a”,
“rssi”: -42,
“txpower”: 0,
“distance”: 0.033417
}

{
“id”: “E9:8E:6C:E6:48:10”,
“mac_type”: 1,
“adv_type”: 0,
“manufacturerdata”: “c500075aa4410106240200000800d23c029940b98eb9”,
“rssi”: -44,
“txpower”: 0,
“distance”: 0.053212
}

8

Thanks @mortenx,

So parts of the last part of the manufacturerdata seems to be frequently changing. What data does the device native app show at these times, and what kind of data is expected?

To be able to see if and what data might be encoded here, some relationship between the actual data needs to be compared.

9

hobo live
hobo live956×2048 73.2 KB

i think sensor measures two things water level through water pressure and temperature

and when connected to app, mqtt dont see changes

{
“id”: “E9:8E:6C:E6:48:10”,
“mac_type”: 1,
“adv_type”: 0,
“manufacturerdata”: “c500075aa4410106240200000800123a029970818aba”,
“rssi”: -80,
“txpower”: 0
}

{
“id”: “E9:8E:6C:E6:48:10”,
“mac_type”: 1,
“adv_type”: 0,
“manufacturerdata”: “c500075aa4410106240000000800d23a0299c055cdb9”,
“rssi”: -90,
“txpower”: 0
}

{
“id”: “E9:8E:6C:E6:48:10”,
“mac_type”: 1,
“adv_type”: 0,
“manufacturerdata”: “c500075aa44101062402000008005239029ac00a81ba”,
“rssi”: -89,
“txpower”: 0
}

10

I cannot see any immediate relationship between the manufacturerdata and the graph from the app, neither for the temperature, but definitely not for the water level, which, while it has quite an amplitude, on the legend it is always in the -0.001 m (negative?) range throughout the whole graph legend.

Instead of a graph actual live data value readings would be better to see it they are contained encoded within the manufacturerdata, like - what is the exact temperature reading which in the graph is a constant line at ~ 19.25 °C?

Additionally data from other days, with very different temperature and water level will help to see if this is encoded in the manufacturerdata at all.