hballard94 commented 1 year ago

The problem

System does not find Mopeka device in order to add it. I have also tried using esp32 with the mopeka_pro_check installed and i get an "unsupported sensor type" error.

What version of Home Assistant Core has the issue?

core-2023.8.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Mopeka

Link to integration documentation on our website

https://www.home-assistant.io/integrations/mopeka/

Diagnostics information

logs_test_run.txt

Example YAML snippet

sensor:

platform: mopeka_pro_check mac_address: D8:EE:F1:8C:A9:15 tank_type: CUSTOM custom_distance_full: 40cm custom_distance_empty: 10mm temperature: name: "Propane c test temp" level: name: "Propane c test level" distance: name: "Propane c test distance" battery_level: name: "Propane c test battery level"

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 1 year ago

Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration (mopeka) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `mopeka` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign mopeka` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

mopeka documentation mopeka source _{^{(message by IssueLinks)}}

Fox350 commented 1 year ago

Same thing here with a Mopeka Pro check Univeral M1017

I'm having this config :

`esp32_ble_tracker:

mopeka_ble:

bluetooth_proxy: active: true sensor:

Example using 20lb vertical propane tank.

platform: mopeka_pro_check mac_address: ED:4D:B6:3C:4B:C4 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"`

jfass17 commented 12 months ago

I am also having this issue. The Mopeka device do not show up.

TelecomRob commented 11 months ago

I recently purchased also a Mopeka Pro check Universal M1017 a few weeks back and have run into the same issue. I can pick up the MAC address with Arduino BLE scanner but not ESHOME esp32_ble_tracker. Is it possible that the BLE in the Mopeka's changed the BLE clip in production or encryption maybe? When I pick it up with Arduino BLE Scanner is doesn't list information of what the device is or anything. I only know its is it by moving the sensor to and from away the board. RRSI goes from -22 beside board to -88 in the other room while scanning so I know that it is it. Anyways figured I'd mention these detail in the chance it provides some direction. I new to ESP32 boards so I don't even know where to begin.

bdraco commented 11 months ago

Please post diagnostics from the ESPHome config entry with the mac address of the device

TelecomRob commented 11 months ago

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

My Config:

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"

Screenshot of CLI:

bdraco commented 11 months ago

It looks like you are trying to use esphome to talk directly to the device and not the HA integration. If that's the case please open an ESPhome issue instead.

TelecomRob commented 11 months ago

For my application that is true, I'm just pointing out it could hardware related possibly. Which could be the issue the other in this post are having?

tkirchbaum commented 11 months ago

I’m having the same issue. I purchased a M1017 (2023 model) and no devices are found in the Mopeka intergation.

CDroge commented 11 months ago

I'm also having the same issue where the Mopeka Pro check Universal M1017 isn't showing up via the HA integration. I've tried two separate Home Assistant instances on separate hardware as well as with esp32 BLE proxies. These two HA instances have previously detected the older model of the Mopeka Pro Check propane sensors. Running HA 2023.11.1 and HA 2023.10.5 with the latest versions of ESPhome.

bmorgenthaler commented 11 months ago

Same issue as others, the newest Mopeka Pro check Universal M1017 (M1017020A) isn't being found. I can see it using BluSee on MacOS or BLE Scanner on iOS. Unfortunately trying to connect to it using bluetoothctl on Linux doesn't seem to work but it does see it.

charlesrg commented 10 months ago

Can anyone confirm that it now works with their Mopeka Pro Universal M1017 ?

bmorgenthaler commented 10 months ago

Just upgraded to 2023.11.3 but the mopeka integration still isn't finding my Mopeka Pro Universal M1017.

CDroge commented 10 months ago

Just upgraded to 2023.11.3 but the mopeka integration still isn't finding my Mopeka Pro Universal M1017.

Same here. Running 2023.11.3 and not finding the Mopeka Pro Universal M1017. I'm also running ESPhome 2023.11.3, in case that matters.

TelecomRob commented 10 months ago

Just upgraded to 2023.11.3 but the mopeka integration still isn't finding my Mopeka Pro Universal M1017.

Same here. Running 2023.11.3 and not finding the Mopeka Pro Universal M1017. I'm also running ESPhome 2023.11.3, in case that matters.

I don't think the fix was added to 2023.11.3 from what I see with the change log.

Changelog 2023.11.3 include payload_open when a lock supports OPEN esphome#5809 by @ccutrer dashboard: Fix online status when api is disabled esphome#5791 by @bdraco fix: compile errors with fonts esphome#5808 by @cvandesande Early return when there are no wifi scan results esphome#5797 by @jesserockz Add some additional VA triggers, part 2 esphome#5811 by @kbx81

Raptor607 commented 10 months ago

Experiencing this as well. My android BLE scanner sees it but neither integration does.

bmorgenthaler commented 10 months ago

Just updated to the latest version (HA Core 2023.12.1) and my 2023 Mopeka Pro Universal M1017 is now being detected. I'm running supervised HomeAssistant so I could check that the latest python libraries were installed for mopeka (mopeka-iot-ble - v0.5.0) by running the following: docker exec -it homeassistant pip list | grep -i mopeka

home-assistant / core

Unable to Find Mopeka Devices #98323

The problem

What version of Home Assistant Core has the issue?

What was the last working version of Home Assistant Core?

What type of installation are you running?

Integration causing the issue

Link to integration documentation on our website

Diagnostics information

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

Example using 20lb vertical propane tank.

Enable logging

Enable Home Assistant API

Enable fallback hotspot (captive portal) in case wifi connection fails

Enable Bluetooth Proxy Components