home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.2k stars 30.22k forks source link

Mopeka sensors show Unavailable unless mobile app is open and connected on another device #121564

Open gtbdf1 opened 3 months ago

gtbdf1 commented 3 months ago

The problem

Mopeka sensors show Unavailable unless mobile app is open and connected on another device. Home Assistant shows Unavailable for all sensors. I then open the Mopeka app on my iPhone, wait for a couple seconds for it to connect and show a reading, then the information appears in Home Assistant. Is this an issue with Mopeka or possibly my bluetooth dongle?

What version of Home Assistant Core has the issue?

core-2024.7.1

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

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 3 months 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. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


mopeka documentation mopeka source (message by IssueLinks)

gtbdf1 commented 3 months ago

I just discovered that the information also populates in Home Assistant if I unplug and replug my bluetooth dongle, so it seems this is likely a dongle issue rather than Mopeka.

KrazyKubz commented 2 months ago

I had the same issue. It's cos of those esphome updates that keep coming what feels like every week!

ianhd83 commented 2 months ago

Hi guys, I just installed this today with the atom m5 and it worked to start with but now it isn’t and just says unavailable. Any ideas?

LuanRousseau commented 2 months ago

Hello, I'm stuck because when I load the integration, it does not detect my Wi-Fi bridge on the network (no device found), but on the phone app, everything is working. Could you please assist?

bdraco commented 2 months ago

This uses Bluetooth, it does not use the bridge. Add Bluetooth proxy near your sensor

bdraco commented 2 months ago

https://esphome.io/components/bluetooth_proxy.html

https://esphome.io/projects/index.html

https://blakadder.com/gl-s10/