jens-maus
commented
9 months ago Well, within a CCU an internal (hidden) program is usually automatically added for every energy counter device (incl. HM-ES-TX-WM). This program is called prgEnergyCounterGAS_<ISEID>_<SERIAL>:<CHANNEL>. And exactly that program takes care to increase the internal ccu device counter system variable which also is automatically added and named svEnergyCounterGas_<ISEID>_<SERIAL>:<CHANNEL>'. See here:
So simply have a look if for your device there is such an internally hidden support program within the program list. And if so (must be) have a look inside the ReGa-Skript which is also automatically generated and then try to debug the issue yourself.
And these special internal energy counter scripts usually looks like the following example one:
object chn = dom.GetObject('<ISEID>');
object oBoot = chn.DPByControl('POWERMETER_IEC1.BOOT');
object oEnergyCounter = chn.DPByControl('POWERMETER_IEC1.GAS_ENERGY_COUNTER');
object oSysVarEnergyCounter = dom.GetObject('svEnergyCounterGas_<ISEID>_<SERIAL>:<CHANNEL>');
object oSysVarEnergyCounterOldVal = dom.GetObject('svEnergyCounterGasOldVal_<ISEID>');
object oSysVarEnergyCounterResetPressed = dom.GetObject('svEnergyCounterGas_<ISEID>_<SERIAL>:<CHANNEL>_RESET');
object oSysVarEnergyCounterTmpOldVal = dom.GetObject('svEnergyCounterGas_<ISEID>_<SERIAL>:<CHANNEL>_TMP_OLDVAL');
object oSysVarEnergyCounterDeviceReset = dom.GetObject('svEnergyCounterGas_<ISEID>_<SERIAL>:<CHANNEL>_DEVICE_RESET');
boolean bootFlag = oBoot.Value();
real devVal = oEnergyCounter.Value();
real devValMax = oEnergyCounter.ValueMax();
real oldDevVal = oSysVarEnergyCounterOldVal.Value();
real tmpOldDevVal = oSysVarEnergyCounterTmpOldVal.Value();
integer ioldDevVal = (tmpOldDevVal.ToString().ToFloat() * 100000).ToInteger();
real diffVal = 0.0;
real sysVarVal = oSysVarEnergyCounter.Value();
integer tmp_devVal = (devVal.ToString().ToFloat() * 100000).ToInteger();
integer tmp_oldDevVal = (oldDevVal.ToString().ToFloat() * 100000).ToInteger();
if ( oBoot.Value() == true ) {
oSysVarEnergyCounterDeviceReset.State(true);
if (ioldDevVal <= 0) {
oSysVarEnergyCounter.State(0);
}
} else {
boolean resetPressed = oSysVarEnergyCounterResetPressed.Value();
! boolean devReset = oSysVarEnergyCounterDeviceReset.Value();
if ( (resetPressed == true) && (oSysVarEnergyCounterDeviceReset.Value() == true) ) {
oSysVarEnergyCounterTmpOldVal.State(0);
tmpOldDevVal = 0;
}
!Normales Hochzaehlen. Geraetwert > vorheriger Wert
if ((tmp_devVal >= tmp_oldDevVal) && (oSysVarEnergyCounterDeviceReset.Value() == false)) {
if (resetPressed == false) {
diffVal = oEnergyCounter.Value() - oldDevVal;
} else {
!Reset pressed
diffVal = oEnergyCounter.Value() - tmpOldDevVal;
if ((diffVal.ToString().ToFloat() * 100000).ToInteger() < 0 ) {
diffVal = oEnergyCounter.Value();
}
oSysVarEnergyCounterResetPressed.State(0);
}
} else {
!Geraetewert ist kleiner vorheriger Wert
!Entweder Ueberlauf, oder Batterietausch
if (oSysVarEnergyCounterDeviceReset.Value() == false) {
!Normaler Geraeteueberlauf
if(tmp_devVal > 0) {
diffVal = (oEnergyCounter.Value() + devValMax) - oldDevVal;
}
} else {
!Zaehle Geraetewert zum CCU-Zaehler
diffVal = oEnergyCounter.Value();
if ((diffVal.ToString().ToFloat() * 100000).ToInteger() == 0) {
oSysVarEnergyCounterDeviceReset.State(true);
} else {
oSysVarEnergyCounterDeviceReset.State(false);
}
}
}
!Erhoehe den CCU-Zaehler
oSysVarEnergyCounter.State(sysVarVal + diffVal);
oSysVarEnergyCounterOldVal.State(oEnergyCounter.Value());
oSysVarEnergyCounterTmpOldVal.State(oEnergyCounter.Value());
}Thus, if you are keen, go and debug that helper script which I guess might run into the wrong if()else() branch for your case so that after each CCU boot the counter is increased by exactly the same amount currently stored in the device internal counter. Have phun!
soosp
github-actions[bot]
Baxxy13
wolwin
jp112sdl
Describe the issue you are experiencing
If you do gas metering with HM-ES-TX-WM_CCU and RaspberryMatic, the "Energy Counter - Central" field is increased with value of "Energy Counter - device" field after a power outage, software update or a simple reboot of RaspberryMatic. Here are the values before reboot:
After reboot:
And these are the values when device first appears:
There was not any gas consumption under this test.
@jp112sdl wrote:
See: also: https://github.com/jp112sdl/Beispiel_AskSinPP/issues/51
Describe the behavior you expected
After reboot the counter is not increased.
Steps to reproduce the issue
What is the version this bug report is based on?
3.71.12.20230826
Which base platform are you running?
rpi3 (RaspberryPi3)
Which HomeMatic/homematicIP radio module are you using?
RPI-RF-MOD
Anything in the logs that might be useful for us?
Additional information
This behavior is not related with this version, it was experienced in earlier RaspberryMatic releases too.