The reason I was trying to force Away is because the Pixel seems to have a hard time (= slow) moving to mobile data. As a result, I can never get my geofences to fire.
They do seem to try their best to hold on to a WiFi connection to the point that there is often a short drop there... I've seen where it is too aggressive in turning OFF the WiFi during sleep as well such that it will wake the applications prior to the network connection, making DomoPad think it needs to switch to mobile.
I'd suggest you do the opposite of what you have -- try only setting the Home address (even if it is an external IP) and turning off the auto-switching. I'm having to do a bunch of rewriting in the application for various technical reasons (some forced by Google, some to technically comply with some laws though this is likely not a huge deal, and some have to be done in order to get to some of the features that I have been promising that turned out to be a dead end with the current implementation). At any rate, I am going to have to look into a new method for spinning up the check because of some of the phone's behavior... as you said, works perfectly on some phones and not so well on others. Geofencing and trying to control from wake (where you had DomoPad open already) are the two biggest symptoms.
Anyway, try the Home address -- I don't think it should have any real consequence of having an external IP in there as long as the Away setting is blanked out. The reason for this is that if something fails miserably (e.g. neither connection is found) it may default to trying the Home location again first before switching.
Adam