2023 Mopeka Devices & esp32_ble_tracker

TelecomRob commented 11 months ago

The problem

Hello, I'm having issues with the esp32_ble_tracker not picking up all ble devices when scanning. It is pick up other bluetooth devices but not a 2023 Model Mopeka Pro check Universal M1017 Sensor. I'm wondering if Mopeka changes the chipset on the boards or encrypted it as if I run a scan using Arduino BLE scanner can see the device.

I have poked around other threads and it seems other people have been having issues with the 2023 Model Mopeka Pro check Universal M1017 Sensor in regards to esp32_ble_tracker not seeing them.

Screenshot of CLI:

Screenshot of HA proving esp32_ble_tracker is detecting other devices: Screenshot 2023-10-26 093134

Which version of ESPHome has the issue?

2023.10.3

What type of installation are you using?

Docker

Which version of Home Assistant has the issue?

No response

What platform are you using?

ESP32

Board

No response

Component causing the issue

No response

Example YAML snippet

esphome:
name: mopeka

esp32:
board: esp32dev
framework:
type: arduino

Enable logging
logger:

Enable Home Assistant API
api:
password: ""

ota:
password: ""

wifi:
ssid: "abc12345"
password: "abc12345"

Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "Mopeka Fallback Hotspot"
password: "abc12345"

captive_portal:

Enable Bluetooth Proxy Components
esp32_ble_tracker:
scan_parameters:
interval: 320ms
window: 120ms
duration: 60s
active: true

bluetooth_proxy:
active: true

mqtt:
broker: 192.168.1.94
username: ""
password: ""
client_id: "mopeka"

sensor:

platform: mopeka_pro_check
mac_address: 4c:3c:19:88:3f:4c
tank_type: 20LB_V
temperature:
name: "Propane test temp"
level:
name: "Propane test level"
distance:
name: "Propane test distance"
battery_level:
name: "Propane test battery level"

Anything in the logs that might be useful for us?

No response

Additional information

How Arduino BLE see device when scan: Advertised Device: Name: , Address: 4c:3c:19:88:3f:4c, manufacturer data: 4c0010061b1940e8a878, txPower: 12, rssi: -10

spbrogan commented 11 months ago

I might suggest a couple of things to try first.

Drop the ble proxy
drop the mqtt stuff.

My guess is the esp32 is not able to handle all the activity generated by the proxy and is having to minimize its ble scanning time and missing stuff. I have seen this on a number of devices and in busy ble environments.

spbrogan commented 11 months ago

You may also want to press the green sync button a bunch of times (like 10+) to see if for some reason it is in mfg mode.

TelecomRob commented 11 months ago

I’ve been doing some digging and it’s looking like the 2023 “universal models” are not supported for now.

runjmc commented 11 months ago

There looks to be a change in the sensor. I see a unsupported sensor type in the logs.

[15:10:50][I][mopeka_ble:081]: MOPEKA PRO (NRF52) SENSOR FOUND: F5:5A:E4:8A:AA:2C [15:10:50][E][mopeka_pro_check:058]: Unsupported Sensor Type (0xC) [15:10:58][I][mopeka_ble:081]: MOPEKA PRO (NRF52) SENSOR FOUND: F5:5A:E4:8A:AA:2C [15:10:58][E][mopeka_pro_check:058]: Unsupported Sensor Type (0xC)

Let me know if I should open up another issue for this.

TelecomRob commented 11 months ago

Update: I have officially confirmed that the Universal Mopeka Pro Check is not compatible. I bought a non universal and everything works fine.