One of my Iotawatt units suddenly stopped responding. Took a look to find solid dull red. Pulled the power, waited 10 seconds, and then plugged it back in. After a very brief green, I get red-red-red repeatedly. Since the docs say this situation is beyond the scope of the documentation and I can’t access the browser interface to inspect the logs, I’m not sure what to do next.
I’ve been reading other threads on this forum about red-red-red, but the only thing I can glean is that perhaps I should swap the SD card?
Virtually all problems for the past couple of years are WiFi or SDcard. There is a high likelihood this is SDcard. Simple enough to replace it. Follow these directions and note that you will get one chance to recover your old config after powering the new card up. Once you edit the default config, it replaces the last saved config.
Thanks for the pointer. Such a quick and easy solve, maybe you want to include it in the documentation?
For those who follow, replacing the SDcard is a 2 minute process and, provided your root issue isn’t wifi, it’s an effective solution.
BTW, @overeasy, removing the cover and seeing the board firsthand, I realized there’s a battery in there. Is this something we should expect to replace every few years? How would the device behave in the event of a low battery?
The battery powers the Real-Time-Clock when USB power is unavailable. That way the IoTaWatt knows what time it is and can start monitoring immediately. Most of the units will post a low battery message in the message log at startup when the voltage gets low. When it gets too low, it will no longer be adequate to run the RTC and the IoTaWatt will not know what the time is after a power failure so will not log data until it can connect to the internet and get the time from an NTP server.