If the application happens to stall unexpectedly, you can perform some debugging on your end.
The first place to look at is the Status page in the application. Does it display any error or is it lagging data processing?
You can also view the Supervisor logfiles, depending on whether your datalogger, webinterface or the data processing is broken.
The logfiles are located by default in
You should find logs here regarding the
Another option is to tail the (recent) logs in Supervisor.
Enter the control panel with
sudo supervisorctl and type
tail -f PROCESSNAME to follow one.
The process names are the ones you see when you started the control panel, or you can just enter
status to see them.
You can also use
restart on the processes to give control them.
Appplication / Django¶
The application has it’s own logfiles as well.
You can find them in the
logs directory inside the project folder.
django.log will list any internal errors regarding the Django framework it’s using.
The other logfile
dsmrreader.log contains application logging, if enabled.
You can log all telegrams received, in base64 format, by adding
DSMRREADER_LOG_TELEGRAMS = True to your
Make sure that you execute
./reload.sh after changing the settings. It should now log the telegrams into