%WIFII

433 views
Skip to first unread message

Bubba

unread,
Aug 17, 2011, 12:42:22 PM8/17/11
to Tasker
Needs some refinement and clarification in the userguide about what it
gives. I expected it to be a simple AP readout, but its not. In order
to read a system variable I had to go and clone it to a user variable
(another gripe, variable list should give the option of showing system
variables, or there should be a variable display for a specific one)
and found it shows not only the AP, but the signal strength and MAC.
Not very useful to be human readable when it is so cumbersome to get
to display anyway. Furthermore, your signal strength isn't ever going
to be predictable and if you have a large wifi network over multiple
routers your MAC is going to vary.

There isn't really a convenient way to do a wifi connection check to a
specific AP without branching it over two profiles and using the "Wifi
connected" state. It would be much simpler if there were a single
variable to call up to check the AP so you could use it in if clauses
in a single profile.

strictlyrude27

unread,
Aug 17, 2011, 9:07:29 PM8/17/11
to Tasker
brandall wrote a way to get the SSID from %WIFII, here's the steps:

1) Variable Split %WIFII , splitter <<<
2) Variable Split %WIFII2 , splitter Mac:
3) Variable Set: %SSID to %WIFII21
4) Variable Clear %WIFII1
5) Variable Clear %WIFII2*, enable pattern match

I run this task upon wifi connected, and %SSID gets set with the AP
name.

BossMan

unread,
Aug 18, 2011, 5:13:50 AM8/18/11
to tas...@googlegroups.com
If you want to only check SSID when "wifi connected", a simple Variable Split, withe empty splitter (empty = default; space) should be enough - SSID is the 4th element (%WIFII4).

BR,
A.

Kevin Taylor

unread,
Aug 18, 2011, 11:13:32 AM8/18/11
to tas...@googlegroups.com
Unless the SSID contains spaces (mine do), in which case strictlyrude27'smethod works better.

Kevin

Bubba

unread,
Aug 20, 2011, 1:38:12 PM8/20/11
to Tasker
Thanks. Its an extra, and IMO unnecessary, step, but it works.
Reply all
Reply to author
Forward
0 new messages