I have created a Tasker Project ( called BillFolder) with a :

Profile – ( called Start )-Boot Device which links to my tasks called wifion.

( to start the project/app when the device is booted)

And a simple task sequence called Wifion.

1-Wait 7 minutes

2-Wifi – Set on

3-Wait 5 seconds

4-Wifi Net – Action Reconnect

5-Wait 7 minutes

6-Goto type Action Number 1

Under preferences – Monitor – Run In Foreground is not selected.

                               UI – Beginner Mode is not selected.

The project has no user interface , and should auto start at power up and

Very detailed background: Calendar entries can have different availability options to mark a calendar entry as "free" or "busy". A normal calendar entry for a meeting would be marked as "busy" and is the default. You can also have an entry marked as "free" when you want more of a reminder of a meeting that you might not attend. This concept exists in both Google Calendar and Microsoft Exchange/Outlook. Google Calendar shows this setting as "Show me as" with options Available and Busy and Exchange shows this setting as "Status" with options Busy, Free, Tentative, or Out of Office.

In

When programmatically updating two scene elements, one element will get the value of the other, at least for Number Pickers. `new_val` acts like a Singleton having just one state.

I've been seeing this behavior for the Expiry Hours element. Logging shows one value of `%new_val` before the assignment and a different value after the assignment.

Logging shows `eh` eventually getting the value meant for `em`.

Calendar insert: All day: true Title: SomeEvent

Test app: Type: Calendar Title Data: %TIMES

expected: returns event "SomeEvent"

got: returns events created manually via google calendar app.