Send Pushover on pump error

[jmcrawford]

Had a delivery failure tonight, which caused pump to be suspended. It was noted in NS, but what about triggering a Pushover on pump alarm conditions?

Pumphistory records: { "_type": "AlarmPump", "_description": "AlarmPump 2017-11-09T23:18:18 head[4], body[0] op[0x06]", "timestamp": "2017-11-09T23:18:18", "_body": "", "_head": "06040bfc", "_date": "92d2574911" }, { "programmed": 0.4, "_type": "Bolus", "_description": "Bolus 2017-11-09T23:18:00 head[8], body[0] op[0x01]", "timestamp": "2017-11-09T23:18:00", "_body": "", "_head": "0100100009009600", "amount": 0.225, "unabsorbed": 3.75, "duration": 0, "type": "normal", "_date": "80d2574911" },

Looks like in this case, a condition where Programmed != Amount would indicate a delivery failure. This might be a useful check to implement, in addition to the AlarmPump record.

[JELCRAWFORD]

Additional info to the above, the delivery error happened on an SMB that was partially delivered as we were going to bed. We noticed the suspended status in the openaps pump status line and investigated to discover the partially delivered SMB, and the pump in suspend due to that error. Had we not noticed that (or had we gone to bed at a reasonable hour) we may not have realized there was trouble until BG was quite high. Would be good to have some other alerting for this.

[scottleibrand]

This probably depends on #789.