NEWS
[Frage] Realisierung Adapter UDP Keba Wallbox
-
@christian-kohlöffel So, hab mir jetzt mal Deinen PR angeschaut.
Was mir auffällt:
- Zeile 70: Die minimale Zeit zum Umschalten ist null. Setzt du die absichtlich erst beim Init? Ein cont ... = 300 würde doch reichen. Logging der Info sehe ich nicht für notwnedig, da es ja ein fester Wert ist.
- Zeile 1026: guter Gedanke, die aktuelle Stromstärke nur bei state ==3 (charging) zu holen und nicht über disabled zu prüfen => alten Code dan aber löschen und nicht kommentieren
- Zeile 1058: kleiner Tippfehler values => value
- Zeile 1065: auch wieder bitte alten Code raus
- Zeile 1206: alten Code bitte raus
- Zeile 1304/1307: die Log-Ausgaben sind eher noch vom Testen, oder?
- Zeile 1372: wenn Du den Wert unbedingt loggen willst, dann solltest Du ihn persistieren. Es könnte sein ,dass im Log ein anderer Wert steht, als der, der von der Funktion zurückgegeben wird, weil genau dazwischen, neue Daten von der Wallbox kamen.
- Zeile 1494/1576/1673: bitte Variable im lowerCamalCase schreiben (kleines s am Anfang)
- Zeile 1495: wenn noch kein Phase-Switch im State vermerkt ist, dann würde ich auch keinen aktuellen Wert setzen. Denn es fand ja kein Switching statt. Ich würde hier einfach false zurückgegeben.
- Zeile 1561 (alt Zeile 1436): warum hast Du da das ausschalten des 1p/3p-Switches deaktiviert? Mir geht es (gerade weil ich einen Öffner einsetze) darum, dass bei Ladepausen der Installationsschütz abgeschaltet wird und somit nicht unnötig daueraktiviert ist.
- Zeile 1673ff: hier wird jetzt nochmals geprüft, wie lange der Phase-Switch zurückliegt. wäre es dann nicht weiter oben obsolet? Ggfs. soltle man das dann in eine zentrale Funktion verlagern, so dass es dann auch für Zeile 1561 passen würde.
Aber insgesamt find ich die Änderung echt gut. Danke dafür!
Noch ne Frage dzu, dass Du die Prüfung auf stateWallBoxDisabled sehr oft entfernt hast: was ist der Hintergrund? Weil current eh null sein sollte, wenn die Wallbox disabled ist?
P.S. Danke fürs Kommentieren der Methoden!
-
@sneak-l8 sagte in [Frage] Realisierung Adapter UDP Keba Wallbox:
Zeile 70: Die minimale Zeit zum Umschalten ist null. Setzt du die absichtlich erst beim Init? Ein cont ... = 300 würde doch reichen. Logging der Info sehe ich nicht für notwnedig, da es ja ein fester Wert ist.
Ja, das hab ich gemacht falls es für andere Wallboxen doch noch andere Werte geben sollte. Könnte man aber auch fix machen
==> Vorschlag das lassen wir so ...@sneak-l8 sagte in [Frage] Realisierung Adapter UDP Keba Wallbox:
Zeile 1561 (alt Zeile 1436): warum hast Du da das ausschalten des 1p/3p-Switches deaktiviert? Mir geht es (gerade weil ich einen Öffner einsetze) darum, dass bei Ladepausen der Installationsschütz abgeschaltet wird und somit nicht unnötig daueraktiviert ist.
Ist aus meiner Sicht nicht nötig, da dies weiter unten, wenn der curr= 0 ist eh auch schon gemacht wird.
Zeile 1664 neu und darunter:
if (curr < getMinCurrent())
Klar, könnte man auch verlagern, hast du eine Vorschlag. Ich verstehe gerade nicht ganz was Dir vorschwebt ....Den Rest habe ich so umgesetzt und auch schon commitet ...
-
@christian-kohlöffel Hey, top! Ja, dassZeile 1561 unnötig ist, istm ir garn icht gleich aufgefallen.
Den anderen Punkt könenn wir auch gerne so lassen. Dann merge ich jetzt mal.
Danach deaktiviere ich mal noch kurz den Firmwre-Check für die c-Series, da er derzeit ja leider nicht mehr funktioniert (siehe Post weiter oben).
Edit: Version ist jetzt bei github -
Danke euch 2!
Ich werde die GH Version mal laden und diese Woche beobachten.
-
@darkiop @christian-kohlöffel Hab nochmal ne Version nachgeschoben, da ich gerade imemr wieder "stop charging for switch of phases" bekam, er aber nie weitermachte...
-
@sneak-l8 Ich lade mir die Version auch gleich mal runter. Morgen früh ist eh wieder laden angesagt ...
-
@christian-kohlöffel Ich hab gerade nochmal einen Fix gemacht. Bei regulateWallbox() hattest du die Ermittlung des oldValues begrenzt auf den Fall ,dass ein Fahrzeug angeschlossen ist. Hier bin ich wieder zurück auf "Wallbox enabled". Denn es geht ja um den Vergleich, um die Ladeleistung einen geänderten Wert hat, der an die Wallbox gesendet werdne muss. Und auch wenn das auto nicht angesteckt ist, kann eine Ladeleistung eingestellt sein, die dann auch erkannt werden muss.
Hatte bei mir sonst den Fall, dass das Fahrzeug beim Anstecken für ein paar Sekunden lädt, obwohl kein ausreichender Überschuss da ist.
-
@sneak-l8 Top Adapter danke!
Ich habe die Firmenwagen Wallbox KC-P30 nun mit der Phasenumschaltung über den X2 Kontakt laufen.
Die bestehende Ladeleistung der Batterie wird dies zum bestehenden Überschuss addiert und bestimmt den Wert Surplus.. soweit ok. Wenn nun die Batterien voll sind wird keine Batterieleistung zum bestehenden Überschuss hinzu addiert da ja keine Ladung vorhanden ist.
Wäre es nicht sinnvoll wenn bei einem SOC über dem eingestellten unteren minimum im Adapter, die maximale Abgabeleistung der Batterie den Überschuss der PV Anlage bis zur maximal mögliche Ladeleistung der Wallbox ergänzt...möglicher weise habe ich auch noch etwas nicht richtig eingestellt.... -
@keksn Da triffst du einen offenen Punkt. Ich hatte weiter oben im Thread mal ein paar Batterie-Ladeszenarien vorgeschlagen. Bisher kann man die Batterie nicht wirklich mit einbinden.
Allerdings wird eine Steuerung abhängig vom SoC (ich denke, Du meinst den des Fahrzeugs und nicht der Batterie?) schwierig. Der SoC kann von der Wallbox nicht ausgelesen werden. Das heißt, es müsste nun der SoC eines bestimmten Fahrzeugs gelesen werden. Es ist aber nirgends prüfbar, ob gerade dieses Fahrzeug gleaden wird oder ein anders (z.B. Gast).
Daher möchte ich diese Abhängigkeit ungern im Adapter implementieren. Ich kann aber die Lademodi als State anlegen. So kann man sie entweder generell über die Einstellungen oder dynamisch (z.B. über ein eigenes Skript, das den SoC berücksichtigt) über einen State regelbar machen. -
@sneak-l8 nein ich meine den SOC der Inverter Batterie. Wenn die Batterie voll geladen ist wäre es gut den Ladevorgang bei Überschussladung auch einzubinden(möglicherweise wahlweise). Um die 100% geladene Batterie zur Abgabe der Energie zu animieren müsste aber der Ladevorgang mit voller Leistung beginnend. Macht das die Regelung jetzt so ?
-
Hi @sneak-l8 , ich hab das Update nun schon mehrere Tage am Laufen und ich habe bisher keine Probleme feststellen können. Also
-
Hallo zusammen,
ich woillte nun das PV Laden einrichten, weiß aber nicht so genau was ich wo ein tragen muss.
Ich möchte einfach nur das wenn ich lade und der Verbrauch mehr als 500 Watt ausm Netz bezträgt, dass der Ladevorgng gestoppt wird.
In
alias.0.strom.stromzaehler.moment_verbrauch
steht der aktuelle Verbrauch in Watt also 1000,2500 oder halt -1500 etc
Aktuell habe ich eine PV Leistung von ca. 3500 Watt
Das Auto lädt mit 5500 Watt
Inkecontact.0.statistics.surplus
steht 2683, müsste hier nicht ein Negativer Wert stehen?
-
weiterhin ist mir aufgefallen, dass wenn ich mein Auto an die Wallbox anschließe und das laden starte dann klappt es, stoppe ich manuell das laden geht es auch, aber wenn ich dann wieder starten will geht das nicht.
kecontact.0.state bleibt auf 5 stehen.auch hat kecontact.0.automatic.pauseWallbox keine Auswirkung das Laden stoppt nicht
-
@malz1902
Der momentan_verbrauch ist positiv, wenn Du Strom aus dem Netz ziehst und negativ, wenn Du Strom einspeist. Richtig?Wenn Du eine nsurplus von 2.683W im Adapter stehen has,t dann sieht das doch ganz gut aus. Die PV liefert 3.500W und der Rest im Haus braucht dan gerade so ca. 900W. Alles plausibel.
Welchen Wallbox-Typ hast Du denn? Und was steht in den Logs?
Das wäre auch für Deine 2. Frage sehr interessant. Denn eigentlich funktionieren die States korrekt.
Beschreibe doch mal, was Du konkret tust. Stoppst Du das Laden über einen State im Adapter, über eine Fahrzeug-App? Was ist das für ein Auto? Sind da vielleicht Probleme mit Überschuss-Laden bekannt?
Und dann gib neben dder Info wann (Uhrzeit) Du was getan hast, das Log dazu. Im Optimalfall im Debug-Modus. Dann kann man sich das Anschauen. Sonst ist das eher ein Rätselraten. -
@sneak-l8 Hab heute wieder den Fehler gehabt, dass die Wallbox nicht abschaltet obwohl die Wallbox von aussen pausiert wurde. Ich hatte noch erinnerung, dass dies genau mit dem von Dir genannten Punkt in Verbindung stand. Dazu sollten wir uns nochmals eine Abfrage einfallen lassen, der das verhindert. Ohne die oben referenziert Änderung hat er noch erkannt, dass er ungewollt weitergeladen hat durch das schalten des X2 Switches ...
-
@christian-kohlöffel hast Du die neuste Version von github im Einsatz?
-
@sneak-l8 said in [Frage] Realisierung Adapter UDP Keba Wallbox:
Der momentan_verbrauch ist positiv, wenn Du Strom aus dem Netz ziehst und negativ, wenn Du Strom einspeist. Richtig?
Ja genau richtig,
@sneak-l8 said in [Frage] Realisierung Adapter UDP Keba Wallbox:
Wenn Du eine nsurplus von 2.683W im Adapter stehen has,t dann sieht das doch ganz gut aus. Die PV liefert 3.500W und der Rest im Haus braucht dan gerade so ca. 900W. Alles plausibel.
Aber sollte die Wallbox dann nicht abschalten, da ja mehr als 1500 Watt aus dem Netz gezogen wird? Oder verssteh ich das falsch?
@sneak-l8 said in [Frage] Realisierung Adapter UDP Keba Wallbox:
Welchen Wallbox-Typ hast Du denn? Und was steht in den Logs?
Keba P90 x-series
@sneak-l8 said in [Frage] Realisierung Adapter UDP Keba Wallbox:
Was ist das für ein Auto?
Auto is ein VW ID4
@sneak-l8 said in [Frage] Realisierung Adapter UDP Keba Wallbox:
Beschreibe doch mal, was Du konkret tust. Stoppst Du das Laden über einen State im Adapter, über eine Fahrzeug-App?
Ich schließe das Kabel der Wallbox ans Auto, geh am PC und setzte im iobroker im state kecontact.0.start meinen RFID Tag, das Laden startet.
Jetzt dachte ich wenn ich kecontact.0.automatic.pauseWallbox von false auf true setze, dann stoppt das Laden, hat aber in diesem Fall nicht funktioniert. Dann habe ich in kecontact.0.stop meinen RFID Tag eingegeben um zu stoppen, auch das ging nicht. Wenn ich über das WebUI der Wallbox gehe und da auf Ladung stoppen klicke unter Aktionen, dann klappt das. kecontact.0.state setzt sich dann auch von 3 was anscheinend laden ist auf 5 was für pausiert steht? Aber ich kann nun das Laden via ioBroker noch direkt in der Ui der Wallbox starten, ich muss bei Aktionen in der WebUI erst auf neu starten klicken, dann setzt sich in iobroker der State kecontact.0.state wie auf 1, erst danach kann ich wieder eine Ladung startenLogs kann ich nachher mal schicken, dann geh ich die Schritte alle nochmal durch
-
2023-10-06 12:20:25.024 - debug: kecontact.0 (392611) UDP datagram from 192.168.188.97:7090: 'TCH-ERR:no need for start kecontact.0 2023-10-06 13:52:29.333 error Error received from wallbox: TCH-ERR:nothing to stop
Das passiert, wenn ich starten bzw stoppen will
So ich habe jetzt das Auto an die Wallbox geschlossen
Noch lädt nichts
Dann habe ich unter kecontact.0.start meine RFID Nummer eingetragen, laden startet kecontact.0.automatic.pauseWallbox steht auf false, kecontact.0.state auf 3.kecontact.0 2023-10-06 11:00:26.458 info vehicle (re)starts to charge
Jetzt habe ich kecontact.0.automatic.pauseWallbox auf true gesetzt:
kecontact.0 2023-10-06 11:01:54.829 info change pause status of wallbox from false to true
Es wird jedoch weiter geladen, kecontact.0.state steht weiterhin auf 3
Auch wenn ich kecontact.0.automatic.pauseWallbox wieder auf false setze steht im Log folgendes aber auch dann wird weiter geladenkecontact.0 2023-10-06 11:03:59.127 info change pause status of wallbox from true to false
Dann habe ich in kecontact.0.stop meinen RFID Tag eingetragen, kecontact.0.state wechselt auf 5, das Laden stoppt, das war um 11:06
Um 11:10:52 habe ich dann nochmal versucht kecontact.0.automatic.pauseWallbox auf true zu setzen, aber auch jetzt startet keine Ladung
kecontact.0.state bleibt auf 5 stehenJetzt habe ich kecontact.0.stop wieder gelöscht
2023-10-06 11:13:17.554 - error: kecontact.0 (371943) Error received from wallbox: TCH-ERR:: wrong parameter count
Danach nochmal kecontact.0.start gespeichert, laden startet wieder
2023-10-06 11:14:07.601 - debug: kecontact.0 (371943) Sent 'start [d7703ef000000000] [d029847f000000000000]' to 192.168.188.97:7090 2023-10-06 11:14:07.602 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: 'TCH-OK :done ' 2023-10-06 11:14:07.602 - debug: kecontact.0 (371943) Received TCH-OK :done 2023-10-06 11:14:08.051 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"Enable sys": 1}' 2023-10-06 11:14:09.034 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"Max curr": 16000}' 2023-10-06 11:14:12.506 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"State": 2}'
kecontact.0.state steht dann wieder auf 3
2023-10-06 10:59:26.052 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 10:59:26.054 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 1, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 1, "Enable sys": 0, "Enable user": 1, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 155476 } ' 2023-10-06 10:59:26.352 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 10:59:26.354 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 107271, "E total": 41137346, "Serial": "22195027", "Sec": 155476 } ' 2023-10-06 10:59:26.405 - debug: kecontact.0 (371943) Available surplus: 5544 2023-10-06 10:59:26.652 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 10:59:26.654 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 107, "Curr HW": 16000, "E start": 41030075, "E pres": 107271, "started[s]": 1696507229, "ended[s]": 1696516717, "started": "2023-10-05 12:00:29.000", "ended": "2023-10-05 14:38:37.000", "reason": 1, "timeQ": 3, "RFID tag": "0d7703ef00000000", "RFID class": "62f7b57f000000000000", "Serial": "22195027", "Sec": 155477 } ' 2023-10-06 10:59:26.655 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 10:59:51.187 - debug: kecontact.0 (371943) Sent 'start [d7703ef000000000] [d029847f000000000000]' to 192.168.188.97:7090 2023-10-06 10:59:51.189 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: 'TCH-OK :done ' 2023-10-06 10:59:51.189 - debug: kecontact.0 (371943) Received TCH-OK :done 2023-10-06 10:59:51.633 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"Enable sys": 1}' 2023-10-06 10:59:52.980 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"Max curr": 16000}' 2023-10-06 10:59:56.052 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 10:59:56.054 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 1, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 0, "Enable sys": 1, "Enable user": 1, "Max curr": 16000, "Max curr %": 266, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 155506 } ' 2023-10-06 10:59:56.307 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"State": 2}' 2023-10-06 10:59:56.352 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 10:59:56.353 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 231, "U2": 231, "U3": 232, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 41137346, "Serial": "22195027", "Sec": 155506 } ' 2023-10-06 10:59:56.452 - debug: kecontact.0 (371943) Available surplus: 5345 2023-10-06 10:59:56.507 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"Max curr": 6000}' 2023-10-06 10:59:56.652 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 10:59:56.653 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 0, "started[s]": 1696582765, "ended[s]": 0, "started": "2023-10-06 08:59:25.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 155507 } ' 2023-10-06 10:59:56.654 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 10:59:58.816 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"State": 3}' 2023-10-06 11:00:00.012 - info: javascript.0 (1762973) script.js.common.speedtest: Speedtest mit Server 29320 gestartet! Der Test dauert zwischen 10 - 20 Sekunden! 2023-10-06 11:00:00.032 - info: javascript.0 (1762973) script.js.strom.zirkulation_on_off: Steckdose ist bereits an - Zirkulation an 2023-10-06 11:00:04.651 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"Max curr": 16000}' 2023-10-06 11:00:05.278 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 56}' 2023-10-06 11:00:11.961 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 156}' 2023-10-06 11:00:16.448 - info: javascript.0 (1762973) script.js.common.speedtest: Speedtest durchgeführt. Ergebnisse: Download: 246.52 MBit/s | Upload: 42.7 MBit/s | Ping: 11.755ms 2023-10-06 11:00:18.437 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 254}' 2023-10-06 11:00:25.121 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 356}' 2023-10-06 11:00:26.052 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:00:26.053 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 3, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 0, "Enable sys": 1, "Enable user": 1, "Max curr": 16000, "Max curr %": 266, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 155536 } ' 2023-10-06 11:00:26.352 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:00:26.353 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 235, "U2": 234, "U3": 234, "I1": 7907, "I2": 8019, "I3": 7948, "P": 5578540, "PF": 994, "E pres": 373, "E total": 41137719, "Serial": "22195027", "Sec": 155536 } ' 2023-10-06 11:00:26.458 - info: kecontact.0 (371943) vehicle (re)starts to charge 2023-10-06 11:00:26.458 - debug: kecontact.0 (371943) Available surplus: 5551.54 2023-10-06 11:00:26.652 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:00:26.653 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 379, "started[s]": 1696582765, "ended[s]": 0, "started": "2023-10-06 08:59:25.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 155537 } ' 2023-10-06 11:00:26.654 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:00:31.385 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 454}' 2023-10-06 11:00:37.861 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 554}' 2023-10-06 11:00:44.335 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 654}' 2023-10-06 11:00:50.808 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 754}' 2023-10-06 11:00:56.052 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:00:56.054 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 3, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 0, "Enable sys": 1, "Enable user": 1, "Max curr": 16000, "Max curr %": 266, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 155566 } ' 2023-10-06 11:00:56.352 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:00:56.354 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 235, "U2": 234, "U3": 234, "I1": 7900, "I2": 8015, "I3": 7960, "P": 5577512, "PF": 994, "E pres": 838, "E total": 41138184, "Serial": "22195027", "Sec": 155566 } ' 2023-10-06 11:00:56.402 - debug: kecontact.0 (371943) Available surplus: 5691.512 2023-10-06 11:00:56.653 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:00:56.655 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 845, "started[s]": 1696582765, "ended[s]": 0, "started": "2023-10-06 08:59:25.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 155567 } ' 2023-10-06 11:00:56.655 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:00:57.282 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 855}' 2023-10-06 11:01:03.757 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 955}' 2023-10-06 11:01:10.232 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 1055}' 2023-10-06 11:01:16.707 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 1155}' 2023-10-06 11:01:23.182 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 1256}' 2023-10-06 11:01:26.052 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:01:26.054 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 3, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 0, "Enable sys": 1, "Enable user": 1, "Max curr": 16000, "Max curr %": 266, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 155596 } ' 2023-10-06 11:01:26.353 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:01:26.354 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 235, "U2": 233, "U3": 235, "I1": 7889, "I2": 8012, "I3": 7934, "P": 5568697, "PF": 994, "E pres": 1304, "E total": 41138650, "Serial": "22195027", "Sec": 155596 } ' 2023-10-06 11:01:26.416 - debug: kecontact.0 (371943) Available surplus: 5506.697 2023-10-06 11:01:26.653 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:01:26.654 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 1307, "started[s]": 1696582765, "ended[s]": 0, "started": "2023-10-06 08:59:25.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 155597 } ' 2023-10-06 11:01:26.654 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:01:29.659 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 1356}' 2023-10-06 11:01:36.136 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 1456}' 2023-10-06 11:01:42.613 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 1557}' 2023-10-06 11:01:48.879 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 1654}' 2023-10-06 11:01:54.829 - info: kecontact.0 (371943) change pause status of wallbox from false to true 2023-10-06 11:01:54.829 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:01:54.831 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 3, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 0, "Enable sys": 1, "Enable user": 1, "Max curr": 16000, "Max curr %": 266, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 155625 } ' 2023-10-06 11:01:55.129 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:01:55.130 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 234, "U2": 233, "U3": 235, "I1": 7929, "I2": 8020, "I3": 7936, "P": 5569891, "PF": 994, "E pres": 1748, "E total": 41139094, "Serial": "22195027", "Sec": 155625 } ' 2023-10-06 11:01:55.177 - debug: kecontact.0 (371943) Available surplus: 5776.891 2023-10-06 11:01:55.356 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 1754}' 2023-10-06 11:01:55.430 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:01:55.431 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 1754, "started[s]": 1696582765, "ended[s]": 0, "started": "2023-10-06 08:59:25.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 155625 } ' 2023-10-06 11:01:55.431 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:01:56.052 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:01:56.054 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 3, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 0, "Enable sys": 1, "Enable user": 1, "Max curr": 16000, "Max curr %": 266, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 155626 } ' 2023-10-06 11:01:56.352 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:01:56.354 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 234, "U2": 233, "U3": 235, "I1": 7942, "I2": 8025, "I3": 7955, "P": 5579952, "PF": 994, "E pres": 1767, "E total": 41139113, "Serial": "22195027", "Sec": 155626 } ' 2023-10-06 11:01:56.396 - debug: kecontact.0 (371943) Available surplus: 5591.952 2023-10-06 11:01:56.653 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:01:56.654 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 1773, "started[s]": 1696582765, "ended[s]": 0, "started": "2023-10-06 08:59:25.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 155627 } ' 2023-10-06 11:01:56.654 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:02:01.829 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 1854}' 2023-10-06 11:02:08.304 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 1954}' 2023-10-06 11:02:14.777 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 2055}' 2023-10-06 11:02:21.252 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 2155}' 2023-10-06 11:02:26.026 - info: javascript.0 (1762973) script.js.strom.zirkulation_on_off: changeStateSteckdoseZirkulation 2023-10-06 11:02:26.026 - info: javascript.0 (1762973) script.js.strom.zirkulation_on_off: Steckdose aus - Zirkulation aus 2023-10-06 11:02:26.052 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:02:26.053 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 3, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 0, "Enable sys": 1, "Enable user": 1, "Max curr": 16000, "Max curr %": 266, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 155656 } ' 2023-10-06 11:02:26.353 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:02:26.354 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 234, "U2": 234, "U3": 234, "I1": 7916, "I2": 8004, "I3": 7951, "P": 5568183, "PF": 994, "E pres": 2233, "E total": 41139579, "Serial": "22195027", "Sec": 155656 } ' 2023-10-06 11:02:26.400 - debug: kecontact.0 (371943) Available surplus: 5480.183 2023-10-06 11:02:26.653 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:02:26.655 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 2236, "started[s]": 1696582765, "ended[s]": 0, "started": "2023-10-06 08:59:25.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 155657 } ' 2023-10-06 11:02:26.655 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:02:27.726 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 2255}' 2023-10-06 11:02:34.205 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 2356}' 2023-10-06 11:02:40.681 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 2456}' 2023-10-06 11:02:47.157 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 2556}' 2023-10-06 11:02:53.634 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 2656}' 2023-10-06 11:02:56.052 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:02:56.054 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 3, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 0, "Enable sys": 1, "Enable user": 1, "Max curr": 16000, "Max curr %": 266, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 155686 } ' 2023-10-06 11:02:56.352 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:02:56.354 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 234, "U2": 234, "U3": 234, "I1": 7831, "I2": 8031, "I3": 7978, "P": 5567567, "PF": 995, "E pres": 2698, "E total": 41140044, "Serial": "22195027", "Sec": 155686 } ' 2023-10-06 11:02:56.414 - debug: kecontact.0 (371943) Available surplus: 5384.567 2023-10-06 11:02:56.652 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:02:56.654 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 2701, "started[s]": 1696582765, "ended[s]": 0, "started": "2023-10-06 08:59:25.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 155687 } ' 2023-10-06 11:02:56.654 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:03:00.108 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 2756}' 2023-10-06 11:03:06.581 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 2856}' 2023-10-06 11:03:13.054 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 2955}' 2023-10-06 11:03:19.533 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 3054}' 2023-10-06 11:03:26.012 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 3154}' 2023-10-06 11:03:26.052 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:03:26.054 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 3, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 0, "Enable sys": 1, "Enable user": 1, "Max curr": 16000, "Max curr %": 266, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 155716 } ' 2023-10-06 11:03:26.352 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:03:26.354 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 234, "U2": 232, "U3": 234, "I1": 7931, "I2": 7905, "I3": 7967, "P": 5535944, "PF": 994, "E pres": 3157, "E total": 41140503, "Serial": "22195027", "Sec": 155716 } ' 2023-10-06 11:03:26.451 - debug: kecontact.0 (371943) Available surplus: 5476.944 2023-10-06 11:03:26.652 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:03:26.653 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 3164, "started[s]": 1696582765, "ended[s]": 0, "started": "2023-10-06 08:59:25.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 155717 } ' 2023-10-06 11:03:26.653 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:03:32.489 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 3254}' 2023-10-06 11:03:39.174 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 3356}' 2023-10-06 11:03:45.650 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 3456}' 2023-10-06 11:03:52.128 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 3555}' 2023-10-06 11:03:56.053 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:03:56.054 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 3, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 0, "Enable sys": 1, "Enable user": 1, "Max curr": 16000, "Max curr %": 266, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 155746 } ' 2023-10-06 11:03:56.353 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:03:56.355 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 235, "U2": 232, "U3": 234, "I1": 7784, "I2": 8021, "I3": 7981, "P": 5523880, "PF": 995, "E pres": 3619, "E total": 41140965, "Serial": "22195027", "Sec": 155746 } ' 2023-10-06 11:03:56.402 - debug: kecontact.0 (371943) Available surplus: 5385.88 2023-10-06 11:03:56.653 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:03:56.654 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 3622, "started[s]": 1696582765, "ended[s]": 0, "started": "2023-10-06 08:59:25.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 155747 } ' 2023-10-06 11:03:56.655 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:03:58.605 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 3654}' 2023-10-06 11:03:59.127 - info: kecontact.0 (371943) change pause status of wallbox from true to false 2023-10-06 11:03:59.127 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:03:59.129 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 3, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 0, "Enable sys": 1, "Enable user": 1, "Max curr": 16000, "Max curr %": 266, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 155749 } ' 2023-10-06 11:03:59.427 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:03:59.429 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 235, "U2": 233, "U3": 234, "I1": 7774, "I2": 8025, "I3": 7981, "P": 5570238, "PF": 994, "E pres": 3664, "E total": 41141010, "Serial": "22195027", "Sec": 155749 } ' 2023-10-06 11:03:59.520 - debug: kecontact.0 (371943) Available surplus: 5538.238 2023-10-06 11:03:59.727 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:03:59.728 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 3671, "started[s]": 1696582765, "ended[s]": 0, "started": "2023-10-06 08:59:25.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 155750 } ' 2023-10-06 11:03:59.729 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:04:05.084 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 3754}' 2023-10-06 11:04:11.563 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 3854}' 2023-10-06 11:04:18.041 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 3954}' 2023-10-06 11:04:24.729 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 4057}' 2023-10-06 11:04:26.053 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:04:26.055 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 3, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 0, "Enable sys": 1, "Enable user": 1, "Max curr": 16000, "Max curr %": 266, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 155776 } ' 2023-10-06 11:04:26.354 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:04:26.355 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 235, "U2": 233, "U3": 234, "I1": 7755, "I2": 7920, "I3": 7954, "P": 5503744, "PF": 994, "E pres": 4079, "E total": 41141425, "Serial": "22195027", "Sec": 155776 } ' 2023-10-06 11:04:26.398 - debug: kecontact.0 (371943) Available surplus: 5301.744 2023-10-06 11:04:26.654 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:04:26.656 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 4086, "started[s]": 1696582765, "ended[s]": 0, "started": "2023-10-06 08:59:25.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 155777 } ' 2023-10-06 11:04:26.656 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:04:31.208 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 4156}' 2023-10-06 11:04:37.686 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 4256}' 2023-10-06 11:04:44.164 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 4356}' 2023-10-06 11:04:50.642 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 4455}' 2023-10-06 11:04:56.053 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:04:56.055 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 3, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 0, "Enable sys": 1, "Enable user": 1, "Max curr": 16000, "Max curr %": 266, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 155806 } ' 2023-10-06 11:04:56.353 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:04:56.355 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 235, "U2": 233, "U3": 233, "I1": 7747, "I2": 8010, "I3": 8001, "P": 5537171, "PF": 994, "E pres": 4542, "E total": 41141888, "Serial": "22195027", "Sec": 155806 } ' 2023-10-06 11:04:56.410 - debug: kecontact.0 (371943) Available surplus: 5029.171 2023-10-06 11:04:56.654 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:04:56.656 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 4545, "started[s]": 1696582765, "ended[s]": 0, "started": "2023-10-06 08:59:25.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 155807 } ' 2023-10-06 11:04:56.656 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:04:57.121 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 4554}' 2023-10-06 11:05:03.597 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 4654}' 2023-10-06 11:05:10.285 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 4757}' 2023-10-06 11:05:16.763 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 4856}' 2023-10-06 11:05:23.241 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 4956}' 2023-10-06 11:05:26.053 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:05:26.055 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 3, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 0, "Enable sys": 1, "Enable user": 1, "Max curr": 16000, "Max curr %": 266, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 155836 } ' 2023-10-06 11:05:26.353 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:05:26.354 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 236, "U2": 233, "U3": 234, "I1": 7779, "I2": 8033, "I3": 7969, "P": 5568973, "PF": 994, "E pres": 5001, "E total": 41142347, "Serial": "22195027", "Sec": 155836 } ' 2023-10-06 11:05:26.415 - debug: kecontact.0 (371943) Available surplus: 5403.973 2023-10-06 11:05:26.654 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:05:26.655 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 5008, "started[s]": 1696582765, "ended[s]": 0, "started": "2023-10-06 08:59:25.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 155837 } ' 2023-10-06 11:05:26.656 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:05:29.720 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 5056}' 2023-10-06 11:05:36.199 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 5156}' 2023-10-06 11:05:42.677 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 5256}' 2023-10-06 11:05:49.156 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 5356}' 2023-10-06 11:05:55.634 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 5456}' 2023-10-06 11:05:56.053 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:05:56.054 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 3, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 0, "Enable sys": 1, "Enable user": 1, "Max curr": 16000, "Max curr %": 266, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 155866 } ' 2023-10-06 11:05:56.353 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:05:56.354 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 236, "U2": 233, "U3": 234, "I1": 7885, "I2": 8045, "I3": 7983, "P": 5581795, "PF": 995, "E pres": 5465, "E total": 41142811, "Serial": "22195027", "Sec": 155866 } ' 2023-10-06 11:05:56.416 - debug: kecontact.0 (371943) Available surplus: 5454.795 2023-10-06 11:05:56.653 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:05:56.656 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 5469, "started[s]": 1696582765, "ended[s]": 0, "started": "2023-10-06 08:59:25.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 155867 } ' 2023-10-06 11:05:56.656 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:06:02.113 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 5556}' 2023-10-06 11:06:08.591 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 5655}' 2023-10-06 11:06:15.070 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 5755}' 2023-10-06 11:06:21.547 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 5855}' 2023-10-06 11:06:26.053 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:06:26.056 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 3, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 0, "Enable sys": 1, "Enable user": 1, "Max curr": 16000, "Max curr %": 266, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 155896 } ' 2023-10-06 11:06:26.353 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:06:26.355 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 236, "U2": 232, "U3": 234, "I1": 7882, "I2": 7911, "I3": 7976, "P": 5539495, "PF": 994, "E pres": 5929, "E total": 41143275, "Serial": "22195027", "Sec": 155896 } ' 2023-10-06 11:06:26.396 - debug: kecontact.0 (371943) Available surplus: 4843.495 2023-10-06 11:06:26.653 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:06:26.655 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 5932, "started[s]": 1696582765, "ended[s]": 0, "started": "2023-10-06 08:59:25.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 155897 } ' 2023-10-06 11:06:26.655 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:06:28.025 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 5954}' 2023-10-06 11:06:34.504 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 6054}' 2023-10-06 11:06:40.981 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"E pres": 6154}' 2023-10-06 11:06:44.167 - debug: kecontact.0 (371943) Sent 'stop [d7703ef000000000] [d029847f000000000000]' to 192.168.188.97:7090 2023-10-06 11:06:44.168 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: 'TCH-OK :done ' 2023-10-06 11:06:44.168 - debug: kecontact.0 (371943) Received TCH-OK :done 2023-10-06 11:06:44.494 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"Enable sys": 0}' 2023-10-06 11:06:44.496 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"State": 5}' 2023-10-06 11:06:44.537 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"Max curr": 0}' 2023-10-06 11:06:56.053 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:06:56.055 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 1, "Enable sys": 0, "Enable user": 1, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 155926 } ' 2023-10-06 11:06:56.353 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:06:56.355 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 6221, "E total": 41143567, "Serial": "22195027", "Sec": 155926 } ' 2023-10-06 11:06:56.404 - debug: kecontact.0 (371943) Available surplus: 4655 2023-10-06 11:06:56.653 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:06:56.655 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 6221, "started[s]": 1696582765, "ended[s]": 1696583179, "started": "2023-10-06 08:59:25.000", "ended": "2023-10-06 09:06:19.000", "reason": 4, "timeQ": 3, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 155927 } ' 2023-10-06 11:06:56.655 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:07:26.053 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:07:26.055 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 1, "Enable sys": 0, "Enable user": 1, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 155956 } ' 2023-10-06 11:07:26.353 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:07:26.355 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 6221, "E total": 41143567, "Serial": "22195027", "Sec": 155956 } ' 2023-10-06 11:07:26.398 - debug: kecontact.0 (371943) Available surplus: 5004 2023-10-06 11:07:26.654 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:07:26.656 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 6221, "started[s]": 1696582765, "ended[s]": 1696583179, "started": "2023-10-06 08:59:25.000", "ended": "2023-10-06 09:06:19.000", "reason": 4, "timeQ": 3, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 155957 } ' 2023-10-06 11:07:26.656 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:07:56.054 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:07:56.056 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 1, "Enable sys": 0, "Enable user": 1, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 155986 } ' 2023-10-06 11:07:56.354 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:07:56.355 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 6221, "E total": 41143567, "Serial": "22195027", "Sec": 155986 } ' 2023-10-06 11:07:56.395 - debug: kecontact.0 (371943) Available surplus: 5024 2023-10-06 11:07:56.655 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:07:56.657 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 6221, "started[s]": 1696582765, "ended[s]": 1696583179, "started": "2023-10-06 08:59:25.000", "ended": "2023-10-06 09:06:19.000", "reason": 4, "timeQ": 3, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 155987 } ' 2023-10-06 11:07:56.657 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:08:26.055 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:08:26.057 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 1, "Enable sys": 0, "Enable user": 1, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 156016 } ' 2023-10-06 11:08:26.355 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:08:26.357 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 6221, "E total": 41143567, "Serial": "22195027", "Sec": 156016 } ' 2023-10-06 11:08:26.421 - debug: kecontact.0 (371943) Available surplus: 4376 2023-10-06 11:08:26.656 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:08:26.657 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 6221, "started[s]": 1696582765, "ended[s]": 1696583179, "started": "2023-10-06 08:59:25.000", "ended": "2023-10-06 09:06:19.000", "reason": 4, "timeQ": 3, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 156017 } ' 2023-10-06 11:08:26.657 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:08:56.055 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:08:56.056 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 1, "Enable sys": 0, "Enable user": 1, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 156046 } ' 2023-10-06 11:08:56.355 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:08:56.357 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 6221, "E total": 41143567, "Serial": "22195027", "Sec": 156046 } ' 2023-10-06 11:08:56.402 - debug: kecontact.0 (371943) Available surplus: 3674 2023-10-06 11:08:56.656 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:08:56.657 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 6221, "started[s]": 1696582765, "ended[s]": 1696583179, "started": "2023-10-06 08:59:25.000", "ended": "2023-10-06 09:06:19.000", "reason": 4, "timeQ": 3, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 156047 } ' 2023-10-06 11:08:56.658 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:09:26.055 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:09:26.057 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 1, "Enable sys": 0, "Enable user": 1, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 156076 } ' 2023-10-06 11:09:26.355 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:09:26.356 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 6221, "E total": 41143567, "Serial": "22195027", "Sec": 156076 } ' 2023-10-06 11:09:26.414 - debug: kecontact.0 (371943) Available surplus: 4203 2023-10-06 11:09:26.655 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:09:26.658 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 6221, "started[s]": 1696582765, "ended[s]": 1696583179, "started": "2023-10-06 08:59:25.000", "ended": "2023-10-06 09:06:19.000", "reason": 4, "timeQ": 3, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 156077 } ' 2023-10-06 11:09:26.658 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:09:56.055 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:09:56.057 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 1, "Enable sys": 0, "Enable user": 1, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 156106 } ' 2023-10-06 11:09:56.355 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:09:56.357 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 6221, "E total": 41143567, "Serial": "22195027", "Sec": 156106 } ' 2023-10-06 11:09:56.406 - debug: kecontact.0 (371943) Available surplus: 5204 2023-10-06 11:09:56.656 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:09:56.658 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 6221, "started[s]": 1696582765, "ended[s]": 1696583179, "started": "2023-10-06 08:59:25.000", "ended": "2023-10-06 09:06:19.000", "reason": 4, "timeQ": 3, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 156107 } ' 2023-10-06 11:09:56.658 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:10:00.034 - info: javascript.0 (1762973) script.js.strom.zirkulation_on_off: changeStateSteckdoseZirkulation 2023-10-06 11:10:00.034 - info: javascript.0 (1762973) script.js.strom.zirkulation_on_off: Steckdose ist bereits aus - Zirkulation aus 2023-10-06 11:10:26.056 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:10:26.057 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 1, "Enable sys": 0, "Enable user": 1, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 156136 } ' 2023-10-06 11:10:26.356 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:10:26.358 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 6221, "E total": 41143567, "Serial": "22195027", "Sec": 156136 } ' 2023-10-06 11:10:26.454 - debug: kecontact.0 (371943) Available surplus: 5275 2023-10-06 11:10:26.656 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:10:26.658 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 6221, "started[s]": 1696582765, "ended[s]": 1696583179, "started": "2023-10-06 08:59:25.000", "ended": "2023-10-06 09:06:19.000", "reason": 4, "timeQ": 3, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 156137 } ' 2023-10-06 11:10:26.658 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:10:52.396 - info: kecontact.0 (371943) change pause status of wallbox from false to true 2023-10-06 11:10:52.397 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:10:52.398 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 1, "Enable sys": 0, "Enable user": 1, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 156162 } ' 2023-10-06 11:10:52.697 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:10:52.699 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 6221, "E total": 41143567, "Serial": "22195027", "Sec": 156163 } ' 2023-10-06 11:10:52.748 - debug: kecontact.0 (371943) Available surplus: 4437 2023-10-06 11:10:52.998 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:10:53.000 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 6221, "started[s]": 1696582765, "ended[s]": 1696583179, "started": "2023-10-06 08:59:25.000", "ended": "2023-10-06 09:06:19.000", "reason": 4, "timeQ": 3, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 156163 } ' 2023-10-06 11:10:53.001 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:10:56.056 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:10:56.057 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 1, "Enable sys": 0, "Enable user": 1, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 156166 } ' 2023-10-06 11:10:56.356 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:10:56.357 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 6221, "E total": 41143567, "Serial": "22195027", "Sec": 156166 } ' 2023-10-06 11:10:56.656 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:10:56.659 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 6221, "started[s]": 1696582765, "ended[s]": 1696583179, "started": "2023-10-06 08:59:25.000", "ended": "2023-10-06 09:06:19.000", "reason": 4, "timeQ": 3, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 156167 } ' 2023-10-06 11:10:56.659 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:10:57.486 - debug: kecontact.0 (371943) Available surplus: 4285 2023-10-06 11:11:26.056 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:11:26.058 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 1, "Enable sys": 0, "Enable user": 1, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 156196 } ' 2023-10-06 11:11:26.356 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:11:26.357 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 6221, "E total": 41143567, "Serial": "22195027", "Sec": 156196 } ' 2023-10-06 11:11:26.409 - debug: kecontact.0 (371943) Available surplus: 4063 2023-10-06 11:11:26.656 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:11:26.658 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 6221, "started[s]": 1696582765, "ended[s]": 1696583179, "started": "2023-10-06 08:59:25.000", "ended": "2023-10-06 09:06:19.000", "reason": 4, "timeQ": 3, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 156197 } ' 2023-10-06 11:11:26.658 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:11:56.056 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:11:56.058 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 1, "Enable sys": 0, "Enable user": 1, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 156226 } ' 2023-10-06 11:11:56.356 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:11:56.358 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 6221, "E total": 41143567, "Serial": "22195027", "Sec": 156226 } ' 2023-10-06 11:11:56.411 - debug: kecontact.0 (371943) Available surplus: 5068 2023-10-06 11:11:56.657 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:11:56.658 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 6221, "started[s]": 1696582765, "ended[s]": 1696583179, "started": "2023-10-06 08:59:25.000", "ended": "2023-10-06 09:06:19.000", "reason": 4, "timeQ": 3, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 156227 } ' 2023-10-06 11:11:56.659 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:12:26.056 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:12:26.058 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 1, "Enable sys": 0, "Enable user": 1, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 156256 } ' 2023-10-06 11:12:26.357 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:12:26.358 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 6221, "E total": 41143567, "Serial": "22195027", "Sec": 156256 } ' 2023-10-06 11:12:26.433 - debug: kecontact.0 (371943) Available surplus: 5056 2023-10-06 11:12:26.656 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:12:26.658 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 6221, "started[s]": 1696582765, "ended[s]": 1696583179, "started": "2023-10-06 08:59:25.000", "ended": "2023-10-06 09:06:19.000", "reason": 4, "timeQ": 3, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 156257 } ' 2023-10-06 11:12:26.658 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:12:56.056 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:12:56.058 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 1, "Enable sys": 0, "Enable user": 1, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 156286 } ' 2023-10-06 11:12:56.356 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:12:56.357 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 6221, "E total": 41143567, "Serial": "22195027", "Sec": 156286 } ' 2023-10-06 11:12:56.413 - debug: kecontact.0 (371943) Available surplus: 5316 2023-10-06 11:12:56.656 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:12:56.658 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 6221, "started[s]": 1696582765, "ended[s]": 1696583179, "started": "2023-10-06 08:59:25.000", "ended": "2023-10-06 09:06:19.000", "reason": 4, "timeQ": 3, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 156287 } ' 2023-10-06 11:12:56.658 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:12:58.191 - info: kecontact.0 (371943) change pause status of wallbox from true to false 2023-10-06 11:12:58.192 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:12:58.194 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 1, "Enable sys": 0, "Enable user": 1, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 156288 } ' 2023-10-06 11:12:58.492 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:12:58.494 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 6221, "E total": 41143567, "Serial": "22195027", "Sec": 156288 } ' 2023-10-06 11:12:58.544 - debug: kecontact.0 (371943) Available surplus: 5366 2023-10-06 11:12:58.792 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:12:58.794 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 6221, "started[s]": 1696582765, "ended[s]": 1696583179, "started": "2023-10-06 08:59:25.000", "ended": "2023-10-06 09:06:19.000", "reason": 4, "timeQ": 3, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 156289 } ' 2023-10-06 11:12:58.794 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:13:17.552 - debug: kecontact.0 (371943) Sent 'stop ' to 192.168.188.97:7090 2023-10-06 11:13:17.553 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: 'TCH-ERR:: wrong parameter count ' 2023-10-06 11:13:17.554 - error: kecontact.0 (371943) Error received from wallbox: TCH-ERR:: wrong parameter count 2023-10-06 11:13:26.057 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:13:26.059 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 1, "Enable sys": 0, "Enable user": 1, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 156316 } ' 2023-10-06 11:13:26.358 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:13:26.359 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 6221, "E total": 41143567, "Serial": "22195027", "Sec": 156316 } ' 2023-10-06 11:13:26.408 - debug: kecontact.0 (371943) Available surplus: 4769 2023-10-06 11:13:26.657 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:13:26.659 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 6221, "started[s]": 1696582765, "ended[s]": 1696583179, "started": "2023-10-06 08:59:25.000", "ended": "2023-10-06 09:06:19.000", "reason": 4, "timeQ": 3, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 156317 } ' 2023-10-06 11:13:26.659 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:13:56.057 - debug: kecontact.0 (371943) Sent 'report 2' to 192.168.188.97:7090 2023-10-06 11:13:56.059 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 1, "Authreq": 1, "Enable sys": 0, "Enable user": 1, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 63000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "Serial": "22195027", "Sec": 156346 } ' 2023-10-06 11:13:56.357 - debug: kecontact.0 (371943) Sent 'report 3' to 192.168.188.97:7090 2023-10-06 11:13:56.359 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 6221, "E total": 41143567, "Serial": "22195027", "Sec": 156346 } ' 2023-10-06 11:13:56.405 - debug: kecontact.0 (371943) Available surplus: 4873 2023-10-06 11:13:56.657 - debug: kecontact.0 (371943) Sent 'report 100' to 192.168.188.97:7090 2023-10-06 11:13:56.659 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{ "ID": "100", "Session ID": 108, "Curr HW": 16000, "E start": 41137346, "E pres": 6221, "started[s]": 1696582765, "ended[s]": 1696583179, "started": "2023-10-06 08:59:25.000", "ended": "2023-10-06 09:06:19.000", "reason": 4, "timeQ": 3, "RFID tag": "0d7703ef00000000", "RFID class": "328c3604000000000000", "Serial": "22195027", "Sec": 156347 } ' 2023-10-06 11:13:56.660 - debug: kecontact.0 (371943) History ID received: 00 2023-10-06 11:14:07.601 - debug: kecontact.0 (371943) Sent 'start [d7703ef000000000] [d029847f000000000000]' to 192.168.188.97:7090 2023-10-06 11:14:07.602 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: 'TCH-OK :done ' 2023-10-06 11:14:07.602 - debug: kecontact.0 (371943) Received TCH-OK :done 2023-10-06 11:14:08.051 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"Enable sys": 1}' 2023-10-06 11:14:09.034 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"Max curr": 16000}' 2023-10-06 11:14:12.506 - debug: kecontact.0 (371943) UDP datagram from 192.168.188.97:7090: '{"State": 2}'
-
@sneak-l8 Klar, ich hab nochmals ein Update im Code gemacht. Nun sollte wahrscheinlich beides funktionieren. Siehe Github ...
-
@christian-kohlöffel Hab den Merge gerade durchgeführt. D.h. die Wallbox war im beschrieben Fall (einer X-Sereis mit X2-Switch) nicht auf enabled, aber im State = 3? Das ist interessant. Denn eigentlich sagt der ena 0/ena 1 ja, ob geladen wird oder nicht. Und selbst wenn nicht geladen werdne soll (ena 0) ist currUser auf dem zuletzt eingestelten Wert.
Deshalb hatte ich auf den enabled-State abgefragt. Sonst wäre currUser immer 6 und er würde bei jeder Berechnung (alle 30 Sekunden) das Laden beenden wollen. Bei ena 0 ist die Stromstärke aber schon null und es ist kein stop-Kommando zu senden.
Es geht im Grund nur darum den "falschen" currUser-Wert auf 0 zu korrigieren, damit der Adapter nicht meint, die Ladung immer wieder stoppen zu müssen.
Oder liegt es an der Freigabe mit RFID und gar nicht an der X-Serie bzw. X2-Switch? Ist das ein weiterer Wert, der zu prüfen ist und aussagt, dass trotz currUser > 0 nicht geladen wird und die Ladung beim Aufruf mit regulateWallbox(0) nicht gestoppt werden muss?