Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Beta ioBroker.plenticore-g3

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Beta ioBroker.plenticore-g3

    This topic has been deleted. Only users with topic management privileges can see it.
    • FernetMenta
      FernetMenta @mule last edited by FernetMenta

      @mule

      Folgende Parameter, welche ich bisher verwende, konnte ich im Adapter nicht finden/zuordnen

      devices.local.battery.SoC ist da und sogar preset
      devices:local/HomePv_P ist auch da (optional)
      devices.local.ToGrid_P gibt es als devices:local/Grid_P (to grid sind negative Werte)
      devices.local.battery.Discharge_P ist in devices:local:battery/P
      devices.local.battery.Charge_P ist auch in devices:local:battery/P

      Der "alte" Adapter macht aus battery/P "Charge und Discharge", was ich nicht besonders glücklich finde: https://github.com/pixcept/ioBroker.plenticore/blob/master/main.js#L274

      1 Reply Last reply Reply Quote 0
      • T
        TomRacoon last edited by

        Hallo,
        hab gerade mal den Adapter installiert und angeworfen. Läuft erstmal soweit ohne Fehler, die Konfiguration der Datenpunkte die ausgelesen werden find eich superklasse.
        Danke dafür.

        Wir hatten in dem anderen Kostal Forumsthread schon einmal über die Gesamterzeugung für den Tag gesprochen und Du hattest geschrieben:

        "Der PV-Ertrag, wie er im Solar-Portal angezeigt wird, dürfte so berechntet werden:
        Statistic:Yield + Statistic:EnergyChargePv - Statistic:EnergyHomeBat
        "

        Müsste da nicht auch noch die Netzeinspeisung hinzugefügt werden, um den Gesamtwert zu bekommen (und somit ist der Wert nicht innerhalb des Adapters zu ermittelten)?
        Den Gesamtwert, so wie er in der App dargestellt wird ist nicht als Datenpunkt verfügbar? Dieser ist ja dann die Gesamterzeugung unabhängig von Verbrauch, Batterien und Einspeisung...

        Mir ist gerade ein möglicher Bug in Verbindung mit der VIS aufgefallen.
        Ich lasse mir die Autarkie bisher in der VIS so anzeigen:

        Selbstversorgung Heute: {wert:alias.0.PV.Aktuell.Autarkie;parseInt(wert).toFixed(1)} % / Gesamt {wert:plenticore-g3.0.processdata.scb.statistic.EnergyFlow.Statistic:Autarky:Total;parseInt(wert).toFixed(1)} %
        

        Hier scheint es so zu sein, dass die VIS mit den Doppelpunkten im Namen nicht klarkommt. Die Anzeige ist NaN.
        Die Anzeige über einen Alias funktioniert:

        Selbstversorgung Heute: {wert:alias.0.PV.Aktuell.Autarkie;parseInt(wert).toFixed(1)} % / Gesamt {wert:alias.0.PV.AutarkieTotal;parseInt(wert).toFixed(1)} %
        

        Grüße,
        Chris

        FernetMenta 1 Reply Last reply Reply Quote 0
        • FernetMenta
          FernetMenta @TomRacoon last edited by FernetMenta

          @tomracoon erst mal danke fürs Testen!

          Müsste da nicht auch noch die Netzeinspeisung hinzugefügt werden

          Die Einspeisung steckt ja im Yield drin und berechnet sich folgendermaßen:

          1
          Einspeisung = Yield - Statistic:EnergyHomeBat - Statistic:EnergyHomePV
          2
          PV-Ertrag = Einspeisung + HomePV + ChargePV

          1 in 2
          PV-Ertrag = Yield - HomeBat - HomePV + HomePV + ChargePV = Yield - HomeBat + ChargePV

          Mir ist gerade ein möglicher Bug in Verbindung mit der VIS aufgefallen

          Guter Punkt. Ich verwende Jarvis und das ist mir nicht aufgefallen. Ich kann den Doppelpunkt durch einen '_' austauschen. Damit kommt die VIS klar?

          EDIT: '_' geht leider nicht, weil der in den Namen schon vorkommen kann. Kann man das VIS Problem irgendwie anders lösen? Ich habe andere Adapter, wie smartmeter, wo ebenfalls ein Doppelpunkt in den Namen vorkommt.

          mcm1957 1 Reply Last reply Reply Quote 0
          • mcm1957
            mcm1957 @FernetMenta last edited by

            @FernetMenta

            Optimaler Weise sollten State Ids nur aus [a-Za-z0-9-_] bestehen. Insbesondere Leerzeichen aber auch andere Sonderzeichen und Umlaute machen immer wieser Probleme mit VISsen oder anderen Adaptern.

            FernetMenta 1 Reply Last reply Reply Quote 0
            • FernetMenta
              FernetMenta @mcm1957 last edited by

              @mcm1957 sagte in Beta ioBroker.plenticore-g3:

              @FernetMenta

              Optimaler Weise sollten State Ids nur aus [a-Za-z0-9-_] bestehen. Insbesondere Leerzeichen aber auch andere Sonderzeichen und Umlaute machen immer wieser Probleme mit VISsen oder anderen Adaptern.

              Hast du eine Idee, wie ich ':' ersetzen kann, so dass die Rückwärtstransformation auch wieder klappt? Vielleicht kennst du das Problem ja von anderen Adaptern.

              mcm1957 1 Reply Last reply Reply Quote 0
              • mcm1957
                mcm1957 @FernetMenta last edited by

                @fernetmenta
                Rückwärtstransformation?
                Ich nehme an du brauchts ein Mapping state id -> "device string".

                Du kannst im native Bereich des State Objects beliebige Infos abspeichern. Da kannst du dir den String den das Device haben will merken. Ansonsten stell die Frage besser im Telegramm / Discord Chat da sind mehr Entwickler vorhanden 🙂

                FernetMenta 1 Reply Last reply Reply Quote 0
                • FernetMenta
                  FernetMenta @mcm1957 last edited by

                  @mcm1957 Danke, gute Tipp mit dem Native-Bereich. Das werde ich machen.

                  Ich bin kein Fan von Telegram und Discord. Das kann man eigentlich nicht benutzen, wenn man die AGBs sorgfältig gelesen hat. Es gibt Signal und Slack als deutlich bessere Alternativen.

                  mcm1957 1 Reply Last reply Reply Quote 0
                  • mcm1957
                    mcm1957 @FernetMenta last edited by

                    @fernetmenta
                    Na ja - dev Support ist halt primär dort.

                    FernetMenta 1 Reply Last reply Reply Quote 0
                    • FernetMenta
                      FernetMenta @mcm1957 last edited by

                      @mcm1957 Ich werde morgen eine neue Version erstellen, die dann ohne ':' auskommen wird. Soll ich die Version im Header hier oben dann anpassen?

                      mcm1957 1 Reply Last reply Reply Quote 0
                      • mcm1957
                        mcm1957 @FernetMenta last edited by

                        @fernetmenta
                        Ja, erster Beitrag sollte immer aktualisiert werden.
                        Titel, Testversion, Veröffentlichungsdatum und ggF. Changelog

                        DANKE

                        P.S. Review hoff ich nächstes Wochenende irgendwie hinzubekommen. Bin den Rest der Woche auf Kurzurlaub und ansonten fehlt jede Menge Zeit ... Sorry.

                        FernetMenta 1 Reply Last reply Reply Quote 1
                        • FernetMenta
                          FernetMenta @mcm1957 last edited by

                          @TomRacoon die neue Version 0.0.7 hat jetzt keine Doppelpunkte mehr in den IDs.

                          T 1 Reply Last reply Reply Quote 0
                          • T
                            TomRacoon @FernetMenta last edited by

                            @fernetmenta
                            Getestet und funktioniert jetzt auch direkt in der Vis.
                            Super,
                            Danke

                            1 Reply Last reply Reply Quote 1
                            • M
                              mule last edited by

                              @FernetMenta
                              Gestern Nacht hat ioBroker die Instance des Adapters aufgrund zu häufiger Crashs gestoppt. Hintergrund war, dass gestern Nacht zu dieser Zeit der Plenticore das neueste Update eingespielt hat und daher zeitweise nicht zur Verfügung stand. Anscheinend führt die Nichtverfügbarkeit des Plenticore dann zum Crash des Adapters, welcher dann immer wieder neu gestartet wird und irgendwann dann von ioBroker vorsichtshalber geblockt wird.

                              FernetMenta 1 Reply Last reply Reply Quote 0
                              • FernetMenta
                                FernetMenta @mule last edited by FernetMenta

                                @mule kannst du bitte das logfile posten?

                                EDIT: Wenn ich das Problem finden kann, kann ich das Updaten dann bei mir gleich testen. Ich habe es noch nciht eingespielt.

                                M 1 Reply Last reply Reply Quote 0
                                • M
                                  mule @FernetMenta last edited by mule

                                  @fernetmenta
                                  Das Update startete um 0:45Uhr

                                  2025-03-28 00:46:06.004  - warn: plenticore-g3.0 (293579) get settings failed with code 503: [object Object]
                                  2025-03-28 00:46:59.494  - warn: plenticore-g3.0 (293579) API request failed with error {"errno":-113,"code":"EHOSTUNREACH","syscall":"connect","address":"192.168.178.180","port":80}
                                  2025-03-28 00:46:59.495  - warn: plenticore-g3.0 (293579) Error: API request failed with error {"errno":-113,"code":"EHOSTUNREACH","syscall":"connect","address":"192.168.178.180","port":80}
                                  2025-03-28 00:47:14.746  - error: plenticore-g3.0 (293579) uncaught exception: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
                                  2025-03-28 00:47:14.747  - error: plenticore-g3.0 (293579) SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
                                      at JSON.parse (<anonymous>)
                                      at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/iobroker.plenticore-g3/lib/plenticoreAPI.js:102:42)
                                      at IncomingMessage.emit (node:events:536:35)
                                      at endReadableNT (node:internal/streams/readable:1698:12)
                                      at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
                                  2025-03-28 00:47:14.748  - error: plenticore-g3.0 (293579) Unexpected token '<', "<!DOCTYPE "... is not valid JSON
                                  2025-03-28 00:47:14.751  - info: plenticore-g3.0 (293579) terminating
                                  2025-03-28 00:47:14.752  - warn: plenticore-g3.0 (293579) Terminated (UNCAUGHT_EXCEPTION): Without reason
                                  2025-03-28 00:47:15.255  - info: plenticore-g3.0 (293579) terminating
                                  2025-03-28 00:47:15.329  - error: host.iobroker instance system.adapter.plenticore-g3.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                                  2025-03-28 00:47:15.329  - info: host.iobroker Restart adapter system.adapter.plenticore-g3.0 because enabled
                                  2025-03-28 00:47:46.060  - info: host.iobroker instance system.adapter.plenticore-g3.0 in version "0.0.7" (non-npm: FernetMenta/ioBroker.plenticore-g3#v0.0.7) started with pid 308438
                                  2025-03-28 00:47:47.643  - info: plenticore-g3.0 (308438) starting. Version 0.0.7 (non-npm: FernetMenta/ioBroker.plenticore-g3#v0.0.7) in /opt/iobroker/node_modules/iobroker.plenticore-g3, node: v20.19.0, js-controller: 7.0.6
                                  2025-03-28 00:47:47.714  - error: plenticore-g3.0 (308438) uncaught exception: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
                                  2025-03-28 00:47:47.715  - error: plenticore-g3.0 (308438) SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
                                      at JSON.parse (<anonymous>)
                                      at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/iobroker.plenticore-g3/lib/plenticoreAPI.js:102:42)
                                      at IncomingMessage.emit (node:events:536:35)
                                      at endReadableNT (node:internal/streams/readable:1698:12)
                                      at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
                                  2025-03-28 00:47:47.716  - error: plenticore-g3.0 (308438) Unexpected token '<', "<!DOCTYPE "... is not valid JSON
                                  2025-03-28 00:47:47.724  - info: plenticore-g3.0 (308438) terminating
                                  2025-03-28 00:47:47.726  - warn: plenticore-g3.0 (308438) Terminated (UNCAUGHT_EXCEPTION): Without reason
                                  2025-03-28 00:47:48.229  - info: plenticore-g3.0 (308438) terminating
                                  2025-03-28 00:47:48.317  - error: host.iobroker instance system.adapter.plenticore-g3.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                                  2025-03-28 00:47:48.318  - info: host.iobroker Restart adapter system.adapter.plenticore-g3.0 because enabled
                                  2025-03-28 00:48:19.068  - info: host.iobroker instance system.adapter.plenticore-g3.0 in version "0.0.7" (non-npm: FernetMenta/ioBroker.plenticore-g3#v0.0.7) started with pid 308469
                                  2025-03-28 00:48:20.650  - info: plenticore-g3.0 (308469) starting. Version 0.0.7 (non-npm: FernetMenta/ioBroker.plenticore-g3#v0.0.7) in /opt/iobroker/node_modules/iobroker.plenticore-g3, node: v20.19.0, js-controller: 7.0.6
                                  2025-03-28 00:48:20.720  - error: plenticore-g3.0 (308469) uncaught exception: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
                                  2025-03-28 00:48:20.721  - error: plenticore-g3.0 (308469) SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
                                      at JSON.parse (<anonymous>)
                                      at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/iobroker.plenticore-g3/lib/plenticoreAPI.js:102:42)
                                      at IncomingMessage.emit (node:events:536:35)
                                      at endReadableNT (node:internal/streams/readable:1698:12)
                                      at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
                                  2025-03-28 00:48:20.722  - error: plenticore-g3.0 (308469) Unexpected token '<', "<!DOCTYPE "... is not valid JSON
                                  2025-03-28 00:48:20.732  - info: plenticore-g3.0 (308469) terminating
                                  2025-03-28 00:48:20.733  - warn: plenticore-g3.0 (308469) Terminated (UNCAUGHT_EXCEPTION): Without reason
                                  2025-03-28 00:48:21.235  - info: plenticore-g3.0 (308469) terminating
                                  2025-03-28 00:48:21.310  - error: host.iobroker instance system.adapter.plenticore-g3.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                                  2025-03-28 00:48:21.311  - info: host.iobroker Restart adapter system.adapter.plenticore-g3.0 because enabled
                                  2025-03-28 00:48:21.311  - warn: host.iobroker Do not restart adapter system.adapter.plenticore-g3.0 because restart loop detected
                                  
                                  FernetMenta 1 Reply Last reply Reply Quote 0
                                  • FernetMenta
                                    FernetMenta @mule last edited by

                                    @mule sagte in Beta ioBroker.plenticore-g3:

                                    00:47:14.74

                                    Danke! Ich sehe den Fehler. Werde eine neue Version erstellen und das Update dann heute Abend bei mir testen.

                                    FernetMenta 1 Reply Last reply Reply Quote 0
                                    • FernetMenta
                                      FernetMenta @FernetMenta last edited by

                                      Neue Version 0.1.0 ist draußen. Für Updates habe ich eine admin Notification eingebaut, wenn es ein neues gibt und man nicht automatisch installieren gewählt hat.

                                      M 1 Reply Last reply Reply Quote 0
                                      • M
                                        mule @FernetMenta last edited by

                                        @fernetmenta Danke!

                                        FernetMenta 1 Reply Last reply Reply Quote 0
                                        • FernetMenta
                                          FernetMenta @mule last edited by

                                          Der Adapter ist jetzt über das beta repo installierbar.

                                          V 1 Reply Last reply Reply Quote 2
                                          • V
                                            vmi @FernetMenta last edited by

                                            @fernetmenta danke für den Adapter.

                                            Habe den Plenticore G3 L und bekomme leider folgende Fehlermeldung:

                                            2025-06-10 21:16:10.779	warn	Error: API request failed with error {"errno":-71,"code":"EPROTO","syscall":"write"}
                                            
                                            2025-06-10 21:16:10.777	warn	API request failed with error {"errno":-71,"code":"EPROTO","syscall":"write"}
                                            

                                            hier noch der debug:

                                            2025-06-10 21:26:11.110	debug	API connection closed
                                            plenticore-g3.0
                                            	2025-06-10 21:26:11.109	debug	Result of API request: code: 200, headers: [object Object], body: [{"moduleid":"devices:local","processdataids":["Bat2Grid_P","BatDetection","Dc_P","DigitalIn","DigitalOut","EM_State","Grid2Bat_P","Grid_L1_I","Grid_L1_P","Grid_L2_I","Grid_L2_P","Grid_L3_I","Grid_L3_P","Grid_P","Grid_Q","Grid_S","HomeBat_P","HomeGrid_P","HomeOwn_P","HomePv_P","Home_P","Inverter:State","Iso_R","LimitEvuAbs","LimitEvuRel","PV2Bat_P","WorkTime","WorkTimeESB"]},{"moduleid":"devices:local:ac","processdataids":["CosPhi","Frequency","InvIn_P","InvOut_P","L1_I","L1_P","L1_U","L2_I","L2_P","L2_U","L3_I","L3_P","L3_U","P","Q","ResidualCDc_I","S"]},{"moduleid":"devices:local:cancom","processdataids":[]},{"moduleid":"devices:local:powermeter","processdataids":["CosPhi","Exp_E","Exp_EQ","Exp_ES","Frequency","Imp_E","Imp_EQ","Imp_ES","L1_I","L1_P","L1_Q","L1_S","L1_U","L2_I","L2_P","L2_Q","L2_S","L2_U","L3_I","L3_P","L3_Q","L3_S","L3_U","P","Q","S"]},{"moduleid":"devices:local:pv1","processdataids":["I","P","U"]},{"moduleid":"devices:local:pv2","processdataids":["I","P","U"]},{"moduleid":"devices:local:pv3","processdataids":["I","P","U"]},{"moduleid":"scb:diagnostics","processdataids":[]},{"moduleid":"scb:event","processdataids":["ErrMc","ErrSFH","Event:ActiveAckCnt","Event:ActiveAckCode","Event:ActiveErrorCnt","Event:ActiveWarningCnt"]},{"moduleid":"scb:export","processdataids":["FtpConActive","PortalConActive"]},{"moduleid":"scb:network:ProcessData","processdataids":[]},{"moduleid":"scb:pemanager","processdataids":["PEM:Charging","PEM:Tarif:ChargingPrice","PEM:Tarif:ChargingStrategy","PEM:Tarif:CurrentPrice"]},{"moduleid":"scb:statistic:EnergyFlow","processdataids":["Statistic:Autarky:Day","Statistic:Autarky:Month","Statistic:Autarky:Total","Statistic:Autarky:Year","Statistic:CO2Saving:Day","Statistic:CO2Saving:Month","Statistic:CO2Saving:Total","Statistic:CO2Saving:Year","Statistic:EnergyChargeGrid:Day","Statistic:EnergyChargeGrid:Month","Statistic:EnergyChargeGrid:Total","Statistic:EnergyChargeGrid:Year","Statistic:EnergyChargeInvIn:Day","Statistic:EnergyChargeInvIn:Month","Statistic:EnergyChargeInvIn:Total","Statistic:EnergyChargeInvIn:Year","Statistic:EnergyChargePv:Day","Statistic:EnergyChargePv:Month","Statistic:EnergyChargePv:Total","Statistic:EnergyChargePv:Year","Statistic:EnergyDischarge:Day","Statistic:EnergyDischarge:Month","Statistic:EnergyDischarge:Total","Statistic:EnergyDischarge:Year","Statistic:EnergyDischargeGrid:Day","Statistic:EnergyDischargeGrid:Month","Statistic:EnergyDischargeGrid:Total","Statistic:EnergyDischargeGrid:Year","Statistic:EnergyHome:Day","Statistic:EnergyHome:Month","Statistic:EnergyHome:Total","Statistic:EnergyHome:Year","Statistic:EnergyHomeBat:Day","Statistic:EnergyHomeBat:Month","Statistic:EnergyHomeBat:Total","Statistic:EnergyHomeBat:Year","Statistic:EnergyHomeGrid:Day","Statistic:EnergyHomeGrid:Month","Statistic:EnergyHomeGrid:Total","Statistic:EnergyHomeGrid:Year","Statistic:EnergyHomeOwn:Total","Statistic:EnergyHomePv:Day","Statistic:EnergyHomePv:Month","Statistic:EnergyHomePv:Total","Statistic:EnergyHomePv:Year","Statistic:EnergyPv1:Day","Statistic:EnergyPv1:Month","Statistic:EnergyPv1:Total","Statistic:EnergyPv1:Year","Statistic:EnergyPv2:Day","Statistic:EnergyPv2:Month","Statistic:EnergyPv2:Total","Statistic:EnergyPv2:Year","Statistic:EnergyPv3:Day","Statistic:EnergyPv3:Month","Statistic:EnergyPv3:Total","Statistic:EnergyPv3:Year","Statistic:OwnConsumptionRate:Day","Statistic:OwnConsumptionRate:Month","Statistic:OwnConsumptionRate:Total","Statistic:OwnConsumptionRate:Year","Statistic:Yield:Day","Statistic:Yield:Month","Statistic:Yield:Total","Statistic:Yield:Year"]},{"moduleid":"scb:system","processdataids":["System:Props:BatOptions","System:Props:Battery","System:Props:CeiInputSupport","System:Props:DigOutMode","System:Props:ExtBatCtrl","System:Props:HWversion","System:Props:InverterGen","System:Props:Lmg","System:Props:Pv","System:Props:RSE","System:Props:ShadowMgmt","System:Props:WlanSupport","System:State"]},{"moduleid":"scb:update","processdataids":["Update:Progress","Update:Status","Update:StatusTime","Update:Version"]}]
                                            plenticore-g3.0
                                            	2025-06-10 21:26:10.578	debug	Making request to endpoint processdata with data {"method":"GET","port":"80","host":"192.168.178.81","path":"/api/v1/processdata","headers":{"User-Agent":"Mozilla/5.0 (X11; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0","Content-Type":"application/json","Authorization":"Session fb772bd52e4683f947ad27f8fc4b55d4a51811cdf85fdd95f3eb2a8e92c9a873"},"rejectUnauthorized":false}
                                            plenticore-g3.0
                                            	2025-06-10 21:25:55.406	debug	API connection closed
                                            plenticore-g3.0
                                            	2025-06-10 21:25:55.406	debug	Result of API request: code: 200, headers: [object Object], body: [{"moduleid":"devices:local","processdataids":["Bat2Grid_P","BatDetection","Dc_P","DigitalIn","DigitalOut","EM_State","Grid2Bat_P","Grid_L1_I","Grid_L1_P","Grid_L2_I","Grid_L2_P","Grid_L3_I","Grid_L3_P","Grid_P","Grid_Q","Grid_S","HomeBat_P","HomeGrid_P","HomeOwn_P","HomePv_P","Home_P","Inverter:State","Iso_R","LimitEvuAbs","LimitEvuRel","PV2Bat_P","WorkTime","WorkTimeESB"]},{"moduleid":"devices:local:ac","processdataids":["CosPhi","Frequency","InvIn_P","InvOut_P","L1_I","L1_P","L1_U","L2_I","L2_P","L2_U","L3_I","L3_P","L3_U","P","Q","ResidualCDc_I","S"]},{"moduleid":"devices:local:cancom","processdataids":[]},{"moduleid":"devices:local:powermeter","processdataids":["CosPhi","Exp_E","Exp_EQ","Exp_ES","Frequency","Imp_E","Imp_EQ","Imp_ES","L1_I","L1_P","L1_Q","L1_S","L1_U","L2_I","L2_P","L2_Q","L2_S","L2_U","L3_I","L3_P","L3_Q","L3_S","L3_U","P","Q","S"]},{"moduleid":"devices:local:pv1","processdataids":["I","P","U"]},{"moduleid":"devices:local:pv2","processdataids":["I","P","U"]},{"moduleid":"devices:local:pv3","processdataids":["I","P","U"]},{"moduleid":"scb:diagnostics","processdataids":[]},{"moduleid":"scb:event","processdataids":["ErrMc","ErrSFH","Event:ActiveAckCnt","Event:ActiveAckCode","Event:ActiveErrorCnt","Event:ActiveWarningCnt"]},{"moduleid":"scb:export","processdataids":["FtpConActive","PortalConActive"]},{"moduleid":"scb:network:ProcessData","processdataids":[]},{"moduleid":"scb:pemanager","processdataids":["PEM:Charging","PEM:Tarif:ChargingPrice","PEM:Tarif:ChargingStrategy","PEM:Tarif:CurrentPrice"]},{"moduleid":"scb:statistic:EnergyFlow","processdataids":["Statistic:Autarky:Day","Statistic:Autarky:Month","Statistic:Autarky:Total","Statistic:Autarky:Year","Statistic:CO2Saving:Day","Statistic:CO2Saving:Month","Statistic:CO2Saving:Total","Statistic:CO2Saving:Year","Statistic:EnergyChargeGrid:Day","Statistic:EnergyChargeGrid:Month","Statistic:EnergyChargeGrid:Total","Statistic:EnergyChargeGrid:Year","Statistic:EnergyChargeInvIn:Day","Statistic:EnergyChargeInvIn:Month","Statistic:EnergyChargeInvIn:Total","Statistic:EnergyChargeInvIn:Year","Statistic:EnergyChargePv:Day","Statistic:EnergyChargePv:Month","Statistic:EnergyChargePv:Total","Statistic:EnergyChargePv:Year","Statistic:EnergyDischarge:Day","Statistic:EnergyDischarge:Month","Statistic:EnergyDischarge:Total","Statistic:EnergyDischarge:Year","Statistic:EnergyDischargeGrid:Day","Statistic:EnergyDischargeGrid:Month","Statistic:EnergyDischargeGrid:Total","Statistic:EnergyDischargeGrid:Year","Statistic:EnergyHome:Day","Statistic:EnergyHome:Month","Statistic:EnergyHome:Total","Statistic:EnergyHome:Year","Statistic:EnergyHomeBat:Day","Statistic:EnergyHomeBat:Month","Statistic:EnergyHomeBat:Total","Statistic:EnergyHomeBat:Year","Statistic:EnergyHomeGrid:Day","Statistic:EnergyHomeGrid:Month","Statistic:EnergyHomeGrid:Total","Statistic:EnergyHomeGrid:Year","Statistic:EnergyHomeOwn:Total","Statistic:EnergyHomePv:Day","Statistic:EnergyHomePv:Month","Statistic:EnergyHomePv:Total","Statistic:EnergyHomePv:Year","Statistic:EnergyPv1:Day","Statistic:EnergyPv1:Month","Statistic:EnergyPv1:Total","Statistic:EnergyPv1:Year","Statistic:EnergyPv2:Day","Statistic:EnergyPv2:Month","Statistic:EnergyPv2:Total","Statistic:EnergyPv2:Year","Statistic:EnergyPv3:Day","Statistic:EnergyPv3:Month","Statistic:EnergyPv3:Total","Statistic:EnergyPv3:Year","Statistic:OwnConsumptionRate:Day","Statistic:OwnConsumptionRate:Month","Statistic:OwnConsumptionRate:Total","Statistic:OwnConsumptionRate:Year","Statistic:Yield:Day","Statistic:Yield:Month","Statistic:Yield:Total","Statistic:Yield:Year"]},{"moduleid":"scb:system","processdataids":["System:Props:BatOptions","System:Props:Battery","System:Props:CeiInputSupport","System:Props:DigOutMode","System:Props:ExtBatCtrl","System:Props:HWversion","System:Props:InverterGen","System:Props:Lmg","System:Props:Pv","System:Props:RSE","System:Props:ShadowMgmt","System:Props:WlanSupport","System:State"]},{"moduleid":"scb:update","processdataids":["Update:Progress","Update:Status","Update:StatusTime","Update:Version"]}]
                                            plenticore-g3.0
                                            	2025-06-10 21:25:55.090	debug	Making request to endpoint processdata with data {"method":"GET","port":"80","host":"192.168.178.81","path":"/api/v1/processdata","headers":{"User-Agent":"Mozilla/5.0 (X11; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0","Content-Type":"application/json","Authorization":"Session fb772bd52e4683f947ad27f8fc4b55d4a51811cdf85fdd95f3eb2a8e92c9a873"},"rejectUnauthorized":false}
                                            plenticore-g3.0
                                            	2025-06-10 21:25:39.912	debug	API connection closed
                                            FernetMenta 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            807
                                            Online

                                            31.7k
                                            Users

                                            79.8k
                                            Topics

                                            1.3m
                                            Posts

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