Bonjour,
Je cherche des éclaircissement sur la fonction emetteur BLE de l’application companion android. Je l’ai activé, j’ai bien un uuid. J’ai bien activé la balise.
Il est vu par mes deux olimex avec proxyBLE mais je ne voit pas du tout comment l’ajouter à ma « personne ». Il n’est pas vu non plus par le ibeacon tracker.
Si quelqu’un pouvait m’expliquer comment faire ?
Personne n’utilise cette option de l’appli ? Le pire c’est que je vois bien les beacon avec l’application android BLE scanner
Salut,
Tu as regardé les device_tracker ?
Tu as l’option d’inclusion auto ?
Oui je l’ai laisser tourner toute la nuit.
Active le logs de BLE sous HA alors
En rajoutant les lignes dans le config.yaml ?
oui :
logger:
logs:
homeassistant.components.bluetooth_le_tracker: debug
Ok je tente ça et je poste le truc.
Je vois bien la découverte des périphériques bluetooth mais aucune trace d'un périphérique beacon. Pourtant ils sont bien vu par mes olimex :
Dans les logs j'ai que des lignes de ce type :
rien avec un uuid et aucune mac n'est celle de mon portable
Je viens de recevoir un ibeacon sensé être compatible avec ha
https://fr.aliexpress.com/item/32826502025.html?gatewayAdapt=glo2fra
il n'est pas vu par l'intégration !
ça genere pas une MAC alétoire ?
Il me semble que c’est une option d’android
Non je suis en mac fixe. Mais même avec un ibeacon sensé être compatible ça ne marche pas. Je dois rater une config.
Bonjour,
dev ← chatziko:ibeacon-allowlist
ouvert 10:21AM - 30 Nov 23 UTC
## Proposed change
This is a followup to #104419 (opening a new PR to keep … it clean), which aims to workaround #80357.
The ibeacon integration ignores beacons with empty/default name, to avoid some users getting lots of "garbage" devices.
This PR adds two independent UUID allowlists to accept iBeacons with empty names:
1. An explicit allowlist configurable via option flow.
2. An automatic allowlist of companion app beacons. We search for `mobile_app` entities with unique_id `*_ble_emitter` (note that the entity_id is `*_ble_transmitter`), and allow the UUID listed in the `id` attribute. This allowlist is kept separate from the explicit one, so it's never visible to the user.
Technical notes:
- Since the allowlist entry might be added after first seeing the beacon we need to store the ignored ones and re-process them later.
- Removing an allowlist entry does not remove any entities, the user will need to deleted them manually.
## Type of change
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [X] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
- This PR fixes or closes issue: fixes #80357
- This PR is related to issue:
- Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/30063
## Checklist
- [X] The code change is tested and works locally.
- [X] Local tests pass. **Your PR cannot be merged unless tests pass**
- [X] There is no commented out code in this PR.
- [X] I have followed the [development checklist][dev-checklist]
- [X] I have followed the [perfect PR recommendations][perfect-pr]
- [X] The code has been formatted using Ruff (`ruff format homeassistant tests`)
- [X] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [X] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
je ne comprend pas comment faire une liste blanche pour les équipements iBeacon UUID
quelqu'un aurait un exemple svp?
tu l’ajoute dans la configuration de l’intégration.
Ok merci.
J ai ajouter mon équipement. Mais j ai toujours aucune détection de mon tel android
Pourtant j ai bien le mineur sur 40004.