The ping tracker will have a state of ‘home’ if the device responds to pings. When it doesn’t, and it hasn’t for the consider_home period, then its state will change to ‘not_home’. The ping device tracker does not provide GPS data.
I haven’t used the GPSLogger platform, but my guess would be it works like other GPS-based trackers in that it will provide GPS coordinates, which will be used to determine where the device is. E.g., if it’s in the home zone, then it will be considered ‘home’. If it’s in another defined zone, then the state of the device_tracker will be the name of the zone. Otherwise, the state will be ‘not_home’.
EDIT: I should add, by default these will each create a unique device_tracker entity, and they will work independently. There will also automatically be a group named group.all_devices, whose state will be ‘home’ if either of the two devices are ‘home’, and will be ‘not_home’ if all of the devices are not ‘home’.
Fair warning: the ping tracker can be fairly, and sometimes very, unreliable. This is due to the fact that many cell phones like to ignore pings to save battery. I happen to be testing it recently myself, and this is what the past day looks like:
Notice all the changes between Home (i.e., ‘home’) and Away (i.e., ‘not_home’) yesterday. I was actually home the whole time. Then you can see when I put the phone on the charger it responded all the time (i.e., the solid Home period.) But then in the morning it became erratic again until I left.
So, typically this type of presence detection must be carefully used in conjunction with others. There are plenty of topics about this. You should read up.
I believe you can control how often it will try to ping, and when it pings how many pings it will send until it gets a good response (if any), and how long of a period of no response should still be considered home. But even with all that, if the device chooses not to respond for an hour or more (which is not uncommon), then you’re still going to have times where the tracker’s state goes to ‘not_home’ when the device is really at home. (And the longer you set the consider_home period to try and compensate, the longer it will take to change to ‘not_home’ when you actually leave.) So previous warning still applies.