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:
