2
Solved

Profile with on Variable Set gets falsely triggered

Here are the relevant profiles:

:    Profile: Ort: Hotel (da Wlan) (53)
        Restore: no
        State: Wifi Near [ SSID:WLAN-412345/SeteColinas MAC:* Capabilities:* Min. Activate Signal Level:0 Channel:0 Toggle Wifi:Off ]
    Enter: Anon (56)
        A1: Variable Set [ Name:%OrtWlan To:Hotel Recurse Variables:Off Do Maths:Off Append:Off ] 
        A2: Variable Set [ Name:%Ort To:Hotel Recurse Variables:Off Do Maths:Off Append:Off ] 
    
    Exit: Ort: Wlan verlassen (22)
        A1: Variable Clear [ Name:%OrtWlan Pattern Matching:Off Local Variables Only:Off ] 
        A2: Variable Clear [ Name:%Ort Pattern Matching:Off Local Variables Only:Off ] If [ %OrtFunk !Set ]
    
    Profile: Hotel Erinnerung (158)
        Event: Variable Set [ Variable:%Ort Value:Hotel User Variables Only:Off ]
    Enter: Erinnerung Hotel zeigen (183)
        A1: Variable Set [ Name:%Erinnerung To:Feuerlöscher entsorgen Lindberghstraße Schwabing Recurse Variables:Off Do Maths:Off Append:Off ] 
        A2: Notify [ Title:%Erinnerung Text: Icon:cust_flag Number:0 Permanent:Off Priority:3 Repeat Alert:Off LED Colour:Unset LED Rate:0 Sound File: Vibration Pattern: Category: ] If [ %Erinnerung neq nix ]

The first profile detects via WIFI near if you are at a hotel and if so sets the variable Ort to 'Hotel'.

The second profile should trigger only when the variable Ort is set to 'Hotel'. However it seems to trigger without a reason (Hotel WiFi is not close because being at home or at work). This happens only a few times a day. I've attaced a filtered run log and the relevant part of the run log unfiltered as well.

Follow

3 replies

Votes Newest Oldest
S

I've not been able to catch a debug log in time for this. Anyway the issue did not occur since a few weeks now so it just might have been fixed by a recent change to the Tasker betas.

Glad to hear that :)

S

HI, I'm sure the variable called 'Ort' (German for location) is not set to 'Hotel' in another place than the given first profile.

If I understand 'Variable Set' correctly my profile should trigger only when the variable is set to 'Hotel'?

I'll search the next time this happens the run log not only for 'Hotel' but also for 'Ort'.

Thank you!

S

I've experienced this again now - well, for a different 'Ort' but the according profiles are built in the same way. Now I've filtered the Run log again and the last change to Ort was at 23:16 to 'Zuhause' (Home). But at 23:37 there occured an Instant Variable Set for Ort that should only trigger when Ort is set to 'Eltern' (Parents). So the profile definitely triggered without even a change to the variable called 'Ort'.

Anything else I should check?

Are you able to please enable logging to external storage and then export the log when this error happens?

Also, can you please let me know which Tasker version you're using?

S

I've enabled the logging to sd but until now it did not occur again.

Regarding the version, I'm using a few weeks old beta posted linked by you in Google drive. Can I find out the exact version like the build number?

S

This is happening for several similar profiles that should be triggered only when the variable is set to a specified value. Last time it happened directly after leaving an unrelated profile and tapping the check mark on top of the main window.

What happens exactly when tapping on that check mark? Is it a stop/start of the TaskService surrounding the instant like on the 2nd screenshot given above?

Hi there. Thanks for the report. What you're saying shouldn't happen... Are you sure that the variable is not set to a different value for a brief period and then brought back to its value?

Topic is closed for comments