DbLogInclude cur_power:60:force funktioniert nicht mehr

[DS_Starter]

addlog -> addLog

[thburkhart]

addlog -> addLog

oh wie peinlich  danke schön

was anderes:
über statistics bekomme zwar readings wie:

Code Auswählen Erweitern

statdayEnergy
Hour: 0.000 Day: 2.408 Month: 2.408 Year: 2.408 (since: 2023-02-28 )

dies obswohl ich als period nur day gesetzt hat.
Ich finde auch keine Möglichkeit, das Reading anders zu formatieren

kann ich ins dblog nur den Teil day also

Code Auswählen Erweitern

2.408 extrahieren ? und wie?

[DS_Starter]

kann ich ins dblog nur den Teil day also
Code: [Auswählen]

2.408

extrahieren ? und wie?

Ja, ich sehe die Möglichkeit ein userReading zu erzeugen und dieses zu loggen oder valueFn in Dblog zu nutzen.
Beides würde mit der Extraktion über ein Regex funktionieren.
Hier als Beispiel für valueFn (ungetestet):

{
   if ($DEVICE eq '<Device>' && $READING eq 'statdayEnergy') {
      $VALUE  =~ /Day:.(\d+(.\d+)?)/;
      $VALUE  = $1;
   }
}

(Fehler korrigiert)

[thburkhart]

ich kriege das TUYA-Device

Code Auswählen Erweitern

[code]define TUYA_SP12 fhempy tuya IGzCi97RpN2Lf9cu 00673231e09806cb13b0 192.168.9.57 b5614e736a41adec 3.3 ea845
attr TUYA_SP12 DbLogExclude .*
attr TUYA_SP12 DbLogInclude energy,cur_power
attr TUYA_SP12 alias SP12 TH Sued1
attr TUYA_SP12 dp_01 switch_1
attr TUYA_SP12 dp_09 countdown_1
attr TUYA_SP12 dp_17 add_ele
attr TUYA_SP12 dp_18 cur_current
attr TUYA_SP12 dp_19 cur_power
attr TUYA_SP12 dp_20 cur_voltage
attr TUYA_SP12 event-min-interval energy:3600,cur_power:600
attr TUYA_SP12 group Schalter (T),Schalter Strang,Schalter Strommessung
attr TUYA_SP12 room - Raum -> Thomas,-TUYA,TUYA Stromverbrauch
attr TUYA_SP12 stateFormat Verbrauch: [$name:energy] kWh, cPower [$name:cur_power] W, cVoltage [$name:cur_voltage] V, Time: [$name:cur_power:t]
attr TUYA_SP12 tuya_spec_functions [{'code': 'switch_1', 'dp_id': 1, 'type': 'Boolean', 'values': {}, 'desc': 'switch 1'}, {'code': 'countdown_1', 'dp_id': 9, 'type': 'Integer', 'values': {'unit': 's', 'min': 0, 'max': 86400, 'scale': 0, 'step': 1}, 'desc': 'countdown 1'}]
attr TUYA_SP12 tuya_spec_status [{'code': 'switch_1', 'dp_id': 1, 'type': 'Boolean', 'values': {}}, {'code': 'countdown_1', 'dp_id': 9, 'type': 'Integer', 'values': {'unit': 's', 'min': 0, 'max': 86400, 'scale': 0, 'step': 1}}, {'code': 'add_ele', 'dp_id': 17, 'type': 'Integer', 'values': {'unit': '', 'min': 0, 'max': 50000, 'scale': 3, 'step': 100}}, {'code': 'cur_current', 'dp_id': 18, 'type': 'Integer', 'values': {'unit': 'mA', 'min': 0, 'max': 30000, 'scale': 0, 'step': 1}}, {'code': 'cur_power', 'dp_id': 19, 'type': 'Integer', 'values': {'unit': 'W', 'min': 0, 'max': 50000, 'scale': 1, 'step': 1}}, {'code': 'cur_voltage', 'dp_id': 20, 'type': 'Integer', 'values': {'unit': 'V', 'min': 0, 'max': 5000, 'scale': 1, 'step': 1}}]
#   DEF        tuya IGzCi97RpN2Lf9cu 00673231e09806cb13b0 192.168.9.57 b5614e736a41adec 3.3 ea8453wdazquzfl08l0e 8a4b27dd759d4c6a9456aa8155d2a0ea
#   DEVICEID   00673231e09806cb13b0
#   FHEMPYTYPE tuya
#   FUUID      63a35f57-f33f-fd5f-d28c-f30c68bc093a1f03
#   IODev      local_pybinding
#   NAME       TUYA_SP12
#   NR         1753
#   PYTHONTYPE tuya
#   STATE      Verbrauch: 7.566 kWh, cPower 18.0 W, cVoltage 225.9 V, Time: 2023-03-14 19:50:24
#   TYPE       fhempy
#   eventCount 779
#   READINGS:
#     2023-01-30 07:59:14   countdown_1     0.0
#     2023-03-14 19:47:02   cur_current     134.0
#     2023-03-14 19:50:24   cur_power       18.0
#     2023-03-14 19:45:31   cur_voltage     225.9
#     2023-01-30 07:59:14   dp_21           1
#     2023-01-30 07:59:14   dp_22           721
#     2023-01-30 07:59:14   dp_23           30787
#     2023-01-30 07:59:14   dp_24           20947
#     2023-01-30 07:59:14   dp_25           995
#     2023-03-14 19:48:26   energy          7.566
#     2023-02-28 16:26:01   energy2212      0
#     2023-03-14 09:47:18   online          1
#     2023-03-14 19:50:24   statEnergy      Hour: 0.014 Day: 0.170 Month: 4.106 Year: 4.120 (since: 2023-02-28 )
#     2023-03-14 18:59:57   statEnergyLast  Hour: 0.018 Day: 0.151 Month: 0.014 Year: - (since: 2023-02-28 )
#     2023-02-28 21:18:13   statdayEnergy   Hour: 0.005 Day: 0.050 Month: 0.050 Year: 0.050 (since:  )
#     2023-02-28 21:00:02   statdayEnergyLast Hour: 0.001 Day: - Month: - Year: -
#     2023-03-14 09:48:25   state           on
#     2023-01-30 07:59:14   switch_1        on
#   args:
#     TUYA_SP12
#     fhempy
#     tuya
#     IGzCi97RpN2Lf9cu
#     00673231e09806cb13b0
#     192.168.9.57
#     b5614e736a41adec
#     3.3
#     ea8453wdazquzfl08l0e
#     8a4b27dd759d4c6a9456aa8155d2a0ea
#   argsh:
#   helper:
#     _98_statistics statistics_TUYA_SP_all
#
setstate TUYA_SP12 Verbrauch: 7.566 kWh, cPower 18.0 W, cVoltage 225.9 V, Time: 2023-03-14 19:50:24
setstate TUYA_SP12 2023-01-30 07:59:14 countdown_1 0.0
setstate TUYA_SP12 2023-03-14 19:47:02 cur_current 134.0
setstate TUYA_SP12 2023-03-14 19:50:24 cur_power 18.0
setstate TUYA_SP12 2023-03-14 19:45:31 cur_voltage 225.9
setstate TUYA_SP12 2023-01-30 07:59:14 dp_21 1
setstate TUYA_SP12 2023-01-30 07:59:14 dp_22 721
setstate TUYA_SP12 2023-01-30 07:59:14 dp_23 30787
setstate TUYA_SP12 2023-01-30 07:59:14 dp_24 20947
setstate TUYA_SP12 2023-01-30 07:59:14 dp_25 995
setstate TUYA_SP12 2023-03-14 19:48:26 energy 7.566
setstate TUYA_SP12 2023-02-28 16:26:01 energy2212 0
setstate TUYA_SP12 2023-03-14 09:47:18 online 1
setstate TUYA_SP12 2023-03-14 19:50:24 statEnergy Hour: 0.014 Day: 0.170 Month: 4.106 Year: 4.120 (since: 2023-02-28 )
setstate TUYA_SP12 2023-03-14 18:59:57 statEnergyLast Hour: 0.018 Day: 0.151 Month: 0.014 Year: - (since: 2023-02-28 )
setstate TUYA_SP12 2023-02-28 21:18:13 statdayEnergy Hour: 0.005 Day: 0.050 Month: 0.050 Year: 0.050 (since:  )
setstate TUYA_SP12 2023-02-28 21:00:02 statdayEnergyLast Hour: 0.001 Day: - Month: - Year: -
setstate TUYA_SP12 2023-03-14 09:48:25 state on
setstate TUYA_SP12 2023-01-30 07:59:14 switch_1 on

[/code]

nicht dazu, cur_power Events zu erzeugen. Mit energy gehts über addlog.

Woran kann es liegen ?

Beste Grüße

Thomas