vl_wake: ' >13.00V FOR 2 s'
ext_wake: ' HIGH FOR 2000 ms'
uart_sleep: ' 900 s'
vl_sleep: ' <12.20V FOR 240 s'
vchg_wake: ' +0.40V IN 1000 ms'
uart_wake: ' 0-30000 us'
Run NoStateIDNameDurationStart TimeComment
49
raspi.installhaveged-installed haveged 40249.56803:23:01
An error was encountered while installing package(s): E: The repository ‘http://repo.saltstack.com/apt/debian/9/armhf/archive/2017.7.5 stretch Release’ does no longer have a Release file.
50
raspi.installhaveged-service-runninghaveged269.45903:23:41The named service haveged is not available
I had a similar problem with a release back in December. I ended up just re-flashing the latest software, it took about 20 minutes. Just be sure to backup your private keys. Your settings should re-sync from the cloud once it’s online.
I never really figured out what the problem was exactly, but I suspect it might have been a corrupt SD card or an SD card that’s reached it’s write cycle limit. There’s at least one thread on here about the AutoPi killing SD cards, and they’ve switched to using high endurance SD cards for new AutoPi’s sold. I replaced the SD card with Samsung Pro Endurance SD card at the same time and so far so good.