Mixture of Cell condition and WLAN event possible in onw rule?

[Christian Langanke]

Hi all,

I just started to use EasyProfiles (great prog BTW) and now came to a point where I can't get a certain rule to work.

Here is my initial problem: identifying my home location by checking for cell ids seems not to be accurate enough, because many cells overlap here. This results in a certain cell being used rarely and only for few seconds, which I wasn't able to catch, because it really shows up only few times a day and onyl for one or two seconds. But this suffices to randonly kick me out of my home location even if I am still there...
OTOH identifying my home by WLAN is said to be consuming (much?) more power. The alternative to reduce this by checking less frequently is not an option in my eyes - I would want the location to be checked all five mins as a minimum.

Here is my intended solution: I tried to identify my home location by cells as well as by my home WLAN at the same time. For that beside a location "Home cell" listing the cells around my home, I created a location "Home WLAN" searching for my WLAN SSID. Then I modified the "Reach home" rule to have a condition hecking all 5 mins of reaching the location "Home cell" and an event checking all 5 mins of reaching the location "Home WLAN" (no precondition or any other condition or event in the rule). If that worked, the WLAN would only be checked if the phone is in reach of the cells around my home. This would make my phone consume the extra power for the WLAN check only while it makes sense.

Here is the technical problem: for both the condition and the event I need to specify a time period before the next check takes place. But no matter how I set the periods of time for the two, it nearly never works. I try this for three days now, and it worked only two of fifteen times. It seems not to make a difference if I choose 2 mins, 5 mins or 10 mins for both the condition and the event and the. Moreover, it never worked when the times the condition and the event were different.

I *think* it should work if I was able to set the time period for the event check of the WLAN to zero mins, but that is currently not possible, and not knowing the exact checking scheme, I certainly may be wrong.

So my questions are: can such a rule work at all? Do I do something wrong? Wouldn't it possibly even make sense to allow a zero time period in the events if a condition is already rechecked only after a non--zero time period?

Thank you very much for a great pogram and for your help in advance!!!

[Sup...@smartdyne.de]

Hi Christian
I would go for two rules and a special profile "search for home WLAN" (sfhw).
Switch into sfhw when you are near (by checking cells).
In that profile the first rule will be deactivated automatically.
Then have another rule that switches into home when you really see your WLAN.
Even better would be to switch to hoome when you connect to your home WLAN.
Switch back to SFHW when disconnected from WLAN.
And switch away from SFHW when you no longer see your home cells.
This is kind of two step approach with away - nearby - at home!
Kay-Ulrich

--
You received this message because you are subscribed to the Google Groups "EasyProfiles User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to easyprofiles-u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
http://SmartDyne.de
Forum:http://groups.google.com/group/easyprofiles-user?hl=en
Translations:http://crowdin.net/profile/SmartDyne

[Christian Langanke]

Hey Kay-Ulrich,

thanks very much for the prompt reply! Your workaround is what I already implemented right after the last post - could not hold myself to make it work ;-)

On Friday, May 2, 2014 7:13:16 PM UTC+2, Sup...@SmartDyne.de wrote:

Hi Christian
I would go for two rules and a special profile "search for home WLAN" (sfhw).
Switch into sfhw when you are near (by checking cells).

, I added a "Home area" location for the cells, and the req. rules of course

 

In that profile the first rule will be deactivated automatically.
Then have another rule that switches into home when you really see your WLAN.

Yup, works like a charm.
 

Even better would be to switch to home when you connect to your home WLAN.

Switch back to SFHW when disconnected from WLAN.

I am not sure if I get that point, but I would not want to do switch off/on WLAN at home manually. However it works well now.

Now that my main WLAN location is well supported, I think about two others where I have WLAN as well. Of course, I would want to avoid to add another location plus two rules for each of these - as always, if one needs to work around a technical limitation of an application, is has drawbacks...

I still think about to make the "Home area" location to "WLAN area location" and add the cells of all WLAN locations to it, this would save me at least the extra in-between location for each WLAN location. But the extra two rules per WLAN location would still be required I think.

While this is doable it is a pita to have to have two more rules to build to check for that rather ordinary situation of reaching a WLAN, this makes the usage of the app even more complicated than it is already, wouldn't you think?

OTOH I would think that it wasn't that much of an effort to allow a non--zero time period for vents when a condition with a time period is defined. Only important would be that the user would have to be notified if (s)he deleted all conditions, while an event with a non--zero time period still existed - the app could automatically raise the time-period to one minute then.

So please consider making the app less complicated, and if, please let me know - I would really love to get rid of the superfluous extra rules !

Otherwise EasyProfiles is unmatched and for sure a great tool - would not want to miss it!

[Christian Langanke]

Hi again,

just thought that it was not absolutely necessarily required to add another two rules and a location - plus another profile (forgot about that in my previous post !) - for the second and third and more WLAN locations.

Possibly one profile "WLAN areas", two rules "Reach WLAN areas" and "Leave WLAN areas" plus a location knowing all cells of all WLAN areas would suffice. However, I think I still would prefer to keep the cells for different areas in different location definitions, so that it would be possible to empty the list of cells for onbe location and rescan them. It should be possible to add enter and leave events for all these locations into the "reach" and "leave" rule - if one fits, the rules should switch from or to the "Car" profile (here named "Road") as desired - is that correct?

Will try that out and post if it works. If so I well can live with that solution, as once the intermediate profile and its rules exist, adding another WLAN location takes exactly the effort as if the scheme was not used (even if my suggestion still seems to make at least some sense ;-))
 
Did you ever think about a section on your website explaining special setups (maybe as a Wiki or alike) ? It could use graphical explanations, just like the manual suggests to draw a picture before implementing profiles and rules. This Cell/WLAN setup possible would make an excellent candidate for such, don't you think?

[Christian Langanke]

Hi all,

the solution mentioned above works very well! Lots of thanks to kay-Ulrich taking the time to think a bout a solution,
and if there ever isa wiki or alike showing config examples I would be glad to contribute a description of it, if this is of interest.

bye Chris