Action Time Limit

[redmed]

How do I set a 30 minute limit to action?
I currently use a "SSID in range" trigger to set "Silence-Vibrate Off (Enable)" and another macro uses a "SSID out of range" trigger to set "Silence-Vibrate Off (Disable)" this works as intended most of the time. Sometimes it misses the "SSID out of range" trigger and my phone is silent the rest of the day. I also see in the log that the two macros bounce on and off while in range of the SSID. I would like to change the "SSID in range" trigger to set "Silence-Vibrate Off (Enable)" to be valid for 30 minutes at a time. That way the most time the phone will be silent will be 30 minute after I leave the SSID area. Also the phone will not be switching between the On macro and OFF macro while in the SSID area.

 

[JA-Translator]

How about this?

You can set the constraint, which doesn't allow to trigger the macro.

Or you can set the time intetval for 30 minutes in the Option setting - Trigger option.

 

[redmed]

Thanks JA-Translater I never thought of changing the background scan rate. I can use this in some of my other macros.

This is what I'm going to try. Works to silence the phone in 30 minute chunks except seems to only trigger when entering the range of the SSID. I want it to identify that the SSID is in range and keep silencing in 30 minute chunks. So the whole time I'm within SSID range the phone is silent. When I leave the SSID the maximum time the phone is silent is 30 minutes.

 

[JA-Translator]

Thanks JA-Translater I never thought of changing the background scan rate.

Just for your information,
the "background scan rate" is not accurate.
So, the better way is to use the global constraint (30 mins restriction) as I mentioned above.

I am looking at your macro...
May I ask you?
Is your macro running as you expect?

I think, if the trigger quite often happens, the macro will never be able to complete the action "Vibrate Disabled"?
You need an Action to stop the trigger for 30 minutes.

 

[JA-Translator]

I think, if the trigger quite often happens, the macro will never be able to complete the action "Vibrate Disabled"?

I mean,
According to my experience "WiFi SSID Range Trigger" problem,

SSID Range trigger sometimes lost the detection for a moment and found it soon again, then the Trigger was repeated many times.

 

[redmed]

I tested it at home using my WiFi as the trigger with a 10 second wait. The log showed it triggered the silence then 10 seconds later disabled the silence. But after the initial trigger (walking into WiFi range) while staying within the WiFi range it did not trigger again. I want it to keep triggering while within the WiFi range so the phone is silent the whole time with a slight moment of unsilence every 30 minutes. Then when I leave the WiFi area the maximum time the phone stays silent is 30 minutes. I have been using two separate macros for years with my LG V20 & LG V60 phones and the two macros have worked great. One macro identifies that I'm entering the WiFi and silences the phone and the second macro identifies that I'm leaving the WiFi and unsilences the phone. Now that I'm using a Pixel 7 the first macro works 90% of the time and the second macro (the unsilence one) only works 40% of the time. So there are days my phone is silent the whole day and I'm not aware. I have missed many calls. So I'm trying to come up with a different macro for the Pixel. The entering the WiFi area seems to work so I'm trying to rely on that one macro. Hence the on for 30 and off, the on again for another 30 and off.

What I don't understand is looking at the log of the original two macro's I see the two macros going on and off while I'm within the WiFi range the entire time. It may silence the phone for 3 minutes or 20 minutes the the leaving macro unsilences the phone for a minute or 4 minutes. Later the silence macro triggers again. In the past I did get a call within the the unsilence gap but over the years that only happened twice so I have lived with it. Now with the Pixel seems to act differently.

 

[redmed]

I mean,
According to my experience "WiFi SSID Range Trigger" problem,

SSID Range trigger sometimes lost the detection for a moment and found it soon again, then the Trigger was repeated many times.

Yes that's I encountered with the r WiFi SSID trigge also. I'm trying to develop a more stable strategy of using the trigger. I have in the past set the silence with the WiFi trigger then unsilenced using the "In Vehicle" trigger with poor results. I don't remember the details but I think the WiFi did trigger the silence well but the "In Vehicle" trigger was untrustworthy.