In 3.0 we are shipping a `reef-pi db` command, which you can use to investigate & change the databased directly, bypassing the controller. Its meant to be used for troubleshooting. With this commmand you can selectively clear/reset those values. Here is an example partinent to your use case. I remembered this as I just did it recently :)
Stop reef-pi
Code:
sudo systemctl stop reef-pi.service
Get the current list of ato, you need the id of the ato that you want to change
Get the usage data of that ato (assuming id is 1) , and save it in a file
Code:
sudo reef-pi db show ato_usage 1 > usage.json
Edit the file, you'll notice the abnormal usage values by searching for those values (for me ato usage 3000), edit them whatever value you prefer, or delete. the update it,
Code:
sudo reef-pi db update -input usage.json ato_usage 1
restart reef-pi
Code:
sudo systemctl stop reef-pi.service
The `reef-pi db` command works across all the things including setting, and has the following pattern:
Code:
reef-pi db list <module>
reef-pi db show <module> <id>
reef-pi db create <module> -input foo.json
reef-pi db update -input foo.json <module> <id>
reef-pi db delete <module> <id>
Example of modules: ato, temperature .. etc . All the bucket names specified here:
https://github.com/reef-pi/reef-pi/blob/master/controller/storage/store.go#L4.
I hope this will help us diagnose & fix issues where reef-pi is not able to start due to inconsistent configuration or the controller is working but UI is broken due to front end code or API related issues.