Page 1 of 1
P1 trouble after Domoticz upgrade
Posted: Sunday 18 October 2026 15:30
by Enlighted17
Hi all,
I have been using Domoticz for quite some time now and recently upgraded from 2025 version to 2026.4 as it looked really promising.
Before the upgrade, the counters of my P1 meter (connected through USB cable on my Raspberry Pi) worked fine and I could see actual and daily usage on my dashboard that were correct.
After the upgrade this seems to be a mess. Actual usage can be seen but the total value for today is wrong. In the evening it even stops registering / adding it to the daily usage.
I noticed some CRC messages in the logs (no errors) but am not sure if they are related.
Can anyone point me in the direction to fix this?
Version: 2026.4 (stable)
Platform: Raspberry Pi
Plugin/Hardware: USB P1 cable
Re: P1 trouble after Domoticz upgrade
Posted: Monday 19 October 2026 9:52
by ReiKurosawa
Two things from the official documentation that fit your symptoms. The Domoticz wiki page for the P1 smart meter (Dutch DSMR) describes a "CRC message validation" option in the P1 hardware settings that prevents reading corrupt telegram messages, so that is worth enabling and it also explains the CRC lines in your log. The development changelog on GitHub also lists a fix that is not yet in 2026.4: a malformed stored meter value previously aborted the short-log update entirely, which matches your "stops adding to the daily usage in the evening" - so the current beta or the next stable should help there. Hypothesis on my side: corrupt telegrams plus that abort bug together would look exactly like what you describe.
Re: P1 trouble after Domoticz upgrade
Posted: Monday 19 October 2026 11:47
by Enlighted17
Thank you for the information.
The CRC validation is enabled by default, and I have left that enabled so that should be ok then. (I suspected that these CRC check failures could prevent data from coming in, especially because before the upgrade I did not have any problems)
I will also take a look at making use of the beta to see if things are improving then.
In the meantime, if there is more to try please let me know.
Re: P1 trouble after Domoticz upgrade
Posted: Monday 19 October 2026 11:48
by jvdz
@ReiKurosawa,
don't think we need any AI generated responses here, so let's refrain from that.
Re: P1 trouble after Domoticz upgrade
Posted: Monday 19 October 2026 19:50
by JayDotR
Enlighted17 wrote: Sunday 18 October 2026 15:30
Hi all,
I have been using Domoticz for quite some time now and recently upgraded from 2025 version to 2026.4 as it looked really promising.
Before the upgrade, the counters of my P1 meter (connected through USB cable on my Raspberry Pi) worked fine and I could see actual and daily usage on my dashboard that were correct.
After the upgrade this seems to be a mess. Actual usage can be seen but the total value for today is wrong. In the evening it even stops registering / adding it to the daily usage.
I noticed some CRC messages in the logs (no errors) but am not sure if they are related.
Can anyone point me in the direction to fix this?
Version: 2026.4 (stable)
Platform: Raspberry Pi
Plugin/Hardware: USB P1 cable
Question : which interval of querying do you use ?
I had similar problems, which were gone since I reduced the frequency of looking for the P1 Data (before trixie, I used to leave it on 5 seconds, now 15 seconds seems fine ...)
Re: P1 trouble after Domoticz upgrade
Posted: Monday 19 October 2026 21:51
by Enlighted17
So far nothing made it work. Moving to Beta duoes not change anything. I was so happy with my Domoticz 2025 and wanted to try the new design and features
Now again in the evening I see a lot of 0 usage but I am surely using electricity and the old situation was showing that properly.
JayDotR wrote: Monday 19 October 2026 19:50
Question : which interval of querying do you use ?
I had similar problems, which were gone since I reduced the frequency of looking for the P1 Data (before trixie, I used to leave it on 5 seconds, now 15 seconds seems fine ...)
I have tried several options but no changes to my problems.
Also spikes can be seen suddenly after it worked for a while.
I just don't know what to try anymore.