The following instructions should make more sense if you think in terms of the following schematic for how everything is connected together.
In our home set-up, the Server device is a cheap Android telephone. This runs the OpenSeizureDetector server application. The main client device is Sandie’s Hudl tablet computer, which runs the Alarm Client app. Both devices are connected to our home wifi network.
Server – shuts down when screen off
On Android 5 (at least on my Huawei P8 Lite test device) apps are shutdown when the screen is off to save power, unless you go to the settings menu and select it in ‘Protected Apps’ – it seems that only ‘Protected Apps’ will carry on running when the screen is off to save power. This will make OpenSeizureDetector Fail without any error beeps – Always function test OpenSeizureDetector by shaking the watch before use to make sure it works.
Server – Pebble Connection
If the server app displays ** Pebble Watch NOT Connected ** in red highlight, and the server device makes regular ‘chirp’ warning sounds, this means either:
- The pebble watch is out of range of the Bluetooth connection (~5m) – move the server phone closer to the watch and see if this fixes it.
- The pebble watch battery may be dead – check the pebble appears to be working ok.
- The connection between the pebble and the sever phone has been lost and needs to be re-set using the “Connect to Pebble” instructions below.
If the server says “Pebble Watch Connected OK” but shows “** Pebble App NOT Running **” in red highlight, there is a problem with the Pebble App not running correctly on the watch.
- The Server App will try to re-start the Pebble Watch App, so leave it 30 seconds to see if it fixes it itself.
- If it does not, there must be a problem with the pebble watch app – try re-starting it as described in “Re-Start Pebble App” below.
Connect to Pebble
To re-connect a pebble watch to the server phone, do the following – click on the small images for more detail of the screen layouts:
- Check the bluetooth radio is switched on on the server phone (bluetooth logo in status bar at top of the screen).
- Start the Pebble Android App, either directly or by using the “Launch Pebble App” menu item on the OpenSeizureDetector Server App.
- Select the ‘Manage Connection’ memu item – if it shows the pebble as ‘DISCONNECTED’ or ‘CONNECTING’, there is a problem with the connection, so try the following.
- Click on the pebble icon to try to connect, or cancel the connection and re-try connection. This should change the pebble status to ‘CONNECTED’.
- If that does not work, re-boot the server phone and try again.
- If that does not work, re-set the Pebble bluetooth as described below and re-try.
Pebble Bluetooth Re-Set
If the pebble is not detected by the server phone, or the phone will not connect to the pebble, switch the bluetooth radio off and on again on the pebble watch. Do this using the following procedure (refer to diagram for button locations)
- Go back to the pebble main screen by pressing the BACK button several times.
- Press the SELECT button to bring up the pebble main menu.
- Press the DOWN button until the Settings option is highlighted (about 4 presses).
- Press SELECT to enter the settings menu.
- The Bluetooth option should be highlighted (if not, use UP/DOWN to highlight it). Press SELECT to enter the Bluetooth menu.
- The Bluetooth ON option should be highlighted (if not, use UP/DOWN to highlight it).
- Press SELECT to switch off Bluetooth.
- Press SELECT to switch on Bluetooth again.
This will have re-set the bluetooth radio, and will make the pebble visible to the android server device so it can connect to it – try Connect to Pebble again.
Re-Start pebble App
If the “Pebble App NOT Running” appears when the pebble watch is connected to the server phone ok, there must be a problem with the Pebble App. Try the following:
- Launch the Pebble Android App from the OpenSeizureDetector server app menu.
- Select the ‘My Pebble’ Option and check that the OpenSeizureDetector app is loaded onto the pebble as shown in the image on right.
- If not, select the ‘Get Apps’ menu option and search for “OpenSeizureDetector” and re-install the OpenSeizureDetector watch app.
- If it looks ok, re-boot the pebble watch
- Press the – BACK button until the main screen appears.
- Press SELECT to show the menu and select ‘Settings’
- Select ‘Shut Down’ – the pebble will switch off.
- Press and Hold any pebble key for a few seconds until the pebble re-starts.
- Repeat the ‘Connect to Pebble‘ instructions.
- If this still does not work, the app must be crashing for some reason – I have not seen this happen on the published version of the app, so please email me (email@example.com) and let me know what is happening.
If the OpenSeizureDetector Client App shows “Warning – No Connectino to Server” in red highlighter, there is a problem with either the Server App, or the wifi connection between the client and the server. Try the following:
- Check that the OpenSeizureDetector server app is running on the server device.
- Check the server device is connected to the wifi network.
- Check teh client device is connected to the same wifi network as the server.
- Check that the client is trying to connect to the same IP address as shown on the server screen – if not change it in the client settings menu.
- If the above does not work, there is an issue with the wifi network. Note the following:
- If the client and server are connected to different wifi networks, the networks need to be configured to forward requests to port 8080 to the server device. Doing this is dependent on your router, so it is difficult to write instructions for doing this!
- Similarly, if you are trying to connect to the server when the client is connected to a mobile network rather than the local wifi, the router on the server’s network needs to be configured to forward port 8080.
Blank screen when trying to view a log file
Err, yes, this is a ‘Feature’ – press the browser refresh button and the log file should appear….I’ll fix it eventually.
See the Log Files page for more details.
If you have trouble with false alarms, you probably need to tune the AlarmFreqMin, AlarmFreqMax and the AlarmRatioThresh settings. First review the log files to see if you can tell what is happening. See the Log Files page for more details. Maybe best to ask on our Facebook page or email firstname.lastname@example.org for help.