Because a need i moved .db file to non default path, i changed the recorder component, URL setting. It worked for HA, but looks like addon look for it on the default path only isnt it?
Is there any way to tell addon where to look for it?
Your best bet is to suggest such feature to the original sqlite-web project. Or, better yet, if you have coding experience you can try implementing it yourself.
(The HA add-on just encapsulates that project into a docker image and pre-configures it to run inside HAOS.)
I would welcome this as well. This add-on famously has no configuration options, but maybe a “path to Db” would be a good addition. My db also is not in the standard path (mainly to keep backups small).
Hey, quick question into the round before I break something: after looking into hardening my backup process a bit recently, I still stumble upon threads where people experience a corrupted sqlite file/db when trying to recover from a backup. As a minimal solution I’d like to manually export longterm stats via the sqlite web addon from time to time (query to csv/sql file), to at least have my energy data put aside somewhere.
What I’m a bit worried about: my HA instance is running on a Pi3, and I’ve had experiences before where the whole system crashed because e.g. compiling esphome stuff brought it to its knees.
Can I break something by executing a potentially long-running “select * …” query against the stats tables? Anyone good or bad experiences with this? Any feedback welcome and appreciated
I’m not sure what is happening, but SQLite Web will not start. I get the following log when starting SQLite Web:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-sqlite-web: starting
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-sqlite-web successfully started
s6-rc: info: service sqlite-web: starting
s6-rc: info: service sqlite-web successfully started
s6-rc: info: service init-nginx successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[10:21:34] INFO: Starting SQLite Web...
* Serving Flask app 'sqlite_web.sqlite_web'
* Debug mode: off
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
* Running on http://127.0.0.1:8080
Press CTRL+C to quit
[10:21:35] INFO: Starting NGINX...
But SQLIte Web has not started. This screenshot after I’ve clicked the Start button.