Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. [Frage] Realisierung Adapter UDP Keba Wallbox

    NEWS

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    [Frage] Realisierung Adapter UDP Keba Wallbox

    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      Sneak-L8 @OpaW last edited by

      @opaw ich gehe davon aus, dass das eine Steuerung ist, die direkt in der Firmware der Keba sitzt. Den Überschuss muss sie irgendwie selbst berechnen. Das kann Die vermutlich nur Keba sagen.

      Und kein Ding wegen deines Doppelposts. Kann ja mal vorkommen. Es gibt leider User, bei denen solche Posts kein Versehen sind...

      1 Reply Last reply Reply Quote 0
      • Christian Kohlöffel
        Christian Kohlöffel @Sneak-L8 last edited by Christian Kohlöffel

        @sneak-l8

        Ich habe heute nochmals PV abhängig mit der neuesten Version von Github geladen. Soweit funktioniert das Umschalten von 1 auf 3 Phasig, von 3 auf 1 Phasig, das Pausieren und stoppen da zu wenig Leistung.

        Einziges Problem welches ich nochmals erzeugen konnte war, dass bei Pausieren nach einem 3 Phasigen Ladevorgang ein Fehler auftritt und daraufhin das Laden wieder gestartet wird, siehe Log. Dies kann entweder durch den von Dir genannten Timer (wie hier der Fall) passieren, der wohl ca. 5min oder 5:30 für Umschalten der Phasen ist ? (Im gestrigen Log ebenfalls zwischen 5 und 5:30 bis er das neue Kommando angenommen hat). Oder möglicher Auslöser wie schon zuvor gesehen durch die 2 aufeinander folgenden Schaltvorgänge, die zu ähnlichem Problem führen könnten (TBC).

        Zeile 60: 2023-08-08 21:06:35.456 debug Sent 'x2 0' to 192.168.178.101:7090
        ..... Viele Versuche dazwischen um X2 zu schalten ....
        Zeile 699: 2023-08-08 21:02:38.255 error Error received from wallbox: TCH-ERR:X2 : not allowed now
        Zeile 705: 2023-08-08 21:02:37.971 info updating X2 for switch of phases from 1 to 0...
        Zeile 714: 2023-08-08 21:02:37.970 info updating X2 for switch of phases from 1 to 0...
        Zeile 732: 2023-08-08 21:02:37.653 info change pause status of wallbox from false to true
        Zeile 945: 2023-08-08 21:01:05.759 info updating X2 for switch of phases from 0 to 1...
        Zeile 975: 2023-08-08 21:01:05.018 info change pause status of wallbox from true to false

        Wie gesagt meine Vermutung nachdem ich versucht habe den Code nachzuvollziehen, dass 2 x schalten beim pausieren kommt von folgenden Zeilen:
        https://github.com/iobroker-community-adapters/ioBroker.kecontact/blob/master/main.js#L1436
        https://github.com/iobroker-community-adapters/ioBroker.kecontact/blob/master/main.js#L1538

        
        kecontact.0
        2023-08-08 21:06:50.157	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:06:50.157	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 196044 } '
        
        kecontact.0
        2023-08-08 21:06:50.155	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:06:49.868	debug	Available surplus: -624
        
        kecontact.0
        2023-08-08 21:06:49.857	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 230, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 196044 } '
        
        kecontact.0
        2023-08-08 21:06:49.856	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:06:49.556	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 3, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 1, "Enable user": 0, "Max curr": 6000, "Max curr %": 100, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 0, "Serial": "23272616", "Sec": 196044 } '
        
        kecontact.0
        2023-08-08 21:06:49.555	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:06:42.957	debug	UDP broadcast datagram from 192.168.178.101:7090: '{"State": 3}'
        
        kecontact.0
        2023-08-08 21:06:42.957	debug	UDP datagram from 192.168.178.101:7090: '{"State": 3}'
        
        kecontact.0
        2023-08-08 21:06:39.353	debug	UDP broadcast datagram from 192.168.178.101:7090: '{"State": 2}'
        
        kecontact.0
        2023-08-08 21:06:39.352	debug	UDP datagram from 192.168.178.101:7090: '{"State": 2}'
        
        kecontact.0
        2023-08-08 21:06:36.098	debug	UDP broadcast datagram from 192.168.178.101:7090: '{"Max curr": 6000}'
        
        kecontact.0
        2023-08-08 21:06:36.098	debug	UDP datagram from 192.168.178.101:7090: '{"Max curr": 6000}'
        
        kecontact.0
        2023-08-08 21:06:35.758	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:06:35.757	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 196030 } '
        
        kecontact.0
        2023-08-08 21:06:35.756	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:06:35.457	debug	Received TCH-OK :done
        
        kecontact.0
        2023-08-08 21:06:35.457	debug	UDP datagram from 192.168.178.101:7090: 'TCH-OK :done '
        
        kecontact.0
        2023-08-08 21:06:35.456	debug	Sent 'x2 0' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:06:35.252	debug	UDP broadcast datagram from 192.168.178.101:7090: '{"Enable sys": 1}'
        
        kecontact.0
        2023-08-08 21:06:35.251	debug	UDP datagram from 192.168.178.101:7090: '{"Enable sys": 1}'
        
        kecontact.0
        2023-08-08 21:06:35.157	debug	Received TCH-OK :done
        
        kecontact.0
        2023-08-08 21:06:35.157	debug	UDP datagram from 192.168.178.101:7090: 'TCH-OK :done '
        
        kecontact.0
        2023-08-08 21:06:35.155	debug	Sent 'x2 0' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:06:34.869	info	updating X2 for switch of phases from 1 to 0...
        
        kecontact.0
        2023-08-08 21:06:34.869	debug	not enough power for charging ...
        
        kecontact.0
        2023-08-08 21:06:34.869	info	updating X2 for switch of phases from 1 to 0...
        
        kecontact.0
        2023-08-08 21:06:34.869	debug	Available surplus: -634
        
        kecontact.0
        2023-08-08 21:06:34.856	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 196029 } '
        
        kecontact.0
        2023-08-08 21:06:34.855	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:06:34.555	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 0, "Enable user": 0, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 1, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 1, "Serial": "23272616", "Sec": 196029 } '
        
        kecontact.0
        2023-08-08 21:06:34.554	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:06:20.156	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:06:20.156	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 196014 } '
        
        kecontact.0
        2023-08-08 21:06:20.155	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:06:19.868	debug	Available surplus: -616
        
        kecontact.0
        2023-08-08 21:06:19.856	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 196014 } '
        
        kecontact.0
        2023-08-08 21:06:19.854	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:06:19.555	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 0, "Enable user": 0, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 1, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 1, "Serial": "23272616", "Sec": 196014 } '
        
        kecontact.0
        2023-08-08 21:06:19.553	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:06:05.756	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:06:05.756	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 196000 } '
        
        kecontact.0
        2023-08-08 21:06:05.755	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:06:05.456	error	Error received from wallbox: TCH-ERR:X2 : not allowed now
        
        kecontact.0
        2023-08-08 21:06:05.455	debug	UDP datagram from 192.168.178.101:7090: 'TCH-ERR:X2 : not allowed now '
        
        kecontact.0
        2023-08-08 21:06:05.454	debug	Sent 'x2 0' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:06:05.155	error	Error received from wallbox: TCH-ERR:X2 : not allowed now
        
        kecontact.0
        2023-08-08 21:06:05.155	debug	UDP datagram from 192.168.178.101:7090: 'TCH-ERR:X2 : not allowed now '
        
        kecontact.0
        2023-08-08 21:06:05.154	debug	Sent 'x2 0' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:06:04.869	info	updating X2 for switch of phases from 1 to 0...
        
        kecontact.0
        2023-08-08 21:06:04.869	debug	not enough power for charging ...
        
        kecontact.0
        2023-08-08 21:06:04.869	info	updating X2 for switch of phases from 1 to 0...
        
        kecontact.0
        2023-08-08 21:06:04.868	debug	Available surplus: -569
        
        kecontact.0
        2023-08-08 21:06:04.855	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 195999 } '
        
        kecontact.0
        2023-08-08 21:06:04.853	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:06:04.555	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 0, "Enable user": 0, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 1, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 1, "Serial": "23272616", "Sec": 195999 } '
        
        kecontact.0
        2023-08-08 21:06:04.553	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:05:50.157	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:05:50.156	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 195984 } '
        
        kecontact.0
        2023-08-08 21:05:50.154	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:05:49.866	debug	Available surplus: -624
        
        kecontact.0
        2023-08-08 21:05:49.855	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 195984 } '
        
        kecontact.0
        2023-08-08 21:05:49.854	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:05:49.555	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 0, "Enable user": 0, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 1, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 1, "Serial": "23272616", "Sec": 195984 } '
        
        kecontact.0
        2023-08-08 21:05:49.553	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:05:35.757	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:05:35.757	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 195970 } '
        
        kecontact.0
        2023-08-08 21:05:35.756	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:05:35.457	error	Error received from wallbox: TCH-ERR:X2 : not allowed now
        
        kecontact.0
        2023-08-08 21:05:35.456	debug	UDP datagram from 192.168.178.101:7090: 'TCH-ERR:X2 : not allowed now '
        
        kecontact.0
        2023-08-08 21:05:35.455	debug	Sent 'x2 0' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:05:35.155	error	Error received from wallbox: TCH-ERR:X2 : not allowed now
        
        kecontact.0
        2023-08-08 21:05:35.155	debug	UDP datagram from 192.168.178.101:7090: 'TCH-ERR:X2 : not allowed now '
        
        kecontact.0
        2023-08-08 21:05:35.154	debug	Sent 'x2 0' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:05:34.867	info	updating X2 for switch of phases from 1 to 0...
        
        kecontact.0
        2023-08-08 21:05:34.867	debug	not enough power for charging ...
        
        kecontact.0
        2023-08-08 21:05:34.867	info	updating X2 for switch of phases from 1 to 0...
        
        kecontact.0
        2023-08-08 21:05:34.867	debug	Available surplus: -591
        
        kecontact.0
        2023-08-08 21:05:34.855	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 195969 } '
        
        kecontact.0
        2023-08-08 21:05:34.854	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:05:34.555	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 0, "Enable user": 0, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 1, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 1, "Serial": "23272616", "Sec": 195969 } '
        
        kecontact.0
        2023-08-08 21:05:34.554	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:05:20.156	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:05:20.156	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 195954 } '
        
        kecontact.0
        2023-08-08 21:05:20.155	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:05:19.869	debug	Available surplus: -602
        
        kecontact.0
        2023-08-08 21:05:19.855	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 195954 } '
        
        kecontact.0
        2023-08-08 21:05:19.854	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:05:19.555	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 0, "Enable user": 0, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 1, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 1, "Serial": "23272616", "Sec": 195954 } '
        
        kecontact.0
        2023-08-08 21:05:19.553	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:05:05.756	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:05:05.756	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 195940 } '
        
        kecontact.0
        2023-08-08 21:05:05.754	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:05:05.455	error	Error received from wallbox: TCH-ERR:X2 : not allowed now
        
        kecontact.0
        2023-08-08 21:05:05.455	debug	UDP datagram from 192.168.178.101:7090: 'TCH-ERR:X2 : not allowed now '
        
        kecontact.0
        2023-08-08 21:05:05.454	debug	Sent 'x2 0' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:05:05.155	error	Error received from wallbox: TCH-ERR:X2 : not allowed now
        
        kecontact.0
        2023-08-08 21:05:05.155	debug	UDP datagram from 192.168.178.101:7090: 'TCH-ERR:X2 : not allowed now '
        
        kecontact.0
        2023-08-08 21:05:05.154	debug	Sent 'x2 0' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:05:04.865	info	updating X2 for switch of phases from 1 to 0...
        
        kecontact.0
        2023-08-08 21:05:04.865	debug	not enough power for charging ...
        
        kecontact.0
        2023-08-08 21:05:04.865	info	updating X2 for switch of phases from 1 to 0...
        
        kecontact.0
        2023-08-08 21:05:04.865	debug	Available surplus: -610
        
        kecontact.0
        2023-08-08 21:05:04.854	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 195939 } '
        
        kecontact.0
        2023-08-08 21:05:04.854	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:05:04.555	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 0, "Enable user": 0, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 1, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 1, "Serial": "23272616", "Sec": 195939 } '
        
        kecontact.0
        2023-08-08 21:05:04.553	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:04:50.156	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:04:50.156	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 195924 } '
        
        kecontact.0
        2023-08-08 21:04:50.154	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:04:49.864	debug	Available surplus: -598
        
        kecontact.0
        2023-08-08 21:04:49.854	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 195924 } '
        
        kecontact.0
        2023-08-08 21:04:49.853	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:04:49.554	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 0, "Enable user": 0, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 1, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 1, "Serial": "23272616", "Sec": 195924 } '
        
        kecontact.0
        2023-08-08 21:04:49.552	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:04:35.756	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:04:35.755	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 195910 } '
        
        kecontact.0
        2023-08-08 21:04:35.754	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:04:35.454	error	Error received from wallbox: TCH-ERR:X2 : not allowed now
        
        kecontact.0
        2023-08-08 21:04:35.454	debug	UDP datagram from 192.168.178.101:7090: 'TCH-ERR:X2 : not allowed now '
        
        kecontact.0
        2023-08-08 21:04:35.453	debug	Sent 'x2 0' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:04:35.153	error	Error received from wallbox: TCH-ERR:X2 : not allowed now
        
        kecontact.0
        2023-08-08 21:04:35.153	debug	UDP datagram from 192.168.178.101:7090: 'TCH-ERR:X2 : not allowed now '
        
        kecontact.0
        2023-08-08 21:04:35.152	debug	Sent 'x2 0' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:04:34.864	info	updating X2 for switch of phases from 1 to 0...
        
        kecontact.0
        2023-08-08 21:04:34.864	debug	not enough power for charging ...
        
        kecontact.0
        2023-08-08 21:04:34.864	info	updating X2 for switch of phases from 1 to 0...
        
        kecontact.0
        2023-08-08 21:04:34.864	debug	Available surplus: -570
        
        kecontact.0
        2023-08-08 21:04:34.853	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 195909 } '
        
        kecontact.0
        2023-08-08 21:04:34.852	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:04:34.553	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 0, "Enable user": 0, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 1, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 1, "Serial": "23272616", "Sec": 195909 } '
        
        kecontact.0
        2023-08-08 21:04:34.552	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:04:20.155	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:04:20.155	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 195894 } '
        
        kecontact.0
        2023-08-08 21:04:20.154	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:04:19.865	debug	Available surplus: -621
        
        kecontact.0
        2023-08-08 21:04:19.854	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 195894 } '
        
        kecontact.0
        2023-08-08 21:04:19.853	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:04:19.554	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 0, "Enable user": 0, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 1, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 1, "Serial": "23272616", "Sec": 195894 } '
        
        kecontact.0
        2023-08-08 21:04:19.552	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:04:05.753	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:04:05.753	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 195880 } '
        
        kecontact.0
        2023-08-08 21:04:05.752	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:04:05.453	error	Error received from wallbox: TCH-ERR:X2 : not allowed now
        
        kecontact.0
        2023-08-08 21:04:05.453	debug	UDP datagram from 192.168.178.101:7090: 'TCH-ERR:X2 : not allowed now '
        
        kecontact.0
        2023-08-08 21:04:05.452	debug	Sent 'x2 0' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:04:05.153	error	Error received from wallbox: TCH-ERR:X2 : not allowed now
        
        kecontact.0
        2023-08-08 21:04:05.153	debug	UDP datagram from 192.168.178.101:7090: 'TCH-ERR:X2 : not allowed now '
        
        kecontact.0
        2023-08-08 21:04:05.152	debug	Sent 'x2 0' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:04:04.865	info	updating X2 for switch of phases from 1 to 0...
        
        kecontact.0
        2023-08-08 21:04:04.865	debug	not enough power for charging ...
        
        kecontact.0
        2023-08-08 21:04:04.865	info	updating X2 for switch of phases from 1 to 0...
        
        kecontact.0
        2023-08-08 21:04:04.864	debug	Available surplus: -604
        
        kecontact.0
        2023-08-08 21:04:04.853	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 195879 } '
        
        kecontact.0
        2023-08-08 21:04:04.852	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:04:04.552	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 0, "Enable user": 0, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 1, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 1, "Serial": "23272616", "Sec": 195879 } '
        
        kecontact.0
        2023-08-08 21:04:04.551	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:03:50.152	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:03:50.152	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 195864 } '
        
        kecontact.0
        2023-08-08 21:03:50.151	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:03:49.862	debug	Available surplus: -616
        
        kecontact.0
        2023-08-08 21:03:49.852	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 195864 } '
        
        kecontact.0
        2023-08-08 21:03:49.851	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:03:49.552	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 0, "Enable user": 0, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 1, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 1, "Serial": "23272616", "Sec": 195864 } '
        
        kecontact.0
        2023-08-08 21:03:49.550	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:03:35.753	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:03:35.753	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 195850 } '
        
        kecontact.0
        2023-08-08 21:03:35.751	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:03:35.453	error	Error received from wallbox: TCH-ERR:X2 : not allowed now
        
        kecontact.0
        2023-08-08 21:03:35.453	debug	UDP datagram from 192.168.178.101:7090: 'TCH-ERR:X2 : not allowed now '
        
        kecontact.0
        2023-08-08 21:03:35.452	debug	Sent 'x2 0' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:03:35.152	error	Error received from wallbox: TCH-ERR:X2 : not allowed now
        
        kecontact.0
        2023-08-08 21:03:35.152	debug	UDP datagram from 192.168.178.101:7090: 'TCH-ERR:X2 : not allowed now '
        
        kecontact.0
        2023-08-08 21:03:35.151	debug	Sent 'x2 0' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:03:34.864	info	updating X2 for switch of phases from 1 to 0...
        
        kecontact.0
        2023-08-08 21:03:34.864	debug	not enough power for charging ...
        
        kecontact.0
        2023-08-08 21:03:34.864	info	updating X2 for switch of phases from 1 to 0...
        
        kecontact.0
        2023-08-08 21:03:34.863	debug	Available surplus: -625
        
        kecontact.0
        2023-08-08 21:03:34.852	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 195849 } '
        
        kecontact.0
        2023-08-08 21:03:34.850	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:03:34.551	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 0, "Enable user": 0, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 1, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 1, "Serial": "23272616", "Sec": 195849 } '
        
        kecontact.0
        2023-08-08 21:03:34.550	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:03:20.152	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:03:20.152	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 195834 } '
        
        kecontact.0
        2023-08-08 21:03:20.151	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:03:19.865	debug	Available surplus: -610
        
        kecontact.0
        2023-08-08 21:03:19.852	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 195834 } '
        
        kecontact.0
        2023-08-08 21:03:19.850	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:03:19.551	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 0, "Enable user": 0, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 1, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 1, "Serial": "23272616", "Sec": 195834 } '
        
        kecontact.0
        2023-08-08 21:03:19.550	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:03:05.753	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:03:05.753	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 195820 } '
        
        kecontact.0
        2023-08-08 21:03:05.752	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:03:05.452	error	Error received from wallbox: TCH-ERR:X2 : not allowed now
        
        kecontact.0
        2023-08-08 21:03:05.452	debug	UDP datagram from 192.168.178.101:7090: 'TCH-ERR:X2 : not allowed now '
        
        kecontact.0
        2023-08-08 21:03:05.452	debug	Sent 'x2 0' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:03:05.152	error	Error received from wallbox: TCH-ERR:X2 : not allowed now
        
        kecontact.0
        2023-08-08 21:03:05.152	debug	UDP datagram from 192.168.178.101:7090: 'TCH-ERR:X2 : not allowed now '
        
        kecontact.0
        2023-08-08 21:03:05.151	debug	Sent 'x2 0' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:03:04.863	info	updating X2 for switch of phases from 1 to 0...
        
        kecontact.0
        2023-08-08 21:03:04.863	debug	not enough power for charging ...
        
        kecontact.0
        2023-08-08 21:03:04.863	info	updating X2 for switch of phases from 1 to 0...
        
        kecontact.0
        2023-08-08 21:03:04.862	debug	Available surplus: -556
        
        kecontact.0
        2023-08-08 21:03:04.852	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 195819 } '
        
        kecontact.0
        2023-08-08 21:03:04.850	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:03:04.551	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 0, "Enable user": 0, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 1, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 1, "Serial": "23272616", "Sec": 195819 } '
        
        kecontact.0
        2023-08-08 21:03:04.549	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:02:50.150	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:02:50.150	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 195804 } '
        
        kecontact.0
        2023-08-08 21:02:50.149	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:02:49.861	debug	Available surplus: -4810
        
        kecontact.0
        2023-08-08 21:02:49.849	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 195804 } '
        
        kecontact.0
        2023-08-08 21:02:49.848	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:02:49.550	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 0, "Enable user": 0, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 1, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 1, "Serial": "23272616", "Sec": 195804 } '
        
        kecontact.0
        2023-08-08 21:02:49.548	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:02:39.743	debug	UDP broadcast datagram from 192.168.178.101:7090: '{"Max curr": 0}'
        
        kecontact.0
        2023-08-08 21:02:39.742	debug	UDP datagram from 192.168.178.101:7090: '{"Max curr": 0}'
        
        kecontact.0
        2023-08-08 21:02:39.625	debug	UDP broadcast datagram from 192.168.178.101:7090: '{"State": 5}'
        
        kecontact.0
        2023-08-08 21:02:39.625	debug	UDP broadcast datagram from 192.168.178.101:7090: '{"Enable sys": 0}'
        
        kecontact.0
        2023-08-08 21:02:39.625	debug	UDP datagram from 192.168.178.101:7090: '{"State": 5}'
        
        kecontact.0
        2023-08-08 21:02:39.624	debug	UDP datagram from 192.168.178.101:7090: '{"Enable sys": 0}'
        
        kecontact.0
        2023-08-08 21:02:39.158	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:02:39.158	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 195793 } '
        
        kecontact.0
        2023-08-08 21:02:39.156	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:02:38.856	error	Error received from wallbox: TCH-ERR:X2 : not allowed now
        
        kecontact.0
        2023-08-08 21:02:38.856	debug	UDP datagram from 192.168.178.101:7090: 'TCH-ERR:X2 : not allowed now '
        
        kecontact.0
        2023-08-08 21:02:38.855	debug	Sent 'x2 0' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:02:38.556	debug	Received TCH-OK :done
        
        kecontact.0
        2023-08-08 21:02:38.556	debug	UDP datagram from 192.168.178.101:7090: 'TCH-OK :done '
        
        kecontact.0
        2023-08-08 21:02:38.555	debug	Sent 'currtime 0 1' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:02:38.255	error	Error received from wallbox: TCH-ERR:X2 : not allowed now
        
        kecontact.0
        2023-08-08 21:02:38.255	debug	UDP datagram from 192.168.178.101:7090: 'TCH-ERR:X2 : not allowed now '
        
        kecontact.0
        2023-08-08 21:02:38.254	debug	Sent 'x2 0' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:02:37.971	info	updating X2 for switch of phases from 1 to 0...
        
        kecontact.0
        2023-08-08 21:02:37.971	info	stop charging
        
        kecontact.0
        2023-08-08 21:02:37.971	debug	not enough power for charging ...
        
        kecontact.0
        2023-08-08 21:02:37.970	info	updating X2 for switch of phases from 1 to 0...
        
        kecontact.0
        2023-08-08 21:02:37.970	debug	Available surplus: -515
        
        kecontact.0
        2023-08-08 21:02:37.954	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 230, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 195792 } '
        
        kecontact.0
        2023-08-08 21:02:37.953	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:02:37.659	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 3, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 1, "Enable user": 1, "Max curr": 6000, "Max curr %": 100, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 6000, "Tmo CT": 0, "Setenergy": 0, "Output": 1, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 1, "Serial": "23272616", "Sec": 195792 } '
        
        kecontact.0
        2023-08-08 21:02:37.653	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:02:37.653	info	change pause status of wallbox from false to true
        
        kecontact.0
        2023-08-08 21:02:35.150	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:02:35.150	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 195789 } '
        
        kecontact.0
        2023-08-08 21:02:35.148	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:02:34.861	debug	wallbox set to charging maximum of 6000 mA
        
        kecontact.0
        2023-08-08 21:02:34.861	debug	Available surplus: -522
        
        kecontact.0
        2023-08-08 21:02:34.849	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 230, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 195789 } '
        
        kecontact.0
        2023-08-08 21:02:34.848	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:02:34.549	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 3, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 1, "Enable user": 1, "Max curr": 6000, "Max curr %": 100, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 6000, "Tmo CT": 0, "Setenergy": 0, "Output": 1, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 1, "Serial": "23272616", "Sec": 195789 } '
        
        kecontact.0
        2023-08-08 21:02:34.548	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:02:20.149	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:02:20.149	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 195774 } '
        
        kecontact.0
        2023-08-08 21:02:20.147	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:02:19.862	debug	Available surplus: -519
        
        kecontact.0
        2023-08-08 21:02:19.849	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 230, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 195774 } '
        
        kecontact.0
        2023-08-08 21:02:19.848	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:02:19.550	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 3, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 1, "Enable user": 1, "Max curr": 6000, "Max curr %": 100, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 6000, "Tmo CT": 0, "Setenergy": 0, "Output": 1, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 1, "Serial": "23272616", "Sec": 195774 } '
        
        kecontact.0
        2023-08-08 21:02:19.548	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:02:05.150	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:02:05.150	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 195759 } '
        
        kecontact.0
        2023-08-08 21:02:05.148	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:02:04.862	debug	wallbox set to charging maximum of 6000 mA
        
        kecontact.0
        2023-08-08 21:02:04.862	debug	Available surplus: -509
        
        kecontact.0
        2023-08-08 21:02:04.849	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 230, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 195759 } '
        
        kecontact.0
        2023-08-08 21:02:04.848	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:02:04.548	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 3, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 1, "Enable user": 1, "Max curr": 6000, "Max curr %": 100, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 6000, "Tmo CT": 0, "Setenergy": 0, "Output": 1, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 1, "Serial": "23272616", "Sec": 195759 } '
        
        kecontact.0
        2023-08-08 21:02:04.547	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:01:50.148	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:01:50.147	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 195744 } '
        
        kecontact.0
        2023-08-08 21:01:50.146	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:01:49.863	debug	Available surplus: -327
        
        kecontact.0
        2023-08-08 21:01:49.848	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 230, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 195744 } '
        
        kecontact.0
        2023-08-08 21:01:49.847	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:01:49.547	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 3, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 1, "Enable user": 1, "Max curr": 6000, "Max curr %": 100, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 6000, "Tmo CT": 0, "Setenergy": 0, "Output": 1, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 1, "Serial": "23272616", "Sec": 195744 } '
        
        kecontact.0
        2023-08-08 21:01:49.546	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:01:35.148	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:01:35.148	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 195729 } '
        
        kecontact.0
        2023-08-08 21:01:35.147	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:01:34.858	debug	wallbox set to charging maximum of 6000 mA
        
        kecontact.0
        2023-08-08 21:01:34.858	debug	Available surplus: -363
        
        kecontact.0
        2023-08-08 21:01:34.847	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 230, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 195729 } '
        
        kecontact.0
        2023-08-08 21:01:34.846	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:01:34.547	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 3, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 1, "Enable user": 1, "Max curr": 6000, "Max curr %": 100, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 6000, "Tmo CT": 0, "Setenergy": 0, "Output": 1, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 1, "Serial": "23272616", "Sec": 195729 } '
        
        kecontact.0
        2023-08-08 21:01:34.545	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:01:20.149	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:01:20.148	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 195714 } '
        
        kecontact.0
        2023-08-08 21:01:20.146	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:01:19.859	debug	Available surplus: 3488
        
        kecontact.0
        2023-08-08 21:01:19.858	info	vehicle (re)starts to charge
        
        kecontact.0
        2023-08-08 21:01:19.847	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 230, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 195714 } '
        
        kecontact.0
        2023-08-08 21:01:19.845	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:01:19.545	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 3, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 1, "Enable user": 1, "Max curr": 6000, "Max curr %": 100, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 6000, "Tmo CT": 0, "Setenergy": 0, "Output": 1, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 1, "Serial": "23272616", "Sec": 195714 } '
        
        kecontact.0
        2023-08-08 21:01:19.544	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:01:14.124	debug	UDP broadcast datagram from 192.168.178.101:7090: '{"State": 3}'
        
        kecontact.0
        2023-08-08 21:01:14.124	debug	UDP datagram from 192.168.178.101:7090: '{"State": 3}'
        
        kecontact.0
        2023-08-08 21:01:10.520	debug	UDP broadcast datagram from 192.168.178.101:7090: '{"State": 2}'
        
        kecontact.0
        2023-08-08 21:01:10.519	debug	UDP datagram from 192.168.178.101:7090: '{"State": 2}'
        
        kecontact.0
        2023-08-08 21:01:07.271	debug	UDP broadcast datagram from 192.168.178.101:7090: '{"Max curr": 6000}'
        
        kecontact.0
        2023-08-08 21:01:07.271	debug	UDP datagram from 192.168.178.101:7090: '{"Max curr": 6000}'
        
        kecontact.0
        2023-08-08 21:01:06.646	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:01:06.646	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 195701 } '
        
        kecontact.0
        2023-08-08 21:01:06.644	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:01:06.355	debug	UDP broadcast datagram from 192.168.178.101:7090: '{"Enable sys": 1}'
        
        kecontact.0
        2023-08-08 21:01:06.354	debug	UDP datagram from 192.168.178.101:7090: '{"Enable sys": 1}'
        
        kecontact.0
        2023-08-08 21:01:06.345	debug	Received TCH-OK :done
        
        kecontact.0
        2023-08-08 21:01:06.344	debug	UDP datagram from 192.168.178.101:7090: 'TCH-OK :done '
        
        kecontact.0
        2023-08-08 21:01:06.344	debug	Sent 'x2 1' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:01:06.045	debug	Received TCH-OK :done
        
        kecontact.0
        2023-08-08 21:01:06.045	debug	UDP datagram from 192.168.178.101:7090: 'TCH-OK :done '
        
        kecontact.0
        2023-08-08 21:01:06.044	debug	Sent 'currtime 6000 1' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:01:05.759	info	(re)start charging
        
        kecontact.0
        2023-08-08 21:01:05.759	debug	wallbox set to charging maximum of 6000 mA
        
        kecontact.0
        2023-08-08 21:01:05.759	info	updating X2 for switch of phases from 0 to 1...
        
        kecontact.0
        2023-08-08 21:01:05.759	debug	Available surplus: -612
        
        kecontact.0
        2023-08-08 21:01:05.745	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "3", "U1": 0, "U2": 0, "U3": 0, "I1": 0, "I2": 0, "I3": 0, "P": 0, "PF": 0, "E pres": 0, "E total": 0, "Serial": "23272616", "Sec": 195700 } '
        
        kecontact.0
        2023-08-08 21:01:05.744	debug	Sent 'report 3' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:01:05.445	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "2", "State": 5, "Error1": 0, "Error2": 0, "Plug": 7, "AuthON": 0, "Authreq": 0, "Enable sys": 0, "Enable user": 0, "Max curr": 0, "Max curr %": 1000, "Curr HW": 16000, "Curr user": 6000, "Curr FS": 0, "Tmo FS": 0, "Curr timer": 0, "Tmo CT": 0, "Setenergy": 0, "Output": 0, "Input": 0, "X2 phaseSwitch source": 4, "X2 phaseSwitch": 0, "Serial": "23272616", "Sec": 195700 } '
        
        kecontact.0
        2023-08-08 21:01:05.444	debug	Sent 'report 2' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:01:05.145	debug	History ID received: 00
        
        kecontact.0
        2023-08-08 21:01:05.145	debug	UDP datagram from 192.168.178.101:7090: '{ "ID": "100", "Session ID": 49, "Curr HW": 16000, "E start": 0, "E pres": 0, "started[s]": 1691519327, "ended[s]": 0, "started": "2023-08-08 18:28:47.000", "ended": "0", "reason": 5, "timeQ": 0, "RFID tag": "0000000000000000", "RFID class": "00000000000000000000", "Serial": "23272616", "Sec": 195699 } '
        
        kecontact.0
        2023-08-08 21:01:05.144	debug	Sent 'report 100' to 192.168.178.101:7090
        
        kecontact.0
        2023-08-08 21:01:05.018	info	change pause status of wallbox from true to false
        
        S 1 Reply Last reply Reply Quote 0
        • S
          Sneak-L8 @Christian Kohlöffel last edited by

          @christian-kohlöffel Hm, also "pause" wird nicht genutzt, um den Ladevorgang bei der Phasenumschaltung zu stoppen. Das ist etwas, das Du manuell über den State anstößt und dann vom Adapter interpretiert und mit currtime 0 1 an die Wallox gesendet wird.

          Warum das X2-Kommando nicht akzeptiert wird, müsstest Du vielleicht mal bei Keba anfragen.

          Mir ist auch nicht klar, warum die Box anfängt zu laden, wenn der Überschuss nur -612W sein soll. Später ist er dann aber plötzlich +3.488W.
          Hast Du "Schließer (is normally open/NO)" eingestellt und hast vielleicht einen Öffner?
          Oder wird die Leistung der Wallbox im Überschuss mit einberechnet?

          So ganz komme ich gerade leider nicht mit, was da genau passiert...

          O Christian Kohlöffel 2 Replies Last reply Reply Quote 0
          • O
            OpaW @Sneak-L8 last edited by

            @sneak-l8 Damit bei mir der Umschaltbefehl für X2 akzeptiert wird, muss ich in der WebUi der Wallbox den Kommunikationskanal für den X2 auf "UDP" stellen!

            S 1 Reply Last reply Reply Quote 0
            • S
              Sneak-L8 @OpaW last edited by

              @opaw das sollte der Adapter beim Start automatisch machen

              O 1 Reply Last reply Reply Quote 0
              • O
                OpaW @Sneak-L8 last edited by

                @sneak-l8 Ok, Der Adapter ist bei mir im Passiv Modus, das wäre eine Erklärung das der State X2 nicht über den Adapter umschaltbar ist.

                Ich habe nun passiv abgewählt. Trotzdem ist der State vom Adapter aus nicht zu verändern. Nach kurzer Zeit springt der Wert wieder von 4 für UDP wieder auf 1. Bei mir eingestellter Wert für Steuerung durch Wallbox im der WebUi. Auch ein Neustart des Adapters brachte keine Veränderung.

                Zusätzlicher Hinweis: Unter Modbus verhält sich die P30X auch so.

                S 1 Reply Last reply Reply Quote 0
                • S
                  Sneak-L8 @OpaW last edited by Sneak-L8

                  @opaw Die X-series hat ja ihre eigene Steuerung. Der Adapter stellt den Modus zwar um, die Keba ist aber wohl so konfiguriert, dass sie weiter auf den anderen Modus umstellt. Vermutlich weil sie selbst aktiv steuern will.
                  Es können aber nicht zwei Systeme aktiv steuern wollen.
                  Da musst Du wohl in der Konfiguration für die Keba nachlesen und Dich für eine Seite entscheiden, die aktiv sein soll

                  O 1 Reply Last reply Reply Quote 0
                  • O
                    OpaW @Sneak-L8 last edited by

                    @sneak-l8 Das ist mir zwischenzeitlich klar, ich kann die P30X so über die WebUi einstellen um entweder über die eingebaute Software, oder Deinem Adapter, oder Modbus zu steuern. Mein Favorit ist zur Zeit Dein UDP Adapter im passiven Modus. Auf diesen greife ich mit einem eigenen Steuerprogramm bezüglich "PV optimiertem Laden mit Hausbatterie" zu. Die Modbus Schnittstelle von Keba ist schlecht gemacht. Die notwendigen beschreibbaren Register liefern keine Statusmeldungen.

                    Bis ich alles durchgetestet habe, lasse ich die Wallbox im normalen Betrieb mit der internen Software agieren. Ist offenbar z.Z die PV optimierteste Lösung. Meine Frau, Kinder stecken den Stecker ins Auto, und alles läuft. Ich muß dann nur manuell hinschauen, dass die für die Nacht vorgesehene Hausbatterie nicht Zweckentfremdet wird.

                    Ich habe parallel nach einer Lösung über Keba (Kontaktformular) gesucht. Ich komme dabei aber nicht an eine Fachkraft und werde mit technisch unsinnigen Antworten abgespeist.

                    1 Reply Last reply Reply Quote 0
                    • Christian Kohlöffel
                      Christian Kohlöffel @Sneak-L8 last edited by Christian Kohlöffel

                      @sneak-l8 , ich hab mir das alles nochmals genauer angeschaut und habe versucht das schalten des X2 Ausgangs mittels einen neu eingeführten Timers umzusetzen und somit den mindest Zeitabstand einzuhalten. Hierzu habe ich dein aktuelles Repository geforked, einen dev-server aufgesetzt und im programmieren versucht. Wäre schön wenn du Dir das mal anschauen könntest und wenn es für Dich auch einen Sinn ergibt bei Dir integriert werden könnte. In meinen ersten Test heute hat es schon mal einige Fehlermeldungen beheben können. Inputs Deiner Seite sind auch gerne wilkommen 🙂

                      https://github.com/iobroker-community-adapters/ioBroker.kecontact/compare/master...christi-ko:ioBroker.kecontact:master

                      @sneak-l8 sagte in [Frage] Realisierung Adapter UDP Keba Wallbox:

                      Warum das X2-Kommando nicht akzeptiert wird, müsstest Du vielleicht mal bei Keba anfragen.

                      Ich habe dazu einen Thread bei einem der anderen Adapter zur KEBA gefunden, schein am implementierten Verhalten in der KEBA zu legen. Nachdem ich ein wenig an den Bedingungen rum gebastelt habe, wie im Log nachzulesen habe ich es geschafft, dass die Box wieder das laden selbständig beendet, wenn das der Fall ist.
                      Hier der Link zum Post: https://www.loxforum.com/forum/hardware-zubehör-sensorik/77402-keba-wallbox?p=398742#post398742

                      In der Anleitung hab ich zufällig gefunden dass es tatsächlich die 300s sind welche implementiert sind.
                      f8bf656e-43c1-4173-ab97-e3de9a64312e-image.png

                      O S 2 Replies Last reply Reply Quote 0
                      • O
                        OpaW @Christian Kohlöffel last edited by

                        @christian-kohlöffel
                        Hallo ich bin an der gleichen Baustelle. Dar x2 Schaltbefehl funktionier bei mir in dem Moment wenn ich in der Webui (P30X) auf UDP umgestaltet hab. Ein Umschalten des State X2phaseSource über den Adapter funktioniert nicht. Der Adapter springt nach kurzer Zeit wieder auf den alten Wert zurück.

                        Ich habe Keba angeschrieben und bezüglich der Beeinflussung interne und externer Steuerungslogik folgende Antwort erhalten:

                        vielen Dank für Ihre Anfrage bezüglich des PV-optimierten Ladevorgangs Ihrer KEBA P30 PV Edition.

                        Wenn Sie die PV-optimierte Ladesteuerung über eine externe Steuerung realisieren möchten und die interne Steuerung der KEBA P30 deaktivieren wollen, müssen Sie dies nicht explizit abschalten. Die externe Steuerung hat Vorrang und überschreibt die internen Einstellungen der Ladestation.

                        Sie können die externe Steuerung, sei es über ein Energiemanagementsystem oder eine andere Lösung, so konfigurieren, dass sie den Ladeprozess basierend auf dem PV-Überschuss optimiert. Die KEBA P30 Wallbox wird dann entsprechend gesteuert, ohne dass Sie manuelle Einstellungen an der internen Steuerung vornehmen müssen.

                        Bitte stellen Sie sicher, dass die externe Steuerung korrekt eingerichtet ist, um den gewünschten PV-optimierten Ladevorgang zu ermöglichen.

                        Die Aussage hört sich erstmal sehr gut an. Überschreiben ist simpelster kämpfen hier nicht zwei Regelsysteme gegeneinander? Auch meine zwischenzeitlichen Erfahrungen können diese Aussage nicht bestätigen. Ich hab die interne Steuerung für die PV optimierte Steuerung abgeschaltet und experimentiere weiter..

                        Christian Kohlöffel 1 Reply Last reply Reply Quote 1
                        • Christian Kohlöffel
                          Christian Kohlöffel @OpaW last edited by

                          @opaw , leider hab ich nur die DE Edition, welche keine internen Features wie Strom und Spannungsmessungen hat. Aber ich muss sagen, der Adapter von sneak funktioniert bei der PV Regelung und der Schaltung meist wie er soll, also wenn Du es schaffst das Eigenverhalten der Box abzustellen, dann hast du gute Chancen damit eine gute PV Abhängige Regelung hin zu bekommen.

                          @opaw sagte in [Frage] Realisierung Adapter UDP Keba Wallbox:

                          Dar x2 Schaltbefehl funktionier bei mir in dem Moment wenn ich in der Webui (P30X) auf UDP umgestaltet hab

                          Ohne UDP kanns ja nicht funktionieren, da der Adapter zur Kommunikation UDP verwendet, oder?

                          @opaw sagte in [Frage] Realisierung Adapter UDP Keba Wallbox:

                          Ein Umschalten des State X2phaseSource über den Adapter funktioniert nicht. Der Adapter springt nach kurzer Zeit wieder auf den alten Wert zurück.

                          Bist du schon im Active Mode im Adapter, normal dürfte er für min. 300s nicht zurückschalten können wenn er mal gesetzt ist. Was sagt er im Log dazu?

                          1 Reply Last reply Reply Quote 0
                          • S
                            Sneak-L8 @Christian Kohlöffel last edited by

                            @christian-kohlöffel Danke für den Fork.

                            Ich hätte jetzt keine Config-Option für den Timeout zum Umschalten 1p/3p gemacht, da der wohl für alle Boxen gleich sein dürfte. Und wenn nicht, dann könnte man das auch je Modell einstellen, die Erkennung ist ja schon da.
                            Gnauer habe ich es noch nicht angeschaut, bin noch eine Weile unterwegs ...

                            1 Reply Last reply Reply Quote 0
                            • Christian Kohlöffel
                              Christian Kohlöffel last edited by Christian Kohlöffel

                              @sneak-l8 sagte in [Frage] Realisierung Adapter UDP Keba Wallbox:

                              Ich hätte jetzt keine Config-Option für den Timeout zum Umschalten 1p/3p gemacht, da der wohl für alle Boxen gleich sein dürfte

                              Ja, da hast du wohl recht. Aber am Anfang war mir das noch nicht klar. Vielleicht macht es ja Sinn diese drin zu lassen um das hin und her schalten bei nicht S10 basierten Systemen zu verzögern? Aber ob das variabel sein muss ist fraglich.
                              Mal schauen, vielleicht baue ich es ja wieder raus, wenn das Wetter die nächsten Tage so bleibt 🙂

                              Update, es ging doch sehr schnell:
                              https://github.com/iobroker-community-adapters/ioBroker.kecontact/compare/master...christi-ko:ioBroker.kecontact:master

                              S 1 Reply Last reply Reply Quote 1
                              • S
                                Sneak-L8 @Christian Kohlöffel last edited by

                                @christian-kohlöffel Sorry, sehe nicht ,dass es zurückgebaut wäre auf einen festen Wert. Konfig ist immer noch drin, oder? Letzter Commit ist vom 11. August. Evtl. Push vergessen?

                                Christian Kohlöffel 1 Reply Last reply Reply Quote 0
                                • Christian Kohlöffel
                                  Christian Kohlöffel @Sneak-L8 last edited by

                                  @sneak-l8 Ich hab da mal eine Pull request gemacht. Dort sollte es drin sein ...
                                  https://github.com/iobroker-community-adapters/ioBroker.kecontact/pulls

                                  S 1 Reply Last reply Reply Quote 0
                                  • S
                                    Sneak-L8 @Christian Kohlöffel last edited by

                                    @christian-kohlöffel Ne, da ist leider auch noch die Konfig erweitert.

                                    Christian Kohlöffel 1 Reply Last reply Reply Quote 0
                                    • Christian Kohlöffel
                                      Christian Kohlöffel @Sneak-L8 last edited by

                                      @sneak-l8 Gibts doch nicht. Ich habe es hier Committet, oder?

                                      https://github.com/iobroker-community-adapters/ioBroker.kecontact/pull/234/commits/244b10a505ae54e9282706ae023393dcd92b5dc3

                                      christi-ko created this issue in iobroker-community-adapters/ioBroker.kecontact

                                      closed Pull request for introduction of min 1P3P switching if done via X2. #234

                                      Christian Kohlöffel S 2 Replies Last reply Reply Quote 0
                                      • Christian Kohlöffel
                                        Christian Kohlöffel @Christian Kohlöffel last edited by

                                        @Sneak-L8 Ich will jetzt nicht meine Hand ins Feuer dafür legen, vielleicht hab ich es ja auch irgendwo vergessen und nicht in allen files raus genommen. Ist ja doch irgendwie an vielen Stellen nötig gewesen rein zu bauen ...

                                        1 Reply Last reply Reply Quote 0
                                        • S
                                          Sneak-L8 @Christian Kohlöffel last edited by

                                          @christian-kohlöffel Ich glaube, ich verstehe jetzt.

                                          Ich hab erstmal falsch geschaut. Im PR stehen die ältesten Commits oben, hatte den neusten erwartet. Die Änderung sind also doch da.
                                          Aber Du hast nicht alles zurückgenommen. Z.B. .create-adapter.json enthält noch den neuen Wert und in den Translations ist es auch noch alles drin.

                                          Danach wäre es eigentlich optimimal, wenn Du Deine Commits zu einem zusammen-squashst. (Das hab ich selbst aber noch nicht gemacht, weil ich mit VSC noch nicht so recht weiß, wo). Aber das ist nicht ganz so wild, beim PR sieht man ja die "overall"-Änderung und sieht dann, dass nur weniges Stellen geändert wurden.

                                          Christian Kohlöffel 1 Reply Last reply Reply Quote 0
                                          • Christian Kohlöffel
                                            Christian Kohlöffel @Sneak-L8 last edited by

                                            @sneak-l8 Ich hab die Änderung gerade noch in create-adapter.json gemacht. Sonst habe ich glaub alles Stellen erwischt. Bezüglich squashsen hab ich nachgelesen. Das kann man wohl direkt in GIT beim Pull Request Mergen als Option ankreuzen (https://www.git-tower.com/learn/git/faq/git-squash) .

                                            S 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            940
                                            Online

                                            31.7k
                                            Users

                                            79.7k
                                            Topics

                                            1.3m
                                            Posts

                                            68
                                            1252
                                            337813
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo