Flowchart with my profiles, events, tasks, etc.: need some advice

[Mickets]

Hello,

I setup some profiles and tasks based on location, state, etc., which
set the values of some variables. The sum of these variables
determines the state (near, at location, near wifi, connected). And
the state is monitored so that things happen or don't happen.

But Tasker is currently responsible for ~30% of battery usage.

I made a flowchart of my setup, which I posted at TinyPic, here:
http://i52.tinypic.com/dcudsw.png

I'll try to embed it below this message, but I don't think that's
allowed here.

Anyway, if anyone could take a look at my setup and offer some advice,
I'll be very thankful.

I know there is one thing I can change (call the Mode tasks directly
instead of setting another variable %MODE and monitoring it), but for
the mean time I'll leave it like that, as it was like this before and
it worked fine (with low battery usage).

It may be that monitoring WiFi Near and WiFi Connected could be
guilty, but I disabled those for some time and nothing changed.

Thanks for any advice.

Mickets

<a href="http://tinypic.com?ref=dcudsw" target="_blank"><img
src="http://i52.tinypic.com/dcudsw.png" border="0" alt="Image and
video hosting by TinyPic"></a>

[IMG]http://i52.tinypic.com/dcudsw.png[/IMG]

[Paul van Rossen]

looks like this is not all? i'm not seeing how %myplace is ever going
to be 20 for example?

is your 'near wifi' state always enabled? That one can drain your
battery.

[Mickets]

No it's not all. %MYPLACE will be 10 when near home, 20 when near
office (which I didn't depict here).

No, "Near WiFi" is only enabled when %MYPLACE > 0 (i.e. I'm near a
known place).

I have to update the flowchart, but I made some basic changes:

- Removed the State: In Location -> Set %MYIN = 2. Often the location
would be incorrect due to poor network or bad GPS reception.
- From above, I now allow %MMODE to be set to the proper mode
according to the location, and as long as %MSTATUS > 0 (no longer >
1). This implies that it will set the mode once I'm in cell coverage
of one of my known locations, which is triggered before I'm actually
in my home, but at least it works and doesn't get hampered by poor
location data as I mentioned above.
- For the WiFi Near states, I enabled "toggle", which means it will
turn on WiFi for a few seconds each check, and then turn it off. One
can change the WiFi check interval in Tasker's settings. Currently
it's 120s, and the battery is not being drained (when I'm away from
WiFi - when I'm close it's always connected anyway). But I may
increase that interval a bit more.

Thanks for your revision.

Michael