It doesnât look like they can be detected when they are connected to your phone. But I turned my bluetooth off and had a look at the output of the ghome and found this:
I have 5 home minis and room detection would allow me to shut off lights when no one is in the room because people have a tendency to walk out and âforgetâ they were on.
Iâve tried and tried but it just wonât work unless bluetooth settings are open.
this seems to be phone specific. I can set my oneplus5 to be discoverable, but I remember that my previous phone only allowed it when the Bluetooth settings were open.
I actually tried that but It wouldnât work either. I also looked at the activity trackers I have and they wonât show up either once paired with a phone.
Yeah my miband2 would work until paired. Fitbits seem to work fine. I had some luck unplugging the Google home then powering up again to get it to detect and report rssi values. Do you have the Google home set to a static IP address also?
I have had some success with my op6t using that option. Although not as reliably as a Fitbit. Not sure why? I am thinking of getting a https://www.beaconzone.co.uk/Wearable/iB001W
Iâve been attempting to recreate @bottsâs setup using a single template sensor, and Iâm close! Below is the template I created to contain the name of the Google Home device with the strongest signal for a given BT MAC. Unfortunately, although it works correctly, it never updates after the initial HA startup. Does anyone know how I might HA to periodically re-evaluate the result of the template and update the sensor?
platform: template
sensors:
jasons_phone_location:
value_template: >
{% set ns = namespace() %}
{% set ns.maxsignal = -100 %}
{% set ns.trackername = "" %}
{% for item in states.device_tracker
if item.state == 'home'
and item.attributes.scanner == 'GoogleHomeDeviceScanner'
and item.attributes.btle_mac_address == '94:65:2d:6d:e8:83' %}
{% if (item.attributes.rssi | int) > ns.maxsignal %}
{% set ns.maxsignal = (item.attributes.rssi | int) %}
{% set ns.trackername = item.attributes.ghname %}
{% endif %}
{% endfor %}
{{ ns.trackername }}
@JayWll I knew there would be a more elegant way of doing it! Nice work! Just need to learn how to write something that way! Also the update_entity has removed the issue of a Google home going âofflineâ
I just did a quick test, and unfortunately not. At the top of that page it says that those options work with components that are based on the âentityâ class. I donât fully grasp what that means, except that I guess the device_tracker components that get created when the Google Home identifies a new BT device are presumably not based on the entity class.
All in all, this turned out to be less useful than Iâd hoped. I found a tile mate at the office weâd received a Christmas Gift from an old vendor so I took it home and attached it to my dog. He gets picked up by one of the Google Homes we have from time to time but generally heâs not found by any of them, even though he actually spends ~80% of his time very close to either the Home Mini we have in the bedroom, or the Home we have in the kitchen.
Itâs a similar story for my phone, which is in the bedroom with me (orange) all through the night but mostly shows up as not being found (purple).
Iâm definitely interested if anyone has any tips and tricks. For now Iâm just glad that I stole the tile Iâm using rather than paying for it