Using passed value to determine Geo fencing state

[jackmasih]

I followed the flow for passing a second person's homestate to my phone. The problem I'm running into is how do I then determine when both are away. I have my homestate and my wife's homestate on my phone, but for the life of me have not been able to trigger only when both of us are away. Please help.

[angus_marshall]

The way I do this is that I have variables for my location (angus_location) and my wife location (kwang_location). Mine is updated by the local Stringify geolocation setting a mode. My wife's is updated using the maker thing approach that I think you have used. So then, in additional flows, you simply use these 2 variables as "only if' things. So set up your flow and then right at the start, hook in both your variables to the first yellow dot of your flow and select them to be "only if variable matches a value". Then, in my case I use angus_location=out for one and kwang_location=out for my wife to indicate we are both out. Use =home for home state. Or =bed or =asleep for different states. It works well.

[jackmasih]

Thanks Angus. That was one of the first things I tried, however, it keeps saying it's an invalid flow. It says I need at least one 'when' trigger. What an I doing wrong? I have resorted to trying all sorts of crazy flows, but nothing seems to work.

[jackmasih]

Ok, I figured it out. I feel like an idiot because it's so simple. I just created two similar flows that do what you said but one was a when trigger and I reversed the variables for the two flows.

Quick question for home mode does it trigger for you every time a person enters? In other words if I'm home and my wife arives it still triggers home mode. I don't think it's a big deal, but figured if I could solve that it'll be perfect.

[jackmasih]

Ok, disregard, I figured it all out, even the home mode. I guess some sleep does miracles for the thinking process.

[angus_marshall]

Ha ha ha, yeah I know the feeling well. Glad you got it working. It's so cool when IoT works properly (which seems for me to not be all the time, unfortunately)