Well, maybe the example is too general. I could, instead of triggering on house mode set by geofencing, trigger on a specific user coming home or going away.
I could use Vera Proximity, but I find the vera app working quite well for geofencing.
It’s hard to build an efficient trigger on device or system attributes. Device variables are complex data structures with the mechanism to watch them, whereas attributes are simply light-weight value holders. AFAIK, the user settings themselves are part of the user_data which itself requires perhaps 200 or 300 Kbytes to download and then you have to parse it. Not something to be done as a regular basis.
I use per user enter/exit scenes triggered by the Vera App geofences and toggle multi switch buttons in those scenes. You then have a device reflecting the home/away status and you can watch those BAU.
BTW, to use with MultiSwitch, create and test the scenes using a browser and only then add the Geofence trigger in the Vera App. After adding a Geofence trigger you will not see the scene in your browser anymore.
I use per user enter/exit scenes triggered by the Vera App geofences and toggle multi switch buttons in those scenes. You then have a device reflecting the home/away status and you can watch those BAU.
BTW, to use with MultiSwitch, create and test the scenes using a browser and only then add the Geofence trigger in the Vera App. After adding a Geofence trigger you will not see the scene in your browser anymore.
Cheers Rene[/quote]
O wow, I wasn?t even aware of this functionality in the app. Thanks a lot!
Best Home Automation shopping experience. Shop at Ezlo!