Zitat von: Prof. Dr. Peter Henning am 27 April 2024, 14:57:131. Wie wurde aWATTar in FHEM integriert?
2. Was heißt "die Werte sehe ich"? In FHEM gibt es Readings, Internals und Attribute - also um was handelt es sich?
LG
pah
ZitatcurrentInverterDev <Inverter Device Name> pv=<Readingname>:<Einheit> etotal=<Readingname>:<Einheit> [capacity=<max. WR-Leistung>]da wäre der totale Tageszähler anzugeben und nicht der totale Zähler über die gesamte Laufzeit...
Legt ein beliebiges Device und dessen Readings zur Lieferung der aktuellen PV Erzeugungswerte fest. Es kann auch ein Dummy Device mit entsprechenden Readings sein. Die Werte mehrerer Inverterdevices führt man z.B. in einem Dummy Device zusammen und gibt dieses Device mit den entsprechenden Readings an.
Die Angabe von capacity ist optional, wird aber zur Optimierung der Vorhersagegenauigkeit dringend empfohlen.
pv Reading welches die aktuelle PV-Erzeugung liefert
etotal Reading welches die gesamte erzeugte PV-Energie liefert (ein stetig aufsteigender Zähler)
Einheit die jeweilige Einheit (W,kW,Wh,kWh)
capacity Bemessungsleistung des Wechselrichters gemäß Datenblatt, d.h. max. möglicher Output in Watt
(Die Angabe ist optional, wird aber dringend empfohlen zu setzen)
Beispiel:
set <name> currentInverterDev STP5000 pv=total_pac:kW etotal=etotal:kWh capacity=5000
# Device STP5000 liefert PV-Werte. Die aktuell erzeugte Leistung im Reading "total_pac" (kW) und die tägliche Erzeugung im Reading "etotal" (kWh). Die max. Leistung des Wechselrichters beträgt 5000 Watt.
2024.04.28 01:20:59 1: HMCCU [RaspberryMatic] CCU port 8181 is reachable
2024.04.28 01:20:59 1: HMCCU [RaspberryMatic] Initialized version 5.0 222930908
2024.04.28 01:20:59 1: HMCCU [RaspberryMatic] Initializing device
2024.04.28 01:20:59 2: HMCCU [RaspberryMatic] Deleting old CCU configuration data
2024.04.28 01:20:59 2: HMCCU [RaspberryMatic] Updating device table
2024.04.28 01:20:59 1: HMCCU [RaspberryMatic] Can't read virtual groups from CCU. Response:
2024.04.28 01:20:59 1: HMCCU [RaspberryMatic] Read 5 devices with 108 channels from CCU 192.168.180.4
2024.04.28 01:20:59 1: HMCCU [RaspberryMatic] Read 0 programs from CCU 192.168.180.4
2024.04.28 01:20:59 1: HMCCU [RaspberryMatic] Read 0 virtual groups from CCU 192.168.180.4
2024.04.28 01:20:59 1: HMCCU [RaspberryMatic] Reading device config from CCU. This may take a couple of seconds ...
2024.04.28 01:20:59 2: HMCCU [RaspberryMatic] Reading Device Descriptions for interface BidCos-RF
2024.04.28 01:20:59 2: HMCCU [RaspberryMatic] Read 59 Device Descriptions for interface BidCos-RF
2024.04.28 01:20:59 2: HMCCU [RaspberryMatic] Reading Paramset Descriptions for interface BidCos-RF
2024.04.28 01:20:59 2: HMCCU [RaspberryMatic] Read 1 Paramset Descriptions for interface BidCos-RF
2024.04.28 01:20:59 2: HMCCU [RaspberryMatic] Reading Peer Descriptions for interface BidCos-RF
2024.04.28 01:20:59 2: HMCCU [RaspberryMatic] Read 3 Peer Descriptions for interface BidCos-RF
2024.04.28 01:20:59 2: HMCCU [RaspberryMatic] Read RPC device configuration: devices/channels=59 parametersets=1 links=3
2024.04.28 01:21:55 2: HMCCU [RaspberryMatic] RPC device for interface BidCos-RF: d_rpc180004BidCos_RF
2024.04.28 01:21:55 2: HMCCURPCPROC [d_rpc180004BidCos_RF] RPC server process started for interface BidCos-RF with PID=29793
2024.04.28 01:21:55 2: HMCCURPCPROC [d_rpc180004BidCos_RF] Initializing RPC server CB2001000002180004 for interface BidCos-RF
2024.04.28 01:21:55 1: HMCCURPCPROC [d_rpc180004BidCos_RF] RPC server starting
2024.04.28 01:21:55 2: HMCCU [RaspberryMatic] RPC server start: 1 started, 0 already running, 0 failed to start
2024.04.28 01:21:56 2: HMCCURPCPROC [d_rpc180004BidCos_RF] Callback server CB2001000002180004 created. Listening on port 7411
2024.04.28 01:21:56 2: HMCCURPCPROC [d_rpc180004BidCos_RF] CB2001000002180004 accepting connections. PID=29793
2024.04.28 01:21:56 2: HMCCURPCPROC [d_rpc180004BidCos_RF] RPC server CB2001000002180004 enters server loop
2024.04.28 01:21:56 2: HMCCURPCPROC [d_rpc180004BidCos_RF] Registering callback http://172.27.0.2:7411/fh2001 of type A with ID CB2001000002180004 at http://192.168.180.4:2001
2024.04.28 01:24:56 2: HMCCURPCPROC [d_rpc180004BidCos_RF] RPC request init failed: RPC::XML::Client::simple_request: RPC::XML::Client::send_request: HTTP server error: read timeout
2024.04.28 01:24:56 2: HMCCURPCPROC [d_rpc180004BidCos_RF] Retrying request init
2024.04.28 01:27:56 2: HMCCURPCPROC [d_rpc180004BidCos_RF] RPC request init failed: RPC::XML::Client::simple_request: RPC::XML::Client::send_request: HTTP server error: read timeout
2024.04.28 01:27:56 2: HMCCURPCPROC [d_rpc180004BidCos_RF] Retrying request init
2024.04.28 01:27:56 1: HMCCURPCPROC [d_rpc180004BidCos_RF] Failed to register callback for ID CB2001000002180004: RPC request init failed: RPC::XML::Client::simple_request: RPC::XML::Client::send_request: HTTP server error: read timeout
2024.04.28 01:27:56 1: HMCCU [RaspberryMatic] All RPC servers error
2024.04.28 01:27:56 2: HMCCURPCPROC [d_rpc180004BidCos_RF] Checking if RPC server process is running
2024.04.28 01:27:56 1: HMCCURPCPROC [d_rpc180004BidCos_RF] RPC server process not running. Cleaning up
2024.04.28 01:27:56 1: HMCCURPCPROC [d_rpc180004BidCos_RF] Housekeeping called. Cleaning up RPC environment
2024.04.28 01:27:56 2: HMCCURPCPROC [d_rpc180004BidCos_RF] Sending signal INT to RPC server process CB2001000002180004 with PID=29793
2024.04.28 01:27:56 2: HMCCURPCPROC [d_rpc180004BidCos_RF] CB2001000002180004 received signal INT
2024.04.28 01:27:56 1: HMCCURPCPROC [d_rpc180004BidCos_RF] RPC server CB2001000002180004 stopped handling connections. PID=29793
2024.04.28 01:27:56 2: HMCCURPCPROC [d_rpc180004BidCos_RF] Number of I/O errors = 0
2024.04.28 01:27:58 2: HMCCURPCPROC [d_rpc180004BidCos_RF] RPC server process CB2001000002180004 deleted
2024.04.28 01:27:58 1: HMCCU [RaspberryMatic] All RPC servers inactive
2024.04.28 01:27:58 2: HMCCURPCPROC [d_rpc180004BidCos_RF] Stop I/O handling
2024.04.28 01:27:58 2: HMCCURPCPROC [d_rpc180004BidCos_RF] RPC server stopped. Cancel delayed shutdown.