The "Home Location" profile looks fine according to the example, assuming that the location and radius cause it to activate when you want it to.
In the "Wifiscan" profile, you have a state context labeled "Wifi scan". Since there is no such context in Tasker, I assume you named the context. Unfortunately I can't tell what it does, but I'll take a guess that it's a Wifi Near context (that would make sense to me). If that's the case, the second context should be "Variable Value %WIFISCAN = 1".
The Variable Value context is true for as long as the value of the variable meets the conditions you established (in this case, for as long as it remains equal to 1). In contrast, the Variable Set context is only true at the moment the variable begins to meet the conditions you established (it's instantaneous). All Event contexts in Tasker work the same way - they're instantaneous.
Looking at that second profile further, it is a VARIABLE SET %WIFISCAN,*. Seems to me it is checking to see if that variable exists, and if it does, then the Wifi Near can start. The task is Turn Wifi on. I'm not sure why the wifi wouldn't just come on and stay on in that scenario.
You are right, that context is Wifi Near. I named it based on following instructions maybe a bit too literally. Actually you can't see what it is doing because of the possibility there are other things in there, But it is doing exactly what the pic says: Turning on WIFI. So that leaves me with the question, do I need to then enter a variable there and set it to 1, like you suggested?
Not to further complicate things, but it's possible to combine these into a single profile, but leaving them separate gives you more flexibility later on if you want to trigger other things to happen when you're home, and you also want those things to happen when you're somewhere else. But let's skip that for now.
Thanks Uncle Mike. (I think I've seen you over in the Google Groups...or someone with same moniker).
I was wandering about that variable. It is set, and has a clear, in that same context. What I need to be able to do is understand how it all works well enough to draw myself a flow chart

In fact, based on the way it looks now, I'm not sure what the first profile has to do with turning on the WIFI Near, unless there is a variable there. I'll add it, and test today at lunch.
I tend to be VERY LITERAL, when following instructions, and often instructions take it for granted that the follower knows enough to fill in the blanks. But then filling in the blanks often leads to trouble too.
By the way, there was a discussion also about the fact that it could be done in 1 profile over on the Google thread too.
[EDIT]
I have not changed anything on the script yet.
But right now I am noticing that the Home Location script is active. The WiFi Near is not (I renamed it from WiFi Scan).
I'm not sure I see how it woudl turn off my WIFI when I leave here. Another thing, I've read that a script won't override manually set items, and of course at the moment I turned it on manually. Maybe it takes a move in/out of a location a time or two?
[EDIT2]
Had an opportunity to test. Very little luck. Here is what I experienced:
I drove for a quite a way that I thought would be out of the reach of NET Location but tasker kept the Home Location alive. I went into Tasker and turned it off, and back on. Long story short, I guess I needed to activate again even though it was 'on'.
So I went for another drive. Let the phone go dark. Went to point I felt definitely was out of HOME, and nothign had happened (I also set a SAY to announce when it changed). As soon as I turned the phone on, it announced "Leaving Home Location". So it appears that it was not working while phone was dark (sleep mode I guess its called).
So I turned around and went home. It did not come back on for NET until I got inside the house and had turned the phone on and off a couple times. The WiFi near never activated.
Speaking of which, ultimately, I'd like the WiFi to go off just as soon as I leave the WIFI reach of my home network, as opposed to the NET.
More testing/changes to do it seems.
I'm going to combine it all in one profile