Qingping Air Monitor Lite not being discovered

mariomaz87 commented 11 months ago

The problem

Hi, I have a Qingping Air Monitor Lite that I added to HomeKit (native integration). I'm trying to integrate it also in HA using the Qingping integration. If I add the integration it says "No devices found on the network". The Air Monitor is connected to my wifi network and Home Assistant is running as a container on a Pi4, with host network setting and with Ethernet connectivity to my router.

What version of Home Assistant Core has the issue?

2023.11.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Qingping

Link to integration documentation on our website

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

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 11 months ago

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

Code owner commands

Code owners of `qingping` 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 qingping` 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)}}

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

bdraco commented 11 months ago

Which Bluetooth adapter are you using?

Have you tried moving the device closer to the Bluetooth adapter?

mariomaz87 commented 11 months ago

Which Bluetooth adapter are you using?

Have you tried moving the device closer to the Bluetooth adapter?

I’m using the Bluetooth adapter integrated in a Rasp Pi4 and now I’ve also tried by moving the device next to the Raspberry but still no luck. Thanks.

jonalbr commented 11 months ago

The Qingping Air Monitor Lite does not transmit over Bluetooth if in home kit mode. You need to reset your Qingping Air Monitor Lite and choose the other option (don’t know what the app called it, just not home kit). Than it should be discovered. You than can add the device back to HomeKit using home assistant as a bridge (not directly as this would again deactivate the Bluetooth transmission as the home kit mode relies on WiFi only)

mariomaz87 commented 11 months ago

Thanks, it’s now working correctly.

flle commented 10 months ago

I am also having issues with the Air monitor lite. I do not have a problem with initial discovery, it is discovered by HA right away via bluetooth and the quingping integration but after a few minutes it becomes unavailable (no more sensor data). I have a bluetooth proxy right next to the air monitor. I have already reset it a few times and it is always the same behaviour: Discovered, sending data for a few minutes and then becomes unavailable. I have not integrated it into any other solution (Home Kit or MI). Any ideas what the issue could be?

jonalbr commented 10 months ago

I had a similar issue (no data after a couple of hours) while I used the ‘Passive BLE monitor integration’ (HACS) along the Qingping integration. It seemed that officially supported integrations that use Bluetooth ble like the Qingping integration and the custom integration from HACS were not able to share the Bluetooth receiver. Only as I removed Passive BLE monitor it worked as expected. An other option which worked for me is to just use Passive BLE monitor as it also supports qingping, just make sure that you don’t have any other BLE integrations.

Honestly, I would’ve thought that having a second Bluetooth receiver like I would expect a Bluetooth proxy works like would solve that sharing issue. So maybe your issue is not related.

issue-triage-workflows[bot] commented 7 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

derpuma commented 7 months ago

Passive BLE monitor

Thanks for your help. So far this worked for me, and Passive BLE Monitor detected the Qingping Air Monitor lite immediately. Unfortunately I get no values. Any idea why?

issue-triage-workflows[bot] commented 4 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ncd7 commented 4 months ago

Watching this thread.

jonalbr commented 4 months ago

@derpuma are you using any native integration that uses Bluetooth? If so see my comment above. All my Bluetooth related problems were gone as soon as I stop using both the custom ble integration and any native Bluetooth integration

issue-triage-workflows[bot] commented 1 month ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

home-assistant / core