# Utilisation de l'émetteur BLE de l'app android

**URL:** <https://forum.hacf.fr/t/utilisation-de-lemetteur-ble-de-lapp-android/28543>\
**Category:** Entraide Home Assistant\
**Tags:** ble-proxy\
**Created:** [Septembre 25, 2023, 5:52 UTC](https://forum.hacf.fr/t/utilisation-de-lemetteur-ble-de-lapp-android/28543 "2023-09-25T17:52:43Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![Idaho947](https://forum.hacf.fr/user_avatar/forum.hacf.fr/idaho947/32/36207_2.png) [@Idaho947](https://forum.hacf.fr/u/Idaho947)\
**Post date:** [Septembre 25, 2023, 5:52 UTC](https://forum.hacf.fr/t/utilisation-de-lemetteur-ble-de-lapp-android/28543/1 "2023-09-25T17:52:43Z")

</div>

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 «&nbsp;personne&nbsp;». Il n’est pas vu non plus par le ibeacon tracker.  
Si quelqu’un pouvait m’expliquer comment faire ?

---

<div class="post-metadata">

**Author:** ![Idaho947](https://forum.hacf.fr/user_avatar/forum.hacf.fr/idaho947/32/36207_2.png) [@Idaho947](https://forum.hacf.fr/u/Idaho947)\
**Post date:** [Septembre 29, 2023, 3:19 UTC](https://forum.hacf.fr/t/utilisation-de-lemetteur-ble-de-lapp-android/28543/2 "2023-09-29T15:19:50Z")

</div>

Personne n’utilise cette option de l’appli ? Le pire c’est que je vois bien les beacon avec l’application android BLE scanner

---

<div class="post-metadata">

**Author:** ![Pulpy-Luke](https://forum.hacf.fr/user_avatar/forum.hacf.fr/pulpy-luke/32/137426_2.png) [@Pulpy-Luke](https://forum.hacf.fr/u/Pulpy-Luke)\
**Post date:** [Septembre 29, 2023, 4:20 UTC](https://forum.hacf.fr/t/utilisation-de-lemetteur-ble-de-lapp-android/28543/3 "2023-09-29T16:20:34Z")

</div>

Salut,

Tu as regardé les `device_tracker` ?  
Tu as l’option d’[inclusion auto](https://www.home-assistant.io/integrations/bluetooth_le_tracker/) ?

---

<div class="post-metadata">

**Author:** ![Idaho947](https://forum.hacf.fr/user_avatar/forum.hacf.fr/idaho947/32/36207_2.png) [@Idaho947](https://forum.hacf.fr/u/Idaho947)\
**Post date:** [Septembre 29, 2023, 4:25 UTC](https://forum.hacf.fr/t/utilisation-de-lemetteur-ble-de-lapp-android/28543/4 "2023-09-29T16:25:38Z")

</div>

Oui je l’ai laisser tourner toute la nuit.

---

<div class="post-metadata">

**Author:** ![Pulpy-Luke](https://forum.hacf.fr/user_avatar/forum.hacf.fr/pulpy-luke/32/137426_2.png) [@Pulpy-Luke](https://forum.hacf.fr/u/Pulpy-Luke)\
**Post date:** [Septembre 29, 2023, 4:30 UTC](https://forum.hacf.fr/t/utilisation-de-lemetteur-ble-de-lapp-android/28543/5 "2023-09-29T16:30:47Z")

</div>

Active le logs de BLE sous HA alors

---

<div class="post-metadata">

**Author:** ![Idaho947](https://forum.hacf.fr/user_avatar/forum.hacf.fr/idaho947/32/36207_2.png) [@Idaho947](https://forum.hacf.fr/u/Idaho947)\
**Post date:** [Septembre 29, 2023, 4:34 UTC](https://forum.hacf.fr/t/utilisation-de-lemetteur-ble-de-lapp-android/28543/6 "2023-09-29T16:34:16Z")

</div>

En rajoutant les lignes dans le config.yaml ?

---

<div class="post-metadata">

**Author:** ![Pulpy-Luke](https://forum.hacf.fr/user_avatar/forum.hacf.fr/pulpy-luke/32/137426_2.png) [@Pulpy-Luke](https://forum.hacf.fr/u/Pulpy-Luke)\
**Post date:** [Septembre 29, 2023, 4:37 UTC](https://forum.hacf.fr/t/utilisation-de-lemetteur-ble-de-lapp-android/28543/7 "2023-09-29T16:37:15Z")

</div>

oui :

```auto
logger:
  logs:
    homeassistant.components.bluetooth_le_tracker: debug

```

---

<div class="post-metadata">

**Author:** ![Idaho947](https://forum.hacf.fr/user_avatar/forum.hacf.fr/idaho947/32/36207_2.png) [@Idaho947](https://forum.hacf.fr/u/Idaho947)\
**Post date:** [Septembre 29, 2023, 4:58 UTC](https://forum.hacf.fr/t/utilisation-de-lemetteur-ble-de-lapp-android/28543/8 "2023-09-29T16:58:19Z")

</div>

Ok je tente ça et je poste le truc.

---

<div class="post-metadata">

**Author:** ![Idaho947](https://forum.hacf.fr/user_avatar/forum.hacf.fr/idaho947/32/36207_2.png) [@Idaho947](https://forum.hacf.fr/u/Idaho947)\
**Post date:** [Septembre 29, 2023, 6:25 UTC](https://forum.hacf.fr/t/utilisation-de-lemetteur-ble-de-lapp-android/28543/9 "2023-09-29T18:25:44Z")

</div>

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 :

 ![image](https://forum.hacf.fr/uploads/default/original/3X/e/b/eb8d352c17328ed05c7e93d9bc7a04d103d3f125.png)

![image](https://forum.hacf.fr/uploads/default/original/3X/4/5/45df2a98edc951b7d366a06ffc3f77f97e549599.png)

Dans les logs j'ai que des lignes de ce type :  
 ![image](https://forum.hacf.fr/uploads/default/original/3X/d/8/d8ed922f84329808d04157218fe663c0bee71e65.png)

rien avec un uuid et aucune mac n'est celle de mon portable

---

<div class="post-metadata">

**Author:** ![Idaho947](https://forum.hacf.fr/user_avatar/forum.hacf.fr/idaho947/32/36207_2.png) [@Idaho947](https://forum.hacf.fr/u/Idaho947)\
**Post date:** [Septembre 30, 2023, 4:49 UTC](https://forum.hacf.fr/t/utilisation-de-lemetteur-ble-de-lapp-android/28543/10 "2023-09-30T16:49:03Z")

</div>

Je viens de recevoir un ibeacon sensé être compatible avec ha  
[https://fr.aliexpress.com/item/32826502025.html?gatewayAdapt=glo2fra](https://fr.aliexpress.com/item/32826502025.html?gatewayAdapt=glo2fra)

il n'est pas vu par l'intégration !

---

<div class="post-metadata">

**Author:** ![Pulpy-Luke](https://forum.hacf.fr/user_avatar/forum.hacf.fr/pulpy-luke/32/137426_2.png) [@Pulpy-Luke](https://forum.hacf.fr/u/Pulpy-Luke)\
**Post date:** [Septembre 30, 2023, 5:34 UTC](https://forum.hacf.fr/t/utilisation-de-lemetteur-ble-de-lapp-android/28543/11 "2023-09-30T17:34:02Z")

</div>

ça genere pas une MAC alétoire ?  
Il me semble que c’est une option d’android

---

<div class="post-metadata">

**Author:** ![Idaho947](https://forum.hacf.fr/user_avatar/forum.hacf.fr/idaho947/32/36207_2.png) [@Idaho947](https://forum.hacf.fr/u/Idaho947)\
**Post date:** [Septembre 30, 2023, 5:41 UTC](https://forum.hacf.fr/t/utilisation-de-lemetteur-ble-de-lapp-android/28543/12 "2023-09-30T17:41:16Z")

</div>

Non je suis en mac fixe. Mais même avec un ibeacon sensé être compatible ça ne marche pas. Je dois rater une config.

---

<div class="post-metadata">

**Author:** ![bastien88](https://forum.hacf.fr/user_avatar/forum.hacf.fr/bastien88/32/48839_2.png) [@bastien88](https://forum.hacf.fr/u/bastien88)\
**Post date:** [Mai 8, 2024, 5:24 UTC](https://forum.hacf.fr/t/utilisation-de-lemetteur-ble-de-lapp-android/28543/13 "2024-05-08T17:24:35Z")

</div>

Bonjour,

> <https://github.com/home-assistant/core/pull/104790>
>
> \## 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?

---

<div class="post-metadata">

**Author:** ![Idaho947](https://forum.hacf.fr/user_avatar/forum.hacf.fr/idaho947/32/36207_2.png) [@Idaho947](https://forum.hacf.fr/u/Idaho947)\
**Post date:** [Mai 8, 2024, 6:22 UTC](https://forum.hacf.fr/t/utilisation-de-lemetteur-ble-de-lapp-android/28543/14 "2024-05-08T18:22:29Z")

</div>

tu l’ajoute dans la configuration de l’intégration.

---

<div class="post-metadata">

**Author:** ![bastien88](https://forum.hacf.fr/user_avatar/forum.hacf.fr/bastien88/32/48839_2.png) [@bastien88](https://forum.hacf.fr/u/bastien88)\
**Post date:** [Mai 9, 2024, 2:18 UTC](https://forum.hacf.fr/t/utilisation-de-lemetteur-ble-de-lapp-android/28543/15 "2024-05-09T14:18:55Z")

</div>

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.
