76_SMAInverter.pm - Abfrage von SMA Wechselrichter

Begonnen von sct14675, 28 Juli 2016, 11:01:16

Vorheriges Thema - Nächstes Thema

MadMax

Dann werde ich da auch noch was zu schreiben. Danke
Lenovo M910Q Tiny Debian 12, FHEM 6.3, 2x Siemens Logo 0BA7, Homematic CCU3, Philips HUE, 6x SMA Wechselrichter, BYD HVM, BYD HVS, SMA EVCharger, KEBA Wallbox, 2x HMS800W, Daikin Wärmepumpe über CAN, viele ESPs

Contrib: https://svn.fhem.de/trac/browser/trunk/fhem/contrib/MadMax

300P

Hinweis:

LG ruft aufgrund eines Vorkommnisses einige nun neu betroffene Batterien wohl zurück 🫣

Bei mir ist die eine LG10HRESU mit BJ  2019 nun auch mit betroffen.
Eine zweite LG10HRESU mit BJ 2020 ist aktuell nicht davon betroffen 😇

Beide werden jeweils an einem eigenen SMA-Batteriewechselrichter (SBS25) unabhängig voneinander betrieben.
Der Rückruf ist, wenn notwendig, wohl aber scheinbar unabhängig vom BWR-Hersteller.

Hier ein Link (warum wieso weshalb weswegen)

Info zu LG10HRESU

Das Thema Rückruf sollte aber in diesem Thread nicht weiter diskutiert werden 😉

Gruß
300P
Gruß
300P

FHEM 6.4|RPi|SMAEM|SMAInverter|SolarForecast|DbLog|DbRep|MariaDB|Buderus-MQTT_EMS|
Fritzbox|fhempy|JsonMod|HTTPMOD|Modbus ser+TCP|ESP32-Digitizer-AI_on_the_Edge|ESP32CAM usw.

300P

#1817
@MadMax:

Ich habe meinen SBS25 gegen einen SBS37 getauscht um eine LG16H-Prime anschliessen und betreiben zu können.

Der Batteriewechselrichter SBS37 liefert im Attribute ,,state" jetzt blöderweise Texte ☹️ wenn die Batterie 100 % voll ist, die Batterie im standby ist oder sich die Batterie ausgeschaltet hat statt einfach eine Leistung von ,,0" zu übermitteln.

Das ergibt dann einiges an Fehlermeldungen im Log.

025.04.04 14:16:19 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.04 14:16:34 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.04 14:16:44 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.04 14:16:58 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.04 14:17:19 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.04 14:17:26 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.04 14:17:50 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.04 14:17:56 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.04 14:18:11 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.04 14:18:35 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.04 14:18:40 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.04 14:18:56 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.04 14:19:12 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.

Kannst du dir das mal ansehen damit der Fehler vermieden wird.

Gruß und Danke im Voraus
300P
Gruß
300P

FHEM 6.4|RPi|SMAEM|SMAInverter|SolarForecast|DbLog|DbRep|MariaDB|Buderus-MQTT_EMS|
Fritzbox|fhempy|JsonMod|HTTPMOD|Modbus ser+TCP|ESP32-Digitizer-AI_on_the_Edge|ESP32CAM usw.

fis14

#1818
Moin,
das fällt gar nicht so ins Auge
ein Reading ist stehen geblieben  :)

Zeile 1395 ist ein vertipper drin

Gruß
Falk

MadMax

#1819
Zitat von: 300P am 04 April 2025, 14:23:22@MadMax:

Ich habe meinen SBS25 gegen einen SBS37 getauscht um eine LG16H-Prime anschliessen und betreiben zu können.

Der Batteriewechselrichter SBS37 liefert im Attribute ,,state" jetzt blöderweise Texte ☹️ wenn die Batterie 100 % voll ist, die Batterie im standby ist oder sich die Batterie ausgeschaltet hat statt einfach eine Leistung von ,,0" zu übermitteln.

Das ergibt dann einiges an Fehlermeldungen im Log.

025.04.04 14:16:19 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.04 14:16:34 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.04 14:16:44 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.04 14:16:58 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.04 14:17:19 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.04 14:17:26 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.04 14:17:50 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.04 14:17:56 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.04 14:18:11 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.04 14:18:35 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.04 14:18:40 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.04 14:18:56 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.04 14:19:12 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.

Kannst du dir das mal ansehen damit der Fehler vermieden wird.

Gruß und Danke im Voraus
300P


Hallo 300p,

welche Version nutzt du vom Modul?

Zeile 2273:
$inv_BAT_TEMP = 0;

Das ist  zwar der bereich vom SBS3.7 aber in der Zeile wird der Fehler nicht sein.
Aktualisiere bitte mal das Moduel und schaue dann nach den Meldungen.

Gruß
Max

Ich korrigiren, in meiner Testversion bin ich 5 Zeilen weiter...

Bitte schick mir mal das Vollständige Log (verbose 5), der SBS3.7 kann ja drei Batterien, scheinbar kommt von Batterie 2 keine Daten (Temperatur), oder du hast keine und dies ist nicht korrekt abgefangen.

if(($inv_BAT_TEMP_B eq -2147483648) || ($inv_BAT_TEMP_B eq 0x80000000) || $inv_BAT_TEMP_B < 0) {$inv_BAT_TEMP_B = "-"; } else {$inv_BAT_TEMP_B = $inv_BAT_TEMP_B / 10; $count = $count + 1; $inv_BAT_TEMP = $inv_BAT_TEMP + $inv_BAT_TEMP_B;}
Lenovo M910Q Tiny Debian 12, FHEM 6.3, 2x Siemens Logo 0BA7, Homematic CCU3, Philips HUE, 6x SMA Wechselrichter, BYD HVM, BYD HVS, SMA EVCharger, KEBA Wallbox, 2x HMS800W, Daikin Wärmepumpe über CAN, viele ESPs

Contrib: https://svn.fhem.de/trac/browser/trunk/fhem/contrib/MadMax

MadMax

Zitat von: fis14 am 04 April 2025, 14:46:29Moin,
das fällt gar nicht so ins Auge
ein Reading ist stehen geblieben  :)

Zeile 1395 ist ein vertipper drin

Gruß
Falk

Gefunden, wird bein nächten update behoben.
Lenovo M910Q Tiny Debian 12, FHEM 6.3, 2x Siemens Logo 0BA7, Homematic CCU3, Philips HUE, 6x SMA Wechselrichter, BYD HVM, BYD HVS, SMA EVCharger, KEBA Wallbox, 2x HMS800W, Daikin Wärmepumpe über CAN, viele ESPs

Contrib: https://svn.fhem.de/trac/browser/trunk/fhem/contrib/MadMax

300P

Zitat von: MadMax am 05 April 2025, 17:38:30Hallo 300p,

welche Version nutzt du vom Modul?

Zeile 2273:
$inv_BAT_TEMP = 0;

Das ist  zwar der bereich vom SBS3.7 aber in der Zeile wird der Fehler nicht sein.
Aktualisiere bitte mal das Moduel und schaue dann nach den Meldungen.

Gruß
Max

Ich korrigiren, in meiner Testversion bin ich 5 Zeilen weiter...

Bitte schick mir mal das Vollständige Log (verbose 5), der SBS3.7 kann ja drei Batterien, scheinbar kommt von Batterie 2 keine Daten (Temperatur), oder du hast keine und dies ist nicht korrekt abgefangen.

if(($inv_BAT_TEMP_B eq -2147483648) || ($inv_BAT_TEMP_B eq 0x80000000) || $inv_BAT_TEMP_B < 0) {$inv_BAT_TEMP_B = "-"; } else {$inv_BAT_TEMP_B = $inv_BAT_TEMP_B / 10; $count = $count + 1; $inv_BAT_TEMP = $inv_BAT_TEMP + $inv_BAT_TEMP_B;}

Hallo MadMax,

meine genutzte Version ist diejenige, die beim normalen Update geladen wird :

- 76_SMAInverter.pm:v2.29.2-s29472/2025-01-02

Ich habe 1 x Batterie LG10HRESU an dem SBS37 angeschlossen.

Gruß
300P

Hier das Log (verbose 5)
2025.04.05 18:28:01 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.05 18:28:15 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
2025.04.05 18:28:29 4: SBS37 - ###############################################################
2025.04.05 18:28:29 4: SBS37 - ##########  Begin of new SMAInverter get data cycle  ##########
2025.04.05 18:28:29 4: SBS37 - ###############################################################
2025.04.05 18:28:29 4: SBS37 - timeout cycles since module start: 1475, Interval: 15
2025.04.05 18:28:29 4: SBS37 - start BlockingCall
2025.04.05 18:28:30 4: SBS37 - running BlockingCall SMAInverter_getstatusDoParse
2025.04.05 18:28:30 4: SBS37 -> INVCLASS 8007
2025.04.05 18:28:30 4: SBS37 -> INVTYPE 9356
2025.04.05 18:28:30 4: SBS37 -> start BlockingCall SMAInverter_getstatusDoParse
2025.04.05 18:28:30 4: SBS37 - current time: 05.04.2025 18:28:30
2025.04.05 18:28:30 4: SBS37 - operation time begin: 05.04.2025 06:21:59
2025.04.05 18:28:30 4: SBS37 - operation time end: 05.04.2025 20:42:01
2025.04.05 18:28:30 4: SBS37 - detail-level: 2
2025.04.05 18:28:30 5: SBS37 - SBS3.7-1VL-10 (Sunny Boy Storage 3.7)
2025.04.05 18:28:30 4: SBS37 - Send login to 192.168.1xx.1xx on Port 9522 with password 12345678 as installer
2025.04.05 18:28:30 5: SBS37 - Send: 534D4100000402A000000001003A001060650EA06901F7C112B40001E90023BB590700010000000001800C04FDFF0A000000840300002E5AF16700000000ECDC0E302B202D2B2A32202D00000000
2025.04.05 18:28:30 5: SBS37 - Received: 534d4100000402a000000001002e001060650be0e90023bb590700016901f7c112b400010000000001800d04fdff0a000000840300002e5af1670000000000000000
2025.04.05 18:28:30 4: SBS37 - logged in to inverter serial: 123456783, susyid: 123
2025.04.05 18:28:30 5: SBS37 - Logged in now
2025.04.05 18:28:30 5: SBS37 -> sup_TypeLabel
2025.04.05 18:28:30 3: SBS37 - Send request 00020058001E8200FF208200 to 192.168.1xx.1xx on port 9522
2025.04.05 18:28:30 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB5907000000000000028000020058001E8200FF20820000000000
2025.04.05 18:28:30 5: SBS37 - Received: 534d4100000402a000000001009e0010606527a0e90023bb590700a06901f7c112b40000000000000280010200580100000003000000071e8210ea95f067534253332e372d31302031383300000000000000000000000000000000000000071f8208ea95f067471f0001feffff0000000000000000000000000000000000000000000000000007208208ea95f0678c2400018e2400008f240000902400009124000092240000feffff000000000000000000
2025.04.05 18:28:30 5: SBS37 - Data identifier 33310
2025.04.05 18:28:30 5: SBS37 - Found Data CLASS=8007 and TYPE=9356
2025.04.05 18:28:30 5: SBS37 -> sup_EnergyProduction
2025.04.05 18:28:30 3: SBS37 - Send request 0002005400012600FF222600 to 192.168.1xx.1xx on port 9522
2025.04.05 18:28:30 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB590700000000000003800002005400012600FF22260000000000
2025.04.05 18:28:30 5: SBS37 - Received: 534d4100000402a00000000100460010606511a0e90023bb590700a06901f7c112b40000000000000380010200540000000001000000070126002d5af16780c7000000000000072226002c5af167c60600000000000000000000
2025.04.05 18:28:30 5: SBS37 - Data identifier 9729
2025.04.05 18:28:30 5: SBS37 - Data SPOT_ETOTAL=51072 and SPOT_ETODAY=1734
2025.04.05 18:28:30 5: SBS37 -> sup_SpotDCPower
2025.04.05 18:28:30 3: SBS37 - Send request 00028053001E2500FF1E2500 to 192.168.1xx.1xx on port 9522
2025.04.05 18:28:30 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB5907000000000000048000028053001E2500FF1E250000000000
2025.04.05 18:28:30 5: SBS37 - Received: 534d4100000402a00000000100260010606509a0e90023bb590700e06901f7c112b4000015000000048001028053001e2500ff1e250000000000
2025.04.05 18:28:30 3: SBS37 - Format of inverter response does not fit.
2025.04.05 18:28:30 5: SBS37 -> sup_SpotACPower
2025.04.05 18:28:30 3: SBS37 - Send request 0002005100404600FF424600 to 192.168.1xx.1xx on port 9522
2025.04.05 18:28:30 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB590700000000000005800002005100404600FF42460000000000
2025.04.05 18:28:30 5: SBS37 - Received: 534d4100000402a000000001007a001060651ea0e90023bb590700a06901f7c112b40000000000000580010200510a0000000c000000074046402c5af1670000008000000080000000800000008001000000074146402c5af1670000000000000000000000000000000001000000074246402c5af167000000800000008000000080000000800100000000000000
2025.04.05 18:28:30 5: SBS37 - Data identifier 17984
2025.04.05 18:28:30 5: SBS37 - Found Data SPOT_PAC1=- and SPOT_PAC2=0 and SPOT_PAC3=-
2025.04.05 18:28:30 5: SBS37 -> sup_SpotACTotalPower
2025.04.05 18:28:30 3: SBS37 - Send request 00020051003F2600FF3F2600 to 192.168.1xx.1xx on port 9522
2025.04.05 18:28:30 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB5907000000000000068000020051003F2600FF3F260000000000
2025.04.05 18:28:30 5: SBS37 - Received: 534d4100000402a00000000100420010606510a0e90023bb590700a06901f7c112b40000000000000680010200510000000000000000073f26402c5af167000000000000000000000000000000000100000000000000
2025.04.05 18:28:30 5: SBS37 - Data identifier 9791
2025.04.05 18:28:30 5: SBS37 - Found Data SPOT_PACTOT=0
2025.04.05 18:28:30 5: SBS37 -> sup_ChargeStatus
2025.04.05 18:28:30 3: SBS37 - Send request 00020051005A2900FF5A2900 to 192.168.1xx.1xx on port 9522
2025.04.05 18:28:30 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB5907000000000000078000020051005A2900FF5A290000000000
2025.04.05 18:28:30 5: SBS37 - Received: 534d4100000402a00000000100420010606510a0e90023bb590700a06901f7c112b40000000000000780010200510200000002000000075a29002c5af167640000006400000064000000640000000100000000000000
2025.04.05 18:28:30 5: SBS37 - Data identifier 10586
2025.04.05 18:28:30 5: SBS37 - Found Data Battery Charge Status=100
2025.04.05 18:28:30 5: SBS37 -> sup_SpotBatteryLoad
2025.04.05 18:28:30 3: SBS37 - Send request 0002005400674900FF674900 to 192.168.1xx.1xx on port 9522
2025.04.05 18:28:30 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB590700000000000008800002005400674900FF67490000000000
2025.04.05 18:28:30 5: SBS37 - Received: 534d4100000402a0000000010036001060650da0e90023bb590700a06901f7c112b40000000000000880010200540900000009000000076749002d5af167733101000000000000000000
2025.04.05 18:28:30 5: SBS37 - Data identifier 18791
2025.04.05 18:28:30 3: SBS37 - BATTERYLOAD_TODAY wasn't delivered from inverter, try to calculate it ...
2025.04.05 18:28:30 3: SBS37 - BATTERYLOAD_TODAY calculated successfully !
2025.04.05 18:28:30 5: SBS37 - Data BAT_LOADTOTAL=78195 and BAT_LOADTODAY=3582
2025.04.05 18:28:30 5: SBS37 -> sup_SpotBatteryUnload
2025.04.05 18:28:30 3: SBS37 - Send request 0002005400684900FF684900 to 192.168.1xx.1xx on port 9522
2025.04.05 18:28:30 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB590700000000000009800002005400684900FF68490000000000
2025.04.05 18:28:30 5: SBS37 - Received: 534d4100000402a0000000010036001060650da0e90023bb590700a06901f7c112b40000000000000980010200540a0000000a000000076849002d5af16760c700000000000000000000
2025.04.05 18:28:30 5: SBS37 - Data identifier 18792
2025.04.05 18:28:30 3: SBS37 - BATTERYUNLOAD_TODAY wasn't delivered from inverter, try to calculate it ...
2025.04.05 18:28:30 3: SBS37 - BATTERYUNLOAD_TODAY calculated successfully !
2025.04.05 18:28:30 3: SBS37 - Data BAT_UNLOADTOTAL=51040 and BAT_UNLOADTODAY=1733
2025.04.05 18:28:30 5: SBS37 -> sup_BatteryInfo_UDC
2025.04.05 18:28:30 3: SBS37 - Send request 00020051005C4900105C4900 to 192.168.1xx.1xx on port 9522
2025.04.05 18:28:30 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB59070000000000000A8000020051005C4900105C490000000000
2025.04.05 18:28:30 5: SBS37 - Received: 534d4100000402a000000001007a001060651ea0e90023bb590700a06901f7c112b40000000000000a80010200514400000046000000075c49002d5af1671e0000001e0000001e0000001e00000001000000075c49002d5af167ffffffffffffffffffffffffffffffff01000000075c49002d5af167ffffffffffffffffffffffffffffffff0100000000000000
2025.04.05 18:28:30 5: SBS37 - Data identifier 18780
2025.04.05 18:28:30 5: SBS37 - Found Data and BAT_UDC=0.3 and BAT_UDC_A=0.3 and BAT_UDC_B=- and BAT_UDC_C=-
2025.04.05 18:28:30 5: SBS37 -> sup_BatteryInfo_IDC
2025.04.05 18:28:30 3: SBS37 - Send request 00020051005D4900105D4900 to 192.168.1xx.1xx on port 9522
2025.04.05 18:28:30 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB59070000000000000B8000020051005D4900105D490000000000
2025.04.05 18:28:30 5: SBS37 - Received: 534d4100000402a000000001007a001060651ea0e90023bb590700a06901f7c112b40000000000000b80010200514700000049000000075d49402d5af1670000000000000000000000000000000001000000075d49402d5af1670000008000000080000000800000008001000000075d49402d5af167000000800000008000000080000000800100000000000000
2025.04.05 18:28:30 5: SBS37 - Data identifier 18781
2025.04.05 18:28:30 5: SBS37 - Found Data and BAT_IDC=0 and BAT_IDC_A=0 and BAT_IDC_B=- and BAT_IDC_C=-
2025.04.05 18:28:30 5: SBS37 -> sup_SpotDCVoltage
2025.04.05 18:28:30 3: SBS37 - Send request 00028053001F4500FF214500 to 192.168.1xx.1xx on port 9522
2025.04.05 18:28:30 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB59070000000000000C8000028053001F4500FF21450000000000
2025.04.05 18:28:30 5: SBS37 - Received: 534d4100000402a00000000100260010606509a0e90023bb590700e06901f7c112b40000150000000c8001028053001f4500ff21450000000000
2025.04.05 18:28:30 3: SBS37 - Format of inverter response does not fit.
2025.04.05 18:28:30 5: SBS37 -> sup_SpotACVoltage
2025.04.05 18:28:30 3: SBS37 - Send request 0002005100484600FF564600 to 192.168.1xx.1xx on port 9522
2025.04.05 18:28:30 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB59070000000000000D800002005100484600FF56460000000000
2025.04.05 18:28:30 5: SBS37 - Received: 534d4100000402a000000001013e001060654fa0e90023bb590700a06901f7c112b40000000000000d80010200510d00000016000000074846002d5af167ffffffffffffffffffffffffffffffff01000000074946002d5af167f05a0000f05a0000f05a0000f05a000001000000074a46002d5af167ffffffffffffffffffffffffffffffff01000000074b46002d5af167ffffffffffffffffffffffffffffffff01000000074c46002d5af167ffffffffffffffffffffffffffffffff01000000074d46002d5af167ffffffffffffffffffffffffffffffff01000000074e46002d5af1676300000063000000630000006300000001000000075346402d5af1670000008000000080000000800000008001000000075446402d5af1670000000000000000000000000000
2025.04.05 18:28:30 5: SBS37 - Data identifier 17992
2025.04.05 18:28:30 5: SBS37 - Found Data SPOT_UAC1=- and SPOT_UAC2=232.8 and SPOT_UAC3=- and inv_SPOT_UAC1_2=- and inv_SPOT_UAC2_3=- and inv_SPOT_UAC3_1=- and inv_SPOT_CosPhi=0.99
2025.04.05 18:28:30 5: SBS37 -> sup_SpotACCurrent
2025.04.05 18:28:30 3: SBS37 - Send request 0002005100534600FF554600 to 192.168.1xx.1xx on port 9522
2025.04.05 18:28:30 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB59070000000000000E800002005100534600FF55460000000000
2025.04.05 18:28:30 5: SBS37 - Received: 534d4100000402a000000001007a001060651ea0e90023bb590700a06901f7c112b40000000000000e80010200511400000016000000075346402d5af1670000008000000080000000800000008001000000075446402d5af1670000000000000000000000000000000001000000075546402d5af167000000800000008000000080000000800100000000000000
2025.04.05 18:28:30 5: SBS37 - Data identifier 18003
2025.04.05 18:28:30 5: SBS37 - Found Data inv_SPOT_IAC1=- and inv_SPOT_IAC2=0 and inv_SPOT_IAC3=-
2025.04.05 18:28:30 5: SBS37 -> sup_SpotGridFrequency
2025.04.05 18:28:30 3: SBS37 - Send request 0002005100574600FF574600 to 192.168.1xx.1xx on port 9522
2025.04.05 18:28:30 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB59070000000000000F800002005100574600FF57460000000000
2025.04.05 18:28:30 5: SBS37 - Received: 534d4100000402a00000000100420010606510a0e90023bb590700a06901f7c112b40000000000000f80010200511700000017000000075746002d5af167841300008413000084130000841300000100000000000000
2025.04.05 18:28:30 5: SBS37 - Data identifier 18007
2025.04.05 18:28:30 5: SBS37 - Found Data SPOT_FREQ=49.96
2025.04.05 18:28:30 5: SBS37 -> sup_OperationTime
2025.04.05 18:28:30 3: SBS37 - Send request 00020054002E4600FF2F4600 to 192.168.1xx.1xx on port 9522
2025.04.05 18:28:30 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB5907000000000000108000020054002E4600FF2F460000000000
2025.04.05 18:28:30 5: SBS37 - Received: 534d4100000402a00000000100460010606511a0e90023bb590700a06901f7c112b40000000000001080010200540500000006000000072e46002d5af1671ba70f0000000000072f46002d5af16752940b000000000000000000
2025.04.05 18:28:30 5: SBS37 - Data identifier 17966
2025.04.05 18:28:30 5: SBS37 - Found Data SPOT_OPERTM=284.94 and SPOT_FEEDTM=210.79
2025.04.05 18:28:30 5: SBS37 -> sup_InverterTemperature
2025.04.05 18:28:30 3: SBS37 - Send request 0002005200772300FF772300 to 192.168.1xx.1xx on port 9522
2025.04.05 18:28:30 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB590700000000000011800002005200772300FF77230000000000
2025.04.05 18:28:30 5: SBS37 - Received: 534d4100000402a00000000100260010606509a0e90023bb590700e06901f7c112b400001500000011800102005200772300ff77230000000000
2025.04.05 18:28:30 3: SBS37 - Format of inverter response does not fit.
2025.04.05 18:28:30 5: SBS37 -> sup_MaxACPower
2025.04.05 18:28:30 3: SBS37 - Send request 00020051001E4100FF204100 to 192.168.1xx.1xx on port 9522
2025.04.05 18:28:30 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB5907000000000000128000020051001E4100FF20410000000000
2025.04.05 18:28:30 5: SBS37 - Received: 534d4100000402a000000001007a001060651ea0e90023bb590700a06901f7c112b40000000000001280010200510300000005000000071e4100235af167600e0000600e0000600e0000600e000001000000071f4100235af167000000000000000000000000000000000000000007204100235af167000000000000000000000000000000000000000000000000
2025.04.05 18:28:30 5: SBS37 - Data identifier 16670
2025.04.05 18:28:30 5: SBS37 - Found Data INV_PACMAX1=3680 and INV_PACMAX2=0 and INV_PACMAX3=0
2025.04.05 18:28:30 5: SBS37 -> sup_MaxACPower2
2025.04.05 18:28:30 3: SBS37 - Send request 00020051002A8300FF2A8300 to 192.168.1xx.1xx on port 9522
2025.04.05 18:28:30 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB5907000000000000138000020051002A8300FF2A830000000000
2025.04.05 18:28:30 5: SBS37 - Received: 534d4100000402a00000000100260010606509a0e90023bb590700e06901f7c112b4000015000000138001020051002a8300ff2a830000000000
2025.04.05 18:28:30 3: SBS37 - Format of inverter response does not fit.
2025.04.05 18:28:30 5: SBS37 -> sup_GridRelayStatus
2025.04.05 18:28:30 3: SBS37 - Send request 0002805100644100FF644100 to 192.168.1xx.1xx on port 9522
2025.04.05 18:28:30 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB590700000000000014800002805100644100FF64410000000000
2025.04.05 18:28:30 5: SBS37 - Received: 534d4100000402a000000001004e0010606513a0e90023bb590700a06901f7c112b40000000000001480010280510d0000000d000000076441082d5af1673300000037010001fdffff00feffff000000000000000000000000000000000000000000
2025.04.05 18:28:30 5: SBS37 - Data identifier 16740
2025.04.05 18:28:30 5: SBS37 - Found Data INV_GRIDRELAY=311
2025.04.05 18:28:30 5: SBS37 -> sup_DeviceStatus
2025.04.05 18:28:30 3: SBS37 - Send request 0002805100482100FF482100 to 192.168.1xx.1xx on port 9522
2025.04.05 18:28:30 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB590700000000000015800002805100482100FF48210000000000
2025.04.05 18:28:30 5: SBS37 - Received: 534d4100000402a000000001004e0010606513a0e90023bb590700a06901f7c112b40000000000001580010280510000000000000000074821082d5af16733010001feffff0000000000000000000000000000000000000000000000000000000000
2025.04.05 18:28:30 5: SBS37 - Data identifier 8520
2025.04.05 18:28:30 5: SBS37 - Found Data inv_STATUS=307
2025.04.05 18:28:30 5: SBS37 -> sup_BatteryInfo_TEMP
2025.04.05 18:28:30 3: SBS37 - Send request 00020051005B4900105B4900 to 192.168.1xx.1xx on port 9522
2025.04.05 18:28:30 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB5907000000000000168000020051005B4900105B490000000000
2025.04.05 18:28:30 5: SBS37 - Received: 534d4100000402a000000001007a001060651ea0e90023bb590700a06901f7c112b40000000000001680010200514100000043000000075b49402d5af1670000008000000080000000800000008001000000075b49402d5af1670000008000000080000000800000008001000000075b49402d5af167000000800000008000000080000000800100000000000000
2025.04.05 18:28:30 5: SBS37 - Data identifier 18779
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2273.
2025.04.05 18:28:31 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
2025.04.05 18:28:44 4: SBS37 - ###############################################################
2025.04.05 18:28:44 4: SBS37 - ##########  Begin of new SMAInverter get data cycle  ##########
2025.04.05 18:28:44 4: SBS37 - ###############################################################
2025.04.05 18:28:44 4: SBS37 - timeout cycles since module start: 1476, Interval: 15
2025.04.05 18:28:44 4: SBS37 - start BlockingCall
2025.04.05 18:28:46 4: SBS37 - running BlockingCall SMAInverter_getstatusDoParse
2025.04.05 18:28:46 4: SBS37 -> INVCLASS 8007
2025.04.05 18:28:46 4: SBS37 -> INVTYPE 9356
2025.04.05 18:28:46 4: SBS37 -> start BlockingCall SMAInverter_getstatusDoParse
2025.04.05 18:28:46 4: SBS37 - current time: 05.04.2025 18:28:46
2025.04.05 18:28:46 4: SBS37 - operation time begin: 05.04.2025 06:21:59
2025.04.05 18:28:46 4: SBS37 - operation time end: 05.04.2025 20:42:01
2025.04.05 18:28:46 4: SBS37 - detail-level: 2
2025.04.05 18:28:46 5: SBS37 - SBS3.7-1VL-10 (Sunny Boy Storage 3.7)
2025.04.05 18:28:46 4: SBS37 - Send login to 192.168.1xx.1xx on Port 9522 with password 12345678 as installer

Gruß
300P

FHEM 6.4|RPi|SMAEM|SMAInverter|SolarForecast|DbLog|DbRep|MariaDB|Buderus-MQTT_EMS|
Fritzbox|fhempy|JsonMod|HTTPMOD|Modbus ser+TCP|ESP32-Digitizer-AI_on_the_Edge|ESP32CAM usw.

300P

Nachsatz: 

Hab mal den Parameter für die Anzahl der Batterien 🔋 im SBS37 versuchsweise einfach reduziert und mal auf ,,1" gesetzt. O:-)

Da aber jetzt seit 19:00 Uhr entladen wird, kann ich den Effekt erst morgen früh sehen (sobald die Batterie wieder 100 % voll geladen ist) ob dies evtl. den von mir geschilderten Error verhindert ?!? ....  ;)
Gruß
300P

FHEM 6.4|RPi|SMAEM|SMAInverter|SolarForecast|DbLog|DbRep|MariaDB|Buderus-MQTT_EMS|
Fritzbox|fhempy|JsonMod|HTTPMOD|Modbus ser+TCP|ESP32-Digitizer-AI_on_the_Edge|ESP32CAM usw.

MadMax

Hallo 300P, im letzten Telegramm kommen für alle "drei" Batterien ungültige daten...

Im Anhang eine Version in der da Abgefangen sein sollte.
Aber dann kommt keine Temperatur mehr von der Batterie, was merkwürdig ist.

Gruß
Max
Lenovo M910Q Tiny Debian 12, FHEM 6.3, 2x Siemens Logo 0BA7, Homematic CCU3, Philips HUE, 6x SMA Wechselrichter, BYD HVM, BYD HVS, SMA EVCharger, KEBA Wallbox, 2x HMS800W, Daikin Wärmepumpe über CAN, viele ESPs

Contrib: https://svn.fhem.de/trac/browser/trunk/fhem/contrib/MadMax

300P

#1824
Hall Max,

hat noch nicht zum Erfolg geführt.  :(

Hier das Log:
2025.04.06 14:54:34 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
2025.04.06 14:54:45 4: SBS37 - ###############################################################
2025.04.06 14:54:45 4: SBS37 - ##########  Begin of new SMAInverter get data cycle  ##########
2025.04.06 14:54:45 4: SBS37 - ###############################################################
2025.04.06 14:54:45 4: SBS37 - timeout cycles since module start: 5, Interval: 15
2025.04.06 14:54:45 4: SBS37 - start BlockingCall
2025.04.06 14:54:45 4: SBS37 - running BlockingCall SMAInverter_getstatusDoParse
2025.04.06 14:54:45 4: SBS37 -> INVCLASS 0
2025.04.06 14:54:45 4: SBS37 -> INVTYPE 0
2025.04.06 14:54:45 4: SBS37 -> start BlockingCall SMAInverter_getstatusDoParse
2025.04.06 14:54:45 4: SBS37 - current time: 06.04.2025 14:54:45
2025.04.06 14:54:45 4: SBS37 - operation time begin: 06.04.2025 06:19:40
2025.04.06 14:54:45 4: SBS37 - operation time end: 06.04.2025 20:43:47
2025.04.06 14:54:45 4: SBS37 - detail-level: 2
2025.04.06 14:54:45 5: SBS37 - SBS3.7-1VL-10 (Sunny Boy Storage 3.7)
2025.04.06 14:54:45 4: SBS37 - Send login to 192.168.1XX.1XX on Port 9522 with password 123456789 as installer
2025.04.06 14:54:45 5: SBS37 - Send: 534D4100000402A000000001003A001060650EA06901F7C112B40001E90023BB590700010000000001800C04FDFF0A000000840300009579F26700000000ECDC0E302B202D2B2A32202D00000000
2025.04.06 14:54:45 5: SBS37 - Received: 534d4100000402a000000001002e001060650be0e90023bb590700016901f7c112b400010000000001800d04fdff0a000000840300009579f2670000000000000000
2025.04.06 14:54:45 4: SBS37 - logged in to inverter serial: 123456789, susyid: 123
2025.04.06 14:54:45 5: SBS37 - Logged in now
2025.04.06 14:54:45 5: SBS37 -> sup_TypeLabel
2025.04.06 14:54:45 3: SBS37 - Send request 00020058001E8200FF208200 to 192.168.1XX.1XX on port 9522
2025.04.06 14:54:45 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB5907000000000000028000020058001E8200FF20820000000000
2025.04.06 14:54:45 5: SBS37 - Received: 534d4100000402a000000001009e0010606527a0e90023bb590700a06901f7c112b40000000000000280010200580100000003000000071e82100c77f267534253332e372d31302031383300000000000000000000000000000000000000071f82080c77f267471f0001feffff00000000000000000000000000000000000000000000000000072082080c77f2678c2400018e2400008f240000902400009124000092240000feffff000000000000000000
2025.04.06 14:54:45 5: SBS37 - Data identifier 33310
2025.04.06 14:54:45 5: SBS37 - Found Data CLASS=8007 and TYPE=9356
2025.04.06 14:54:45 5: SBS37 -> sup_EnergyProduction
2025.04.06 14:54:45 3: SBS37 - Send request 0002005400012600FF222600 to 192.168.1XX.1XX on port 9522
2025.04.06 14:54:45 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB590700000000000003800002005400012600FF22260000000000
2025.04.06 14:54:45 5: SBS37 - Received: 534d4100000402a00000000100460010606511a0e90023bb590700a06901f7c112b40000000000000380010200540000000001000000070126009379f26745ce000000000000072226009479f267c30100000000000000000000
2025.04.06 14:54:45 5: SBS37 - Data identifier 9729
2025.04.06 14:54:45 5: SBS37 - Data SPOT_ETOTAL=52805 and SPOT_ETODAY=451
2025.04.06 14:54:45 5: SBS37 -> sup_SpotDCPower
2025.04.06 14:54:45 3: SBS37 - Send request 00028053001E2500FF1E2500 to 192.168.1XX.1XX on port 9522
2025.04.06 14:54:45 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB5907000000000000048000028053001E2500FF1E250000000000
2025.04.06 14:54:45 5: SBS37 - Received: 534d4100000402a00000000100260010606509a0e90023bb590700e06901f7c112b4000015000000048001028053001e2500ff1e250000000000
2025.04.06 14:54:45 3: SBS37 - Format of inverter response does not fit.
2025.04.06 14:54:45 5: SBS37 -> sup_SpotACPower
2025.04.06 14:54:45 3: SBS37 - Send request 0002005100404600FF424600 to 192.168.1XX.1XX on port 9522
2025.04.06 14:54:45 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB590700000000000005800002005100404600FF42460000000000
2025.04.06 14:54:45 5: SBS37 - Received: 534d4100000402a000000001007a001060651ea0e90023bb590700a06901f7c112b40000000000000580010200510a0000000c000000074046409479f2670000008000000080000000800000008001000000074146409479f2670000000000000000000000000000000001000000074246409479f267000000800000008000000080000000800100000000000000
2025.04.06 14:54:45 5: SBS37 - Data identifier 17984
2025.04.06 14:54:45 5: SBS37 - Found Data SPOT_PAC1=- and SPOT_PAC2=0 and SPOT_PAC3=-
2025.04.06 14:54:45 5: SBS37 -> sup_SpotACTotalPower
2025.04.06 14:54:45 3: SBS37 - Send request 00020051003F2600FF3F2600 to 192.168.1XX.1XX on port 9522
2025.04.06 14:54:45 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB5907000000000000068000020051003F2600FF3F260000000000
2025.04.06 14:54:45 5: SBS37 - Received: 534d4100000402a00000000100420010606510a0e90023bb590700a06901f7c112b40000000000000680010200510000000000000000073f26409479f267000000000000000000000000000000000100000000000000
2025.04.06 14:54:45 5: SBS37 - Data identifier 9791
2025.04.06 14:54:45 5: SBS37 - Found Data SPOT_PACTOT=0
2025.04.06 14:54:45 5: SBS37 -> sup_BatteryInfo_UDC
2025.04.06 14:54:45 3: SBS37 - Send request 00020051005C4900105C4900 to 192.168.1XX.1XX on port 9522
2025.04.06 14:54:45 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB5907000000000000078000020051005C4900105C490000000000
2025.04.06 14:54:45 5: SBS37 - Received: 534d4100000402a000000001007a001060651ea0e90023bb590700a06901f7c112b40000000000000780010200514400000046000000075c49009479f2671e0000001e0000001e0000001e00000001000000075c49009479f267ffffffffffffffffffffffffffffffff01000000075c49009479f267ffffffffffffffffffffffffffffffff0100000000000000
2025.04.06 14:54:45 5: SBS37 - Data identifier 18780
2025.04.06 14:54:45 5: SBS37 - Found Data and BAT_UDC=0.3 and BAT_UDC_A=0.3 and BAT_UDC_B=- and BAT_UDC_C=-
2025.04.06 14:54:45 5: SBS37 -> sup_BatteryInfo_IDC
2025.04.06 14:54:45 3: SBS37 - Send request 00020051005D4900105D4900 to 192.168.1XX.1XX on port 9522
2025.04.06 14:54:45 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB5907000000000000088000020051005D4900105D490000000000
2025.04.06 14:54:45 5: SBS37 - Received: 534d4100000402a000000001007a001060651ea0e90023bb590700a06901f7c112b40000000000000880010200514700000049000000075d49409479f2670000000000000000000000000000000001000000075d49409479f2670000008000000080000000800000008001000000075d49409479f267000000800000008000000080000000800100000000000000
2025.04.06 14:54:45 5: SBS37 - Data identifier 18781
2025.04.06 14:54:45 5: SBS37 - Found Data and BAT_IDC=0 and BAT_IDC_A=0 and BAT_IDC_B=- and BAT_IDC_C=-
2025.04.06 14:54:45 5: SBS37 -> sup_SpotDCVoltage
2025.04.06 14:54:45 3: SBS37 - Send request 00028053001F4500FF214500 to 192.168.1XX.1XX on port 9522
2025.04.06 14:54:45 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB5907000000000000098000028053001F4500FF21450000000000
2025.04.06 14:54:45 5: SBS37 - Received: 534d4100000402a00000000100260010606509a0e90023bb590700e06901f7c112b4000015000000098001028053001f4500ff21450000000000
2025.04.06 14:54:45 3: SBS37 - Format of inverter response does not fit.
2025.04.06 14:54:45 5: SBS37 -> sup_SpotACVoltage
2025.04.06 14:54:45 3: SBS37 - Send request 0002005100484600FF564600 to 192.168.1XX.1XX on port 9522
2025.04.06 14:54:45 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB59070000000000000A800002005100484600FF56460000000000
2025.04.06 14:54:45 5: SBS37 - Received: 534d4100000402a000000001013e001060654fa0e90023bb590700a06901f7c112b40000000000000a80010200510d00000016000000074846009479f267ffffffffffffffffffffffffffffffff01000000074946009479f2678f5d00008f5d00008f5d00008f5d000001000000074a46009479f267ffffffffffffffffffffffffffffffff01000000074b46009479f267ffffffffffffffffffffffffffffffff01000000074c46009479f267ffffffffffffffffffffffffffffffff01000000074d46009479f267ffffffffffffffffffffffffffffffff01000000074e46009479f2676300000063000000630000006300000001000000075346409479f2670000008000000080000000800000008001000000075446409479f2670000000000000000000000000000
2025.04.06 14:54:45 5: SBS37 - Data identifier 17992
2025.04.06 14:54:45 5: SBS37 - Found Data SPOT_UAC1=- and SPOT_UAC2=239.51 and SPOT_UAC3=- and inv_SPOT_UAC1_2=- and inv_SPOT_UAC2_3=- and inv_SPOT_UAC3_1=- and inv_SPOT_CosPhi=0.99
2025.04.06 14:54:45 5: SBS37 -> sup_SpotACCurrent
2025.04.06 14:54:45 3: SBS37 - Send request 0002005100534600FF554600 to 192.168.1XX.1XX on port 9522
2025.04.06 14:54:45 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB59070000000000000B800002005100534600FF55460000000000
2025.04.06 14:54:45 5: SBS37 - Received: 534d4100000402a000000001007a001060651ea0e90023bb590700a06901f7c112b40000000000000b80010200511400000016000000075346409479f2670000008000000080000000800000008001000000075446409479f2670000000000000000000000000000000001000000075546409479f267000000800000008000000080000000800100000000000000
2025.04.06 14:54:45 5: SBS37 - Data identifier 18003
2025.04.06 14:54:45 5: SBS37 - Found Data inv_SPOT_IAC1=- and inv_SPOT_IAC2=0 and inv_SPOT_IAC3=-
2025.04.06 14:54:45 5: SBS37 -> sup_SpotGridFrequency
2025.04.06 14:54:45 3: SBS37 - Send request 0002005100574600FF574600 to 192.168.1XX.1XX on port 9522
2025.04.06 14:54:45 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB59070000000000000C800002005100574600FF57460000000000
2025.04.06 14:54:45 5: SBS37 - Received: 534d4100000402a00000000100420010606510a0e90023bb590700a06901f7c112b40000000000000c80010200511700000017000000075746009479f267871300008713000087130000871300000100000000000000
2025.04.06 14:54:45 5: SBS37 - Data identifier 18007
2025.04.06 14:54:45 5: SBS37 - Found Data SPOT_FREQ=49.99
2025.04.06 14:54:45 5: SBS37 -> sup_OperationTime
2025.04.06 14:54:45 3: SBS37 - Send request 00020054002E4600FF2F4600 to 192.168.1XX.1XX on port 9522
2025.04.06 14:54:45 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB59070000000000000D8000020054002E4600FF2F460000000000
2025.04.06 14:54:45 5: SBS37 - Received: 534d4100000402a00000000100460010606511a0e90023bb590700a06901f7c112b40000000000000d80010200540500000006000000072e46009479f26784c6100000000000072f46009479f26755670c000000000000000000
2025.04.06 14:54:45 5: SBS37 - Data identifier 17966
2025.04.06 14:54:45 5: SBS37 - Found Data SPOT_OPERTM=305.38 and SPOT_FEEDTM=225.8
2025.04.06 14:54:45 5: SBS37 -> sup_MaxACPower
2025.04.06 14:54:45 3: SBS37 - Send request 00020051001E4100FF204100 to 192.168.1XX.1XX on port 9522
2025.04.06 14:54:45 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB59070000000000000E8000020051001E4100FF20410000000000
2025.04.06 14:54:45 5: SBS37 - Received: 534d4100000402a000000001007a001060651ea0e90023bb590700a06901f7c112b40000000000000e80010200510300000005000000071e41008d79f267600e0000600e0000600e0000600e000001000000071f41008d79f2670000000000000000000000000000000000000000072041008d79f267000000000000000000000000000000000000000000000000
2025.04.06 14:54:45 5: SBS37 - Data identifier 16670
2025.04.06 14:54:45 5: SBS37 - Found Data INV_PACMAX1=3680 and INV_PACMAX2=0 and INV_PACMAX3=0
2025.04.06 14:54:45 5: SBS37 -> sup_MaxACPower2
2025.04.06 14:54:45 3: SBS37 - Send request 00020051002A8300FF2A8300 to 192.168.1XX.1XX on port 9522
2025.04.06 14:54:45 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB59070000000000000F8000020051002A8300FF2A830000000000
2025.04.06 14:54:45 5: SBS37 - Received: 534d4100000402a00000000100260010606509a0e90023bb590700e06901f7c112b40000150000000f8001020051002a8300ff2a830000000000
2025.04.06 14:54:45 3: SBS37 - Format of inverter response does not fit.
2025.04.06 14:54:45 5: SBS37 -> sup_GridRelayStatus
2025.04.06 14:54:45 3: SBS37 - Send request 0002805100644100FF644100 to 192.168.1XX.1XX on port 9522
2025.04.06 14:54:45 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB590700000000000010800002805100644100FF64410000000000
2025.04.06 14:54:46 5: SBS37 - Received: 534d4100000402a000000001004e0010606513a0e90023bb590700a06901f7c112b40000000000001080010280510d0000000d000000076441089479f2673300000037010001fdffff00feffff000000000000000000000000000000000000000000
2025.04.06 14:54:46 5: SBS37 - Data identifier 16740
2025.04.06 14:54:46 5: SBS37 - Found Data INV_GRIDRELAY=311
2025.04.06 14:54:46 5: SBS37 -> sup_DeviceStatus
2025.04.06 14:54:46 3: SBS37 - Send request 0002805100482100FF482100 to 192.168.1XX.1XX on port 9522
2025.04.06 14:54:46 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB590700000000000011800002805100482100FF48210000000000
2025.04.06 14:54:46 5: SBS37 - Received: 534d4100000402a000000001004e0010606513a0e90023bb590700a06901f7c112b40000000000001180010280510000000000000000074821089579f26733010001feffff0000000000000000000000000000000000000000000000000000000000
2025.04.06 14:54:46 5: SBS37 - Data identifier 8520
2025.04.06 14:54:46 5: SBS37 - Found Data inv_STATUS=307
2025.04.06 14:54:46 5: SBS37 -> sup_BatteryInfo_TEMP
2025.04.06 14:54:46 3: SBS37 - Send request 00020051005B4900105B4900 to 192.168.1XX.1XX on port 9522
2025.04.06 14:54:46 5: SBS37 - send: 534D4100000402A00000000100260010606509A06901F7C112B40000E90023BB5907000000000000128000020051005B4900105B490000000000
2025.04.06 14:54:46 5: SBS37 - Received: 534d4100000402a000000001007a001060651ea0e90023bb590700a06901f7c112b40000000000001280010200514100000043000000075b49409479f2670000008000000080000000800000008001000000075b49409479f2670000008000000080000000800000008001000000075b49409479f267000000800000008000000080000000800100000000000000
2025.04.06 14:54:46 5: SBS37 - Data identifier 18779
Illegal division by zero at ./FHEM/76_SMAInverter.pm line 2282.
2025.04.06 14:54:47 1: SMAInverter SBS37 -> BlockingCall SMAInverter_getstatusDoParse Process died prematurely
2025.04.06 14:55:00 4: SBS37 - ###############################################################
2025.04.06 14:55:00 4: SBS37 - ##########  Begin of new SMAInverter get data cycle  ##########
2025.04.06 14:55:00 4: SBS37 - ###############################################################
2025.04.06 14:55:00 4: SBS37 - timeout cycles since module start: 6, Interval: 15
2025.04.06 14:55:00 4: SBS37 - start BlockingCall
2025.04.06 14:55:00 4: SBS37 - running BlockingCall SMAInverter_getstatusDoParse
2025.04.06 14:55:00 4: SBS37 -> INVCLASS 0
2025.04.06 14:55:00 4: SBS37 -> INVTYPE 0

Der BWR ist aber auch Brutal - er schaltet die Batterie und sich auf "AUS" wenn er "100 % voll" ist - war beim SBS25 nicht so  :o
Vorher ist beim "LADEN" und "ENTLADEN" alles okay.

Gruß
300P
Gruß
300P

FHEM 6.4|RPi|SMAEM|SMAInverter|SolarForecast|DbLog|DbRep|MariaDB|Buderus-MQTT_EMS|
Fritzbox|fhempy|JsonMod|HTTPMOD|Modbus ser+TCP|ESP32-Digitizer-AI_on_the_Edge|ESP32CAM usw.

MadMax

Hallo 300p,

ich habe den Fehler gefunden, es lag an der durchschnittlichen Batterietemperatur.

if($count > 0) {$inv_BAT_TEMP = $inv_BAT_TEMP / $count;} else {$inv_BAT_TEMP = "-";}

Das habe ich jetzt abgefangen.

Gruß
Max
Lenovo M910Q Tiny Debian 12, FHEM 6.3, 2x Siemens Logo 0BA7, Homematic CCU3, Philips HUE, 6x SMA Wechselrichter, BYD HVM, BYD HVS, SMA EVCharger, KEBA Wallbox, 2x HMS800W, Daikin Wärmepumpe über CAN, viele ESPs

Contrib: https://svn.fhem.de/trac/browser/trunk/fhem/contrib/MadMax

MadMax

Merkwürdig ist, ich hatte mal einen SBS5.0 da ist der Fehler nie aufgetreten aber naja.
Lenovo M910Q Tiny Debian 12, FHEM 6.3, 2x Siemens Logo 0BA7, Homematic CCU3, Philips HUE, 6x SMA Wechselrichter, BYD HVM, BYD HVS, SMA EVCharger, KEBA Wallbox, 2x HMS800W, Daikin Wärmepumpe über CAN, viele ESPs

Contrib: https://svn.fhem.de/trac/browser/trunk/fhem/contrib/MadMax

300P

Könnte es sein das daran liegt das dies ein SBS37 ohne WLAN ist ???
Gruß
300P

FHEM 6.4|RPi|SMAEM|SMAInverter|SolarForecast|DbLog|DbRep|MariaDB|Buderus-MQTT_EMS|
Fritzbox|fhempy|JsonMod|HTTPMOD|Modbus ser+TCP|ESP32-Digitizer-AI_on_the_Edge|ESP32CAM usw.

300P

#1828
Hallo MadMax,
sieht aktuell gut aus - nur die bat_temp / bat_temp_a als Temperatur wird nicht mehr ausgelesen.
(grad gemerkt - das muss ja solange sein bis das die Batterie / WR wieder eingeschaltet ist -ist jetzt wieder beides "AUS")


Schau trotzdem morgen früh wenn die Batterie dann wieder "voll" ist.
Gruß
300P

EDIT Text geändert !!!
Gruß
300P

FHEM 6.4|RPi|SMAEM|SMAInverter|SolarForecast|DbLog|DbRep|MariaDB|Buderus-MQTT_EMS|
Fritzbox|fhempy|JsonMod|HTTPMOD|Modbus ser+TCP|ESP32-Digitizer-AI_on_the_Edge|ESP32CAM usw.

300P

Jetzt - nachdem die Batterie aus dem Dornröschenschlaf erwacht ist (Status < 100 %) wird die bat_temp und die bat_temp_a wieder aktualisiert.

Ich habe mal den darauf folgenden Log auf 2 gesetzt und schau mal wie es morgen früh aussieht wenn die Batterie wieder zu 100 % voll ist und schlafen geht.
Bei dem Wetter klappt mein Ansinnen sicherlich  ;D
Gruß
300P

FHEM 6.4|RPi|SMAEM|SMAInverter|SolarForecast|DbLog|DbRep|MariaDB|Buderus-MQTT_EMS|
Fritzbox|fhempy|JsonMod|HTTPMOD|Modbus ser+TCP|ESP32-Digitizer-AI_on_the_Edge|ESP32CAM usw.