Latch Alarm not working properly with Garmin

[seaside1]

Hi!

I'm starting to move over from Pebble to Garmin vivoactive 3. As far as I can tell the Latch Alarm is not working with Garmin (at least not working as it does with Pebble).

Using the same phone (Nexus 6P and also tested with Samsung S23 Ultra) For Pebble Alarm will sound throughout the entire period set in the latch alarm duration For Garmin Alarm will only sound periodically at start and then nothing.

Two recording of the problem one with a Garmin and one with a Pebble https://drive.google.com/file/d/1roXqGK2-mj0Zx3cSe7CazFF9POQZQAiB/view?usp=sharing https://drive.google.com/file/d/1rntG3Q1ySptkh_kfdx8lUF_EM6dmoMze/view?usp=sharing

[jones139]

Thank you for the feedback - you have answered one of the things I have been wondering about, which is whether anyone was still using Pebble watches or not! (I was thinking of removing support for them in a future version of the Android App).

Latch Alarms is not a feature I ever use, so it is possible that I may have broken it and not noticed (this is another example of why I would like some automated tests for this app when I get the chance!).

I have just tested it using the PineTime watch (which is what I have set up for development at the moment), and Version 4.2.2 of the Android App, and it latches ok, but does not seem to un-latch after the specified time like it should, and pressing the Accept Alarm does not re-set it. I had to go into the phone Apps settings and force stop openseizuredetector to re-set it....so we have an issue there.

I'll test Garmin next, but I think this is an issue with the Android App rather than the watch app, so don't be alarmed if I close this issue and open another one in the Android App repository.

[jones139]

With the Garmin version the latch again worked but did not timeout after the 30 seconds that I have set in the settings, but pressing Accept Alarm did re-set it correctly. So this is an issue with the Android App.

[jones139]

I saw two issues in your videos though that might be relevant too:

1. In one video OpenSeizureDetector is in a bit of a funny state - you are getting pop-up messages saying that OSD did not shutdown correctly - please do a 'Force Stop' of OpenSeizureDetector form the phone Settings->Apps->OpenSeizureDetector menu and test again - especially the Garmin test.
2. It took a long time for you to persuade the Garmin test to go into alarm - that did not look correct, and on the Garmin watch display I can see an ERR:Retry message - this is the watch saying that it failed to send data to the phone for some reason and it is re-trying it - so I think there is a problem with the bluetooth communications between the phone and the watch - please re-start both the phone and the watch and see if you still get these errors - it might be a sign that there is a problem with the bluetooth radio in the watch.

[jones139]

Closing this issue as we will track it under the Android App repository: https://github.com/OpenSeizureDetector/Android_Pebble_SD/issues/146

[seaside1]

Thanks for the quick feedback! 1) Yes it was in some sort of funny state (after switching back and forth with a pebble). After a reboot it seems to be ok. The issue is still the same with the latching. 2) Yes seems to take longer time when comparing to the pebble

I will test on the S23 Ultra to confirm if it is the same.

Another thing I noticed is that the Alarm is working if you enable sms location alarm, until it sends the sms, after that it starts failing.

I also see some other message but unsure what is its (See screenshot)

[jones139]

I don't recognise that 'Certificate Authority' warning, so I don't think it is anything to do with OpenSeizureDetector - we do not do anything fancy with security certificates.

I'll raise another issue about a possible interaction with SMS alerts - thanks for reporting this - it is another feature I do not use so could have missed a problem.

[seaside1]

Yes was not the certificate warning, that one is done by me, by using my own Root CA.