Autor Thema: ModbusAttr an Wechselrichter SolarEdge SE10k [gelöst]  (Gelesen 9798 mal)

Offline Butzel

  • New Member
  • *
  • Beiträge: 29
Antw:ModbusAttr an Wechselrichter SolarEdge SE10k [gelöst]
« Antwort #105 am: 28 Mai 2019, 14:33:22 »
Dann kann es jetzt weiter gehen.
Ich muss erst mal schauen, warum meine Produktion als deckungsgleicher Eigenverbrauch angezeigt wird (nicht mehr grün, sondern blau). Das ist so seit einem Switch-Ausfall und der Installation von SolarView. Vielleicht liefert die SV auch ein Ergebnis an den Eigenverbrauch.....
Ich kann das kurzfristig ändern (wieder in grün), indem ich in der Portal-Admin den Eigenverbrauchszähler deaktiviere. Der kommt aber nach einer kurzen Zeit wieder.

Offline schachti

  • New Member
  • *
  • Beiträge: 25
Antw:ModbusAttr an Wechselrichter SolarEdge SE10k [gelöst]
« Antwort #106 am: 29 Mai 2019, 18:11:23 »
Eine Sache ist mir aufgefallen: das Mapping der Statuswerte (I_Status) ist unvollständig - gemappt werden nur 1 (Aus), 2 (Sleep) und 4 (An), laut https://www.solaredge.com/sites/default/files/sunspec-implementation-technical-note.pdf gehen aber die möglichen Werte von 1 bis 8.

Offline pejonp

  • Hero Member
  • *****
  • Beiträge: 1075
Antw:ModbusAttr an Wechselrichter SolarEdge SE10k [gelöst]
« Antwort #107 am: 29 Mai 2019, 18:17:33 »
@schachti

beim SE5K für den ich das Modul geschrieben habe, gibt es nur diese Werte. Für andere WR muss es angepaßt werden und auch noch andere Werte. Bin aber noch nicht dazu gekommen und ist ja auch die Frage welche Werte werden benötigt oder sind sinnvoll.

pejonp
« Letzte Änderung: 29 Mai 2019, 18:26:31 von pejonp »
JeeLink (RFM69CW) LGW 868MHz:WT470+TFA+TX37-IT+EMT7110+FS20+W136+WH25A HP1003+WH2621
SignalD(CC1101):Bresser+WS-0101(868MHz WH1080) Velux KLF200
MAX!:HM-MOD-UART:Rauch HM-SEC-SD
VITOSOLIC 200 + RESOL VBUS-LAN
SolarEdge SE5K(TCP 24 RS485)+Sonnenbatterie ComfortS(Vera3)+TD3511+DRT710M(RS485

Offline CaptainHook

  • Full Member
  • ***
  • Beiträge: 201
  • Geht nicht! Gibt's nicht!
Antw:ModbusAttr an Wechselrichter SolarEdge SE10k [gelöst]
« Antwort #108 am: 10 Juni 2019, 16:34:56 »
Hi,

ich habe mir das Module mal geforkt und ein paar kleine Anpassungen gemacht; das Repro liegt unter https://github.com/CaptainRoot/FHEM---SolarEdge.

Was habe ich geändert.
- Erweiterung um einen externen Zähler (Modbuszähler)
- "Englische" Readings
- Phasen werden wie in der Spec mit A,B,C bezeichnet
- Wie von schachti angemerkt die Status angepasst (in der englischen Spec gibt es mehr als in der deutschen Übersetzung)

Wenn gewünscht erstelle ich gerne ein pull-Request

Grüße,
Stephan
Raspberry Pi 3|
WS0002|NC-7200|Funksteckdosen|FHT80BTFn|FHT80-TF2|Revolt NC-5462|OWL+USB|HM-SEC-MDIR|HM-SEC-RHS|HM-SEC-SC2|TFA 30.3125|
ESP8266@ESPEasy (MOD)|HMS100 TFK|HM-PB-FM2|HM-LC-Sw1-PBU-FM|HM-CFG-USB|OLIMEXINO-32U4@CULfw|nanoCUL|Signalduino
FHEM-Tablet-UI@Odys Neo Quad 1| SolarEdge SE10K
Gefällt mir Gefällt mir x 1 Liste anzeigen

Offline panzi

  • New Member
  • *
  • Beiträge: 15
Antw:ModbusAttr an Wechselrichter SolarEdge SE10k [gelöst]
« Antwort #109 am: 20 Juni 2019, 16:03:20 »
Hallo,
hab seit einiger zeit meinen SE wr in fhem hier super integriert.
Ich habe allerdings auch einen s0 Zähler eingebaut und kann im solaredge monitoring (website und app) hier den aktuellen verbrauch und die einspeisung/bezug anzeigen.
Kann man das auch irgendwie nach fhem bekommen?
danke

Offline CaptainHook

  • Full Member
  • ***
  • Beiträge: 201
  • Geht nicht! Gibt's nicht!
Antw:ModbusAttr an Wechselrichter SolarEdge SE10k [gelöst]
« Antwort #110 am: 20 Juni 2019, 16:10:31 »
Hi,

Sicher das es ein S0 zähler ist? An den solarEdge Wechselrichter kommt eigentlich ein RS485 / Modbus Zähler.

Wenn du möchtest kannst mal das "Modul" von meinem GitHub testen, da ist der Meter 1 (über RS485/Mobus am WR) mit drin.
Da sind (fast) alle Werte mit drin die auch an das Monitoring von SolarEdge gehen drin (Import/ Export usw)

Das Modul erweitere ich derzeit fast täglich. Kannst es dir ja mal aschauen und falls dir was auffällt bzw du wünsche hast sag Bescheid

Grüße,
Stephan

Raspberry Pi 3|
WS0002|NC-7200|Funksteckdosen|FHT80BTFn|FHT80-TF2|Revolt NC-5462|OWL+USB|HM-SEC-MDIR|HM-SEC-RHS|HM-SEC-SC2|TFA 30.3125|
ESP8266@ESPEasy (MOD)|HMS100 TFK|HM-PB-FM2|HM-LC-Sw1-PBU-FM|HM-CFG-USB|OLIMEXINO-32U4@CULfw|nanoCUL|Signalduino
FHEM-Tablet-UI@Odys Neo Quad 1| SolarEdge SE10K

Offline panzi

  • New Member
  • *
  • Beiträge: 15
Antw:ModbusAttr an Wechselrichter SolarEdge SE10k [gelöst]
« Antwort #111 am: 20 Juni 2019, 18:16:42 »
ja - ist ein s0 Zähler der über ein adapterkabel beim wr angeschlossen ist
KEIN modbus zähler

Offline Metalomaniac

  • New Member
  • *
  • Beiträge: 5
Antw:ModbusAttr an Wechselrichter SolarEdge SE10k [gelöst]
« Antwort #112 am: 07 Juli 2019, 09:32:28 »
Hallo zusammen,
bin neu hier und seit kurzem mit SE Wechselrichter (mit SE Modbus Zähler) am Start.
Hab ihn mit SolarEdgeAPI erfolgreich eingebunden, hätte aber gerne mehr als alle paar Minuten einen Wert.

Was ich bis jetzt mit der API mache: 
aus den Produktions-/Verbrauchsdaten Regeln um Steckdosen (in Zukunft irgendwann einen go-echarger Auto-Lader) zu schalten.
 
An ModBusAttr (nach wiki-Eintrag) und Captains Modul scheitere ich aber bis jetzt.
Wo muss ich weiterlesen, damit ich FHEM gut genug verstehe um das hinzubekommen?

Offline pejonp

  • Hero Member
  • *****
  • Beiträge: 1075
Antw:ModbusAttr an Wechselrichter SolarEdge SE10k [gelöst]
« Antwort #113 am: 07 Juli 2019, 10:51:42 »
@Metalomaniac

SOLAREDGE API ist aber nicht modbus..

Versuche es mal mit diesem Modul (Modbus) https://forum.fhem.de/index.php/topic,80767.msg853967.html#msg853967

Hast du alle erforderlichen Module installiert (Perl,fhem,...).

Mach mal ein list von deiner Modbus Definition.
Wie hast du den WR angebunden : Modbus IP oder rs485 .

Pejonp
JeeLink (RFM69CW) LGW 868MHz:WT470+TFA+TX37-IT+EMT7110+FS20+W136+WH25A HP1003+WH2621
SignalD(CC1101):Bresser+WS-0101(868MHz WH1080) Velux KLF200
MAX!:HM-MOD-UART:Rauch HM-SEC-SD
VITOSOLIC 200 + RESOL VBUS-LAN
SolarEdge SE5K(TCP 24 RS485)+Sonnenbatterie ComfortS(Vera3)+TD3511+DRT710M(RS485

Offline Metalomaniac

  • New Member
  • *
  • Beiträge: 5
Antw:ModbusAttr an Wechselrichter SolarEdge SE10k [gelöst]
« Antwort #114 am: 07 Juli 2019, 18:26:49 »
Ich versuch mich heute abend mal an deinem Modulvorschlag.
Das API nicht Modbus ist, sondern über das SE Monitoring Web funktioniert ist mir klar.

"Angeschlossen" hab ich meinen WR über Modbus IP.

Offline Metalomaniac

  • New Member
  • *
  • Beiträge: 5
Antw:ModbusAttr an Wechselrichter SolarEdge SE10k [gelöst]
« Antwort #115 am: 07 Juli 2019, 22:49:56 »
Habe das Modul gestartet und meinen WR definiert.
Ergebnis:

Internals:
   CFGFN     
   DEF        1 60 192.168.178.79:502 TCP
   DeviceName 192.168.178.79:502
   EXPECT     idle
   FD         16
   FUUID      5d22590b-f33f-ee07-0ce3-bf3eb697079f769e
   INTERVAL   60
   IODev      SEdge
   LASTOPEN   1562532107.96569
   MODBUSID   1
   MODE       master
   MODULEVERSION Modbus 4.1.2 - 17.4.2019
   NAME       SEdge
   NOTIFYDEV  global
   NR         600
   NTFY_ORDER 50-SEdge
   PARTIAL   
   PROTOCOL   TCP
   STATE      opened
   TCPConn    1
   TIMEOUTS   20
   TRIGGERTIME 1562532410.02683
   TRIGGERTIME_FMT 2019-07-07 22:46:50
   TYPE       SolarEdge
   devioLoglevel 3
   lastUpdate 1562532350.02683
   nextOpenDelay 60
   QUEUE:
   READ:
     BUFFER     
   READINGS:
     2019-07-07 22:41:47   state           opened
   REMEMBER:
     lid        1
     lname      SEdge
     lsend      1562532356.05969
   defptr:
     SEdge      1
   lastRead:
Attributes:

Offline pejonp

  • Hero Member
  • *****
  • Beiträge: 1075
Antw:ModbusAttr an Wechselrichter SolarEdge SE10k [gelöst]
« Antwort #116 am: 08 Juli 2019, 00:45:37 »
@Metalomaniac

verbose = 5 und log anhängen. Ansonsten muss ich meine Glaskugel befragen. Etwas mehr Angaben währe hilfreich.
Stimmt die ID,Port,... ?

pejonp
JeeLink (RFM69CW) LGW 868MHz:WT470+TFA+TX37-IT+EMT7110+FS20+W136+WH25A HP1003+WH2621
SignalD(CC1101):Bresser+WS-0101(868MHz WH1080) Velux KLF200
MAX!:HM-MOD-UART:Rauch HM-SEC-SD
VITOSOLIC 200 + RESOL VBUS-LAN
SolarEdge SE5K(TCP 24 RS485)+Sonnenbatterie ComfortS(Vera3)+TD3511+DRT710M(RS485

Offline Metalomaniac

  • New Member
  • *
  • Beiträge: 5
Antw:ModbusAttr an Wechselrichter SolarEdge SE10k [gelöst]
« Antwort #117 am: 08 Juli 2019, 23:34:58 »
Hallo, ich habe momentan Captains Modul eingebunden, aber ich denke, dass ist deinem recht ähnlich...
ID sollte mit "1" bei TCP stimmen, denke ich.
Ports habe ich schon 1502 und 502 ausprobiert (an WR und FHEM umgestellt)

FHEM und mein WR reden irgendwie nicht miteinander.

auf jeden Fall sieht es so aus:

Internals:
   CFGFN     
   DEF        1 60 192.168.178.79:1502 TCP
   DeviceName 192.168.178.79:1502
   EXPECT     idle
   FD         7
   FUUID      5d239ebc-f33f-ee07-b9c8-b46a58ee3a4f3a3a
   INTERVAL   60
   IODev      TestEdge
   LASTOPEN   1562619750.40032
   MODBUSID   1
   MODE       master
   MODULEVERSION Modbus 4.1.2 - 17.4.2019
   NAME       TestEdge
   NOTIFYDEV  global
   NR         122
   NTFY_ORDER 50-TestEdge
   PARTIAL   
   PROTOCOL   TCP
   STATE      opened
   TCPConn    1
   TIMEOUTS   225
   TRIGGERTIME 1562621258.61608
   TRIGGERTIME_FMT 2019-07-08 23:27:38
   TRIGGERTIME_SAVED
   TYPE       SolarEdge
   devioLoglevel 3
   lastUpdate 1562621198.61608
   nextOpenDelay 60
   QUEUE:
   READ:
     BUFFER     
   READINGS:
     2019-07-08 23:02:30   state           opened
   REMEMBER:
     lid        1
     lname      TestEdge
     lsend      1562621214.71512
   defptr:
     TestEdge   1
   lastRead:
Attributes:
   room       Photovoltaik
   verbose    5

2019.07.08 23:29:38 5: TestEdge: GetUpdate called from HandleTimeout
2019.07.08 23:29:38 5: TestEdge: SetartUpdateTimer called from GetUpdate updated timer, will call GetUpdate in 60.0 sec at 2019-07-08 23:30:38, interval 60
2019.07.08 23:29:38 5: TestEdge: GetUpdate objects from attributes:
2019.07.08 23:29:38 5: TestEdge: GetUpdate full object list: h40000 h40004 h40020 h40044 h40052 h40068 h40069 h40071 h40076 h40077 h40078 h40079 h40080 h40081 h40082 h40083 h40085 h40087 h40089 h40091 h40093 h40096 h40098 h40100 h40103 h40107 h40123 h40139 h40155 h40163 h40171 h40187 h40188 h40190 h40195 h40196 h40197 h40198 h40199 h40204 h40206 h40211 h40216 h40221 h40226 h40243
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40000 => C_SunSpec_ID, poll = once, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request C_SunSpec_ID
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40004 => C_Manufacturer, poll = once, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request C_Manufacturer
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40020 => Block_C_Model, poll = once, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request Block_C_Model
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40044 => C_Version, poll = once, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request C_Version
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40052 => C_SerialNumber, poll = once, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request C_SerialNumber
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40068 => C_DeviceAddress, poll = once, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request C_DeviceAddress
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40069 => C_SunSpec_DID, poll = once, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request C_SunSpec_DID
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40071 => Block_AC_Current, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request Block_AC_Current
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40076 => I_AC_VoltageAB, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request I_AC_VoltageAB
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40077 => I_AC_VoltageBC, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request I_AC_VoltageBC
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40078 => I_AC_VoltageCA, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request I_AC_VoltageCA
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40079 => I_AC_VoltageAN, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request I_AC_VoltageAN
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40080 => I_AC_VoltageBN, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request I_AC_VoltageBN
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40081 => I_AC_VoltageCN, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request I_AC_VoltageCN
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40082 => I_AC_Voltage_SF, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request I_AC_Voltage_SF
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40083 => Block_AC_Power, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request Block_AC_Power
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40085 => Block_AC_Frequency, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request Block_AC_Frequency
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40087 => Block_AC_VA, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request Block_AC_VA
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40089 => Block_AC_VAR, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request Block_AC_VAR
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40091 => Block_AC_PF, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request Block_AC_PF
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40093 => Block_AC_Energy_WH, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request Block_AC_Energy_WH
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40096 => Block_DC_Current, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request Block_DC_Current
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40098 => Block_DC_Voltage, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request Block_DC_Voltage
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40100 => Block_DC_Power, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request Block_DC_Power
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40103 => I_Temp_HeatSink, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request I_Temp_HeatSink
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40107 => I_Status, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request I_Status
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40123 => X_Meter_1_C_Manufacturer, poll = once, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request X_Meter_1_C_Manufacturer
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40139 => X_Meter_1_Block_C_Model, poll = once, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request X_Meter_1_Block_C_Model
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40155 => X_Meter_1_C_Option, poll = once, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request X_Meter_1_C_Option
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40163 => X_Meter_1_C_Version, poll = once, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request X_Meter_1_C_Version
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40171 => X_Meter_1_C_SerialNumber, poll = once, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request X_Meter_1_C_SerialNumber
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40187 => X_Meter_1_C_DeviceAddress, poll = once, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request X_Meter_1_C_DeviceAddress
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40188 => X_Meter_1_C_SunSpec_DID, poll = once, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request X_Meter_1_C_SunSpec_DID
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40190 => X_Meter_1_Block_AC_Current, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request X_Meter_1_Block_AC_Current
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40195 => X_Meter_1_M_AC_Voltage_LN, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request X_Meter_1_M_AC_Voltage_LN
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40196 => X_Meter_1_M_AC_Voltage_AN, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request X_Meter_1_M_AC_Voltage_AN
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40197 => X_Meter_1_M_AC_Voltage_BN, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request X_Meter_1_M_AC_Voltage_BN
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40198 => X_Meter_1_M_AC_Voltage_CN, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request X_Meter_1_M_AC_Voltage_CN
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40199 => X_Meter_1_Block_AC_Voltage_LL, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request X_Meter_1_Block_AC_Voltage_LL
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40204 => X_Meter_1_Block_AC_Frequency, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request X_Meter_1_Block_AC_Frequency
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40206 => X_Meter_1_Block_AC_Power, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request X_Meter_1_Block_AC_Power
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40211 => X_Meter_1_Block_AC_VA, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request X_Meter_1_Block_AC_VA
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40216 => X_Meter_1_Block_AC_VAR, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request X_Meter_1_Block_AC_VAR
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40221 => X_Meter_1_Block_AC_PF, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request X_Meter_1_Block_AC_PF
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40226 => X_Meter_1_Block_Energy_W, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request X_Meter_1_Block_Energy_W
2019.07.08 23:29:38 5: TestEdge: GetUpdate check h40243 => X_Meter_1_Block_Energy_VA, poll = 1, last = 0
2019.07.08 23:29:38 4: TestEdge: GetUpdate will request X_Meter_1_Block_Energy_VA
2019.07.08 23:29:38 5: TestEdge: GetUpdate tries to combine read commands
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for C_SunSpec_ID (h40000) with C_Manufacturer (h40004), span=12, max=30, drop read for h40004
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for C_SunSpec_ID (h40000) with Block_C_Model (h40020), span=28, max=30, drop read for h40020
2019.07.08 23:29:38 5: TestEdge: GetUpdate cant combine request for C_SunSpec_ID / h40000 with C_Version / h40044, span 52 > max 30
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for C_Version (h40044) with C_SerialNumber (h40052), span=16, max=30, drop read for h40052
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for C_Version (h40044) with C_DeviceAddress (h40068), span=25, max=30, drop read for h40068
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for C_Version (h40044) with C_SunSpec_DID (h40069), span=26, max=30, drop read for h40069
2019.07.08 23:29:38 5: TestEdge: GetUpdate cant combine request for C_Version / h40044 with Block_AC_Current / h40071, span 32 > max 30
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for Block_AC_Current (h40071) with I_AC_VoltageAB (h40076), span=6, max=30, drop read for h40076
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for Block_AC_Current (h40071) with I_AC_VoltageBC (h40077), span=7, max=30, drop read for h40077
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for Block_AC_Current (h40071) with I_AC_VoltageCA (h40078), span=8, max=30, drop read for h40078
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for Block_AC_Current (h40071) with I_AC_VoltageAN (h40079), span=9, max=30, drop read for h40079
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for Block_AC_Current (h40071) with I_AC_VoltageBN (h40080), span=10, max=30, drop read for h40080
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for Block_AC_Current (h40071) with I_AC_VoltageCN (h40081), span=11, max=30, drop read for h40081
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for Block_AC_Current (h40071) with I_AC_Voltage_SF (h40082), span=12, max=30, drop read for h40082
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for Block_AC_Current (h40071) with Block_AC_Power (h40083), span=14, max=30, drop read for h40083
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for Block_AC_Current (h40071) with Block_AC_Frequency (h40085), span=16, max=30, drop read for h40085
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for Block_AC_Current (h40071) with Block_AC_VA (h40087), span=18, max=30, drop read for h40087
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for Block_AC_Current (h40071) with Block_AC_VAR (h40089), span=20, max=30, drop read for h40089
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for Block_AC_Current (h40071) with Block_AC_PF (h40091), span=22, max=30, drop read for h40091
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for Block_AC_Current (h40071) with Block_AC_Energy_WH (h40093), span=25, max=30, drop read for h40093
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for Block_AC_Current (h40071) with Block_DC_Current (h40096), span=27, max=30, drop read for h40096
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for Block_AC_Current (h40071) with Block_DC_Voltage (h40098), span=29, max=30, drop read for h40098
2019.07.08 23:29:38 5: TestEdge: GetUpdate cant combine request for Block_AC_Current / h40071 with Block_DC_Power / h40100, span 31 > max 30
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for Block_DC_Power (h40100) with I_Temp_HeatSink (h40103), span=4, max=30, drop read for h40103
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for Block_DC_Power (h40100) with I_Status (h40107), span=8, max=30, drop read for h40107
2019.07.08 23:29:38 5: TestEdge: GetUpdate cant combine request for Block_DC_Power / h40100 with X_Meter_1_C_Manufacturer / h40123, span 31 > max 30
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for X_Meter_1_C_Manufacturer (h40123) with X_Meter_1_Block_C_Model (h40139), span=24, max=30, drop read for h40139
2019.07.08 23:29:38 5: TestEdge: GetUpdate cant combine request for X_Meter_1_C_Manufacturer / h40123 with X_Meter_1_C_Option / h40155, span 40 > max 30
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for X_Meter_1_C_Option (h40155) with X_Meter_1_C_Version (h40163), span=16, max=30, drop read for h40163
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for X_Meter_1_C_Option (h40155) with X_Meter_1_C_SerialNumber (h40171), span=24, max=30, drop read for h40171
2019.07.08 23:29:38 5: TestEdge: GetUpdate cant combine request for X_Meter_1_C_Option / h40155 with X_Meter_1_C_DeviceAddress / h40187, span 33 > max 30
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for X_Meter_1_C_DeviceAddress (h40187) with X_Meter_1_C_SunSpec_DID (h40188), span=2, max=30, drop read for h40188
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for X_Meter_1_C_DeviceAddress (h40187) with X_Meter_1_Block_AC_Current (h40190), span=8, max=30, drop read for h40190
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for X_Meter_1_C_DeviceAddress (h40187) with X_Meter_1_M_AC_Voltage_LN (h40195), span=9, max=30, drop read for h40195
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for X_Meter_1_C_DeviceAddress (h40187) with X_Meter_1_M_AC_Voltage_AN (h40196), span=10, max=30, drop read for h40196
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for X_Meter_1_C_DeviceAddress (h40187) with X_Meter_1_M_AC_Voltage_BN (h40197), span=11, max=30, drop read for h40197
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for X_Meter_1_C_DeviceAddress (h40187) with X_Meter_1_M_AC_Voltage_CN (h40198), span=12, max=30, drop read for h40198
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for X_Meter_1_C_DeviceAddress (h40187) with X_Meter_1_Block_AC_Voltage_LL (h40199), span=17, max=30, drop read for h40199
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for X_Meter_1_C_DeviceAddress (h40187) with X_Meter_1_Block_AC_Frequency (h40204), span=19, max=30, drop read for h40204
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for X_Meter_1_C_DeviceAddress (h40187) with X_Meter_1_Block_AC_Power (h40206), span=24, max=30, drop read for h40206
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for X_Meter_1_C_DeviceAddress (h40187) with X_Meter_1_Block_AC_VA (h40211), span=29, max=30, drop read for h40211
2019.07.08 23:29:38 5: TestEdge: GetUpdate cant combine request for X_Meter_1_C_DeviceAddress / h40187 with X_Meter_1_Block_AC_VAR / h40216, span 34 > max 30
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for X_Meter_1_Block_AC_VAR (h40216) with X_Meter_1_Block_AC_PF (h40221), span=10, max=30, drop read for h40221
2019.07.08 23:29:38 5: TestEdge: GetUpdate combines request for X_Meter_1_Block_AC_VAR (h40216) with X_Meter_1_Block_Energy_W (h40226), span=27, max=30, drop read for h40226
2019.07.08 23:29:38 5: TestEdge: GetUpdate cant combine request for X_Meter_1_Block_AC_VAR / h40216 with X_Meter_1_Block_Energy_VA / h40243, span 44 > max 30
2019.07.08 23:29:38 5: TestEdge: GetUpdate doesn't sort objList before sending requests
2019.07.08 23:29:38 4: TestEdge: DoRequest called from GetUpdate created request: id 1, fCode 3, tid 176, type h, adr 40216, len 27 for device TestEdge reading X_Meter_1_Block_AC_VAR (getUpdate), read buffer empty
2019.07.08 23:29:38 5: TestEdge: QueueRequest called from DoRequest (TestEdge) with h40216, qlen 0
2019.07.08 23:29:38 4: TestEdge: ProcessRequestQueue called from QueueRequest, qlen 1, next entry to id 1 (TestEdge), last send to this device was 44.008 secs ago, last read never, last read on bus never from id 1 (TestEdge)
2019.07.08 23:29:38 5: TestEdge: CheckDelay called from ProcessRequestQueue sendDelay (0.1s since 23:28:54.789) for TestEdge, delay 43.908secs over
2019.07.08 23:29:38 4: TestEdge: ProcessRequestQueue (V4.1.2 - 17.4.2019) qlen 1, sending 00b00000000601039d18001b request: id 1, fCode 3, tid 176, type h, adr 40216, len 27 for device TestEdge reading X_Meter_1_Block_AC_VAR (getUpdate), queued 0.00 secs ago, read buffer empty
2019.07.08 23:29:38 5: SW: 00b00000000601039d18001b
2019.07.08 23:29:38 5: TestEdge: StartQueueTimer called from ProcessRequestQueue removes internal timer because it is not needed now
2019.07.08 23:29:38 4: TestEdge: DoRequest called from GetUpdate created request: id 1, fCode 3, tid 173, type h, adr 40044, len 26 for device TestEdge reading C_Version (getUpdate), read buffer empty
2019.07.08 23:29:38 5: TestEdge: QueueRequest called from DoRequest (TestEdge) with h40044, qlen 0
2019.07.08 23:29:38 5: TestEdge: StartQueueTimer called form QueueRequest sets internal timer to call Modbus_ProcessRequestQueue in 1.000 seconds
2019.07.08 23:29:38 4: TestEdge: DoRequest called from GetUpdate created request: id 1, fCode 3, tid 10, type h, adr 40155, len 24 for device TestEdge reading X_Meter_1_C_Option (getUpdate), read buffer empty
2019.07.08 23:29:38 5: TestEdge: QueueRequest called from DoRequest (TestEdge) with h40155, qlen 1
2019.07.08 23:29:38 4: TestEdge: DoRequest called from GetUpdate created request: id 1, fCode 3, tid 7, type h, adr 40100, len 8 for device TestEdge reading Block_DC_Power (getUpdate), read buffer empty
2019.07.08 23:29:38 5: TestEdge: QueueRequest called from DoRequest (TestEdge) with h40100, qlen 2
2019.07.08 23:29:38 4: TestEdge: DoRequest called from GetUpdate created request: id 1, fCode 3, tid 180, type h, adr 40187, len 29 for device TestEdge reading X_Meter_1_C_DeviceAddress (getUpdate), read buffer empty
2019.07.08 23:29:38 5: TestEdge: QueueRequest called from DoRequest (TestEdge) with h40187, qlen 3
2019.07.08 23:29:38 4: TestEdge: DoRequest called from GetUpdate created request: id 1, fCode 3, tid 99, type h, adr 40071, len 29 for device TestEdge reading Block_AC_Current (getUpdate), read buffer empty
2019.07.08 23:29:38 5: TestEdge: QueueRequest called from DoRequest (TestEdge) with h40071, qlen 4
2019.07.08 23:29:38 4: TestEdge: DoRequest called from GetUpdate created request: id 1, fCode 3, tid 121, type h, adr 40000, len 28 for device TestEdge reading C_SunSpec_ID (getUpdate), read buffer empty
2019.07.08 23:29:38 5: TestEdge: QueueRequest called from DoRequest (TestEdge) with h40000, qlen 5
2019.07.08 23:29:38 4: TestEdge: DoRequest called from GetUpdate created request: id 1, fCode 3, tid 52, type h, adr 40123, len 24 for device TestEdge reading X_Meter_1_C_Manufacturer (getUpdate), read buffer empty
2019.07.08 23:29:38 5: TestEdge: QueueRequest called from DoRequest (TestEdge) with h40123, qlen 6
2019.07.08 23:29:38 4: TestEdge: DoRequest called from GetUpdate created request: id 1, fCode 3, tid 8, type h, adr 40243, len 17 for device TestEdge reading X_Meter_1_Block_Energy_VA (getUpdate), read buffer empty
2019.07.08 23:29:38 5: TestEdge: QueueRequest called from DoRequest (TestEdge) with h40243, qlen 7
2019.07.08 23:29:39 5: TestEdge: ProcessRequestQueue called from HandleTimeout returns, Fhem is still waiting for response, request: id 1, fCode 3, tid 176, type h, adr 40216, len 27 for device TestEdge reading X_Meter_1_Block_AC_VAR (getUpdate), queued 1.01 secs ago, sent 1.01 secs ago, read buffer empty, qlen 8, try again in 1 seconds
2019.07.08 23:29:39 5: TestEdge: StartQueueTimer called form ProcessRequestQueue sets internal timer to call Modbus_ProcessRequestQueue in 1.000 seconds
2019.07.08 23:29:40 3: TestEdge: Timeout waiting for a modbus response request: id 1, fCode 3, tid 176, type h, adr 40216, len 27 for device TestEdge reading X_Meter_1_Block_AC_VAR (getUpdate), queued 2.00 secs ago, sent 2.00 secs ago, read buffer empty
2019.07.08 23:29:40 5: TestEdge: DropFrame - drop
2019.07.08 23:29:40 5: TestEdge: StartQueueTimer called form ResponseTimeout sets internal timer to call Modbus_ProcessRequestQueue in 0.000 seconds
2019.07.08 23:29:40 4: TestEdge: ProcessRequestQueue called from HandleTimeout, qlen 8, next entry to id 1 (TestEdge), last send to this device was 2.001 secs ago, last read never, last read on bus never from id 1 (TestEdge)
2019.07.08 23:29:40 5: TestEdge: CheckDelay called from ProcessRequestQueue sendDelay (0.1s since 23:29:38.800) for TestEdge, delay 1.901secs over
2019.07.08 23:29:40 4: TestEdge: ProcessRequestQueue (V4.1.2 - 17.4.2019) qlen 8, sending 00ad0000000601039c6c001a request: id 1, fCode 3, tid 173, type h, adr 40044, len 26 for device TestEdge reading C_Version (getUpdate), queued 2.00 secs ago, read buffer empty
2019.07.08 23:29:40 5: SW: 00ad0000000601039c6c001a
2019.07.08 23:29:40 5: TestEdge: StartQueueTimer called form ProcessRequestQueue sets internal timer to call Modbus_ProcessRequestQueue in 1.000 seconds
2019.07.08 23:29:41 5: TestEdge: ProcessRequestQueue called from HandleTimeout returns, Fhem is still waiting for response, request: id 1, fCode 3, tid 173, type h, adr 40044, len 26 for device TestEdge reading C_Version (getUpdate), queued 3.00 secs ago, sent 1.01 secs ago, read buffer empty, qlen 7, try again in 1 seconds
2019.07.08 23:29:41 5: TestEdge: StartQueueTimer called form ProcessRequestQueue sets internal timer to call Modbus_ProcessRequestQueue in 1.000 seconds
2019.07.08 23:29:42 3: TestEdge: Timeout waiting for a modbus response request: id 1, fCode 3, tid 173, type h, adr 40044, len 26 for device TestEdge reading C_Version (getUpdate), queued 4.00 secs ago, sent 2.00 secs ago, read buffer empty
2019.07.08 23:29:42 5: TestEdge: DropFrame - drop
2019.07.08 23:29:42 5: TestEdge: StartQueueTimer called form ResponseTimeout sets internal timer to call Modbus_ProcessRequestQueue in 0.000 seconds
2019.07.08 23:29:42 4: TestEdge: ProcessRequestQueue called from HandleTimeout, qlen 7, next entry to id 1 (TestEdge), last send to this device was 2.000 secs ago, last read never, last read on bus never from id 1 (TestEdge)
2019.07.08 23:29:42 5: TestEdge: CheckDelay called from ProcessRequestQueue sendDelay (0.1s since 23:29:40.804) for TestEdge, delay 1.901secs over
2019.07.08 23:29:42 4: TestEdge: ProcessRequestQueue (V4.1.2 - 17.4.2019) qlen 7, sending 000a0000000601039cdb0018 request: id 1, fCode 3, tid 10, type h, adr 40155, len 24 for device TestEdge reading X_Meter_1_C_Option (getUpdate), queued 4.00 secs ago, read buffer empty
2019.07.08 23:29:42 5: SW: 000a0000000601039cdb0018
2019.07.08 23:29:42 5: TestEdge: StartQueueTimer called form ProcessRequestQueue sets internal timer to call Modbus_ProcessRequestQueue in 1.000 seconds
2019.07.08 23:29:43 5: TestEdge: ProcessRequestQueue called from HandleTimeout returns, Fhem is still waiting for response, request: id 1, fCode 3, tid 10, type h, adr 40155, len 24 for device TestEdge reading X_Meter_1_C_Option (getUpdate), queued 5.00 secs ago, sent 1.01 secs ago, read buffer empty, qlen 6, try again in 1 seconds
2019.07.08 23:29:43 5: TestEdge: StartQueueTimer called form ProcessRequestQueue sets internal timer to call Modbus_ProcessRequestQueue in 1.000 seconds
2019.07.08 23:29:44 3: TestEdge: Timeout waiting for a modbus response request: id 1, fCode 3, tid 10, type h, adr 40155, len 24 for device TestEdge reading X_Meter_1_C_Option (getUpdate), queued 6.00 secs ago, sent 2.00 secs ago, read buffer empty
2019.07.08 23:29:44 5: TestEdge: DropFrame - drop
2019.07.08 23:29:44 5: TestEdge: StartQueueTimer called form ResponseTimeout sets internal timer to call Modbus_ProcessRequestQueue in 0.000 seconds
2019.07.08 23:29:44 4: TestEdge: ProcessRequestQueue called from HandleTimeout, qlen 6, next entry to id 1 (TestEdge), last send to this device was 2.000 secs ago, last read never, last read on bus never from id 1 (TestEdge)
2019.07.08 23:29:44 5: TestEdge: CheckDelay called from ProcessRequestQueue sendDelay (0.1s since 23:29:42.807) for TestEdge, delay 1.901secs over
2019.07.08 23:29:44 4: TestEdge: ProcessRequestQueue (V4.1.2 - 17.4.2019) qlen 6, sending 00070000000601039ca40008 request: id 1, fCode 3, tid 7, type h, adr 40100, len 8 for device TestEdge reading Block_DC_Power (getUpdate), queued 6.00 secs ago, read buffer empty
2019.07.08 23:29:44 5: SW: 00070000000601039ca40008
2019.07.08 23:29:44 5: TestEdge: StartQueueTimer called form ProcessRequestQueue sets internal timer to call Modbus_ProcessRequestQueue in 1.000 seconds
2019.07.08 23:29:45 5: TestEdge: ProcessRequestQueue called from HandleTimeout returns, Fhem is still waiting for response, request: id 1, fCode 3, tid 7, type h, adr 40100, len 8 for device TestEdge reading Block_DC_Power (getUpdate), queued 7.01 secs ago, sent 1.01 secs ago, read buffer empty, qlen 5, try again in 1 seconds
2019.07.08 23:29:45 5: TestEdge: StartQueueTimer called form ProcessRequestQueue sets internal timer to call Modbus_ProcessRequestQueue in 1.000 seconds
2019.07.08 23:29:46 3: TestEdge: Timeout waiting for a modbus response request: id 1, fCode 3, tid 7, type h, adr 40100, len 8 for device TestEdge reading Block_DC_Power (getUpdate), queued 8.00 secs ago, sent 2.00 secs ago, read buffer empty
2019.07.08 23:29:46 5: TestEdge: DropFrame - drop
2019.07.08 23:29:46 5: TestEdge: StartQueueTimer called form ResponseTimeout sets internal timer to call Modbus_ProcessRequestQueue in 0.000 seconds
2019.07.08 23:29:46 4: TestEdge: ProcessRequestQueue called from HandleTimeout, qlen 5, next entry to id 1 (TestEdge), last send to this device was 2.000 secs ago, last read never, last read on bus never from id 1 (TestEdge)
2019.07.08 23:29:46 5: TestEdge: CheckDelay called from ProcessRequestQueue sendDelay (0.1s since 23:29:44.811) for TestEdge, delay 1.901secs over
2019.07.08 23:29:46 4: TestEdge: ProcessRequestQueue (V4.1.2 - 17.4.2019) qlen 5, sending 00b40000000601039cfb001d request: id 1, fCode 3, tid 180, type h, adr 40187, len 29 for device TestEdge reading X_Meter_1_C_DeviceAddress (getUpdate), queued 8.01 secs ago, read buffer empty
2019.07.08 23:29:46 5: SW: 00b40000000601039cfb001d
2019.07.08 23:29:46 5: TestEdge: StartQueueTimer called form ProcessRequestQueue sets internal timer to call Modbus_ProcessRequestQueue in 1.000 seconds
2019.07.08 23:29:47 5: TestEdge: ProcessRequestQueue called from HandleTimeout returns, Fhem is still waiting for response, request: id 1, fCode 3, tid 180, type h, adr 40187, len 29 for device TestEdge reading X_Meter_1_C_DeviceAddress (getUpdate), queued 9.01 secs ago, sent 1.01 secs ago, read buffer empty, qlen 4, try again in 1 seconds
2019.07.08 23:29:47 5: TestEdge: StartQueueTimer called form ProcessRequestQueue sets internal timer to call Modbus_ProcessRequestQueue in 1.000 seconds
2019.07.08 23:29:48 3: TestEdge: Timeout waiting for a modbus response request: id 1, fCode 3, tid 180, type h, adr 40187, len 29 for device TestEdge reading X_Meter_1_C_DeviceAddress (getUpdate), queued 10.01 secs ago, sent 2.00 secs ago, read buffer empty
2019.07.08 23:29:48 5: TestEdge: DropFrame - drop
2019.07.08 23:29:48 5: TestEdge: StartQueueTimer called form ResponseTimeout sets internal timer to call Modbus_ProcessRequestQueue in 0.000 seconds
2019.07.08 23:29:48 4: TestEdge: ProcessRequestQueue called from HandleTimeout, qlen 4, next entry to id 1 (TestEdge), last send to this device was 2.003 secs ago, last read never, last read on bus never from id 1 (TestEdge)
2019.07.08 23:29:48 5: TestEdge: CheckDelay called from ProcessRequestQueue sendDelay (0.1s since 23:29:46.815) for TestEdge, delay 1.904secs over
2019.07.08 23:29:48 4: TestEdge: ProcessRequestQueue (V4.1.2 - 17.4.2019) qlen 4, sending 00630000000601039c87001d request: id 1, fCode 3, tid 99, type h, adr 40071, len 29 for device TestEdge reading Block_AC_Current (getUpdate), queued 10.01 secs ago, read buffer empty
2019.07.08 23:29:48 5: SW: 00630000000601039c87001d
2019.07.08 23:29:48 5: TestEdge: StartQueueTimer called form ProcessRequestQueue sets internal timer to call Modbus_ProcessRequestQueue in 1.000 seconds
2019.07.08 23:29:49 5: TestEdge: ProcessRequestQueue called from HandleTimeout returns, Fhem is still waiting for response, request: id 1, fCode 3, tid 99, type h, adr 40071, len 29 for device TestEdge reading Block_AC_Current (getUpdate), queued 11.01 secs ago, sent 1.01 secs ago, read buffer empty, qlen 3, try again in 1 seconds
2019.07.08 23:29:49 5: TestEdge: StartQueueTimer called form ProcessRequestQueue sets internal timer to call Modbus_ProcessRequestQueue in 1.000 seconds
2019.07.08 23:29:50 3: TestEdge: Timeout waiting for a modbus response request: id 1, fCode 3, tid 99, type h, adr 40071, len 29 for device TestEdge reading Block_AC_Current (getUpdate), queued 12.01 secs ago, sent 2.00 secs ago, read buffer empty
2019.07.08 23:29:50 5: TestEdge: DropFrame - drop
2019.07.08 23:29:50 5: TestEdge: StartQueueTimer called form ResponseTimeout sets internal timer to call Modbus_ProcessRequestQueue in 0.000 seconds
2019.07.08 23:29:50 4: TestEdge: ProcessRequestQueue called from HandleTimeout, qlen 3, next entry to id 1 (TestEdge), last send to this device was 2.000 secs ago, last read never, last read on bus never from id 1 (TestEdge)
2019.07.08 23:29:50 5: TestEdge: CheckDelay called from ProcessRequestQueue sendDelay (0.1s since 23:29:48.821) for TestEdge, delay 1.901secs over
2019.07.08 23:29:50 4: TestEdge: ProcessRequestQueue (V4.1.2 - 17.4.2019) qlen 3, sending 00790000000601039c40001c request: id 1, fCode 3, tid 121, type h, adr 40000, len 28 for device TestEdge reading C_SunSpec_ID (getUpdate), queued 12.01 secs ago, read buffer empty
2019.07.08 23:29:50 5: SW: 00790000000601039c40001c
2019.07.08 23:29:50 5: TestEdge: StartQueueTimer called form ProcessRequestQueue sets internal timer to call Modbus_ProcessRequestQueue in 1.000 seconds
2019.07.08 23:29:51 5: TestEdge: ProcessRequestQueue called from HandleTimeout returns, Fhem is still waiting for response, request: id 1, fCode 3, tid 121, type h, adr 40000, len 28 for device TestEdge reading C_SunSpec_ID (getUpdate), queued 13.02 secs ago, sent 1.01 secs ago, read buffer empty, qlen 2, try again in 1 seconds
2019.07.08 23:29:51 5: TestEdge: StartQueueTimer called form ProcessRequestQueue sets internal timer to call Modbus_ProcessRequestQueue in 1.000 seconds
2019.07.08 23:29:52 3: TestEdge: Timeout waiting for a modbus response request: id 1, fCode 3, tid 121, type h, adr 40000, len 28 for device TestEdge reading C_SunSpec_ID (getUpdate), queued 14.01 secs ago, sent 2.00 secs ago, read buffer empty
2019.07.08 23:29:52 5: TestEdge: DropFrame - drop
2019.07.08 23:29:52 5: TestEdge: StartQueueTimer called form ResponseTimeout sets internal timer to call Modbus_ProcessRequestQueue in 0.000 seconds
2019.07.08 23:29:52 4: TestEdge: ProcessRequestQueue called from HandleTimeout, qlen 2, next entry to id 1 (TestEdge), last send to this device was 2.000 secs ago, last read never, last read on bus never from id 1 (TestEdge)
2019.07.08 23:29:52 5: TestEdge: CheckDelay called from ProcessRequestQueue sendDelay (0.1s since 23:29:50.825) for TestEdge, delay 1.901secs over
2019.07.08 23:29:52 4: TestEdge: ProcessRequestQueue (V4.1.2 - 17.4.2019) qlen 2, sending 00340000000601039cbb0018 request: id 1, fCode 3, tid 52, type h, adr 40123, len 24 for device TestEdge reading X_Meter_1_C_Manufacturer (getUpdate), queued 14.01 secs ago, read buffer empty
2019.07.08 23:29:52 5: SW: 00340000000601039cbb0018
2019.07.08 23:29:52 5: TestEdge: StartQueueTimer called form ProcessRequestQueue sets internal timer to call Modbus_ProcessRequestQueue in 1.000 seconds
2019.07.08 23:29:53 5: TestEdge: ProcessRequestQueue called from HandleTimeout returns, Fhem is still waiting for response, request: id 1, fCode 3, tid 52, type h, adr 40123, len 24 for device TestEdge reading X_Meter_1_C_Manufacturer (getUpdate), queued 15.02 secs ago, sent 1.01 secs ago, read buffer empty, qlen 1, try again in 1 seconds
2019.07.08 23:29:53 5: TestEdge: StartQueueTimer called form ProcessRequestQueue sets internal timer to call Modbus_ProcessRequestQueue in 1.000 seconds
2019.07.08 23:29:54 3: TestEdge: Timeout waiting for a modbus response request: id 1, fCode 3, tid 52, type h, adr 40123, len 24 for device TestEdge reading X_Meter_1_C_Manufacturer (getUpdate), queued 16.01 secs ago, sent 2.00 secs ago, read buffer empty
2019.07.08 23:29:54 5: TestEdge: DropFrame - drop
2019.07.08 23:29:54 5: TestEdge: StartQueueTimer called form ResponseTimeout sets internal timer to call Modbus_ProcessRequestQueue in 0.000 seconds
2019.07.08 23:29:54 4: TestEdge: ProcessRequestQueue called from HandleTimeout, qlen 1, next entry to id 1 (TestEdge), last send to this device was 1.999 secs ago, last read never, last read on bus never from id 1 (TestEdge)
2019.07.08 23:29:54 5: TestEdge: CheckDelay called from ProcessRequestQueue sendDelay (0.1s since 23:29:52.828) for TestEdge, delay 1.900secs over
2019.07.08 23:29:54 4: TestEdge: ProcessRequestQueue (V4.1.2 - 17.4.2019) qlen 1, sending 00080000000601039d330011 request: id 1, fCode 3, tid 8, type h, adr 40243, len 17 for device TestEdge reading X_Meter_1_Block_Energy_VA (getUpdate), queued 16.02 secs ago, read buffer empty
2019.07.08 23:29:54 5: SW: 00080000000601039d330011
2019.07.08 23:29:54 5: TestEdge: StartQueueTimer called from ProcessRequestQueue removes internal timer because it is not needed now
2019.07.08 23:29:56 3: TestEdge: Timeout waiting for a modbus response request: id 1, fCode 3, tid 8, type h, adr 40243, len 17 for device TestEdge reading X_Meter_1_Block_Energy_VA (getUpdate), queued 18.02 secs ago, sent 2.00 secs ago, read buffer empty
2019.07.08 23:29:56 5: TestEdge: DropFrame - drop
2019.07.08 23:29:56 5: TestEdge: StartQueueTimer called from ResponseTimeout removes internal timer because it is not needed now

Offline Metalomaniac

  • New Member
  • *
  • Beiträge: 5
Antw:ModbusAttr an Wechselrichter SolarEdge SE10k [gelöst]
« Antwort #118 am: 10 Juli 2019, 20:31:31 »
Ich bin mal die ganzen Tipps nochmal durchgegangen und hab einfach alles nochmal probiert...
Ich bin mir eigentlich sicher, dass ich Modbus ID "2" auch schon getestet habe - und es nicht funktioniert hat...... jetzt hat es geklappt. Lag bestimmt an mir, Tippfehler oder so.

Danke allen Helfern!

Offline TomS85

  • New Member
  • *
  • Beiträge: 4
Antw:ModbusAttr an Wechselrichter SolarEdge SE10k [gelöst]
« Antwort #119 am: 09 Oktober 2019, 11:19:09 »
Versuche mal ein Update. Ich habe das Modul auf github zu liegen. https://github.com/pejonp/FHEM---SolarEdge

update all https://raw.githubusercontent.com/pejonp/FHEM---SolarEdge/master/controls_SolarEdge.txt

@pejonp
Blöde Frage - ich habe gestern erst mit FHEM begonnen und möchte das Modul einbinden. Ich habe zwar schon begonnen, nach der Anleitung in der Wiki die Werte meine SE25k auszulesen, was auch soweit funktioniert. Aber ich möchte nun doch gerne dein Modul installieren, da ich mich derzeit schwer tue, über die Attribute und Dummys hinaus den Perl Code einzubinden (scheint bei mir irgendwie nicht zu funktionieren). Daher hatte ich mal deine Module von github heruntergeladen und ins FHEM Verzeichnis geladen. Aber nun weiß ich nicht, wie ich die einbinden kann. Kannst du vielleicht weiterhelfen?

Danke und Gruß,
Tom