I fixed the Home Zone problem

Tasker can be tricky and lately I’ve noticed that my home profile was misbehaving which caused late triggers and irenaeus behaviour. The profile is designed to trigger a wireless connection to the home WiFi and run various tasks effectively adjusting my phone to the home environment.

Originally the profile was triggered by a simple location geofence; once I’ve crossed the boundary of the geofence, the profile would be triggered. However, this caused issues with the profile triggering more than once especially when getting close to the geofence boundaries. Given my current location, the GPS signal was a little shaky which caused random triggers of the profiles.

In order to fix the profile, I’ve devised a two zone system. The map above shows a sample location and how the geofence zones work with Tasker, the external zone (A) enables wireless connectivity which means that Android will start looking for familiar wireless networks; once it establishes a connection with the home network (internal zone B) the system will trigger all protocols responsible to enabling home mode.

A profile which manages the opposite, leaving the home mode, works by monitoring a smaller version of zone A; once the phone detects that you are outside of this geofence, it disables wireless connectivity and triggers various tasks which put the phone in ‘travel mode’.