Nach Reboot keine Daten EVU Discovergy

Fragen zur Nutzung, Features, usw..
martinbrokate
Beiträge: 56
Registriert: Fr Feb 04, 2022 10:36 am
Kontaktdaten:

Nach Reboot keine Daten EVU Discovergy

Beitrag von martinbrokate »

Hallo zusammen,
habe seit gestern eine neue Custom (Series 2+, ohne Display)
Bin noch dabei diverse Module einzurichten. Habe hier schon über einige Probleme mit dem Discovergy Modul gelesen, aber mein Fehler konnte ich so noch nicht zuordnen.
Schalte ich die Box aus, oder reboote ich sie, so empfängt sie anschließend keine daten mehr vom EVU Zähler (Discovergy) Hatte ihn gestern erfolgreich eingerichtet, aber heute morgen dann keine Daten mehr.

Was hilft ist der Update Button, also wenn ich die vorhandene Version noch mal draufspiele. (Habe nur den EVU Zähler, der Produktionszähler lässt noch auf sich warten)
Protokollierung ist aktiv, aber wie komme ich an die Datei ran?
Ich hoffe hierzu hat jemand ne Idee. Ich habe von allen Version Sicherungen angelegt, 1.9.244 St, 254 BE, und 255 NI. Leider tritt der Fehler in jeder Version bei einem Neustart oder ShutDown auf. Aktuell ist die 255 NI drauf.
Alle Relevanten Zähler + OPEN WB werden über DHCP verwaltet, aber mit einer aus der Box zugewiesenen festen Adresse.

1. Bild nach Update, 2. Bild nach Reboot.
Dateianhänge
Screenshot 2022-02-10 130715.jpg
Screenshot 2022-02-10 125727.jpg
PV 4,32kwp aus 2003, PV 5,4kwp aus 2010, PV 42,21kwp aus 2010 mit oWB Custom aus 2022, und EQA 250.
derNeueDet
Beiträge: 4395
Registriert: Mi Nov 11, 2020 7:16 pm
Has thanked: 1 time
Been thanked: 14 times

Re: Nach Reboot keine Daten EVU Discovergy

Beitrag von derNeueDet »

Die Protokolle findest du unter dem Reiter Status. Wenn du da ganz nach unten gehst, findest du das Debug log. Poste mal einen Teil hier rein.

VG
det
10kWp PV mit SMA Tripower 10000TL-10 (PE11 mit SDM72V2); 2,4kWp mit Solis 2.5 G6 (EE11 mit SDM120). OpenWB Standard+. EVU EM540 an einem Raspi mit Venus OS. BEV Mercedes EQA 250 (07/2023) und EQA 300 (06/2024)
martinbrokate
Beiträge: 56
Registriert: Fr Feb 04, 2022 10:36 am
Kontaktdaten:

Re: Nach Reboot keine Daten EVU Discovergy

Beitrag von martinbrokate »

Jo besten dank. Mach ich. Da ich noch kein Produktionszähler habe, habe ich mal versucht die Sunny Webbox einzubinden. Nicht wundern wenn s hier mit im Protokoll steht.
PV 4,32kwp aus 2003, PV 5,4kwp aus 2010, PV 42,21kwp aus 2010 mit oWB Custom aus 2022, und EQA 250.
martinbrokate
Beiträge: 56
Registriert: Fr Feb 04, 2022 10:36 am
Kontaktdaten:

Re: Nach Reboot keine Daten EVU Discovergy

Beitrag von martinbrokate »

2022-02-10 14:41:18: **** FATAL ********************************* (LV0) at 61 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:41:18: **** FATAL Regulation loop needs 27 seconds (LV0) at 60 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:41:18: **** FATAL ********************************* (LV0) at 59 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:41:17: Timing Umschaltung: 480 / 480 (LV1) at 15 u1p3pswitch u1p3p.sh
2022-02-10 14:41:17: automatische Umschaltung aktiv (LV1) at 14 u1p3pswitch u1p3p.sh
2022-02-10 14:41:17: Zeit zum abfragen aller Werte 26 Sekunden (LV1) at 176 main /var/www/html/openWB/regel.sh
2022-02-10 14:41:16: chargestatlp1 0 chargestatlp2 0 chargestatlp3 0 (LV1) at 1275 loadvars loadvars.sh
2022-02-10 14:41:16: plugstatlp1 0 plugstatlp2 0 plugstatlp3 0 (LV1) at 1274 loadvars loadvars.sh
2022-02-10 14:41:16: lp1enabled 1 lp2enabled 1 lp3enabled 1 (LV1) at 1273 loadvars loadvars.sh
2022-02-10 14:41:16: EVU 1:V/-18A 2: V/-18A 3: V/-18A (LV1) at 1272 loadvars loadvars.sh
2022-02-10 14:41:16: lla3 0 llv3 0.0 llas13 llas23 soclp1 0 soclp2 (LV1) at 1271 loadvars loadvars.sh
2022-02-10 14:41:16: lla2 0 llv2 0.0 llas12 llas22 sofortll 17 hausverbrauch 0 wattbezug -12852 uberschuss 12852 (LV1) at 1270 loadvars loadvars.sh
2022-02-10 14:41:16: lla1 0 llv1 235.9 llas11 llas21 mindestuberschuss 1500 abschaltuberschuss 5 lademodus 3 (LV1) at 1269 loadvars loadvars.sh
2022-02-10 14:41:16: pv1watt -11594 pv2watt pvwatt -11594 ladeleistung 0 llalt 0 nachtladen 1 nachtladen 0 minimalA 6 maximalA 17 (LV1) at 1268 loadvars loadvars.sh
2022-02-10 14:41:16: PID: 13334: legacy run server: Completed running command in 20.05s: ["modules.discovergy.device","martinbrokate@web.de","D7-tqZg!KVYdkSX","ff664211d9d04f62b1e90fb61d3f3
2022-02-10 14:41:16: PID: 13334: Discovergy: Update completed
2022-02-10 14:41:15: PID: 13334: requests.packages.urllib3.connectionpool: Starting new HTTPS connection (1): api.discovergy.com:443
2022-02-10 14:41:15: PID: 13334: Discovergy: Beginning update
2022-02-10 14:41:15: PID: 13334: legacy run server: Received command ["modules.discovergy.device","martinbrokate@web.de","D7-tqZg!KVYdkSX","ff664211d9d04f62b1e90fb61d3f3
2022-02-10 14:41:14: PID: 6905: SMA ModbusTCP WR: Update completed successfully
2022-02-10 14:41:14: PID: 6905: ValueStore: Saving InverterState(counter=477202921.0, currents=[0, 0, 0], power=-11594)
2022-02-10 14:41:14: PID: 6905: requests.packages.urllib3.connectionpool: http://192.168.178.100:80 "POST /rpc HTTP/1.1" 200 398
2022-02-10 14:41:14: PID: 6905: requests.packages.urllib3.connectionpool: Starting new HTTP connection (1): 192.168.178.100:80
2022-02-10 14:41:14: PID: 6905: SMA ModbusTCP WR: Beginning update
2022-02-10 14:41:11: **** Regulation loop start **** (LV1) at 70 main /var/www/html/openWB/regel.sh
2022-02-10 14:41:08: **** FATAL ********************************* (LV0) at 61 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:41:08: **** FATAL Regulation loop needs 27 seconds (LV0) at 60 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:41:08: **** FATAL ********************************* (LV0) at 59 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:41:08: Timing Umschaltung: 480 / 480 (LV1) at 15 u1p3pswitch u1p3p.sh
2022-02-10 14:41:08: automatische Umschaltung aktiv (LV1) at 14 u1p3pswitch u1p3p.sh
2022-02-10 14:41:08: Zeit zum abfragen aller Werte 27 Sekunden (LV1) at 176 main /var/www/html/openWB/regel.sh
2022-02-10 14:41:07: chargestatlp1 0 chargestatlp2 0 chargestatlp3 0 (LV1) at 1275 loadvars loadvars.sh
2022-02-10 14:41:07: plugstatlp1 0 plugstatlp2 0 plugstatlp3 0 (LV1) at 1274 loadvars loadvars.sh
2022-02-10 14:41:07: lp1enabled 1 lp2enabled 1 lp3enabled 1 (LV1) at 1273 loadvars loadvars.sh




2022-02-10 14:40:41: **** Regulation loop start **** (LV1) at 70 main /var/www/html/openWB/regel.sh
2022-02-10 14:40:41: **** FATAL ********************************* (LV0) at 61 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:40: **** FATAL Regulation loop needs 9 seconds (LV0) at 60 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:40: **** FATAL ********************************* (LV0) at 59 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:39: **** FATAL ********************************* (LV0) at 61 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:39: **** FATAL ********************************* (LV0) at 61 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:39: **** FATAL Regulation loop needs 28 seconds (LV0) at 60 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:39: **** FATAL Regulation loop needs 18 seconds (LV0) at 60 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:39: **** FATAL ********************************* (LV0) at 59 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:39: **** FATAL ********************************* (LV0) at 59 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:38: Timing Umschaltung: 480 / 480 (LV1) at 15 u1p3pswitch u1p3p.sh
2022-02-10 14:40:38: automatische Umschaltung aktiv (LV1) at 14 u1p3pswitch u1p3p.sh
2022-02-10 14:40:38: Zeit zum abfragen aller Werte 7 Sekunden (LV1) at 176 main /var/www/html/openWB/regel.sh
2022-02-10 14:40:37: Timing Umschaltung: 480 / 480 (LV1) at 15 u1p3pswitch u1p3p.sh
2022-02-10 14:40:37: automatische Umschaltung aktiv (LV1) at 14 u1p3pswitch u1p3p.sh
2022-02-10 14:40:37: Timing Umschaltung: 480 / 480 (LV1) at 15 u1p3pswitch u1p3p.sh
2022-02-10 14:40:37: automatische Umschaltung aktiv (LV1) at 14 u1p3pswitch u1p3p.sh
2022-02-10 14:40:37: Zeit zum abfragen aller Werte 26 Sekunden (LV1) at 176 main /var/www/html/openWB/regel.sh
2022-02-10 14:40:37: Zeit zum abfragen aller Werte 16 Sekunden (LV1) at 176 main /var/www/html/openWB/regel.sh
2022-02-10 14:40:37: chargestatlp1 0 chargestatlp2 0 chargestatlp3 0 (LV1) at 1275 loadvars loadvars.sh
2022-02-10 14:40:37: plugstatlp1 0 plugstatlp2 0 plugstatlp3 0 (LV1) at 1274 loadvars loadvars.sh
2022-02-10 14:40:36: lp1enabled 1 lp2enabled 1 lp3enabled 1 (LV1) at 1273 loadvars loadvars.sh
2022-02-10 14:40:36: EVU 1:V/-18A 2: V/-18A 3: V/-18A (LV1) at 1272 loadvars loadvars.sh
2022-02-10 14:40:36: lla3 0 llv3 0.0 llas13 llas23 soclp1 0 soclp2 (LV1) at 1271 loadvars loadvars.sh
2022-02-10 14:40:36: lla2 0 llv2 0.0 llas12 llas22 sofortll 17 hausverbrauch 0 wattbezug -12852 uberschuss 12852 (LV1) at 1270 loadvars loadvars.sh
2022-02-10 14:40:36: lla1 0 llv1 235.5 llas11 llas21 mindestuberschuss 1500 abschaltuberschuss 5 lademodus 3 (LV1) at 1269 loadvars loadvars.sh
2022-02-10 14:40:36: pv1watt -11594 pv2watt pvwatt -11594 ladeleistung 0 llalt 0 nachtladen 1 nachtladen 0 minimalA 6 maximalA 17 (LV1) at 1268 loadvars loadvars.sh
2022-02-10 14:40:36: chargestatlp1 0 chargestatlp2 0 chargestatlp3 0 (LV1) at 1275 loadvars loadvars.sh
2022-02-10 14:40:36: plugstatlp1 0 plugstatlp2 0 plugstatlp3 0 (LV1) at 1274 loadvars loadvars.sh
2022-02-10 14:40:36: chargestatlp1 0 chargestatlp2 0 chargestatlp3 0 (LV1) at 1275 loadvars loadvars.sh
2022-02-10 14:40:36: lp1enabled 1 lp2enabled 1 lp3enabled 1 (LV1) at 1273 loadvars loadvars.sh
2022-02-10 14:40:36: PID: 13334: legacy run server: Completed running command in 0.41s: ["modules.discovergy.device","martinbrokate@web.de","D7-tqZg!KVYdkSX","ff664211d9d04f62b1e90fb61d3f3
2022-02-10 14:40:36: plugstatlp1 0 plugstatlp2 0 plugstatlp3 0 (LV1) at 1274 loadvars loadvars.sh
2022-02-10 14:40:36: PID: 13334: Discovergy: Update completed
2022-02-10 14:40:36: EVU 1:V/-13A 2: V/-14A 3: V/-13A (LV1) at 1272 loadvars loadvars.sh
2022-02-10 14:40:36: lp1enabled 1 lp2enabled 1 lp3enabled 1 (LV1) at 1273 loadvars loadvars.sh
2022-02-10 14:40:36: lla3 0 llv3 0.0 llas13 llas23 soclp1 0 soclp2 (LV1) at 1271 loadvars loadvars.sh
2022-02-10 14:40:36: PID: 13334: ValueStore: Saving CounterState(powers=[-4210.83, -4340.28, -4301.78], imported=287422.2511, exported=157722121.6801, voltages=[230, 230, 230], frequency=50, currents=[-18.30795652173913, -18.870782608695652, -18.703391304347825], power=-12852.89, power_factors=[0, 0, 0])
2022-02-10 14:40:36: EVU 1:V/-13A 2: V/-14A 3: V/-13A (LV1) at 1272 loadvars loadvars.sh
2022-02-10 14:40:36: PID: 13334: root: Get-Response: {"time":1644500436325,"values":{"power":-12852890,"power3":-4301780,"energyOut":1577221216801000,"power1":-4210830,"energy":2874222511000,"power2":-4340280}}
2022-02-10 14:40:36: lla2 0 llv2 0.0 llas12 llas22 sofortll 17 hausverbrauch 0 wattbezug -9592 uberschuss 9592 (LV1) at 1270 loadvars loadvars.sh
2022-02-10 14:40:36: PID: 13334: requests.packages.urllib3.connectionpool: https://api.discovergy.com:443 "GET /public/v1/last_reading?meterId=ff664211d9d04f62b1e90fb61d3f3aad HTTP/1.1" 200 None
2022-02-10 14:40:36: lla3 0 llv3 0.0 llas13 llas23 soclp1 0 soclp2 (LV1) at 1271 loadvars loadvars.sh
2022-02-10 14:40:36: lla1 0 llv1 235.5 llas11 llas21 mindestuberschuss 1500 abschaltuberschuss 5 lademodus 3 (LV1) at 1269 loadvars loadvars.sh
2022-02-10 14:40:36: lla2 0 llv2 0.0 llas12 llas22 sofortll 17 hausverbrauch 0 wattbezug -9592 uberschuss 9592 (LV1) at 1270 loadvars loadvars.sh
2022-02-10 14:40:36: pv1watt -7515 pv2watt pvwatt -7515 ladeleistung 0 llalt 0 nachtladen 1 nachtladen 0 minimalA 6 maximalA 17 (LV1) at 1268 loadvars loadvars.sh
2022-02-10 14:40:36: lla1 0 llv1 235.5 llas11 llas21 mindestuberschuss 1500 abschaltuberschuss 5 lademodus 3 (LV1) at 1269 loadvars loadvars.sh
2022-02-10 14:40:36: pv1watt -7515 pv2watt pvwatt -7515 ladeleistung 0 llalt 0 nachtladen 1 nachtladen 0 minimalA 6 maximalA 17 (LV1) at 1268 loadvars loadvars.sh
2022-02-10 14:40:36: PID: 13334: legacy run server: Completed running command in 20.09s: ["modules.discovergy.device","martinbrokate@web.de","D7-tqZg!KVYdkSX","ff664211d9d04f62b1e90fb61d3f3
2022-02-10 14:40:36: PID: 13334: Discovergy: Update completed
2022-02-10 14:40:36: PID: 13334: legacy run server: Completed running command in 10.14s: ["modules.discovergy.device","martinbrokate@web.de","D7-tqZg!KVYdkSX","ff664211d9d04f62b1e90fb61d3f3
2022-02-10 14:40:36: PID: 13334: Discovergy: Update completed
2022-02-10 14:40:36: PID: 13334: requests.packages.urllib3.connectionpool: Starting new HTTPS connection (1): api.discovergy.com:443
2022-02-10 14:40:36: PID: 13334: Discovergy: Beginning update
2022-02-10 14:40:36: PID: 13334: legacy run server: Received command ["modules.discovergy.device","martinbrokate@web.de","D7-tqZg!KVYdkSX","ff664211d9d04f62b1e90fb61d3f3
2022-02-10 14:40:35: PID: 2032: SMA ModbusTCP WR: Update completed successfully
2022-02-10 14:40:35: PID: 2032: ValueStore: Saving InverterState(currents=[0, 0, 0], counter=477202561.0, power=-11594)
2022-02-10 14:40:35: PID: 2032: requests.packages.urllib3.connectionpool: http://192.168.178.100:80 "POST /rpc HTTP/1.1" 200 398
2022-02-10 14:40:34: PID: 2032: requests.packages.urllib3.connectionpool: Starting new HTTP connection (1): 192.168.178.100:80
2022-02-10 14:40:34: PID: 2032: SMA ModbusTCP WR: Beginning update
2022-02-10 14:40:31: **** Regulation loop start **** (LV1) at 70 main /var/www/html/openWB/regel.sh
2022-02-10 14:40:28: **** FATAL ********************************* (LV0) at 61 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:28: **** FATAL Regulation loop needs 27 seconds (LV0) at 60 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:28: **** FATAL ********************************* (LV0) at 59 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:27: Timing Umschaltung: 480 / 480 (LV1) at 15 u1p3pswitch u1p3p.sh
2022-02-10 14:40:27: automatische Umschaltung aktiv (LV1) at 14 u1p3pswitch u1p3p.sh
2022-02-10 14:40:27: Zeit zum abfragen aller Werte 26 Sekunden (LV1) at 176 main /var/www/html/openWB/regel.sh
2022-02-10 14:40:26: chargestatlp1 0 chargestatlp2 0 chargestatlp3 0 (LV1) at 1275 loadvars loadvars.sh
2022-02-10 14:40:26: plugstatlp1 0 plugstatlp2 0 plugstatlp3 0 (LV1) at 1274 loadvars loadvars.sh
2022-02-10 14:40:26: lp1enabled 1 lp2enabled 1 lp3enabled 1 (LV1) at 1273 loadvars loadvars.sh
2022-02-10 14:40:26: EVU 1:V/-13A 2: V/-14A 3: V/-13A (LV1) at 1272 loadvars loadvars.sh
2022-02-10 14:40:26: lla3 0 llv3 0.0 llas13 llas23 soclp1 0 soclp2 (LV1) at 1271 loadvars loadvars.sh
2022-02-10 14:40:26: lla2 0 llv2 0.0 llas12 llas22 sofortll 17 hausverbrauch 0 wattbezug -9592 uberschuss 9592 (LV1) at 1270 loadvars loadvars.sh
2022-02-10 14:40:26: lla1 0 llv1 235.4 llas11 llas21 mindestuberschuss 1500 abschaltuberschuss 5 lademodus 3 (LV1) at 1269 loadvars loadvars.sh
2022-02-10 14:40:26: pv1watt -7515 pv2watt pvwatt -7515 ladeleistung 0 llalt 0 nachtladen 1 nachtladen 0 minimalA 6 maximalA 17 (LV1) at 1268 loadvars loadvars.sh
2022-02-10 14:40:26: PID: 13334: legacy run server: Completed running command in 20.07s: ["modules.discovergy.device","martinbrokate@web.de","D7-tqZg!KVYdkSX","ff664211d9d04f62b1e90fb61d3f3
2022-02-10 14:40:26: PID: 13334: Discovergy: Update completed
2022-02-10 14:40:26: PID: 13334: requests.packages.urllib3.connectionpool: Starting new HTTPS connection (1): api.discovergy.com:443
2022-02-10 14:40:26: PID: 13334: Discovergy: Beginning update
2022-02-10 14:40:26: PID: 13334: legacy run server: Received command ["modules.discovergy.device","martinbrokate@web.de","D7-tqZg!KVYdkSX","ff664211d9d04f62b1e90fb61d3f3
2022-02-10 14:40:24: PID: 835: SMA ModbusTCP WR: Update completed successfully
2022-02-10 14:40:24: PID: 835: ValueStore: Saving InverterState(currents=[0, 0, 0], counter=477202561.0, power=-7515)
2022-02-10 14:40:24: PID: 835: requests.packages.urllib3.connectionpool: http://192.168.178.100:80 "POST /rpc HTTP/1.1" 200 397
2022-02-10 14:40:24: PID: 835: requests.packages.urllib3.connectionpool: Starting new HTTP connection (1): 192.168.178.100:80
2022-02-10 14:40:24: PID: 835: SMA ModbusTCP WR: Beginning update
2022-02-10 14:40:21: **** Regulation loop start **** (LV1) at 70 main /var/www/html/openWB/regel.sh
2022-02-10 14:40:18: **** FATAL ********************************* (LV0) at 61 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:18: **** FATAL Regulation loop needs 27 seconds (LV0) at 60 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:18: **** FATAL ********************************* (LV0) at 59 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:17: Timing Umschaltung: 480 / 480 (LV1) at 15 u1p3pswitch u1p3p.sh
2022-02-10 14:40:17: automatische Umschaltung aktiv (LV1) at 14 u1p3pswitch u1p3p.sh
2022-02-10 14:40:17: Zeit zum abfragen aller Werte 25 Sekunden (LV1) at 176 main /var/www/html/openWB/regel.sh
2022-02-10 14:40:17: chargestatlp1 0 chargestatlp2 0 chargestatlp3 0 (LV1) at 1275 loadvars loadvars.sh
2022-02-10 14:40:17: plugstatlp1 0 plugstatlp2 0 plugstatlp3 0 (LV1) at 1274 loadvars loadvars.sh
2022-02-10 14:40:16: lp1enabled 1 lp2enabled 1 lp3enabled 1 (LV1) at 1273 loadvars loadvars.sh
2022-02-10 14:40:16: EVU 1:V/-13A 2: V/-14A 3: V/-13A (LV1) at 1272 loadvars loadvars.sh
2022-02-10 14:40:16: lla3 0 llv3 0.0 llas13 llas23 soclp1 0 soclp2 (LV1) at 1271 loadvars loadvars.sh
2022-02-10 14:40:16: lla2 0 llv2 0.0 llas12 llas22 sofortll 17 hausverbrauch 0 wattbezug -9592 uberschuss 9592 (LV1) at 1270 loadvars loadvars.sh
2022-02-10 14:40:16: lla1 0 llv1 235.4 llas11 llas21 mindestuberschuss 1500 abschaltuberschuss 5 lademodus 3 (LV1) at 1269 loadvars loadvars.sh
2022-02-10 14:40:16: pv1watt -7515 pv2watt pvwatt -7515 ladeleistung 0 llalt 0 nachtladen 1 nachtladen 0 minimalA 6 maximalA 17 (LV1) at 1268 loadvars loadvars.sh
2022-02-10 14:40:16: PID: 13334: legacy run server: Completed running command in 20.05s: ["modules.discovergy.device","martinbrokate@web.de","D7-tqZg!KVYdkSX","ff664211d9d04f62b1e90fb61d3f3
2022-02-10 14:40:16: PID: 13334: Discovergy: Update completed
2022-02-10 14:40:16: PID: 13334: requests.packages.urllib3.connectionpool: Starting new HTTPS connection (1): api.discovergy.com:443
2022-02-10 14:40:16: PID: 13334: Discovergy: Beginning update
2022-02-10 14:40:16: PID: 13334: legacy run server: Received command ["modules.discovergy.device","martinbrokate@web.de","D7-tqZg!KVYdkSX","ff664211d9d04f62b1e90fb61d3f3
2022-02-10 14:40:15: PID: 32055: SMA ModbusTCP WR: Update completed successfully
2022-02-10 14:40:14: PID: 32055: ValueStore: Saving InverterState(currents=[0, 0, 0], counter=477202561.0, power=-7515)
2022-02-10 14:40:14: PID: 32055: requests.packages.urllib3.connectionpool: http://192.168.178.100:80 "POST /rpc HTTP/1.1" 200 397
2022-02-10 14:40:14: PID: 32055: requests.packages.urllib3.connectionpool: Starting new HTTP connection (1): 192.168.178.100:80
2022-02-10 14:40:14: PID: 32055: SMA ModbusTCP WR: Beginning update
2022-02-10 14:40:11: **** Regulation loop start **** (LV1) at 70 main /var/www/html/openWB/regel.sh
2022-02-10 14:40:09: **** FATAL ********************************* (LV0) at 61 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:09: **** FATAL Regulation loop needs 28 seconds (LV0) at 60 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:09: **** FATAL ********************************* (LV0) at 59 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:09: LP1 Modbus 0 korrekt (LV1) at 236 evsemodbuscheck evsedintest.sh
Zuletzt geändert von martinbrokate am Do Feb 10, 2022 6:18 pm, insgesamt 1-mal geändert.
PV 4,32kwp aus 2003, PV 5,4kwp aus 2010, PV 42,21kwp aus 2010 mit oWB Custom aus 2022, und EQA 250.
HSC
Beiträge: 3941
Registriert: So Jan 10, 2021 8:49 am

Re: Nach Reboot keine Daten EVU Discovergy

Beitrag von HSC »

Schau mal in Status/ EVU und poste mal den Screen davon.
Im Log wird der Zählerstand und die aktuelle Leistung ausgelesen: "counter=477202921.0, power=-11594"
Passen die Zahlenfolgen zu den Werten auf dem Zählerdisplay? Die Leistung ändert sich natürlich laufend...
VG
martinbrokate
Beiträge: 56
Registriert: Fr Feb 04, 2022 10:36 am
Kontaktdaten:

Re: Nach Reboot keine Daten EVU Discovergy

Beitrag von martinbrokate »

Habe nun mal rebootet um den Fehler zu reproduzieren.

daten aus MQTT Log:


requests.exceptions.ConnectionError: HTTPSConnectionPool(host='api.discovergy.com', port=443): Max retries exceeded with url: /public/v1/last_reading?meterId=ff664211d9d04f62b1e90fb61d3f3aad (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPSConnection object at 0x74d26a10>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',))
raise ConnectionError(e, request=request)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 487, in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 609, in send
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 488, in request
return self.request('GET', url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 501, in get
timeout=3
File "/var/www/html/openWB/packages/modules/discovergy/api.py", line 10, in get_last_reading
self.__persister(get_last_reading(session, self.__meter_id))
File "/var/www/html/openWB/packages/modules/discovergy/utils.py", line 17, in update
component.update(self.__session)
File "/var/www/html/openWB/packages/modules/discovergy/device.py", line 48, in update
Traceback (most recent call last):

During handling of the above exception, another exception occurred:

requests.packages.urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='api.discovergy.com', port=443): Max retries exceeded with url: /public/v1/last_reading?meterId=ff664211d9d04f62b1e90fb61d3f3aad (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPSConnection object at 0x74d26a10>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',))
raise MaxRetryError(_pool, url, error or ResponseError(cause))
File "/usr/local/lib/python3.5/dist-packages/urllib3/util/retry.py", line 592, in increment
method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2]
File "/usr/local/lib/python3.5/dist-packages/urllib3/connectionpool.py", line 786, in urlopen
timeout=timeout
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 423, in send
Traceback (most recent call last):

During handling of the above exception, another exception occurred:

requests.packages.urllib3.exceptions.NewConnectionError: <requests.packages.urllib3.connection.HTTPSConnection object at 0x74d26a10>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution
self, "Failed to establish a new connection: %s" % e
File "/usr/local/lib/python3.5/dist-packages/urllib3/connection.py", line 187, in _new_conn
conn = self._new_conn()
File "/usr/local/lib/python3.5/dist-packages/urllib3/connection.py", line 358, in connect
conn.connect()
File "/usr/local/lib/python3.5/dist-packages/urllib3/connectionpool.py", line 1040, in _validate_conn
self._validate_conn(conn)
File "/usr/local/lib/python3.5/dist-packages/urllib3/connectionpool.py", line 386, in _make_request
chunked=chunked,
File "/usr/local/lib/python3.5/dist-packages/urllib3/connectionpool.py", line 710, in urlopen
Traceback (most recent call last):

During handling of the above exception, another exception occurred:

socket.gaierror: [Errno -3] Temporary failure in name resolution
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
File "/usr/lib/python3.5/socket.py", line 733, in getaddrinfo
for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
File "/usr/local/lib/python3.5/dist-packages/urllib3/util/connection.py", line 72, in create_connection
(self._dns_host, self.port), self.timeout, **extra_kw
File "/usr/local/lib/python3.5/dist-packages/urllib3/connection.py", line 175, in _new_conn
Traceback (most recent call last):
2022-02-10 15:01:37: PID: 2054: root: Discovergy Zähler: FaultState FaultStateLevel.ERROR, FaultStr Die Verbindung zum Server https://api.discovergy.com/public/v1/la ... b61d3f3aad ist fehlgeschlagen. Überprüfe Adresse und Netzwerk., Traceback:
2022-02-10 15:01:36: PID: 2054: requests.packages.urllib3.connectionpool: Starting new HTTPS connection (1): api.discovergy.com:443
2022-02-10 15:01:36: PID: 2054: Discovergy: Beginning update
2022-02-10 15:01:36: PID: 2054: legacy run server: Received command ["modules.discovergy.device","martinbrokate@web.de","D7-tqZg!KVYdkSX","ff664211d9d04f62b1e90fb61d3f3
2022-02-10 15:01:35: PID: 381: SMA ModbusTCP WR: Update completed successfully
2022-02-10 15:01:35: PID: 381: ValueStore: Saving InverterState(power=-6180, counter=477205449.0, currents=[0, 0, 0])
2022-02-10 15:01:35: PID: 381: requests.packages.urllib3.connectionpool: http://192.168.178.100:80 "POST /rpc HTTP/1.1" 200 397
2022-02-10 15:01:35: PID: 381: requests.packages.urllib3.connectionpool: Starting new HTTP connection (1): 192.168.178.100:80
2022-02-10 15:01:35: PID: 381: SMA ModbusTCP WR: Beginning update
2022-02-10 15:01:32: **** Regulation loop start **** (LV1) at 70 main /var/www/html/openWB/regel.sh
2022-02-10 15:01:28: **** FATAL ********************************* (LV0) at 61 cleanup /var/www/html/openWB/regel.sh
2022-02-10 15:01:28: **** FATAL Regulation loop needs 27 seconds (LV0) at 60 cleanup /var/www/html/openWB/regel.sh
2022-02-10 15:01:28: **** FATAL ********************************* (LV0) at 59 cleanup /var/www/html/openWB/regel.sh
2022-02-10 15:01:28: Timing Umschaltung: 480 / 480 (LV1) at 15 u1p3pswitch u1p3p.sh
2022-02-10 15:01:28: automatische Umschaltung aktiv (LV1) at 14 u1p3pswitch u1p3p.sh
2022-02-10 15:01:28: Zeit zum abfragen aller Werte 26 Sekunden (LV1) at 176 main /var/www/html/openWB/regel.sh
2022-02-10 15:01:27: chargestatlp1 0 chargestatlp2 0 chargestatlp3 0 (LV1) at 1275 loadvars loadvars.sh
2022-02-10 15:01:27: plugstatlp1 0 plugstatlp2 0 plugstatlp3 0 (LV1) at 1274 loadvars loadvars.sh
2022-02-10 15:01:27: lp1enabled 1 lp2enabled 1 lp3enabled 1 (LV1) at 1273 loadvars loadvars.sh
2022-02-10 15:01:27: EVU 1:V/-8A 2: V/-9A 3: V/-9A (LV1) at 1272 loadvars loadvars.sh
2022-02-10 15:01:27: lla3 0 llv3 0.0 llas13 llas23 soclp1 0 soclp2 (LV1) at 1271 loadvars loadvars.sh
2022-02-10 15:01:27: lla2 0 llv2 0.0 llas12 llas22 sofortll 17 hausverbrauch 0 wattbezug -6370 uberschuss 6370 (LV1) at 1270 loadvars loadvars.sh
2022-02-10 15:01:27: lla1 0 llv1 236.2 llas11 llas21 mindestuberschuss 1500 abschaltuberschuss 5 lademodus 3 (LV1) at 1269 loadvars loadvars.sh
2022-02-10 15:01:27: pv1watt -6180 pv2watt pvwatt -6180 ladeleistung 0 llalt 0 nachtladen 1 nachtladen 0 minimalA 6 maximalA 17 (LV1) at 1268 loadvars loadvars.sh
2022-02-10 15:01:26: PID: 2054: legacy run server: Completed running command in 20.05s: ["modules.discovergy.device","martinbrokate@web.de","D7-tqZg!KVYdkSX","ff664211d9d04f62b1e90fb61d3f3
2022-02-10 15:01:26: PID: 2054: Discovergy: Update completed

requests.exceptions.ConnectionError: HTTPSConnectionPool(host='api.discovergy.com', port=443): Max retries exceeded with url: /public/v1/last_reading?meterId=ff664211d9d04f62b1e90fb61d3f3aad (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPSConnection object at 0x74d3a3b0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',))
raise ConnectionError(e, request=request)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 487, in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 609, in send
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 488, in request
return self.request('GET', url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 501, in get
timeout=3
File "/var/www/html/openWB/packages/modules/discovergy/api.py", line 10, in get_last_reading
self.__persister(get_last_reading(session, self.__meter_id))
File "/var/www/html/openWB/packages/modules/discovergy/utils.py", line 17, in update
component.update(self.__session)
File "/var/www/html/openWB/packages/modules/discovergy/device.py", line 48, in update
Traceback (most recent call last):

During handling of the above exception, another exception occurred:
Zuletzt geändert von martinbrokate am Do Feb 10, 2022 6:15 pm, insgesamt 1-mal geändert.
PV 4,32kwp aus 2003, PV 5,4kwp aus 2010, PV 42,21kwp aus 2010 mit oWB Custom aus 2022, und EQA 250.
martinbrokate
Beiträge: 56
Registriert: Fr Feb 04, 2022 10:36 am
Kontaktdaten:

Re: Nach Reboot keine Daten EVU Discovergy

Beitrag von martinbrokate »

Discovergy Daten (Mitte) passen nicht, der hängt fest. Müsste 39irgendwas sein und nicht 6370.
Dateianhänge
2.jpg
PV 4,32kwp aus 2003, PV 5,4kwp aus 2010, PV 42,21kwp aus 2010 mit oWB Custom aus 2022, und EQA 250.
LutzB
Beiträge: 3707
Registriert: Di Feb 25, 2020 9:23 am
Been thanked: 5 times

Re: Nach Reboot keine Daten EVU Discovergy

Beitrag von LutzB »

Nimm mal schnell Deine privaten Anmeldedaten aus dem Log raus!
martinbrokate
Beiträge: 56
Registriert: Fr Feb 04, 2022 10:36 am
Kontaktdaten:

Re: Nach Reboot keine Daten EVU Discovergy

Beitrag von martinbrokate »

Danke!! Hab neue Passwörter vergeben.

So nach dem ich das auto-generierte Passwort gewechselt habe, habe ich die oWB nun per Netzwerk Kabel angeschlossen. Obwohl die WLan Verbindung nie weg war, kann es sein das das WLan Modul ganz schön Rechen Leistung braucht?
Habe den obigen Text in den Postings mal gehörig eingekürzt, dabei den Begriff "FATAL" bemerkt, Dies taucht nun mit LAN Anbindung nicht mehr auf. Kanns das schon gewesen sein, oder was bedeutet das sonst?

2022-02-10 14:40:41: **** Regulation loop start **** (LV1) at 70 main /var/www/html/openWB/regel.sh
2022-02-10 14:40:41: **** FATAL ********************************* (LV0) at 61 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:40: **** FATAL Regulation loop needs 9 seconds (LV0) at 60 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:40: **** FATAL ********************************* (LV0) at 59 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:39: **** FATAL ********************************* (LV0) at 61 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:39: **** FATAL ********************************* (LV0) at 61 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:39: **** FATAL Regulation loop needs 28 seconds (LV0) at 60 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:39: **** FATAL Regulation loop needs 18 seconds (LV0) at 60 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:39: **** FATAL ********************************* (LV0) at 59 cleanup /var/www/html/openWB/regel.sh
2022-02-10 14:40:39: **** FATAL ********************************* (LV0) at 59 cleanup /var/www/html/openWB/regel.sh
PV 4,32kwp aus 2003, PV 5,4kwp aus 2010, PV 42,21kwp aus 2010 mit oWB Custom aus 2022, und EQA 250.
martinbrokate
Beiträge: 56
Registriert: Fr Feb 04, 2022 10:36 am
Kontaktdaten:

Re: Nach Reboot keine Daten EVU Discovergy

Beitrag von martinbrokate »

Vielen Dank schon mal für die schnelle Hilfe vorhin. :)
PV 4,32kwp aus 2003, PV 5,4kwp aus 2010, PV 42,21kwp aus 2010 mit oWB Custom aus 2022, und EQA 250.
Antworten