OpenSeizureDetector V2.0.8 Released

A quick bug-fix beta release (Thank you Damian for reporting it!) – if you have an incompatible version of the watch app installed it will now pop up a friendly-ish message asking you to upgrade the watch app, rather than crashing with an obscure error.

Available on for beta testing here:

Sorry for the inconvenience again!

Detection of Short Seizures

I originally set up OpenSeizureDetector to detect long (>1 minute) seizures so it waits to see seizure-like shaking for several seconds before raising alarms.

A couple of users said they would like to detect short (few second) seizures, so I have created a new version of the app that allows the sample period to be set by the user, so you can tell it to analyse data say every second rather than the default 5 seconds.

New settings in v2.0.7 - sample period and sample frequency.
New settings in v2.0.7 – sample period and sample frequency.

I suspect that doing this will give a lot of false alarms, but I have provided this so the users can try it and see if it works for them.

This feature is available in version 2.0.7 of the OpenSeizureDetector Android app, and version 2.3 of the watch app.  The correct version of the watch app is included in the Android package so you can install it from the OpenSeizureDetector menu.

It is available on the Beta testing channel of Google Play Store – subscribe here to access it.

As usual, feedback would be appreciated – if you do not change the settings, it should behave the same as before – please let me know if this is not the case.


OpenSeizureDetector Reliability Issues?

We have been woken up during the last couple of nights with the annoying warning pip from OpenSeizureDetector.   I am not sure what the issue is because I don’t think any of the software has changed for a few weeks and it just started happening.

There have been two issues

  1. the ‘server’ phone disconnected from our home wifi for some reason and only re-connected when I turned its screen on (no idea why, but not too much of a worry – probably some sort of wifi interference from somewhere).
  2. the ‘server’ phone showed a ‘Fault’ warning with ‘Watch App Not Running’ – this means it has not received any data from the Pebble watch recently.   The watch appears to be working ok, so I don’t know if it is a problem with the watch not sending data, or the Android Pebble App on the phone not telling OpenSeizureDetector that it has received some data for it.

I have set up our spare watch and phone to see if they do the same – I might end up swapping over the watches – the spare is older though and its battery is not as good and its screen keeps corrupting, which might annoy Benjamin…..

Is anyone else seeing similar problems?  Please let me know ( or the OpenSeizureDetector Facebook page).