wichtiges UPDATE für controller 7.2.2 im stable

[fuzzy1955]

@Qlink sagte:

Gibt es eine Einstellungsmöglichkeit wo ich angeben kann, dass die dynamische Ladeleistung immer z.B. 500W UNTER der aktuellen PV Leistung eingestellt werden soll

Hallo,

ich habe auch eine P30 und steuere den Ladestrom dynamisch mit einem JavaScript (kecontact.0.currentUser). Das müsste zur PV Leistung mit einer Formel auch funktionieren, z.B.:

iLadestrom (mA) = PV-Leistung (mW) / Wechselrichter-Ausgangsspannung (V)
19565 = (5000000 - 500000) / 230 (bei einphasigem Laden)

setState('kecontact.0.currentUser',iLadestrom,false)

Änderung alle 5 Minuten. Versuch es mal.

Gruß, Fuzzy

[Sneak-L8]

Ok, probiere mal bitte mal die Version bei github. Die Beschreibung habe ich bisher nur im State automatic.addPower angepasst, noch nicht in den Einstellungen. Sollte aber damit gehen.

[Qlink]

@sneak-l8 Hat die Version auch eine neue Versionsnummer ? Ich habe die 3.6.0 installiert und auf Github sehe ich aktuell auch nur die 3.6.0...

[Sneak-L8]

Nein, keine neue Versions-Nr. Das kommt erst bei Veröffentlichung.

[Qlink]

Wie kann ich die dann installieren? Update gibt's ja nicht...

[Sneak-L8]

Amin-Mode in ioBroker aktivieren (das Icon mit der Sturmmaske). Dann im Register auf das Katzensymbol, Reiter "von github". Im Text unten kecontact eingeben und installieren.

[Qlink]

@sneak-l8
Danke. Hab das heute mal ausprobiert.
Es hat allerdings keinen Effekt ob ich bei addPower 500 oder -500 eintrage. Er verbraucht bzw. lädt immer gleich, egal was ich eintrage.

[Sneak-L8]

Bitte mal Adapter auf debug stellen und Log posten.

[Qlink]

@sneak-l8

Hier das Log:

2026-07-02 15:14:26.423 - debug: kecontact.0 (10200) Redis Objects: Use Redis connection: 172.18.0.5:6379
2026-07-02 15:14:26.442 - debug: kecontact.0 (10200) Objects client ready ... initialize now
2026-07-02 15:14:26.443 - debug: kecontact.0 (10200) Objects create System PubSub Client
2026-07-02 15:14:26.444 - debug: kecontact.0 (10200) Objects create User PubSub Client
2026-07-02 15:14:26.653 - debug: kecontact.0 (10200) Objects client initialize lua scripts
2026-07-02 15:14:26.658 - debug: kecontact.0 (10200) Objects connected to redis: 172.18.0.5:6379
2026-07-02 15:14:26.668 - debug: kecontact.0 (10200) Redis States: Use Redis connection: redis:6379
2026-07-02 15:14:26.680 - debug: kecontact.0 (10200) States create System PubSub Client
2026-07-02 15:14:26.681 - debug: kecontact.0 (10200) States create User PubSub Client
2026-07-02 15:14:26.686 - debug: kecontact.0 (10200) States connected to redis: redis:6379
2026-07-02 15:14:26.717 - debug: kecontact.0 (10200) Plugin sentry Initialize Plugin (enabled=true)
2026-07-02 15:14:28.243 - info: sql.0 (3717) enabled logging of kecontact.0.p, Alias=false, WriteNulls=false
2026-07-02 15:14:28.531 - info: kecontact.0 (10200) starting. Version 3.6.0 (non-npm: iobroker-community-adapters/ioBroker.kecontact) in /opt/iobroker/node_modules/iobroker.kecontact, node: v22.21.0, js-controller: 7.2.2
2026-07-02 15:14:28.555 - info: kecontact.0 (10200) starting charging station in active mode
2026-07-02 15:14:28.603 - debug: kecontact.0 (10200) config host: 192.168.30.15
2026-07-02 15:14:28.604 - debug: kecontact.0 (10200) config passiveMode: false
2026-07-02 15:14:28.604 - debug: kecontact.0 (10200) config pollInterval: 5
2026-07-02 15:14:28.604 - debug: kecontact.0 (10200) config loadChargingSessions: true
2026-07-02 15:14:28.604 - debug: kecontact.0 (10200) config lessInfoLogs: false
2026-07-02 15:14:28.604 - debug: kecontact.0 (10200) config useX1forAutomatic: false
2026-07-02 15:14:28.604 - debug: kecontact.0 (10200) config authChargingTime: 60
2026-07-02 15:14:28.604 - debug: kecontact.0 (10200) config stateRegard: sma-em.0.1901701237.pregard
2026-07-02 15:14:28.604 - debug: kecontact.0 (10200) config stateSurplus: sma-em.0.1901701237.psurplus
2026-07-02 15:14:28.604 - debug: kecontact.0 (10200) config stateBatteryCharging:
2026-07-02 15:14:28.604 - debug: kecontact.0 (10200) config stateBatteryDischarging:
2026-07-02 15:14:28.605 - debug: kecontact.0 (10200) config stateBatterySoC:
2026-07-02 15:14:28.605 - debug: kecontact.0 (10200) config batteryPower: 0
2026-07-02 15:14:28.605 - debug: kecontact.0 (10200) config batteryChargePower: 0
2026-07-02 15:14:28.605 - debug: kecontact.0 (10200) config batteryMinSoC: 10
2026-07-02 15:14:28.605 - debug: kecontact.0 (10200) config batteryLimitSoC: 95
2026-07-02 15:14:28.605 - debug: kecontact.0 (10200) config batteryStorageStrategy: 0
2026-07-02 15:14:28.605 - debug: kecontact.0 (10200) config statesIncludeWallbox: true
2026-07-02 15:14:28.605 - debug: kecontact.0 (10200) config.state1p3pSwitch:
2026-07-02 15:14:28.605 - debug: kecontact.0 (10200) config.1p3pViax2: false
2026-07-02 15:14:28.606 - debug: kecontact.0 (10200) config.1p3pSwitchIsNO: true, 1p = 0, 3p = 1, off = 0
2026-07-02 15:14:28.606 - debug: kecontact.0 (10200) config minAmperage: 6000
2026-07-02 15:14:28.606 - debug: kecontact.0 (10200) config addPower: 100
2026-07-02 15:14:28.606 - debug: kecontact.0 (10200) config delta: 500
2026-07-02 15:14:28.606 - debug: kecontact.0 (10200) config underusage: 100
2026-07-02 15:14:28.606 - debug: kecontact.0 (10200) config minTime: 120
2026-07-02 15:14:28.606 - debug: kecontact.0 (10200) config regardTime: 120
2026-07-02 15:14:28.606 - debug: kecontact.0 (10200) config stateEnWG:
2026-07-02 15:14:28.606 - debug: kecontact.0 (10200) config dynamicEnWG: false
2026-07-02 15:14:28.606 - debug: kecontact.0 (10200) config maxPower: 0
2026-07-02 15:14:28.607 - debug: kecontact.0 (10200) config stateEnergyMeter1:
2026-07-02 15:14:28.607 - debug: kecontact.0 (10200) config stateEnergyMeter2:
2026-07-02 15:14:28.607 - debug: kecontact.0 (10200) config stateEnergyMeter3:
2026-07-02 15:14:28.607 - debug: kecontact.0 (10200) config wallboxNotIncluded: false
2026-07-02 15:14:28.607 - debug: kecontact.0 (10200) config maxAmperage: 0
2026-07-02 15:14:28.607 - debug: kecontact.0 (10200) config stateAmperagePhase1:
2026-07-02 15:14:28.607 - debug: kecontact.0 (10200) config stateAmperagePhase2:
2026-07-02 15:14:28.607 - debug: kecontact.0 (10200) config stateAmperagePhase3:
2026-07-02 15:14:28.607 - debug: kecontact.0 (10200) config amperageUnit: mA => factor is 1
2026-07-02 15:14:28.613 - debug: kecontact.0 (10200) UDP server listening on 0.0.0.0:7090
2026-07-02 15:14:28.613 - debug: kecontact.0 (10200) UDP broadcast server listening on 0.0.0.0:7092
2026-07-02 15:14:28.648 - debug: kecontact.0 (10200) subscribe state sma-em.0.1901701237.pregard - current value: 0
2026-07-02 15:14:28.650 - debug: kecontact.0 (10200) subscribe state sma-em.0.1901701237.psurplus - current value: 178.79
2026-07-02 15:14:28.885 - debug: kecontact.0 (10200) Sent "report 1" to 192.168.30.15:7090
2026-07-02 15:14:28.923 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "1",
"Product": "KC-P30-ES2400B2-M0R",
"Serial": "20296767",
"Firmware":"P30 v 3.10.80 (251002-115400)",
"COM-module": 1,
"Backend": 0,
"timeQ": 3,
"setBoot": 0,
"DIP-Sw1": "0x26",
"DIP-Sw2": "0x00",
"Sec": 2762357
}
"
2026-07-02 15:14:29.184 - debug: kecontact.0 (10200) Sent "report 101" to 192.168.30.15:7090
2026-07-02 15:14:29.186 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "101",
"Session ID": 343,
"Curr HW": 20000,
"E start": 76549739,
"E pres": 0,
"started[s]": 1782993418,
"ended[s]": 0,
"started": "2026-07-02 11:56:58.000",
"ended": "0",
"reason": 5,
"timeQ": 0,
"RFID tag": "f6c4c58600000000",
"RFID class": "cc4db022000000000000",
"Serial": "20296767",
"Sec": 2762357
}
"
2026-07-02 15:14:29.186 - debug: kecontact.0 (10200) History ID received: 01
2026-07-02 15:14:29.417 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{"E pres": 112761}"
2026-07-02 15:14:29.484 - debug: kecontact.0 (10200) Sent "report 102" to 192.168.30.15:7090
2026-07-02 15:14:29.486 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "102",
"Session ID": 342,
"Curr HW": 20000,
"E start": 76527546,
"E pres": 22193,
"started[s]": 1782832928,
"ended[s]": 1782839524,
"started": "2026-06-30 15:22:08.000",
"ended": "2026-06-30 17:12:04.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "31681f19000000000000",
"Serial": "20296767",
"Sec": 2762357
}
"
2026-07-02 15:14:29.487 - debug: kecontact.0 (10200) History ID received: 02
2026-07-02 15:14:29.785 - debug: kecontact.0 (10200) Sent "report 103" to 192.168.30.15:7090
2026-07-02 15:14:29.787 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "103",
"Session ID": 341,
"Curr HW": 20000,
"E start": 76345348,
"E pres": 182198,
"started[s]": 1782727227,
"ended[s]": 1782744808,
"started": "2026-06-29 10:00:27.000",
"ended": "2026-06-29 14:53:28.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "b696d212000000000000",
"Serial": "20296767",
"Sec": 2762357
}
"
2026-07-02 15:14:29.788 - debug: kecontact.0 (10200) History ID received: 03
2026-07-02 15:14:30.085 - debug: kecontact.0 (10200) Sent "report 104" to 192.168.30.15:7090
2026-07-02 15:14:30.138 - debug: kecontact.0 (10200) Keba firmware check: section found, examing "description": "Software\u002DUpdate\u0020\u0028x\u002Dseries\u0029",
"version": "2.0.1",
"distribution": {
"@type": "DataDownload",
"contentUrl": "https://dataspace.keba.com/public/download-shares/OxQl4muru084hhG19F2kbV8wMqDOMwQ2 ",
"encodingFormat": "application/octet-stream"
...
2026-07-02 15:14:30.139 - debug: kecontact.0 (10200) Keba firmware check: found firmware 2.0.1
2026-07-02 15:14:30.139 - debug: kecontact.0 (10200) Keba firmware check: section found, examing "description": "Software\u002DUpdate\u0020\u0028x\u002Dseries\u0029",
"version": "1.19.6",
"distribution": {
"@type": "DataDownload",
"contentUrl": "https://dataspace.keba.com/public/download-shares/kQkOz1g1rwyUq056SgkjjeNbxcC4OfZ0",
"encodingFormat": "application/octet-stream"
...
2026-07-02 15:14:30.139 - debug: kecontact.0 (10200) Keba firmware check: found firmware 1.19.6
2026-07-02 15:14:30.140 - debug: kecontact.0 (10200) Keba firmware check: section found, examing "description": "Software\u002DUpdate\u0020\u0028x\u002Dseries\u0029",
"version": "1.19",
"distribution": {
"@type": "DataDownload",
"contentUrl": "https://dataspace.keba.com/public/download-shares/2A6eBZSBNIgVO3c7L4B1Rsrc9R5EV5Ws",
"encodingFormat": "application/octet-stream"
...
2026-07-02 15:14:30.140 - debug: kecontact.0 (10200) Keba firmware check: found firmware 1.19
2026-07-02 15:14:30.140 - debug: kecontact.0 (10200) Keba firmware check: section found, examing "description": "Software\u002DUpdate\u0020\u0028x\u002Dseries\u0029",
"version": "1.17.2",
"distribution": {
"@type": "DataDownload",
"contentUrl": "https://www.keba.com/p30-software-1-17-2",
"encodingFormat": "application/octet-stream"
...
2026-07-02 15:14:30.140 - debug: kecontact.0 (10200) Keba firmware check: found firmware 1.17.2
2026-07-02 15:14:30.140 - debug: kecontact.0 (10200) Keba firmware check: section found, examing "description": "Software\u002DUpdate\u0020\u0028x\u002Dseries\u0029",
"version": "1.17.1",
"distribution": {
"@type": "DataDownload",
"contentUrl": "https://dataspace.keba.com/public/download-shares/nQapVonPJfCjzam1ik8UkFFEGIzePV10",
"encodingFormat": "application/octet-stream"
...
2026-07-02 15:14:30.140 - debug: kecontact.0 (10200) Keba firmware check: found firmware 1.17.1
2026-07-02 15:14:30.140 - debug: kecontact.0 (10200) Keba firmware check: section found, examing "description": "Software\u002DUpdate\u0020\u0028x\u002Dseries\u0029",
"version": "1.16.1",
"distribution": {
"@type": "DataDownload",
"contentUrl": "https://dataspace.keba.com/public/download-shares/cjKCbcvnfS1i6ziiN2po9ykpWOPy5BQ4",
"encodingFormat": "application/octet-stream"
...
2026-07-02 15:14:30.140 - debug: kecontact.0 (10200) Keba firmware check: found firmware 1.16.1
2026-07-02 15:14:30.140 - debug: kecontact.0 (10200) Keba firmware check: section found, examing "description": "Software\u002DUpdate\u0020\u0028x\u002Dseries\u0029",
"version": "1.15.1",
"distribution": {
"@type": "DataDownload",
"contentUrl": "https://dataspace.keba.com/public/download-shares/WqnTsQmz1MDJZ1or5UkI3WVDD0ZQz50k",
"encodingFormat": "application/octet-stream"
...
2026-07-02 15:14:30.141 - debug: kecontact.0 (10200) Keba firmware check: found firmware 1.15.1
2026-07-02 15:14:30.141 - debug: kecontact.0 (10200) Keba firmware check: section found, examing "description": "Software\u002DUpdate\u0020\u0028x\u002Dseries\u0029",
"version": "1.14.1",
"distribution": {
"@type": "DataDownload",
"contentUrl": "https://dataspace.keba.com/public/download-shares/otgzyuSzoaAEFTDAlIn4DlxZKoDMzyq8",
"encodingFormat": "application/octet-stream"
...
2026-07-02 15:14:30.141 - debug: kecontact.0 (10200) Keba firmware check: found firmware 1.14.1
2026-07-02 15:14:30.141 - debug: kecontact.0 (10200) Keba firmware check: section found, examing "description": "Software\u002DUpdate\u0020\u0028x\u002Dseries\u0029",
"version": "1.13",
"distribution": {
"@type": "DataDownload",
"contentUrl": "https://dataspace.keba.com/public/download-shares/d0SmxPWKKLCLdORjmBDShzGg4sNddzCN",
"encodingFormat": "application/octet-stream"
...
2026-07-02 15:14:30.141 - debug: kecontact.0 (10200) Keba firmware check: found firmware 1.13
2026-07-02 15:14:30.141 - debug: kecontact.0 (10200) Keba firmware check: section found, examing "description": "Software\u002DUpdate\u0020\u0028x\u002Dseries\u0029",
"version": "1.12.1",
"distribution": {
"@type": "DataDownload",
"contentUrl": "https://dataspace.keba.com/#/public/shares-downloads/h0NmXHvtTxYl2pw2uetpw5WKVJaix7YT",
"encodingFormat": "application/octet-stream"
...
2026-07-02 15:14:30.141 - debug: kecontact.0 (10200) Keba firmware check: found firmware 1.12.1
2026-07-02 15:14:30.141 - debug: kecontact.0 (10200) Keba firmware check: section found, examing "description": "Software\u002DUpdate\u0020\u0028x\u002Dseries\u0029",
"version": "1.11",
"distribution": {
"@type": "DataDownload",
"contentUrl": "https://dataspace.keba.com/#/public/shares-downloads/ogoEsbvMgEd0YFpvTNh7n8WKVKNORqpD",
"encodingFormat": "application/octet-stream"
...
2026-07-02 15:14:30.142 - debug: kecontact.0 (10200) Keba firmware check: found firmware 1.11
2026-07-02 15:14:30.142 - debug: kecontact.0 (10200) Keba firmware check: section found, examing "description": "Software\u002DUpdate\u0020\u0028x\u002Dseries\u0029",
"version": "1.10",
"distribution": {
"@type": "DataDownload",
"contentUrl": "https://dataspace.keba.com/#/public/shares-downloads/8luWNKcccEpCSGd1d3siJ8IC7vS4jAXV",
"encodingFormat": "application/octet-stream"
...
2026-07-02 15:14:30.142 - debug: kecontact.0 (10200) Keba firmware check: found firmware 1.10
2026-07-02 15:14:30.142 - debug: kecontact.0 (10200) Keba firmware check: section found, examing "description": "Software\u002DUpdate\u0020\u0028x\u002Dseries\u0029",
"version": "1.9.10",
"distribution": {
"@type": "DataDownload",
"contentUrl": "https://dataspace.keba.com/#/public/shares-downloads/HGjja7PqmgyhfJgwn9PZWeYQzZSa1Okd",
"encodingFormat": "application/octet-stream"
...
2026-07-02 15:14:30.142 - debug: kecontact.0 (10200) Keba firmware check: found firmware 1.9.10
2026-07-02 15:14:30.142 - debug: kecontact.0 (10200) Keba firmware check: section found, examing "description": "Software\u002DUpdate\u0020\u0028x\u002Dseries\u0029",
"version": "1.8.2",
"distribution": {
"@type": "DataDownload",
"contentUrl": "https://dataspace.keba.com/#/public/shares-downloads/Iy2YUn4H2JfGyRYk8ShbXh9pCuMjFw4y",
"encodingFormat": "application/octet-stream"
...
2026-07-02 15:14:30.142 - debug: kecontact.0 (10200) Keba firmware check: found firmware 1.8.2
2026-07-02 15:14:30.142 - debug: kecontact.0 (10200) Keba firmware check: section found, examing "description": "Software\u002DUpdate\u0020\u0028x\u002Dseries\u0029",
"version": "1.7",
"distribution": {
"@type": "DataDownload",
"contentUrl": "https://dataspace.keba.com/#/public/shares-downloads/T3EfK890pYOORWLPX8xJRDNAbU09i5Hv",
"encodingFormat": "application/octet-stream"
...
2026-07-02 15:14:30.143 - debug: kecontact.0 (10200) Keba firmware check: found firmware 1.7
2026-07-02 15:14:30.143 - debug: kecontact.0 (10200) Keba firmware check: section found, examing "description": "Software\u002DUpdate\u0020\u0028x\u002Dseries\u0029",
"version": "1.6.3",
"distribution": {
"@type": "DataDownload",
"contentUrl": "https://dataspace.keba.com/public/download-shares/Bfs4hy4YD3WjeQMJoNQFGcMSPc5vhCc9",
"encodingFormat": "application/octet-stream"
...
2026-07-02 15:14:30.143 - debug: kecontact.0 (10200) Keba firmware check: found firmware 1.6.3
2026-07-02 15:14:30.143 - debug: kecontact.0 (10200) Keba firmware check: section found, examing "description": "Software\u002DUpdate\u0020\u0028x\u002Dseries\u0029",
"version": "1.5",
"distribution": {
"@type": "DataDownload",
"contentUrl": "https://dataspace.keba.com/public/download-shares/w08qwgwGMzC5W9nDjYlN7AIEEbDfeqkg",
"encodingFormat": "application/octet-stream"
...
2026-07-02 15:14:30.143 - debug: kecontact.0 (10200) Keba firmware check: found firmware 1.5
2026-07-02 15:14:30.143 - debug: kecontact.0 (10200) Keba firmware check: section found, examing "description": "Software\u002DUpdate\u0020\u0028x\u002Dseries\u0029",
"version": "1.4",
"distribution": {
"@type": "DataDownload",
"contentUrl": "https://dataspace.keba.com/public/download-shares/67GO3FZQg4YvGeYlPL4U54Ycna3MYyEn",
"encodingFormat": "application/octet-stream"
...
2026-07-02 15:14:30.143 - debug: kecontact.0 (10200) Keba firmware check: found firmware 1.4
2026-07-02 15:14:30.147 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "104",
"Session ID": 340,
"Curr HW": 20000,
"E start": 76273803,
"E pres": 71545,
"started[s]": 1782720590,
"ended[s]": 1782724806,
"started": "2026-06-29 08:09:50.000",
"ended": "2026-06-29 09:20:06.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "ae3e6d12000000000000",
"Serial": "20296767",
"Sec": 2762358
}
"
2026-07-02 15:14:30.148 - debug: kecontact.0 (10200) History ID received: 04
2026-07-02 15:14:30.386 - debug: kecontact.0 (10200) Sent "report 105" to 192.168.30.15:7090
2026-07-02 15:14:30.388 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "105",
"Session ID": 339,
"Curr HW": 20000,
"E start": 76086393,
"E pres": 187410,
"started[s]": 1782641979,
"ended[s]": 1782652041,
"started": "2026-06-28 10:19:39.000",
"ended": "2026-06-28 13:07:21.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "d1b8bd0d000000000000",
"Serial": "20296767",
"Sec": 2762358
}
"
2026-07-02 15:14:30.388 - debug: kecontact.0 (10200) History ID received: 05
2026-07-02 15:14:30.685 - debug: kecontact.0 (10200) Sent "report 106" to 192.168.30.15:7090
2026-07-02 15:14:30.687 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "106",
"Session ID": 338,
"Curr HW": 20000,
"E start": 75846126,
"E pres": 240267,
"started[s]": 1782453568,
"ended[s]": 1782466745,
"started": "2026-06-26 05:59:28.000",
"ended": "2026-06-26 09:39:05.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "abff8202000000000000",
"Serial": "20296767",
"Sec": 2762358
}
"
2026-07-02 15:14:30.688 - debug: kecontact.0 (10200) History ID received: 06
2026-07-02 15:14:30.986 - debug: kecontact.0 (10200) Sent "report 107" to 192.168.30.15:7090
2026-07-02 15:14:30.987 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "107",
"Session ID": 337,
"Curr HW": 20000,
"E start": 75745419,
"E pres": 100707,
"started[s]": 1782395794,
"ended[s]": 1782452402,
"started": "2026-06-25 13:56:34.000",
"ended": "2026-06-26 05:40:02.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "494c117f000000000000",
"Serial": "20296767",
"Sec": 2762359
}
"
2026-07-02 15:14:30.987 - debug: kecontact.0 (10200) History ID received: 07
2026-07-02 15:14:31.286 - debug: kecontact.0 (10200) Sent "report 108" to 192.168.30.15:7090
2026-07-02 15:14:31.290 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "108",
"Session ID": 336,
"Curr HW": 20000,
"E start": 75723924,
"E pres": 21495,
"started[s]": 1782314246,
"ended[s]": 1782365702,
"started": "2026-06-24 15:17:26.000",
"ended": "2026-06-25 05:35:02.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "e7f4347a000000000000",
"Serial": "20296767",
"Sec": 2762359
}
"
2026-07-02 15:14:31.290 - debug: kecontact.0 (10200) History ID received: 08
2026-07-02 15:14:31.587 - debug: kecontact.0 (10200) Sent "report 109" to 192.168.30.15:7090
2026-07-02 15:14:31.588 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "109",
"Session ID": 335,
"Curr HW": 20000,
"E start": 75678299,
"E pres": 45625,
"started[s]": 1782228285,
"ended[s]": 1782235851,
"started": "2026-06-23 15:24:45.000",
"ended": "2026-06-23 17:30:51.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "bf481575000000000000",
"Serial": "20296767",
"Sec": 2762359
}
"
2026-07-02 15:14:31.589 - debug: kecontact.0 (10200) History ID received: 09
2026-07-02 15:14:31.888 - debug: kecontact.0 (10200) Sent "report 110" to 192.168.30.15:7090
2026-07-02 15:14:31.890 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "110",
"Session ID": 334,
"Curr HW": 20000,
"E start": 75617755,
"E pres": 60544,
"started[s]": 1782125470,
"ended[s]": 1782131565,
"started": "2026-06-22 10:51:10.000",
"ended": "2026-06-22 12:32:45.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "1da1f46e000000000000",
"Serial": "20296767",
"Sec": 2762360
}
"
2026-07-02 15:14:31.890 - debug: kecontact.0 (10200) History ID received: 10
2026-07-02 15:14:32.189 - debug: kecontact.0 (10200) Sent "report 111" to 192.168.30.15:7090
2026-07-02 15:14:32.190 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "111",
"Session ID": 333,
"Curr HW": 20000,
"E start": 75502824,
"E pres": 114931,
"started[s]": 1782119223,
"ended[s]": 1782124408,
"started": "2026-06-22 09:07:03.000",
"ended": "2026-06-22 10:33:28.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "dc02956e000000000000",
"Serial": "20296767",
"Sec": 2762360
}
"
2026-07-02 15:14:32.190 - debug: kecontact.0 (10200) History ID received: 11
2026-07-02 15:14:32.490 - debug: kecontact.0 (10200) Sent "report 112" to 192.168.30.15:7090
2026-07-02 15:14:32.491 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "112",
"Session ID": 332,
"Curr HW": 20000,
"E start": 75438252,
"E pres": 64572,
"started[s]": 1781870757,
"ended[s]": 1781884249,
"started": "2026-06-19 12:05:57.000",
"ended": "2026-06-19 15:50:49.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "5bdbc55f000000000000",
"Serial": "20296767",
"Sec": 2762360
}
"
2026-07-02 15:14:32.491 - debug: kecontact.0 (10200) History ID received: 12
2026-07-02 15:14:32.790 - debug: kecontact.0 (10200) Sent "report 113" to 192.168.30.15:7090
2026-07-02 15:14:32.791 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "113",
"Session ID": 331,
"Curr HW": 20000,
"E start": 75305429,
"E pres": 132823,
"started[s]": 1781862832,
"ended[s]": 1781870507,
"started": "2026-06-19 09:53:52.000",
"ended": "2026-06-19 12:01:47.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "2c184d5f000000000000",
"Serial": "20296767",
"Sec": 2762360
}
"
2026-07-02 15:14:32.791 - debug: kecontact.0 (10200) History ID received: 13
2026-07-02 15:14:33.090 - debug: kecontact.0 (10200) Sent "report 114" to 192.168.30.15:7090
2026-07-02 15:14:33.092 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "114",
"Session ID": 330,
"Curr HW": 20000,
"E start": 75158652,
"E pres": 146777,
"started[s]": 1781854155,
"ended[s]": 1781860963,
"started": "2026-06-19 07:29:15.000",
"ended": "2026-06-19 09:22:43.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "0288c85e000000000000",
"Serial": "20296767",
"Sec": 2762361
}
"
2026-07-02 15:14:33.092 - debug: kecontact.0 (10200) History ID received: 14
2026-07-02 15:14:33.390 - debug: kecontact.0 (10200) Sent "report 115" to 192.168.30.15:7090
2026-07-02 15:14:33.392 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "115",
"Session ID": 329,
"Curr HW": 20000,
"E start": 75112456,
"E pres": 46196,
"started[s]": 1781849665,
"ended[s]": 1781851789,
"started": "2026-06-19 06:14:25.000",
"ended": "2026-06-19 06:49:49.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "4f2b845e000000000000",
"Serial": "20296767",
"Sec": 2762361
}
"
2026-07-02 15:14:33.392 - debug: kecontact.0 (10200) History ID received: 15
2026-07-02 15:14:33.690 - debug: kecontact.0 (10200) Sent "report 116" to 192.168.30.15:7090
2026-07-02 15:14:33.692 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "116",
"Session ID": 328,
"Curr HW": 20000,
"E start": 75070448,
"E pres": 42008,
"started[s]": 1781796520,
"ended[s]": 1781847260,
"started": "2026-06-18 15:28:40.000",
"ended": "2026-06-19 05:34:20.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "0607595b000000000000",
"Serial": "20296767",
"Sec": 2762361
}
"
2026-07-02 15:14:33.692 - debug: kecontact.0 (10200) History ID received: 16
2026-07-02 15:14:33.808 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{"E pres": 112864}"
2026-07-02 15:14:33.991 - debug: kecontact.0 (10200) Sent "report 117" to 192.168.30.15:7090
2026-07-02 15:14:33.993 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "117",
"Session ID": 327,
"Curr HW": 20000,
"E start": 74721562,
"E pres": 348886,
"started[s]": 1781342575,
"ended[s]": 1781424369,
"started": "2026-06-13 09:22:55.000",
"ended": "2026-06-14 08:06:09.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "54644a40000000000000",
"Serial": "20296767",
"Sec": 2762362
}
"
2026-07-02 15:14:33.993 - debug: kecontact.0 (10200) History ID received: 17
2026-07-02 15:14:34.291 - debug: kecontact.0 (10200) Sent "report 118" to 192.168.30.15:7090
2026-07-02 15:14:34.292 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "118",
"Session ID": 326,
"Curr HW": 20000,
"E start": 74647534,
"E pres": 74028,
"started[s]": 1780918479,
"ended[s]": 1780921629,
"started": "2026-06-08 11:34:39.000",
"ended": "2026-06-08 12:27:09.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "75380327000000000000",
"Serial": "20296767",
"Sec": 2762362
}
"
2026-07-02 15:14:34.292 - debug: kecontact.0 (10200) History ID received: 18
2026-07-02 15:14:34.591 - debug: kecontact.0 (10200) Sent "report 119" to 192.168.30.15:7090
2026-07-02 15:14:34.593 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "119",
"Session ID": 325,
"Curr HW": 20000,
"E start": 74571408,
"E pres": 76126,
"started[s]": 1780742082,
"ended[s]": 1780757084,
"started": "2026-06-06 10:34:42.000",
"ended": "2026-06-06 14:44:44.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "679d7f1c000000000000",
"Serial": "20296767",
"Sec": 2762362
}
"
2026-07-02 15:14:34.593 - debug: kecontact.0 (10200) History ID received: 19
2026-07-02 15:14:34.891 - debug: kecontact.0 (10200) Sent "report 120" to 192.168.30.15:7090
2026-07-02 15:14:34.893 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "120",
"Session ID": 324,
"Curr HW": 20000,
"E start": 74398266,
"E pres": 173142,
"started[s]": 1780568906,
"ended[s]": 1780664178,
"started": "2026-06-04 10:28:26.000",
"ended": "2026-06-05 12:56:18.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "08592d12000000000000",
"Serial": "20296767",
"Sec": 2762363
}
"
2026-07-02 15:14:34.893 - debug: kecontact.0 (10200) History ID received: 20
2026-07-02 15:14:35.191 - debug: kecontact.0 (10200) Sent "report 121" to 192.168.30.15:7090
2026-07-02 15:14:35.193 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "121",
"Session ID": 323,
"Curr HW": 20000,
"E start": 74398266,
"E pres": 0,
"started[s]": 1780568855,
"ended[s]": 1780568865,
"started": "2026-06-04 10:27:35.000",
"ended": "2026-06-04 10:27:45.000",
"reason": 4,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "498f2c12000000000000",
"Serial": "20296767",
"Sec": 2762363
}
"
2026-07-02 15:14:35.193 - debug: kecontact.0 (10200) History ID received: 21
2026-07-02 15:14:35.491 - debug: kecontact.0 (10200) Sent "report 122" to 192.168.30.15:7090
2026-07-02 15:14:35.493 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "122",
"Session ID": 322,
"Curr HW": 20000,
"E start": 74286527,
"E pres": 111739,
"started[s]": 1780560900,
"ended[s]": 1780565713,
"started": "2026-06-04 08:15:00.000",
"ended": "2026-06-04 09:35:13.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "bb0f577e000000000000",
"Serial": "20296767",
"Sec": 2762363
}
"
2026-07-02 15:14:35.493 - debug: kecontact.0 (10200) History ID received: 22
2026-07-02 15:14:35.791 - debug: kecontact.0 (10200) Sent "report 123" to 192.168.30.15:7090
2026-07-02 15:14:35.793 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "123",
"Session ID": 321,
"Curr HW": 20000,
"E start": 74238984,
"E pres": 47543,
"started[s]": 1780225278,
"ended[s]": 1780235329,
"started": "2026-05-31 11:01:18.000",
"ended": "2026-05-31 13:48:49.000",
"reason": 5,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "d3e0b17d000000000000",
"Serial": "20296767",
"Sec": 2762364
}
"
2026-07-02 15:14:35.793 - debug: kecontact.0 (10200) History ID received: 23
2026-07-02 15:14:36.091 - debug: kecontact.0 (10200) Sent "report 124" to 192.168.30.15:7090
2026-07-02 15:14:36.093 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "124",
"Session ID": 320,
"Curr HW": 20000,
"E start": 74172492,
"E pres": 66492,
"started[s]": 1780141454,
"ended[s]": 1780165601,
"started": "2026-05-30 11:44:14.000",
"ended": "2026-05-30 18:26:41.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "20f3b278000000000000",
"Serial": "20296767",
"Sec": 2762364
}
"
2026-07-02 15:14:36.094 - debug: kecontact.0 (10200) History ID received: 24
2026-07-02 15:14:36.392 - debug: kecontact.0 (10200) Sent "report 125" to 192.168.30.15:7090
2026-07-02 15:14:36.393 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "125",
"Session ID": 319,
"Curr HW": 20000,
"E start": 74162019,
"E pres": 10473,
"started[s]": 1780139321,
"ended[s]": 1780140591,
"started": "2026-05-30 11:08:41.000",
"ended": "2026-05-30 11:29:51.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "851b9278000000000000",
"Serial": "20296767",
"Sec": 2762364
}
"
2026-07-02 15:14:36.394 - debug: kecontact.0 (10200) History ID received: 25
2026-07-02 15:14:36.692 - debug: kecontact.0 (10200) Sent "report 126" to 192.168.30.15:7090
2026-07-02 15:14:36.694 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "126",
"Session ID": 318,
"Curr HW": 20000,
"E start": 74088206,
"E pres": 73813,
"started[s]": 1780046021,
"ended[s]": 1780052998,
"started": "2026-05-29 09:13:41.000",
"ended": "2026-05-29 11:09:58.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "268f0273000000000000",
"Serial": "20296767",
"Sec": 2762364
}
"
2026-07-02 15:14:36.694 - debug: kecontact.0 (10200) History ID received: 26
2026-07-02 15:14:36.992 - debug: kecontact.0 (10200) Sent "report 127" to 192.168.30.15:7090
2026-07-02 15:14:36.994 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "127",
"Session ID": 317,
"Curr HW": 20000,
"E start": 73959595,
"E pres": 128611,
"started[s]": 1780039593,
"ended[s]": 1780044748,
"started": "2026-05-29 07:26:33.000",
"ended": "2026-05-29 08:52:28.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "8460a072000000000000",
"Serial": "20296767",
"Sec": 2762365
}
"
2026-07-02 15:14:36.994 - debug: kecontact.0 (10200) History ID received: 27
2026-07-02 15:14:37.294 - debug: kecontact.0 (10200) Sent "report 128" to 192.168.30.15:7090
2026-07-02 15:14:37.296 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "128",
"Session ID": 316,
"Curr HW": 20000,
"E start": 73941794,
"E pres": 17801,
"started[s]": 1779979079,
"ended[s]": 1779980122,
"started": "2026-05-28 14:37:59.000",
"ended": "2026-05-28 14:55:22.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "a82a056f000000000000",
"Serial": "20296767",
"Sec": 2762365
}
"
2026-07-02 15:14:37.296 - debug: kecontact.0 (10200) History ID received: 28
2026-07-02 15:14:37.594 - debug: kecontact.0 (10200) Sent "report 129" to 192.168.30.15:7090
2026-07-02 15:14:37.596 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "129",
"Session ID": 315,
"Curr HW": 20000,
"E start": 73894085,
"E pres": 47709,
"started[s]": 1779895467,
"ended[s]": 1779947231,
"started": "2026-05-27 15:24:27.000",
"ended": "2026-05-28 05:47:11.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "bc2d096a000000000000",
"Serial": "20296767",
"Sec": 2762365
}
"
2026-07-02 15:14:37.596 - debug: kecontact.0 (10200) History ID received: 29
2026-07-02 15:14:37.897 - debug: kecontact.0 (10200) Sent "report 130" to 192.168.30.15:7090
2026-07-02 15:14:37.899 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "130",
"Session ID": 314,
"Curr HW": 20000,
"E start": 73886143,
"E pres": 7942,
"started[s]": 1779860657,
"ended[s]": 1779862939,
"started": "2026-05-27 05:44:17.000",
"ended": "2026-05-27 06:22:19.000",
"reason": 1,
"timeQ": 3,
"RFID tag": "f6c4c58600000000",
"RFID class": "560df667000000000000",
"Serial": "20296767",
"Sec": 2762366
}
"
2026-07-02 15:14:37.899 - debug: kecontact.0 (10200) History ID received: 30
2026-07-02 15:14:37.987 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{"E pres": 112963}"
2026-07-02 15:14:38.198 - debug: kecontact.0 (10200) Sent "report 2" to 192.168.30.15:7090
2026-07-02 15:14:38.200 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "2",
"State": 3,
"Error1": 0,
"Error2": 0,
"Plug": 7,
"AuthON": 1,
"Authreq": 0,
"Enable sys": 1,
"Enable user": 1,
"Max curr": 12500,
"Max curr %": 208,
"Curr HW": 20000,
"Curr user": 12500,
"Curr FS": 0,
"Tmo FS": 0,
"Curr timer": 12500,
"Tmo CT": 0,
"Setenergy": 0,
"Output": 0,
"Input": 0,
"X2 phaseSwitch source": 0,
"X2 phaseSwitch": 0,
"Serial": "20296767",
"Sec": 2762366
}
"
2026-07-02 15:14:38.213 - info: semp.0 (9778) Keba KeContact P30X: Keba KeContact P30X wallbox plug connected true
2026-07-02 15:14:38.498 - debug: kecontact.0 (10200) Sent "report 3" to 192.168.30.15:7090
2026-07-02 15:14:38.499 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "3",
"U1": 232,
"U2": 237,
"U3": 235,
"I1": 11988,
"I2": 12053,
"I3": 12090,
"P": 8479473,
"PF": 998,
"E pres": 112973,
"E total": 76662712,
"Serial": "20296767",
"Sec": 2762366
}
"
2026-07-02 15:14:38.525 - debug: kecontact.0 (10200) current max current is 20000
2026-07-02 15:14:38.526 - debug: kecontact.0 (10200) Available surplus: 8361.543
2026-07-02 15:14:38.526 - debug: kecontact.0 (10200) pvAutomaticsActive: true, vehicleIsPlugged: true
2026-07-02 15:14:38.527 - debug: kecontact.0 (10200) power: 8361.543 - 0 / voltage: 230 * 1000 / delta: 500 / phases: 3 * delta = 12118.178260869565
2026-07-02 15:14:38.527 - debug: kecontact.0 (10200) first calculation for current is 12000
2026-07-02 15:14:38.528 - debug: kecontact.0 (10200) authTimestamp is object with value Thu Jul 02 2026 13:57:22 GMT+0200 (Mitteleuropäische Sommerzeit), time diff 4636526
2026-07-02 15:14:38.529 - debug: kecontact.0 (10200) curr is 12000, minCurrent 6000, mintime = 60000
2026-07-02 15:14:38.529 - debug: kecontact.0 (10200) wallbox set to charging maximum of 12000 mA
2026-07-02 15:14:38.530 - info: kecontact.0 (10200) regulate wallbox from 12500 to 12000mA
2026-07-02 15:14:38.798 - debug: kecontact.0 (10200) Sent "currtime 12000 1" to 192.168.30.15:7090
2026-07-02 15:14:38.799 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "TCH-OK :done
"
2026-07-02 15:14:38.799 - debug: kecontact.0 (10200) Received TCH-OK :done
2026-07-02 15:14:39.098 - debug: kecontact.0 (10200) Sent "report 100" to 192.168.30.15:7090
2026-07-02 15:14:39.100 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "100",
"Session ID": 343,
"Curr HW": 20000,
"E start": 76549739,
"E pres": 112987,
"started[s]": 1782993418,
"ended[s]": 0,
"started": "2026-07-02 11:56:58.000",
"ended": "0",
"reason": 5,
"timeQ": 0,
"RFID tag": "f6c4c58600000000",
"RFID class": "cc4db022000000000000",
"Serial": "20296767",
"Sec": 2762367
}
"
2026-07-02 15:14:39.100 - debug: kecontact.0 (10200) History ID received: 00
2026-07-02 15:14:42.168 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{"E pres": 113061}"
2026-07-02 15:14:43.884 - debug: kecontact.0 (10200) Sent "report 2" to 192.168.30.15:7090
2026-07-02 15:14:43.886 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "2",
"State": 3,
"Error1": 0,
"Error2": 0,
"Plug": 7,
"AuthON": 1,
"Authreq": 0,
"Enable sys": 1,
"Enable user": 1,
"Max curr": 12500,
"Max curr %": 208,
"Curr HW": 20000,
"Curr user": 12000,
"Curr FS": 0,
"Tmo FS": 0,
"Curr timer": 12000,
"Tmo CT": 0,
"Setenergy": 0,
"Output": 0,
"Input": 0,
"X2 phaseSwitch source": 0,
"X2 phaseSwitch": 0,
"Serial": "20296767",
"Sec": 2762372
}
"
2026-07-02 15:14:43.902 - info: semp.0 (9778) Keba KeContact P30X: Keba KeContact P30X wallbox plug connected true
2026-07-02 15:14:44.185 - debug: kecontact.0 (10200) Sent "report 3" to 192.168.30.15:7090
2026-07-02 15:14:44.186 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "3",
"U1": 232,
"U2": 236,
"U3": 234,
"I1": 12023,
"I2": 12084,
"I3": 12122,
"P": 8486061,
"PF": 997,
"E pres": 113106,
"E total": 76662845,
"Serial": "20296767",
"Sec": 2762372
}
"
2026-07-02 15:14:44.217 - debug: kecontact.0 (10200) current max current is 20000
2026-07-02 15:14:44.218 - debug: kecontact.0 (10200) Available surplus: 7930.181
2026-07-02 15:14:44.485 - debug: kecontact.0 (10200) Sent "report 100" to 192.168.30.15:7090
2026-07-02 15:14:44.487 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "100",
"Session ID": 343,
"Curr HW": 20000,
"E start": 76549739,
"E pres": 113116,
"started[s]": 1782993418,
"ended[s]": 0,
"started": "2026-07-02 11:56:58.000",
"ended": "0",
"reason": 5,
"timeQ": 0,
"RFID tag": "f6c4c58600000000",
"RFID class": "cc4db022000000000000",
"Serial": "20296767",
"Sec": 2762372
}
"
2026-07-02 15:14:44.488 - debug: kecontact.0 (10200) History ID received: 00
2026-07-02 15:14:45.928 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{"Max curr": 12000}"
2026-07-02 15:14:46.555 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{"E pres": 113165}"
2026-07-02 15:14:50.735 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{"E pres": 113263}"
2026-07-02 15:14:54.916 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{"E pres": 113362}"
2026-07-02 15:14:57.225 - info: semp.0 (9778) State value to set for "semp.0.Devices.Keba KeContact P30X.TimeFrames.1.RemainingMaxEnergy" has to be type "number" but received type "string"
2026-07-02 15:14:58.885 - debug: kecontact.0 (10200) Sent "report 2" to 192.168.30.15:7090
2026-07-02 15:14:58.887 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "2",
"State": 3,
"Error1": 0,
"Error2": 0,
"Plug": 7,
"AuthON": 1,
"Authreq": 0,
"Enable sys": 1,
"Enable user": 1,
"Max curr": 12000,
"Max curr %": 200,
"Curr HW": 20000,
"Curr user": 12000,
"Curr FS": 0,
"Tmo FS": 0,
"Curr timer": 12000,
"Tmo CT": 0,
"Setenergy": 0,
"Output": 0,
"Input": 0,
"X2 phaseSwitch source": 0,
"X2 phaseSwitch": 0,
"Serial": "20296767",
"Sec": 2762387
}
"
2026-07-02 15:14:58.901 - info: semp.0 (9778) Keba KeContact P30X: Keba KeContact P30X wallbox plug connected true
2026-07-02 15:14:59.093 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{"E pres": 113461}"
2026-07-02 15:14:59.185 - debug: kecontact.0 (10200) Sent "report 3" to 192.168.30.15:7090
2026-07-02 15:14:59.186 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "3",
"U1": 233,
"U2": 236,
"U3": 235,
"I1": 12042,
"I2": 12096,
"I3": 12152,
"P": 8519545,
"PF": 999,
"E pres": 113461,
"E total": 76663200,
"Serial": "20296767",
"Sec": 2762387
}
"
2026-07-02 15:14:59.213 - debug: kecontact.0 (10200) current max current is 20000
2026-07-02 15:14:59.215 - debug: kecontact.0 (10200) Available surplus: 7908.775
2026-07-02 15:14:59.486 - debug: kecontact.0 (10200) Sent "report 100" to 192.168.30.15:7090
2026-07-02 15:14:59.487 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "100",
"Session ID": 343,
"Curr HW": 20000,
"E start": 76549739,
"E pres": 113466,
"started[s]": 1782993418,
"ended[s]": 0,
"started": "2026-07-02 11:56:58.000",
"ended": "0",
"reason": 5,
"timeQ": 0,
"RFID tag": "f6c4c58600000000",
"RFID class": "cc4db022000000000000",
"Serial": "20296767",
"Sec": 2762387
}
"
2026-07-02 15:14:59.487 - debug: kecontact.0 (10200) History ID received: 00
2026-07-02 15:15:00.073 - info: javascript.0 (568) script.js.Pool.Pool_Dosierscript_PH_+_Chlor-V2: Chlor dosierung Start
2026-07-02 15:15:03.482 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{"E pres": 113564}"
2026-07-02 15:15:07.662 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{"E pres": 113663}"
2026-07-02 15:15:09.934 - info: kecontact.0 (10200) change additional power from grid consumption from 100 to -500
2026-07-02 15:15:09.935 - debug: kecontact.0 (10200) set automatic.addPower to -500
2026-07-02 15:15:11.843 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{"E pres": 113761}"
2026-07-02 15:15:13.885 - debug: kecontact.0 (10200) Sent "report 2" to 192.168.30.15:7090
2026-07-02 15:15:13.887 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "2",
"State": 3,
"Error1": 0,
"Error2": 0,
"Plug": 7,
"AuthON": 1,
"Authreq": 0,
"Enable sys": 1,
"Enable user": 1,
"Max curr": 12000,
"Max curr %": 200,
"Curr HW": 20000,
"Curr user": 12000,
"Curr FS": 0,
"Tmo FS": 0,
"Curr timer": 12000,
"Tmo CT": 0,
"Setenergy": 0,
"Output": 0,
"Input": 0,
"X2 phaseSwitch source": 0,
"X2 phaseSwitch": 0,
"Serial": "20296767",
"Sec": 2762402
}
"
2026-07-02 15:15:13.897 - info: semp.0 (9778) Keba KeContact P30X: Keba KeContact P30X wallbox plug connected true
2026-07-02 15:15:14.186 - debug: kecontact.0 (10200) Sent "report 3" to 192.168.30.15:7090
2026-07-02 15:15:14.187 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "3",
"U1": 233,
"U2": 236,
"U3": 235,
"I1": 12020,
"I2": 12064,
"I3": 12120,
"P": 8499005,
"PF": 998,
"E pres": 113816,
"E total": 76663555,
"Serial": "20296767",
"Sec": 2762402
}
"
2026-07-02 15:15:14.217 - debug: kecontact.0 (10200) current max current is 20000
2026-07-02 15:15:14.217 - debug: kecontact.0 (10200) Available surplus: 7799.844999999999
2026-07-02 15:15:14.218 - debug: kecontact.0 (10200) pvAutomaticsActive: true, vehicleIsPlugged: true
2026-07-02 15:15:14.218 - debug: kecontact.0 (10200) power: 7799.844999999999 - 500 / voltage: 230 * 1000 / delta: 500 / phases: 3 * delta = 12028.760869565216
2026-07-02 15:15:14.218 - debug: kecontact.0 (10200) first calculation for current is 12000
2026-07-02 15:15:14.219 - debug: kecontact.0 (10200) authTimestamp is object with value Thu Jul 02 2026 13:57:22 GMT+0200 (Mitteleuropäische Sommerzeit), time diff 4672218
2026-07-02 15:15:14.219 - debug: kecontact.0 (10200) curr is 12000, minCurrent 6000, mintime = 60000
2026-07-02 15:15:14.219 - debug: kecontact.0 (10200) wallbox set to charging maximum of 12000 mA
2026-07-02 15:15:14.486 - debug: kecontact.0 (10200) Sent "report 100" to 192.168.30.15:7090
2026-07-02 15:15:14.488 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "100",
"Session ID": 343,
"Curr HW": 20000,
"E start": 76549739,
"E pres": 113820,
"started[s]": 1782993418,
"ended[s]": 0,
"started": "2026-07-02 11:56:58.000",
"ended": "0",
"reason": 5,
"timeQ": 0,
"RFID tag": "f6c4c58600000000",
"RFID class": "cc4db022000000000000",
"Serial": "20296767",
"Sec": 2762402
}
"
2026-07-02 15:15:14.489 - debug: kecontact.0 (10200) History ID received: 00
2026-07-02 15:15:16.232 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{"E pres": 113865}"
2026-07-02 15:15:20.412 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{"E pres": 113964}"
2026-07-02 15:15:24.592 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{"E pres": 114062}"
2026-07-02 15:15:28.772 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{"E pres": 114161}"
2026-07-02 15:15:28.885 - debug: kecontact.0 (10200) Sent "report 2" to 192.168.30.15:7090
2026-07-02 15:15:28.887 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "2",
"State": 3,
"Error1": 0,
"Error2": 0,
"Plug": 7,
"AuthON": 1,
"Authreq": 0,
"Enable sys": 1,
"Enable user": 1,
"Max curr": 12000,
"Max curr %": 200,
"Curr HW": 20000,
"Curr user": 12000,
"Curr FS": 0,
"Tmo FS": 0,
"Curr timer": 12000,
"Tmo CT": 0,
"Setenergy": 0,
"Output": 0,
"Input": 0,
"X2 phaseSwitch source": 0,
"X2 phaseSwitch": 0,
"Serial": "20296767",
"Sec": 2762417
}
"
2026-07-02 15:15:28.898 - info: semp.0 (9778) Keba KeContact P30X: Keba KeContact P30X wallbox plug connected true
2026-07-02 15:15:29.185 - debug: kecontact.0 (10200) Sent "report 3" to 192.168.30.15:7090
2026-07-02 15:15:29.187 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "3",
"U1": 233,
"U2": 236,
"U3": 235,
"I1": 12039,
"I2": 12085,
"I3": 12127,
"P": 8502029,
"PF": 998,
"E pres": 114171,
"E total": 76663910,
"Serial": "20296767",
"Sec": 2762417
}
"
2026-07-02 15:15:29.219 - debug: kecontact.0 (10200) current max current is 20000
2026-07-02 15:15:29.220 - debug: kecontact.0 (10200) Available surplus: 7770.459000000001
2026-07-02 15:15:29.485 - debug: kecontact.0 (10200) Sent "report 100" to 192.168.30.15:7090
2026-07-02 15:15:29.486 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{
"ID": "100",
"Session ID": 343,
"Curr HW": 20000,
"E start": 76549739,
"E pres": 114176,
"started[s]": 1782993418,
"ended[s]": 0,
"started": "2026-07-02 11:56:58.000",
"ended": "0",
"reason": 5,
"timeQ": 0,
"RFID tag": "f6c4c58600000000",
"RFID class": "cc4db022000000000000",
"Serial": "20296767",
"Sec": 2762417
}
"
2026-07-02 15:15:29.487 - debug: kecontact.0 (10200) History ID received: 00
2026-07-02 15:15:33.161 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{"E pres": 114264}"
2026-07-02 15:15:37.341 - debug: kecontact.0 (10200) UDP datagram from 192.168.30.15:7090: "{"E pres": 1143

Was mir ebenfalls aufgefallen ist:

Bei jedem Adapter Neustart wird der addPower Wert wieder auf 100W zurückgesetzt.

[Qlink]

@sneak-l8

Update: Ich glaube ich habe die Werte falsch verstanden und war zu ungeduldig.
Ich dachte -500 bei addPower ergibt effektiv den 500W Puffer.

Allerdings habe ich den 500W Puffer wenn ich 500 als Wert eingebe, wie ich nun mittlerweile nach einigen weiteren Tests festgestellt habe.
Scheint also soweit ganz gut zu funktionieren

Ich werds weiter beobachten.

[FernetMenta]

@Qlink sagte:

Allerdings habe ich den 500W Puffer wenn ich 500 als Wert eingebe, wie ich nun mittlerweile nach einigen weiteren Tests festgestellt habe.

Das wäre schlecht, weil es bestehende Funktionalität brechen würde. Bist du sicher? 500W bei addPower sollten zusätzliche 500W aus dem Netz bewirken.

[Sneak-L8]

@Qlink sagte:

@sneak-l8

Hier das Log:

Bitte die Logs immer als Spoiler anlegen. Sonst wird der Beitrag zu groß.

Im Log steht:

power: 8361.543 - 0

Das heißt, dass die neue Version zieht, aber bisher kein zusätzlicher Überschuss verlangt wird.

Was mir ebenfalls aufgefallen ist:

Bei jedem Adapter Neustart wird der addPower Wert wieder auf 100W zurückgesetzt.

Und das ist schon die Antwort: Du hast in den Einstellungen auch ein addPower. Der Wert wird bei Adapterstart immer in den state addPower geschrieben. Wenn das nicht gewünscht ist, dann setze dort in den Einstellungen die 0.

[Qlink]

@sneak-l8
addPower in den Einstellungen hab ich auf 0 gesetzt und addPower unter Objekte auf 750

Trotzdem ergibt es nicht den gewünschten Effekt.

Ich würde gerne den leichten Netzbezug den die Regelung des Adapters meistens erzeugt in eine leichte Einspeisung verwandeln.

Ich hätte erwartet, dass wenn ich addPower 750 eingebe, es sich eine Einspeisung von 400 - 500W ergeben sollte... dem ist aber nicht so ?

Beste Grüße

[Sneak-L8]

Wenn Du +750 angibst, dann werden bis zu 750W dauerhaft aus dem Netz entnommen, um den Ladevorgang (mit minimaler Stromstärke) aufrecht zu erhalten. Bei großer PV-Produktion ist das also wirkungslos.
Wenn Du es umgekehrt willst und ein Überschuss verbleiben soll, dann müsstest Du -750W angeben. Dann werden einfach 750W vom aktuellen Leistungsfluss (egal ob derzeit positiv oder negativ) 750W abgezogen und dann die Berechnung zum Ladeüberschuss durchgeführt.

[Qlink]

@sneak-l8

das kann ich so im Verhalten nicht bestätigen.
Ich nehme an du redest von addPower unter Objekte richtig ?

Wenn ich unter addPower unter Objekte einen Wert von -750 eingebe, dann schauts bei mir so aus:

Wenn ich unter addPower unter Objekte einen Wert von 750 eingebe, dann schauts so aus: