These are chat archives for nightscout/intend-to-bolus
cat ~/myopenaps/monitor/glucose.jsonreturns nothing
nano pump.iniask Google also for hints on nano
*/5 * * * * (bash /root/http.sh) 2>&1 | tee -a /var/log/openaps/http.log
@jdhigh that's a lot more often than we get, yes that's an unusual amount of instances. However, if you have one instance that goes on for a long period of time, pushover will keep alerting until you both snooze NS alarm AND acknowledge the pushover alert. So one longer time of OpenAPS being offline could lead to a lot of notifications for the same instance if the alarm/alerts aren't acknowledged.
But generally speaking, we'd go days without any significant periods of OpenAPS not looping. Our alerts were set to 20min. So usually we don't notice until it gets longer than 20 min of OpenAPS being out.
Starting pump-loop at Fri Sep 1 15:33:04 EDT 2017: Sep 01 15:33:04 natopenaps pump-loop.log: Waiting up to 4 minutes for new BG: glucose.json newer than pump_loop_completed Sep 01 15:33:38 natopenaps pump-loop.log: Radio ok. Listening: .No pump comms detected from other rigs Sep 01 15:34:07 natopenaps pump-loop.log: Profile less than 60m old. glucose.json newer than temp_basal.json. Temp refreshmmeowlink.exceptions.CommsException: No acknowledgement from pump on wakeup. Is it out of range or is the battery too low?