Ich nutze PowerMap seit einiger Zeit, um bei Devices ohne consumption-/energy-Readings den Stromverbrauch (ungefähr) zu tracken. Das läuft super.
Nun habe ich zwei Devices, die mir zwar currentConsumption-Readings liefern (reale Werte) aber leider keinen Gesamtverbrauch (kontinuierlicher Zähler).
Ich hatte die Hoffnung, dass ich PowerMap auch so einsetzen kann und mit dem Attribut
powerMap_rname_P
das Device-Power-Reading zu benennen, so dass ich in
powerMap_rname_E
dann das Reading benenne, in dem PowerMap den kontinuierlichen Zähler liefert.
Das funktioniert so aber leider nicht. Habe ich noch etwas falsch?
define sonnenbatterie HTTPMOD ... 120
attr sonnenbatterie DbLogExclude .*
attr sonnenbatterie DbLogInclude Apparent_output,BackupBuffer,BatteryCharging,BatteryDischarging,Consumption_W,Fac,FlowConsumptionBattery,FlowConsumptionGrid,FlowConsumptionProduction,FlowGridBattery,FlowProductionBattery,FlowProductionGrid,GridFeedIn_W,OperatingMode,Pac_total_W,Production_W,RSOC,RemainingCapacity_Wh,Sac1,SystemStatus,USOC,Uac,Ubat,energy_num
...
attr sonnenbatterie event-on-change-reading Apparent_output,BackupBuffer,BatteryCharging,BatteryDischarging,Consumption_W,Fac,FlowConsumptionBattery,FlowConsumptionGrid,FlowConsumptionProduction,FlowGridBattery,FlowProductionBattery,FlowProductionGrid,GridFeedIn_W,OperatingMode,Pac_total_W,Production_W,RSOC,RemainingCapacity_Wh,Sac1,SystemStatus,USOC,Uac:3,Ubat:2,energy_num
...
attr sonnenbatterie powerMap_interval 120
attr sonnenbatterie powerMap_noEnergy 0
attr sonnenbatterie powerMap_noPower 0
attr sonnenbatterie powerMap_rname_E energy_num
attr sonnenbatterie powerMap_rname_P Consumption_W
# BUSY 0
# DEF ... 120
# FUUID ...
# Interval 120
# MainURL ...
# ModuleVersion 4.1.15 - 17.12.2022
# NAME sonnenbatterie
# NOTIFYDEV global
# NR 712
# NTFY_ORDER 50-sonnenbatterie
# STATE Verbrauch 304 W: 0 W aus PV + 2 W in Speicher + 305 W aus Grid, SOC 30% + 0010
# TYPE HTTPMOD
# eventCount 6360
# value
# Helper:
# DBLOG:
# Consumption_W:
# dblog:
# TIME 1685706911.63402
# VALUE 304.0
...
# HttpUtils:
# NAME
# addr ...
# auth 0
# buf
# code 200
# compress 1
# conn
# data
# displayurl ...
# header Auth-Token: ...
# host ...
# httpheader HTTP/1.1 200 OK
#Date: Fri, 02 Jun 2023 11:55:11 GMT
#Content-Type: application/json
#Transfer-Encoding: chunked
#Connection: close
#Content-Security-Policy: default-src 'self' sentry.sonnenbatterie.de 'unsafe-inline'
#Referrer-Policy: same-origin
#X-Content-Type-Options: nosniff
#X-Frame-Options:: sameorigin
#X-Permitted-Cross-Domain-Policies:: none
#X-XSS-Protection: 1; mode=block
#Content-Encoding: gzip
# httpversion 1.1
# hu_blocking 0
# hu_filecount 1
# hu_port 80
# hu_portSfx
# ignoreredirects 1
# loglevel 4
# path /api/v2/latestdata
# protocol http
# redirects 0
# timeout 2
# url ...
# sslargs:
# QUEUE:
# READINGS:
...
# 2023-06-02 13:55:11 Consumption_W 304
...
# REQUEST:
# context reading
# data
# header ...
# ignoreredirects 0
# num unknown
# retryCount 0
# type update
# url ...
# defptr:
# readingBase:
# Consumption_W reading
...
# readingNum:
# Consumption_W unknown
...
# readingOutdated:
# requestReadings:
# update:
# Consumption_W reading unknown
...
# powerMap:
# readingsDesc:
# Consumption_W:
# rtype w
# energy_num:
# rtype whr
#
...
setstate sonnenbatterie 2023-06-02 13:55:11 Consumption_W 304
...