Month: July 2023

At least three users have confirmed the issue with Garmin VenuSQ devices returning incorrect heart rate readings (after several hours it stops updating heart rate, and returns the same value all the time, even though the accelerometer data is updating correctly and Garmin Connect reports correctly varying heart rate). More details here: https://github.com/OpenSeizureDetector/Garmin_SD/issues/22.

V4.1.10 of the OpenSeizureDetector Android App is now available on play store. This version will enter a fault condition if this heart rate issue occurs while you have heart rate alarms active – so please run this version and let me know if you experience the issue, and which watch you are using.

V3.1.3 of the Garmin Watch app (Available from here: https://github.com/OpenSeizureDetector/Garmin_SD/blob/master/WatchApp/build/GarminSD_v1.3.3.prg) uses a different way of updating the heart rate data, and I am hoping that will address the issue – please will you try this version if you are affected by the issue and let me know if it fixes it or not?
Thanks,

Graham (graham@openseizuredetector.org.uk)

V4.1.10 of the OpenSeizureDetector Android App should be available on Google Play Store shortly.

The only change introduced is to add a fault warning ‘pip’ if the heart rate measurement freezes and does not change value for more than 1 minute. This is to help users to identify problems with their data source, in particular the issue that has been identified with the Garmin VenuSQ device.

If you experience this fault, the heart rate section of the main app screen will be highlighted in magenta, and you will hear a fault ‘pip’ every 5 seconds. On my Garmin VenuSQ I have found that this can be re-set by either removing the watch from my wrist for about 1 minute, until the heart rate indicates ‘null’, then replacing the watch, or stopping and starting the watch app.

I will work on a fix for the issue, but thought I should get a version of the phone app working to warn users if it occurs so they can re-set it. If this turns out to be too annoying, it can be switched off in the seizure detector settings of the phone app.

Please let me know if you find any issues by raising an issue in the bug tracker here, or emailing graham@openseizuredetector.org.uk.

Thanks!

Graham.

Over the past week, two users have reported that they have seen the heart rate reading stops updating and freezes on an old value after several hours. All the reports have been on Garmin VenuSQ watches. See the discussion here: https://github.com/OpenSeizureDetector/Garmin_SD/issues/22. After wearing the watch for three nights, I have managed to reproduce the issue on my VenuSQ watch too.

I do not know why this is happening so do not have an immediate solution. I found that shutting down the watch app and re-starting it solved the problem.

The main concern is that the user will not know that the issue has occurred unless they observe the heart rate value themselves, as no fault alarm will be generated. I propose to make an update to the Android app to generate fault pip sounds if the heart rate does not change for more than a specified time to provide us with a work around for now.

If you see this issue on your device, please report any information on which device you are using, and how you re-set it to get it working again – either by commenting on the issue here: https://github.com/OpenSeizureDetector/Garmin_SD/issues/22, or emailing graham@openseizuredetector.org.uk and I will update the issue in the bug tracker.

Thanks, Graham.

Version 4.1.9 of the OpenSeizureDetector Android App is now live on Google Play Store. This release fixes a number of user-reported issues and crashes, incuding:

• Continuous alarm generation if you enable heart rate or O2Sat alarms when using the Phone Data Source.
• Crashes if you try to scan for BLE devices when not using BLE data source (no-one should be using the BLE data source!).
• An issue with the average heart rate alarm not working correctly.
• Logging data associated with the adaptive heart rate alarm settings to the Data Sharing Database.

Please let me know if you find any issues with this release (either email graham@openseizuredetector.org.uk or [preferably] raise an issue on our github source code repository.

Thanks, Graham.

I have failed to make the data sharing system user proof!

The disk on the data sharing system has filled up suddenly, so I need to free up some space on it – I have shut it down for now to avoid losing any data.

I should be able to get it back tonight, but will have to come up with a solution to prevent the app uploading loads of data if it is configured incorrectly….

Update 20:15, 05/07/2023: Server back up now after backing up the data and deleting it from the on-line database.

Graham.