Add ability to prevent SMS being sent using watch buttons.

[jones139]

It would be helpful to be able to prevent false alarm SMS messages being sent by using the watch buttons as well as the phone app interface.

[jones139]

A new user is interested in implementing this, so I think we'll have a go at it. I think what is required is:

• When the phone sends the response back to the watch, it currently sends 'Alarm' if it is in an alarm state
• When the watch app receives that we pop up a dialog with a Confirm or Cancel option
• If the user selects Cancel we post a http request back to the phone telling it to cancel the alarm.
• We will need an update to the phone app to respond to the cancel command.
• We will also want to implement this in the BLE data source for PineTime, but that will be a bit trickier....

[pmithrandir]

HiSeems quite complex for a limited usage.From my pov, if you are able to use watch button, you should be able to access the phone and do the same action on it. Introducing a delay to send alert on the phone (30 sec for exemple for the SMS.) to give time to cancel.We saw that each addition to the watch code imply losing battery autonomy. Doesn't seem worth the cost.Sent from Android deviceLe 5 nov. 2024 12:38, Graham Jones ***@***.***> a écrit : A new user is interested in implementing this, so I think we'll have a go at it. I think what is required is: When the phone sends the response back to the watch, it currently sends 'Alarm' if it is in an alarm stateWhen the watch app receives that we pop up a dialog with a Confirm or Cancel optionIf the user selects Cancel we post a http request back to the phone telling it to cancel the alarm.We will need an update to the phone app to respond to the cancel command.We will also want to implement this in the BLE data source for PineTime, but that will be a bit trickier.... —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[jones139]

I know what you mean, but if you have the phone in a pocket or bag then getting it out, unlocking it, opening the OSD application and then cancelling the alarm is not that easy. (the way we use it at home the OSD app is always in the foreground so it is nice and easy, but other users will not have their phone open all the time). But it will need to be another selectable feature because not everyone will want the user to be able to do things on the watch...

…

On Tue, 5 Nov 2024 at 12:34, Pierre Bonneau ***@***.***> wrote: HiSeems quite complex for a limited usage.From my pov, if you are able to use watch button, you should be able to access the phone and do the same action on it. Introducing a delay to send alert on the phone (30 sec for exemple for the SMS.) to give time to cancel.We saw that each addition to the watch code imply losing battery autonomy. Doesn&#39;t seem worth the cost.Sent from Android deviceLe 5 nov. 2024 12:38, Graham Jones ***@***.***&gt; a écrit : <br> A new user is interested in implementing this, so I think we&#39;ll have a go at it. I think what is required is: <br> When the phone sends the response back to the watch, it currently sends &#39;Alarm&#39; if it is in an alarm stateWhen the watch app receives that we pop up a dialog with a Confirm or Cancel optionIf the user selects Cancel we post a http request back to the phone telling it to cancel the alarm.We will need an update to the phone app to respond to the cancel command.We will also want to implement this in the BLE data source for PineTime, but that will be a bit trickier.... <br> <br> —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***&gt; — Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACLSY7VZRULWNXYJ45YUYDZ7C3NXAVCNFSM6AAAAABRGK22JSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJXGA2TGNBTG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Graham Jones <http://google.com/+GrahamJones> Hartlepool, UK.