Great add-on @sanderdw!
Unfortunately, I’m having an issue with it, hopefully someone can point me in the right direction.
After setting everything up according to instructions, I’m getting readable telegrams only ~3 times per hour.
According to the rejected telegrams sensor from the
DSMR reader integration, about 15000 telegrams are being rejected per day.
The DSMR add-on logs also show that the datalogger and backend services restart quite often, even though I’m not touching anything.
2021-07-20 03:19:37,137 INFO exited: dsmr_datalogger (exit status 0; expected)
2021-07-20 03:19:38,154 INFO spawned: 'dsmr_datalogger' with pid 2231
2021-07-20 03:19:39,160 INFO success: dsmr_datalogger entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-07-20 05:15:54,042 INFO exited: dsmr_datalogger (exit status 0; expected)
2021-07-20 05:15:55,058 INFO spawned: 'dsmr_datalogger' with pid 2233
2021-07-20 05:15:56,066 INFO success: dsmr_datalogger entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-07-20 07:35:52,530 INFO exited: dsmr_backend (exit status 0; expected)
2021-07-20 07:35:53,545 INFO spawned: 'dsmr_backend' with pid 2234
2021-07-20 07:35:54,551 INFO success: dsmr_backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-07-20 07:57:21,916 INFO exited: dsmr_backend (exit status 0; expected)
2021-07-20 07:57:22,930 INFO spawned: 'dsmr_backend' with pid 2235
2021-07-20 07:57:23,935 INFO success: dsmr_backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-07-20 08:12:13,779 INFO exited: dsmr_datalogger (exit status 0; expected)
2021-07-20 08:12:14,792 INFO spawned: 'dsmr_datalogger' with pid 2236
2021-07-20 08:12:15,796 INFO success: dsmr_datalogger entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-07-20 08:17:11,268 INFO exited: dsmr_datalogger (exit status 0; expected)
2021-07-20 08:17:12,282 INFO spawned: 'dsmr_datalogger' with pid 2237
2021-07-20 08:17:13,287 INFO success: dsmr_datalogger entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-07-20 09:11:16,835 INFO exited: dsmr_datalogger (exit status 0; expected)
2021-07-20 09:11:17,853 INFO spawned: 'dsmr_datalogger' with pid 2238
2021-07-20 09:11:18,857 INFO success: dsmr_datalogger entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-07-20 09:11:51,114 INFO exited: dsmr_datalogger (exit status 0; expected)
2021-07-20 09:11:52,130 INFO spawned: 'dsmr_datalogger' with pid 2239
2021-07-20 09:11:53,137 INFO success: dsmr_datalogger entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-07-20 09:19:55,327 INFO exited: dsmr_backend (exit status 0; expected)
2021-07-20 09:19:56,343 INFO spawned: 'dsmr_backend' with pid 2240
2021-07-20 09:19:57,349 INFO success: dsmr_backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-07-20 09:54:55,996 INFO exited: dsmr_backend (exit status 0; expected)
2021-07-20 09:54:57,010 INFO spawned: 'dsmr_backend' with pid 2241
2021-07-20 09:54:58,017 INFO success: dsmr_backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-07-20 10:12:14,686 INFO exited: dsmr_backend (exit status 0; expected)
2021-07-20 10:12:15,700 INFO spawned: 'dsmr_backend' with pid 2242
2021-07-20 10:12:16,705 INFO success: dsmr_backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-07-20 10:16:53,423 INFO exited: dsmr_datalogger (exit status 0; expected)
2021-07-20 10:16:54,438 INFO spawned: 'dsmr_datalogger' with pid 2243
2021-07-20 10:16:55,445 INFO success: dsmr_datalogger entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
I’ve tried attaching the P1 cable to a different USB port on the Raspberry Pi, nothing has changed.
Could that be a faulty cable, configuration or something else? Is there any way to enable any sort of debugging to pinpoint the issue? Many thanks in advance for support.