Hello @cwajciec! We became aware of this issue on 1/3/20. It is an issue with the firmware writing an incorrect cumulative value, which causes the generation spike. We’ve identified the cause of the glitch and hopefully we’ll have it fixed today – January 6th, with an over-the-air firmware push. Once the cause is fixed, we’ll look into options for addressing the historical data. Our sincere apologies for any inconvenience this has caused.