Do your tags transmit (or can they be configured to transmit) any stable identifier like an iBeacon packet, apart from their function as Google FMDN devices? If so, local tracking should be possible using Bermuda etc, and a local integration to ping them to chime might be also.
But it’s quite possible they act only as FMDN devices, in which case I think you’ll need to have a FMDN integration. But once someone cracks that (and it looks like it should be do-able) that should also allow us to derive/verify the current BLE MAC so that Bermuda etc can track it locally as well.
@awh 's link to leonboe1’s repo seems to be the “head” of current actual efforts that I’m aware of. Google requires that manufacturers and I think end-user accounts register their devices so things are a bit trickier than the Apple system, but at least it’s openly documented - I’d think that for someone with the time and motivation, it might be possible to implement the registration and tracking of GFMDN tags entirely within HA - at least as a “development device” which would require frequent re-registration, but it will be a decent chunk of work (and I could easily be missing something that would be a total roadblock).
this is great, installed on device and have the server up.
Do you know of any way to integrate this FMD service into HASS? Like device location and such? with ntfy and FMD, I can send the device commands and automate that via HASS (button to turn ringer on, etc.) but I would like to get the location data from FMD as well in HASS and use it as a device tracker.
I have a LocaTag on my sneaky cat, and I would like to have a notification on Home Assistant every time he runs away, and a map to see the location.
Is that possible?
I opened an issue for a feature request for the fmd-server to support MQTT so we can integrate into Hass as device tracker, etc.
The maintainer seems willing to create some sort of way for us to make this possible, whenever that functionality is exposed, I will write the Hass integration to get things working in Hass.
@baudneo I don’t think that does what you think it does. As I read it FMD server only works to located devices running this “FMD app” not with google’s Find My Device network.
Nowhere in any of my posts did I say it has anything to do with Googles find my device network. Have you installed and deployed the FMD server and app?
You can remotely request GPS, Open Cell ID and network location (or all 3 at once), which would work great for a device tracker. I’d argue its much better than anything else because we can initiate a GPS ping from our end.
You can also send commands to take a picture and ring the phone using the Alarm channel (to bypass DnD). If you have root or use ADB, you can even make it that sending a command will enable location services if they are turned off.
All of this is to say, this software has AMAZING potential to be automated via HASS. “ok nabu, I lost my phone, please ring it and send a location request”
Hi @anon31320818 i think the confusion is that this thread is about Google/Android’s Find My Device network - I think what you are posting about is indeed interesting but its slightly different from the original ask. Plus if it gains traction it will be a big discussion in of itself as a FOSS alternative - so it probably needs its own thread.
That’s fair. Tbh, it doesn’t seem like the maintainer is interested in adding that functionality, so more than likely, it will never happen.
The reason I replied in this thread is because this is where I found the information on fmd-server, so I figured this was the best place to put that information.
I don’t think using Google’s Find My Device (a.k.a. Find Hub) network is possible for now, since the API isn’t open yet.
After they release an API, that should be easy (in general not for me ) create a way to view the devices, trigger alarms, etc.
But integrating this project fmd-foss is a good idea. I’m trying to break apart from Google these times and a way to tracker my devices would be nice.
) create a way to view the devices, trigger alarms, etc.