Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Fenecon/OpenEMS Adapter

    NEWS

    • Änderungen iob CLI/Installer/Fixer mit Root Accounts

    • ioBroker Community-Treffen 9.11.24 ausverkauft

    • js-controller Lucy (v7.0.0) jetzt im Beta Repository

    Fenecon/OpenEMS Adapter

    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      sunnylaila @Marius 0 last edited by

      @marius-0

      Hallo zusammen,
      Ich habe gestern mal den Adapter installiert er verbindet sich perfekt mit der Fenecon und liefert alle Daten die es zum auslesen anscheinend gibt. Ich habe natürlich noch keine Ahnung was er da alles ausliest.
      Was ich zum Beispiel noch suche ist der Wert für die Autarkie

      Gruß

      H M 2 Replies Last reply Reply Quote 0
      • R
        rewenode @Marius 0 last edited by

        @marius-0 Den Adapter kannte ich gar nicht. Wenn ich das richtig sehe, pollt der jede Sec. tatsächlich alle Daten per REST-Api.
        Da ich den nicht kannte und per Modbus nicht alle (von mir gewollten) Daten erreichbar waren, habe ich mir einen kleinen Node-Red-Flow gebastelt, der sich die gewünschten Daten per Websocket schicken läßt.
        2024-05-22_10-49-43.png

        2024-05-22_10-45-44.png

        Alle gewünschte Daten werden per JSON konfiguriert. Läuft seit Februar bis jetzt zuverlässigt. Falls die Verbindung mal abbricht (kommt alle paar Wochen mal vor, wenn ich an anderen Flows rumbastel oder Updates mache) wird sie automatisch wieder hergestellt.

        Die Idee und die Infos habe ich vom original HA-Fenecon-Adapter

        Die Websocket Schnistelle ist weder von Fenecon, noch von OpenEMS voll dokumentiert.
        Man kann sich die Infos einigermaßen bei OpenEMS zusammenlesen.

        Hab das Ganze zuerst als Pythonscript gebastelt. Und das Konzept dann als JS-Script in NodeRed umgesetzt.

        Also wenn das jemand braucht und Erfahrung mit NodeRed hat, kann er sich gern melden.

        1 Reply Last reply Reply Quote 0
        • H
          hugo1217 @sunnylaila last edited by

          @sunnylaila

          Hallo,

          hat jemand in den Autarkie Wert gefunden??

          Gruß Hugo

          1 Reply Last reply Reply Quote 0
          • M
            mrg @sunnylaila last edited by

            @sunnylaila,
            @hugo1217

            Habe in meinen Fenecon Adapter die Autarkie mit aufgenommen.
            Dieser wird berechnet und wird nicht direkt ausgelesen.
            Ist jetzt hier: _sum.Autarchy zu finden.

            W 1 Reply Last reply Reply Quote 0
            • W
              Wolf-B @mrg last edited by Wolf-B

              Warum gibt es denn den Fenecon-Adapter noch nicht in den Adaptern zum installieren ? Wann wird er kommen ?

              M 1 Reply Last reply Reply Quote 0
              • H
                hugo1217 last edited by

                @mrg

                wie berechnest du diesen??

                M 1 Reply Last reply Reply Quote 0
                • M
                  mrg @Wolf-B last edited by

                  @wolf-b
                  Der Adapter ist ganz frisch und ich bin noch nicht so fit im Adapterprogrammieren.
                  Werden ihn aber die Tage in das Beta-Repository einchecken.

                  W 1 Reply Last reply Reply Quote 0
                  • M
                    mrg @hugo1217 last edited by

                    @hugo1217
                    Die Berechnung habe ich von openems abgeschaut.
                    Die benötigten Werte sind im _sum Ordner zu finden.

                    if (consumptionActivePower <= 0) {
    autarchy = 100;
} else {
    autarchy = Math.round(Math.max(0, Math.min(100, (1 - gridAcivePower / consumptionActivePower) * 100)));
}
                    1 Reply Last reply Reply Quote 0
                    • W
                      Wolf-B @mrg last edited by Wolf-B

                      @mrg sagte in Fenecon/OpenEMS Adapter:

                      @wolf-b
                      Der Adapter ist ganz frisch und ich bin noch nicht so fit im Adapterprogrammieren.
                      Werden ihn aber die Tage in das Beta-Repository einchecken.

                      Das freut sicher nicht nur mich, wenn Du den Adapter zur Verfügung stellst - ich sage jetzt schonmal DANKE !

                      Mojo1985 1 Reply Last reply Reply Quote 0
                      • Mojo1985
                        Mojo1985 @Wolf-B last edited by

                        Oh ja... ich hätte auch großes Interesse daran. Ich warte schon lang auf eine einfache Lösung die Daten meines Fenecon Home in den ioBroker zu bekommen.

                        Wie installiert man den Adapter denn aktuell? Über GitHub gehts ja noch nicht.
                        Sorry für die Frage, aber ich bin leider ein bisschen raus aus dem Thema.

                        M 1 Reply Last reply Reply Quote 0
                        • M
                          mrg @Mojo1985 last edited by

                          @mojo1985
                          du kannst den Adapter vorerst manuell über Github installieren.

                          Wie das geht ist hier zu finden: https://www.iobroker.net/?lang=de#de/documentation/admin/adapter.md unter Abschnitt 5.
                          Der Link zum Github lautet: https://github.com/sg-app/ioBroker.fenecon.git

                          Gruß Georg

                          Mojo1985 1 Reply Last reply Reply Quote 1
                          • S
                            sunnylaila last edited by

                            Hallo zusammen, der neue Adapter ist ja super endlich auch die Autarkie Berechnung. Hat der Adapter auch den Eigenverbrauch oder kann ich den in Prozent irgendwie mit dem Adapter berechnen lassen?
                            Und noch eine Frage hat jemand fürs ViS die Ansicht so hinbekommen wie im Original Fenecon Fems ?

                            Gruß Sunnylaila

                            M 1 Reply Last reply Reply Quote 0
                            • M
                              mrg @sunnylaila last edited by

                              @sunnylaila
                              Danke für dein Lob.

                              @nobroker hat die Fenecon-Seite nachgebaut hat er geschrieben. Vielleicht stellt er uns das zur Verfügung?

                              Die Berechnung von Eigenverbrauch kannst du selber machen.
                              Berechnet muss werden:

                              (1-(_sum.GridActivePower *-1 / _sum.ProductionActivePower)) *100

                              In meiner nächsten Version habe ich die Berechnung mit eingebaut.

                              Gruß Georg

                              S 1 Reply Last reply Reply Quote 0
                              • S
                                sunnylaila @mrg last edited by

                                @mrg

                                super gerade die neueste Version installiert funktioniert klasse
                                Danke für deine Mühen

                                S 1 Reply Last reply Reply Quote 0
                                • S
                                  sunnylaila @sunnylaila last edited by sunnylaila

                                  @mrg

                                  habe jetzt gerade gesehen das ich im log einen haufen Warnungen vom fenecon Adapter
                                  siehe log

                                  fenecon.0
2024-07-21 20:11:24.211	warn	Got terminate signal. Checking desired PID: 0 vs own PID 4209

fenecon.0
2024-07-21 20:11:22.188	warn	State "fenecon.0._sum.SelfConsumption" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:22.179	warn	State "fenecon.0._sum.Autarchy" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:22.171	warn	State "fenecon.0.charger1._PropertySafetyCountry" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:22.164	warn	State "fenecon.0.charger1.Current" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:22.158	warn	State "fenecon.0.charger1._PropertyControlMode" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:22.152	warn	State "fenecon.0.charger1._PropertyMpptForShadowEnable" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:22.145	warn	State "fenecon.0.charger1._PropertyMaxBatteryPower" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:22.139	warn	State "fenecon.0.charger1.State" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:22.132	warn	State "fenecon.0.charger1.HasNoDcPv" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:22.126	warn	State "fenecon.0.charger1._PropertyId" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:22.079	warn	State "fenecon.0.charger1.ActualPower" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:22.073	warn	State "fenecon.0.charger1._PropertyRcrEnable" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:22.067	warn	State "fenecon.0.charger1._PropertySetfeedInPowerSettings" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:22.061	warn	State "fenecon.0.charger1._PropertyEnabled" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:22.055	warn	State "fenecon.0.charger1._PropertyGoodWeMeterCategory" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:22.049	warn	State "fenecon.0.charger1.ActualEnergy" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:22.044	warn	State "fenecon.0.charger1._PropertyAlias" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:22.038	warn	State "fenecon.0.charger1.MaxActualPower" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:22.032	warn	State "fenecon.0.charger1.Voltage" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:22.026	warn	State "fenecon.0.charger1._PropertyEssOrBatteryInverterId" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:22.020	warn	State "fenecon.0.charger1._PropertyStartStop" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:22.014	warn	State "fenecon.0.charger1._PropertyBackupEnable" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:22.006	warn	State "fenecon.0.charger1._PropertyExternalMeterRatioValueB" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.951	warn	State "fenecon.0.charger1._PropertyFeedPowerEnable" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.930	warn	State "fenecon.0.charger1._PropertyExternalMeterRatioValueA" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.923	warn	State "fenecon.0.charger1.ModbusCommunicationFailed" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.917	warn	State "fenecon.0.charger1._PropertyMpptPort" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.867	warn	State "fenecon.0.charger1._PropertyPvPort" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.860	warn	State "fenecon.0.charger1._PropertyFeedPowerPara" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.853	warn	State "fenecon.0.charger1._PropertyModbusUnitId" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.846	warn	State "fenecon.0.charger1._PropertyCapacity" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.798	warn	State "fenecon.0.charger1._PropertyModbusId" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.791	warn	State "fenecon.0.meter2._PropertySafetyCountry" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.783	warn	State "fenecon.0.meter2.Frequency" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.776	warn	State "fenecon.0.meter2._PropertyMaxBatteryPower" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.768	warn	State "fenecon.0.meter2._PropertyId" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.760	warn	State "fenecon.0.meter2._PropertyEnabled" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.752	warn	State "fenecon.0.meter2._PropertyGoodWeMeterCategory" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.745	warn	State "fenecon.0.meter2.ActiveProductionEnergyL2" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.737	warn	State "fenecon.0.meter2.ActiveProductionEnergyL1" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.682	warn	State "fenecon.0.meter2.ReactivePower" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.668	warn	State "fenecon.0.meter2.ActiveProductionEnergyL3" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.658	warn	State "fenecon.0.meter2._PropertyAlias" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.608	warn	State "fenecon.0.meter2.CurrentL2" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.601	warn	State "fenecon.0.meter2.CurrentL1" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.538	warn	State "fenecon.0.meter2.ActiveProductionEnergy" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.533	warn	State "fenecon.0.meter2.Voltage" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.527	warn	State "fenecon.0.meter2._PropertyBackupEnable" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.521	warn	State "fenecon.0.meter2.FrequencyL2" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.515	warn	State "fenecon.0.meter2._PropertyExternalMeterRatioValueB" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.510	warn	State "fenecon.0.meter2.FrequencyL3" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.503	warn	State "fenecon.0.meter2.ActiveConsumptionEnergy" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.497	warn	State "fenecon.0.meter2._PropertyExternalMeterRatioValueA" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.449	warn	State "fenecon.0.meter2.FrequencyL1" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.442	warn	State "fenecon.0.meter2.ActiveConsumptionEnergyL2" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.413	warn	State "fenecon.0.meter2.ActiveConsumptionEnergyL1" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.406	warn	State "fenecon.0.meter2.ModbusCommunicationFailed" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.358	warn	State "fenecon.0.meter2.ActiveConsumptionEnergyL3" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.352	warn	State "fenecon.0.meter2._PropertyModbusId" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.347	warn	State "fenecon.0.meter2.Current" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.342	warn	State "fenecon.0.meter2._PropertyControlMode" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.286	warn	State "fenecon.0.meter2._PropertyMpptForShadowEnable" has no existing object, this might lead to an error in future versions

fenecon.0
2024-07-21 20:11:21.281	warn	State "fenecon.0.meter2.State" has no existing object, this might lead to an error in future versions


                                  	2024-07-21 20:11:24.236	warn	Got terminate signal. Checking desired PID: 9356 vs own PID 4209

                                  habe mir angeschaut ob es Objekte mit dem Namen gibt und sie sind da und trotzdem die Warnung kannst du damit etwas anfangen?

                                  M 1 Reply Last reply Reply Quote 0
                                  • M
                                    mrg @sunnylaila last edited by

                                    @sunnylaila
                                    Bitte Stoppe mal die Instanz, lösche alle Objekte von fenecon und starte die Instanz nochmal.
                                    Ich musste hier einiges ändern damit der Adapter in das offizielle Repo aufgenommen wird.

                                    S 1 Reply Last reply Reply Quote 1
                                    • S
                                      sunnylaila @mrg last edited by

                                      @mrg

                                      ja so hat es geklappt die Warnungen tauchen nicht mehr auf danke

                                      1 Reply Last reply Reply Quote 0
                                      • Mojo1985
                                        Mojo1985 @mrg last edited by

                                        @mrg Super! Ich danke dir! 🙂

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

                                          Mist... funktioniert bei mir irgendwie nicht 😞

                                          Das spuckt er mir aus:

                                          $ iobroker url https://github.com/sg-app/ioBroker.fenecon.git --host iobroker --debug

install sg-app/ioBroker.fenecon#28e5fb459ac358c90b884acd4a5be6809e177ef1

NPM version: 9.6.1Installing sg-app/ioBroker.fenecon#28e5fb459ac358c90b884acd4a5be6809e177ef1... (System call)

npm WARN ERESOLVE overriding peer dependency

npm WARN npm WARN Could not resolve dependency:npm WARN peer @iobroker/types@"^6.0.0" from @iobroker/adapter-core@3.1.6npm WARN node_modules/iobroker.iot/node_modules/@iobroker/adapter-corenpm WARN @iobroker/adapter-core@"^3.0.4" from iobroker.iot@3.3.0npm WARN node_modules/iobroker.iotnpm WARN npm WARN Conflicting peer dependency: @iobroker/types@6.0.9

npm WARN node_modules/@iobroker/typesnpm WARN peer @iobroker/types@"^6.0.0" from @iobroker/adapter-core@3.1.6

npm WARN node_modules/iobroker.iot/node_modules/@iobroker/adapter-corenpm WARN @iobroker/adapter-core@"^3.0.4" from iobroker.iot@3.3.0npm WARN node_modules/iobroker.iot

npm ERR! code EBADENGINE

npm ERR! engine Unsupported engine

npm ERR! engine Not compatible with your version of node/npm: iobroker.fenecon@0.4.0npm ERR! notsup Not compatible with your version of node/npm: iobroker.fenecon@0.4.0npm ERR! notsup Required: {"node":">= 18"}npm ERR! notsup Actual: {"npm":"9.6.1","node":"v16.19.1"}

npm ERR! A complete log of this run can be found in:npm ERR! /home/iobroker/.npm/_logs/2024-07-29T07_09_19_886Z-debug-0.log

host.iobroker Cannot install sg-app/ioBroker.fenecon#28e5fb459ac358c90b884acd4a5be6809e177ef1: 1

ERROR: Process exited with code 25
                                          Homoran 1 Reply Last reply Reply Quote 0
                                          • Homoran
                                            Homoran Global Moderator Administrators @Mojo1985 last edited by

                                            @mojo1985 sagte in Fenecon/OpenEMS Adapter:

                                            ERR! notsup Required: {"node":">= 18"}npm ERR! notsup Actual: {"npm":"9.6.1","node":"v16.19.1"}

                                            Mojo1985 1 Reply Last reply Reply Quote 1
                                            • First post
                                              Last post

                                            Support us

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

                                            1.4k
                                            Online

                                            30.2k
                                            Users

                                            76.3k
                                            Topics

                                            1.2m
                                            Posts

                                            fems openems fenecon
                                            18
                                            57
                                            3759
                                            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