Error on record insertion

[casperleenheer]

Long story short: I upgraded dsmr running with docker compose, but I didn't check if it was succesful. After a month (today) I noticed it was missing entries in the compose file. I added them and dsmr and dsmrdb came up. However I am getting these now:

dsmrdb  | 2026-03-20 17:02:10.898 CET [12415] ERROR:  null value in column "delivered_1" of relation "dsmr_consumption_electricityconsumption" violates not-null constraint
dsmrdb  | 2026-03-20 17:02:10.898 CET [12415] DETAIL:  Failing row contains (3212523, 2026-03-20 13:33:00+00, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null).
dsmrdb  | 2026-03-20 17:02:10.898 CET [12415] STATEMENT:  INSERT INTO "dsmr_consumption_electricityconsumption" ("read_at", "delivered_1", "returned_1", "delivered_2", "returned_2", "currently_delivered", "currently_returned", "phase_currently_delivered_l1", "phase_currently_delivered_l2", "phase_currently_delivered_l3", "phase_currently_returned_l1", "phase_currently_returned_l2", "phase_currently_returned_l3", "phase_voltage_l1", "phase_voltage_l2", "phase_voltage_l3", "phase_power_current_l1", "phase_power_current_l2", "phase_power_current_l3") VALUES ('2026-03-20T14:33:00+01:00'::timestamptz, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL) RETURNING "dsmr_consumption_electricityconsumption"."id"
dsmr    | 2026-03-20 17:02:10,898 ERROR    schedule     execute_scheduled_processes      39 | (IntegrityError) dsmr_consumption.services.run errored: null value in column "delivered_1" of relation "dsmr_consumption_electricityconsumption" violates not-null constraint
dsmr    | DETAIL:  Failing row contains (3212523, 2026-03-20 13:33:00+00, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null).
dsmr    |  

I restored a different backups, but they all have the same issue. Any help is appreciated!

[dennissiemensma]

xirixiz/dsmr-reader-docker#412 (comment)

[casperleenheer]

This solved the issue. Thanks!