- Frequently Asked Questions (FAQ)
- I need help!
- How can I update my application?
- How can I downgrade my application?
- How can I move the database location?
- Recalculate prices retroactively
- I’m not seeing any gas readings
- How do I restore a database backup?
- How do I enable timezone support for MySQL?
- How do I retain MQTT support when upgrading to v1.23.0 or higher?
- How do I uninstall DSMR-reader?
- How can I use the datalogger only and forward the telegrams?
- How can I check the logfiles?
- How can I restart the application or processes?
- How do I fix errors such as
DETAIL: Key (id)=(123) already exists?
- I’ve changed to a different smart meter
- How can I create the (super)user or update its password?
- How do I fix:
Error: Already running on PID 1234 (or pid file '/var/tmp/gunicorn--dsmr_webinterface.pid' is stale)?
If you can’t find the answer in the documentation, do not hesitate in looking for help.
I’ve adjusted my energy prices but there are no changes! How can I regenerate them with my new prices?
sudo su - dsmr ./manage.py dsmr_stats_recalculate_prices
Please make sure that your meter supports reading gas consumption and that you’ve waited for a few hours for any graphs to render. The gas meter positions are only be updated once per hour (for DSMR v4). The Status page will give you insight in this as well.
Check these docs for more information about how to enable timezone support on MySQL.
On recent versions it should be as simple as executing the following command as root/sudo user:
mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root mysql
This depends on the situation, but you can always try this yourself first:
# Note: dsmr_sqlsequencereset is only available in DSMR-reader v3.3.0 and higher sudo su - dsmr ./manage.py dsmr_sqlsequencereset
If it does not resolve your issue, ask for support.
Sometimes, when relocating or due to replacement of your meter, the meter positions read by DSMR-reader will cause invalid data (e.g.: big gaps or inverted consumption). Any consecutive days should not be affected by this issue, so you will only have to adjust the data for one day.
The day after, you should be able to manually adjust any invalid Day or Hour Statistics in the admin interface for the invalid day.
DSMR_PASSWORD of the Env Settings.
sudo su - dsmr ./manage.py dsmr_superuser
The user should either be created or the existing user should have its password updated.
How do I fix:
Error: Already running on PID 1234 (or pid file '/var/tmp/gunicorn--dsmr_webinterface.pid' is stale)?¶
Just delete the PID file and restart the webinterface:
sudo supervisorctl restart dsmr_webinterface