Just a few comments on the update process.
The process has moved on leaps and bounds in recent years, the components page in particular is excellent, but there are still a couple of sticky issues;
- Log The log vanishes once complete. The only way to get it is to click on a different page and click back then quickly click on ‘Download Log’ before it vanishes again.
- Full update - it isn’t clear what happens to firmware updates if you happen to not be running an standard EmonPi. I’d rather that firmware update was kept separate or a choice on the type of system in use (EmonBase, EmonPi, Serially connected), equally I’m not sure some of these would update the firmware anyway. The Full Update is the only way from the UI to update the OS.
- Errors Difficult to identify if something has failed - providing more feedback is difficult to do, but a useful feature. Directing users to the components page to check the versions might help.
- Services I noticed that a service I’d disabled got re-enabled - this shouldn’t happen.
On EmonSD image update,
- It needs to move to the latest piOS base, but there have been reports of the SWAP filling up on systems using the latest Kernel.
- Can we move past the use of
sudo pip- there are lots of errors regarding this and eventually it just will not work
Happy to help with testing!
