Thanks, Just testing it out now and created a work Zone. When I select sources it doesn’t seem to pick anything up as a source to add it as a subject. Is it possible to say when my wife who’s a homey user leaves a work zone I could get a push notification? thanks
Sources are automatically discovered from devices exposing latitude and longitude. Because a homey user is not a device and doesn’t expose these values you can’t use it as a source.
On my side I use FindMy to get my iPhone position, there are some other possibilities for android users.
@Anoniemand
As I understand you’ll need something on each phone-to-track to provide for and send actual Lat & Lon information to Homey, like Macrodroid sending webhooks with f.i. geo as event, and latitude and longitude as tag, and then save this per flow to a virtual device via capabilities named measure_latitude and measure_longitude.
Only then this app can read the position(s) via this virtual device (one each phone).
I’m stuck.
Because I can’t create a virtual sensor with measure_latitude & measure_longitude, those capabilities don’t exist (yet) on Homey.
We can’t create our own custom capabilities with (Advanced) Virtual Devices apps
Thanks for the details.
Indeed you’re right, Device Capabilities doesn’t seems to enable lattitude & longitude as virtual capabilities.
Also some bugs on the previous version of GeoZones didn’t work properly so I made the v1.0.4 that now enables to create subjects from flowcards and you can enter the subject coordinates directly in flow cards like so (sorry i’m using french, but you’ll find this card as “Update [subject] with [Latitude], [Longitude]”):
After this card you can eather use the tokens created by the card (zone, previous_zone, speed, tags, etc) or use a trigger card “[Subject] Recalculated” or other to continue with the actions you want to set
Let me know if it works for you after that.
Also I’m curious from where you’ll retrieve the lat/long you want to use, MQTT, websocket, etc ?
Maybe I can in the future implement it as native source.
Unfortunately homey users doesn’t expose any info except presence and this is not working properly for most people. If you wish to have some geoposition logic you’ll need an external source for lat/long, then you’ll be able to use it in the app
It’s been discussed before, about why the Homey app doesn’t (seem to) allow access to the location of a mobile device, and not even to the owner.
At best you’d send a request to Athom, about allowing apps with certain rights to access location data of a mobile device of a Homey user account.
Like in HomeAssistant, like all sensors of mobile device, one can choose to pass a mobile devices’ location to H.A., which is no doubt familiar to Athom devs.
Looks quite uncomplicated to me (but hey, I’m no app developer)
So you can use the “Find my” app to pass the location data
My first thought was: when this app can do it, your app can do it? No clue how hard it is to implement, it was just a thought.
I don’t know if such an app exists for Android;
I’m quite familiar with the mobile Android app Macrodroid > with this app one has to define geofences, and then you can have it send commands depending on entering/leaving a specific geozone (it uses the Athom cloud)
One ‘issue’: one won’t need your app to send user geofence data to Homey and process it with flows.
But it’s fit to use for your app anyways.
To command Homey (from anywhere), we can use the webhook construction:
to pass data on, it has an event and a tag option.
I use the event name ‘geozones’, to trigger the corresponding listening flow;
I use the tag data formatted as JSON, to be able to split the lat & lon coordinates @ Homey
It’s been discussed before, about why the Homey app doesn’t (seem to) allow access to the location of a mobile device, and not even to the owner.
At best you’d send a request to Athom, about allowing apps with certain rights to access location data of a mobile device of a Homey user account with Homey app installed.
HomeAssistant, one can choose to pass a mobile devices’ location to H.A., which is with no doubt familiar to Athom devs.
Looks quite uncomplicated to me (but hey, I’m no app developer)
So you can use the (Homey & ios) “Find my” app to pass the location data.
My first thought was: when this app can do it, your app can do it? No clue how hard it is to implement, it was just a thought.
I don’t know if such an app exists for Android;
I checked life360 but this Android app needs my phone number as first setup step > a nono for me.
I’m quite familiar with the mobile Android app Macrodroid > with this app one has to define geofences, and then you can have it send commands depending on entering/leaving a specific geozone (it uses the Athom cloud)
One ‘issue’: one won’t need your app to send user geofence data to Homey and process it with flows.
But it’s fit to use for your app anyways.
To command Homey (from anywhere), we can use the webhook construction:
to pass data on, it has an event and a tag option.
I use the event name ‘geozones’, to trigger the corresponding listening flow;
I use the tag data formatted as JSON, to be able to split the lat & lon coordinates @ Homey
I’ve got it working via Home Assistant, it’s the last thing that isn’t easy (without a 3rd party app) replaceable in Homey. But after hanging around here for about 3 months now, I’m moving more towards keeping both (HA and Homey) instead of only using one of them.
Install the latest test version here:
