After update the trigger "Wifi scan results available" is firing over and over again. This leads to deactivation of flow.
The list of access_points in the log file contains the same wifis.
Bug? WLAN scan result trigger fires too often
Moderator: Martin
-
alexk195@gmx.de
- Posts: 1
- Joined: 15 Jun 2014 10:19
Re: Bug? WLAN scan result trigger fires too often
Hi,
The flow is executed whenever the system provides a scan result. It does not necessarily mean that the scan results contains any changes as far as I remember.
You could reduce the number of flow executions by changing the execution policy to Skip... or Stop... and by adding an action Sleep: 5s to the flow. To change the execution policy, open the flow, select Menu->Options and select Skip... or Stop.... The former is useful when you want to reduce the number of flow executions and prefer to process the earlier scan result, the latter is useful when you want to ensure that the newest scan result is processed (in this case, add the sleep action as a first action to the flow).
Regards,
Martin
The flow is executed whenever the system provides a scan result. It does not necessarily mean that the scan results contains any changes as far as I remember.
You could reduce the number of flow executions by changing the execution policy to Skip... or Stop... and by adding an action Sleep: 5s to the flow. To change the execution policy, open the flow, select Menu->Options and select Skip... or Stop.... The former is useful when you want to reduce the number of flow executions and prefer to process the earlier scan result, the latter is useful when you want to ensure that the newest scan result is processed (in this case, add the sleep action as a first action to the flow).
Regards,
Martin