Handling errors a little bit better
Added 2019-01-22 15:00:03 +0000 UTCUp until now the way I've handled errors was to simply let the application break, log the error, and do nothing. This wasn't really ideal, but errors have been pretty uncommon (according to my logs anyways) so it worked for now.
Given the ecobee server issues yesterday, I thought it was probably time to fix that. The first problem is that beestat completely dies when ecobee goes down. This is because the API call to my server that fetches your graph data is tightly coupled to the API call to ecobee that syncs your data. It'll take a few hours of effort but I'll break those apart so you can still use beestat even if ecobee goes down.
The second problem is that I simply have no presentation to the user when there's an error. I was able to correct that by throwing up a simple modal window with some information about the error when it happens. I get all kinds of email notifications and summaries for these errors already, but it sucks for the user to not be alerted. Some people just let beestat "load" for extended amounts of time when it's really just sitting there broken with a loading animation.
This update and a few other minor bug fixes coming later this week. Outside of this maintenance, the 1.3 home efficiency algorithm is looking promising; seeing some very good results!
