by Scott » Mon Jul 10, 2017 3:17 pm
Most likely not directly with the webapp. It's likely possible with a little Python code, though. Did you happen to capture what it looked like from the AlarmDecoder's perspective when it happened?
If you're just seeing the error message in the message's text portion, the only way you'd be able to get a notification from the webapp is if it's generating an alarm. Otherwise you're going to have to roll your own.
If you don't mind getting your hands dirty with Python you could combine the email & socket examples in the Python library to look for the 6F error in the message text, or numeric code, or wherever it's showing up and build yourself a little emergency email notification script. This is probably the simplest method of getting it done.
If you want to take it a step further, we recently redid the LRR (Long-Range Radio) format in the latest firmware release so that it reports the specific ContactID codes that would be sent to the monitoring station. There's a fairly good chance that an LRR message will be produced when it loses connection to the tower. I'm still working on adding official support for all of this in the library, but you should still be able to roll your own LRR handler using the library with a little bit of effort by combining the LRR, email, and socket examples from the Python library. Eventually I'd like to allow you to pick & choose LRR events to subscribe to for notifications in the webapp, but that's a little down the road, I think. Let me know if you do manage to get an LRR message out of it and I can help you decipher what it means.
Hopefully that helps!
