WifiNear issue

[BossMan]

Hi Pent,

I have been observing for some time some issues with my profiles
misbehaving when exiting the "night mode". Today I managed to capture
the log from that situation.

Long story short: my HomeWifi profile depends on the variable HOMESYNC
("equals 1") and Wifi Near contexts. Once the "night- sync off-
mode" ;) ends, HOMESYNC changes to 1 and I would expect a wifi scan
here. Wifi scan is not started but the HomeWifi profile becomes active
anyway and the entry task is started. Couple of seconds later Wifi is
turned on (from that entry task) and a scan is executed. The requested
AP is not found in the first scan, and the context WifiNear becomes
inactive and the profile goes inactive too.
Eventually, I have both exit task and entry task running
simultanously ;)

Based on the syslog, I can say that wifi near state was active all the
time during night, and it was only "blocked" by a variable context.

D/Tasker ( 3744): 01.44.18#StateContext: checkMatch: Wifi Near: false
-> true
===> sync off starts couple of seconds later, no need for more Wifi
scans

===> 6:59 - sync off ends
D/Tasker ( 3744): 06.59.25#StateContext: checkMatch: Wifi Near: true -
> false <==== this is where the ongoing WifiNear profile becomes
inactive

D/Tasker ( 3744): 07.14.53#StateContext: checkMatch: Wifi Near: false
-> true <==== here everything returned to normal

I have sent you the log - let me know if you need anything more :)

BR,
A.

[UncleMike]

If you're using Variable Subtract to alter the value of the variable,
this may be the problem. I reported to Pent the other day that tis
function seems to always set the value to zero. As a workaround I
have done something like:

Variable Set %HOMESYNC (%HOMESYNC - 1)

[BossMan]

No, it's not the problem with variables - they're set correctly (I
don't use add/subtract actions anyway). The issue is, WiFi Near
context reports as "active" without even performing a wifi scan.

BR,
A.

[Pent]

I got the log, will keep it, but won't be able to do anything for next
release.

Priority is getting onto the new google validation system so I don't
have to answer
10000 questions about validation in 7 days when the Lifehacker influx
'matures'.

Pent

[BossMan]

I haven't said anything - I'm a patient customer ;-)

Fully understood. Thanks,
A.