Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Voice PE / Improv Wi-Fi device Not Discovered #4936

Closed
PTracks opened this issue Dec 26, 2024 · 14 comments · Fixed by #4952
Closed

Voice PE / Improv Wi-Fi device Not Discovered #4936

PTracks opened this issue Dec 26, 2024 · 14 comments · Fixed by #4952
Labels
bug Something isn't working

Comments

@PTracks
Copy link

PTracks commented Dec 26, 2024

Home Assistant Android app version(s):
2024.12.1-full
Android version(s):
Android 15
Device model(s):
Pixel 6 Pro
Home Assistant version:
2024.12.4
Last working Home Assistant release (if known):

Description of problem, include YAML if issue is related to notifications:
Companion App will not discover the Voice PE device. Voice PE displaying warm twinkle animation. App precise location permission is set to allow all the time.

Companion App Logs:


Screenshot or video of problem:

Additional information:
Android pair new Bluetooth device does show "home-assistan-xxxxxx" as an available device but manual pairing does not complete.

@PTracks PTracks added the bug Something isn't working label Dec 26, 2024
@jpelgrom
Copy link
Member

jpelgrom commented Dec 26, 2024

Do you have Bluetooth on and Nearby devices permission enabled for the app?

If yes, can you turn on the device, go to devices and services and wait a second or 10 for scanning, and then get logs from the app? That could provide more details if it is failing to scan.

@jpelgrom jpelgrom changed the title Voice PE Not Discovered Voice PE / Improv Wi-Fi device Not Discovered Dec 26, 2024
@PTracks
Copy link
Author

PTracks commented Dec 26, 2024

Bluetooth is enabled and app has the nearby devices permission. Here is the app log:

homeassistant_companion_log_11-26-2024_13-16-32.txt

@jpelgrom
Copy link
Member

Your log file shows that scanning is started, but no obvious errors 🤔

12-26 13:15:56.183 25505 25648 D WebviewActivity: External bus {"type":"improv/scan","id":45} 12-26 13:16:00.010 25505 25505 D SensorReceiver: Received intent: android.intent.action.TIME_TICK 12-26 13:16:00.014 25505 25525 I SensorReceiver: Skipping faster update because not charging/different preference 12-26 13:16:13.522 25505 25648 D WebviewActivity: External bus {"type":"improv/scan","id":46} 12-26 13:16:19.938 25505 25648 D WebviewActivity: External bus {"type":"config_screen/show","id":47}

Could you try the following? It may help resolve the problem or indicate where the issue lies.

  1. Turn Bluetooth off and on again on your phone.
  2. Force stop the Home Assistant app from system settings.
  3. Turn the voice hardware off and on again so the advertisement is transmitted again.

@PTracks
Copy link
Author

PTracks commented Dec 26, 2024

I tried those steps and it's still not detected. Here is a new log.

homeassistant_companion_log_11-26-2024_14-31-10.txt

@jpelgrom
Copy link
Member

Thanks for the quick response. Unfortunately, still nothing pointing to things going wrong.

I do see a line about beacons in the log. Are you using the Bluetooth scanner/transmitter in the app by any chance, or have another app active doing stuff like that? If so, could you try pausing those?

@PTracks
Copy link
Author

PTracks commented Dec 26, 2024

I'm not aware of intentionally setting up any Bluetooth scanning either in HA or another app. I'll do some investigation, but don't think this is the issue.

@dshokouhi
Copy link
Member

I'm not aware of intentionally setting up any Bluetooth scanning either in HA

Looks like you have our beacon monitor sensor enabled, can you try turning off the monitor or disabling the sensor?

Settings > companion app > manage sensors > beacon monitor

12-26 14:30:00.725 25702 25702 I BeaconManager: BeaconManager started up on pid 25702 named 'io.homeassistant.companion.android' for application package 'io.homeassistant.companion.android'.  isMainProcess=true

@PTracks
Copy link
Author

PTracks commented Dec 27, 2024

Looks like you have our beacon monitor sensor enabled

Not as far as I can tell. The Beacon Monitor sensor was already disabled.

Screenshot_20241226-231327

@kkellner
Copy link

I'm having the same issue. Only difference is I'm on Pixel 9 Pro and all of my Bluetooth sensors in the settings are turned off.

@kamaradclimber
Copy link

kamaradclimber commented Dec 30, 2024

Same behavior on a fairphone 4 and all bluetooth sensors are turned off as well

Fixed by following: https://community.home-assistant.io/t/home-assistant-not-discovering-voice-pe/816137/16?u=kamaradclimber

@jpelgrom
Copy link
Member

jpelgrom commented Jan 3, 2025

The latest beta release, 2024.12.7, includes some additional logging to (hopefully) figure out what the issue is. If you're willing to join the beta please try again and post your logs, or wait for this version to release as a stable version soon.

@PTracks
Copy link
Author

PTracks commented Jan 3, 2025

The latest beta release, 2024.12.7, includes some additional logging to (hopefully) figure out what the issue is. If you're willing to join the beta please try again and post your logs, or wait for this version to release as a stable version soon.

Updated to the beta app and tried to discover again. Looks like the app is complaining about permissions even though precise location and nearby device permissions are both enabled.

homeassistant_companion_log_0-3-2025_11-23-0.txt

01-03 11:21:09.873 8698 8902 D WebviewActivity: External bus {"type":"improv/scan","id":8}
01-03 11:21:09.873 8698 8698 D WebViewPresenterImpl: Improv scan request ignored because app doesn't have permission

Screenshot_20250103-112718
Screenshot_20250103-112735

@PTracks
Copy link
Author

PTracks commented Jan 3, 2025

Ok, I was finally able to get it to work with my Android phone. I removed the location and nearby devices permissions. Force closed the app. And then re-enabled the permissions. The voice PE was then discovered and on-boarded successfully.

@jpelgrom
Copy link
Member

jpelgrom commented Jan 3, 2025

Thanks for the log and workaround (force closing shouldn't be necessary; if you revoke permissions Android will do that for you).

Based on your data, I guess there is a difference between the permission group (settings screen) and actual permissions (what the app checks) which is why the app doesn't prompt for the additional permission. There is some logic to not continue prompting in case you don't want to give the app permission, which must be triggered here, so this will take some consideration in updating that check 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants