Wifi Connected trigger bug?

[MURTUMA]

I have noticed that sometimes when I'm connected to a public hotspot (ie. in a train or a local bar), the Wifi connected trigger runs three to six times very quickly(less than a second). The wifi does NOT get disconnected in between, at least not so that Automagic could detect it.

Could it be a "feature" of the router or my device(SGS+, GB) or is it a bug in the trigger. I have never seen that in a protected wlan but only in free hotspots. I've been unable to record exact timing of the trigger firing but it seems to happen randomly between 15min and one hour.

[Martin]

Hi,

I have not observed this behavior on my devices yet. It would be interesting to see what's going on when this happens.
Could you please enable Debug log in the preferences of Automagic and send the log to me when this happens the next time (menu->Manage->Log, Menu->Send Log, send to info@automagic4android.com).

Depending on the flow you could build a workaround by adding an action Sleep: 5s to the flow and enable Skip execution when an instance is already executing in the options of the flow (menu->Options).

Regards,
Martin

[Wibbly]

I think I have seen this too, and have used a workaround like you suggest

[MURTUMA]

It might take some time, before I have a chance to test this again, but I'll try to remember to log it. Which begs me another question: can you make it possible to automate turning "log to SD" option? The "debug log" check box should be in the same action.

Currently I use defferent workaround. I have the Wifi connected and Wifi disconnected in the same flow but they follow different paths. I put boolean variables at the end of both paths to check which one has ran lastly. If the DISconnection path hasn't run, the Exeption condition stops the connection path short. That works too, flawlessly.

[Martin]

An action to toggle the Debug log and SD log settings should be easy to add. When would you like to use such actions in particular? I'm asking because it could be too late to turn on the debug log in a flow when you want to see the debug log lines pertaining to the trigger of the flow.

[MURTUMA]

In this case, the trigger Wifi connected would actually work as the bug happens only while being connected. Never at the start of connection.

I can get to use public hotspots so rarely that I doubt I remember to turn them on on my own. Or maybe I could just make a flow to remind me about this, as it is possible already.

[MURTUMA]

Sorry, I almost forgot this.

The only relevant log entry for this issue was this:
14.01.2015 15:05:03.512 Received intent Intent { act=android.net.wifi.STATE_CHANGE flg=0x30000000 (has extras) } extras: networkInfo=NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true, bssid=ec:43:f6:fd:3a:bb

The entries related to the trigger were as they should, but this was something I don't understand. However, it only appeared once before each time the trigger run in quick succession.

[evebrea]

I have this happen to me. My flow that sets off "speech : Welcome home sir". she says welcome home 5-6 times when i hit my home wifi. I used wifi because gps is unreliable and would say i was home when i was still 2 miles away.

it MIGHT be related to the delay in speech. Not sure, but once it goes off, it's like :
welcome home sir welcome home sir welcome home sir welcome home sir welcome home sir welcome home sir

[Wibbly]

welcome home sir welcome home sir welcome home sir welcome home sir welcome home sir welcome home sir

... when it should just say "VERY welcome home sir"?

[evebrea]

actually it's just supposed to say it once. i have my phone giving me a lot of voice notifications using the british female voice. like my own version of jarvis XP