P1 trouble after Domoticz upgrade

Please use template to report bugs and problems. Post here your questions when not sure where else to post
Only for bugs in the Domoticz application! other problems go in different subforums!

Moderators: leecollings, remb0

Forum rules
Before posting here, make sure you are on the latest Beta or Stable version.
If you have problems related to the web gui, clear your browser cache + appcache first.

Use the following template when posting here:

Version: xxxx
Platform: xxxx
Plugin/Hardware: xxxx
Description:
.....

If you are having problems with scripts/blockly, always post the script (in a spoiler or code tag) or screenshots of your blockly

If you are replying, please do not quote images/code from the first post

Please mark your topic as Solved when the problem is solved.
Post Reply
Enlighted17
Posts: 2
Joined: Sunday 18 October 2026 15:21
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

P1 trouble after Domoticz upgrade

Post 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
ReiKurosawa
Posts: 3
Joined: Saturday 17 October 2026 9:26
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: P1 trouble after Domoticz upgrade

Post 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.
Enlighted17
Posts: 2
Joined: Sunday 18 October 2026 15:21
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: P1 trouble after Domoticz upgrade

Post 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.
User avatar
jvdz
Posts: 2484
Joined: Tuesday 30 December 2014 19:25
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.107
Location: Netherlands
Contact:

Re: P1 trouble after Domoticz upgrade

Post by jvdz »

@ReiKurosawa,
don't think we need any AI generated responses here, so let's refrain from that.
Post Reply