Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Einsteigerfragen
    4. Einbindung von Geräten
    5. Victron-Energy Adapter - will nicht - doppelte Geräte-ID?

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    Victron-Energy Adapter - will nicht - doppelte Geräte-ID?

    This topic has been deleted. Only users with topic management privileges can see it.
    • Stefan Falt
      Stefan Falt @derAlff last edited by

      @deralff Danke. Erledigt.

      derAlff 1 Reply Last reply Reply Quote 1
      • derAlff
        derAlff Developer @Stefan Falt last edited by

        @stefan-falt ich habe da noch eine Frage. Was ist das für ein Gerät? Ich meine, die ID ist normalerweise nur ein einziges Mal vorhanden.

        Homoran Stefan Falt 2 Replies Last reply Reply Quote 0
        • Homoran
          Homoran Global Moderator Administrators @derAlff last edited by Homoran

          @deralff Das ist ein Multiplus II mit integriertem GX.

          die IDs sind IMHO nicht wirklich doppelt, haben hier anscheinend nur 2 Bezeichner. Dahinter steckt jeweils dasselbe.
          sieht bei mir genauso aus
          Screenshot_20230901-085053_Firefox.jpg
          und macht per modbus keine Probleme.

          derAlff 1 Reply Last reply Reply Quote 1
          • derAlff
            derAlff Developer @Homoran last edited by

            @homoran das Hub4 hab ich noch nie gesehen… daher bin ich etwas verwirrt 🙈

            Homoran 1 Reply Last reply Reply Quote 0
            • Homoran
              Homoran Global Moderator Administrators @derAlff last edited by

              @deralff sagte in Victron-Energy Adapter - will nicht - doppelte Geräte-ID?:

              @homoran das Hub4 hab ich noch nie gesehen… daher bin ich etwas verwirrt 🙈

              ich denke das sind die Register bei unit 100, die eigentlich von anderen Geräten kommen und auch noch unter deren ID zu finden sind, wie z.b. GridWerte vom EVU-NETZ über den Energymeter

              derAlff 1 Reply Last reply Reply Quote 1
              • derAlff
                derAlff Developer @Homoran last edited by derAlff

                @homoran ne, die kommen über „system“. Deshalb bin ich ja so verwirrt 😅

                Jetzt habe ich ein Problem 🙈
                Das ist dieses nette kleine Teil…
                IMG_2298.png

                Homoran 2 Replies Last reply Reply Quote 1
                • Homoran
                  Homoran Global Moderator Administrators @derAlff last edited by Homoran

                  @deralff sagte in Victron-Energy Adapter - will nicht - doppelte Geräte-ID?:

                  Das ist dieses nette kleine Teil…

                  der Herr haben editiert!? 😀

                  Das ist der Hub? das ist doch der color control GX
                  oder kann es sein dass alle GX Geräte einen HuB beinhalten.
                  ich hab einen Cerbo und @Stefan-Falt einen MPII GX

                  1 Reply Last reply Reply Quote 0
                  • Homoran
                    Homoran Global Moderator Administrators @derAlff last edited by

                    @deralff weitergesucht ich habe!

                    Hub-4 is a Grid-parallel Energy Storage system

                    von hier:
                    Screenshot_20230901-093701_Firefox.jpg

                    nach Link aus hier:

                    Screenshot_20230901-093610_Firefox.jpg

                    1 Reply Last reply Reply Quote 0
                    • Stefan Falt
                      Stefan Falt @derAlff last edited by Stefan Falt

                      @deralff said in Victron-Energy Adapter - will nicht - doppelte Geräte-ID?:

                      @stefan-falt ich habe da noch eine Frage. Was ist das für ein Gerät? Ich meine, die ID ist normalerweise nur ein einziges Mal vorhanden.

                      Das ist ein Victron Multiplus II GX 70-50 Firmware 2.93(?) mit einem EM24, sonst ist nichts mehr angeschlossen.
                      Der hat auch schon mal anstandslos funktioniert mit deinem Adapter. Warum nach der Neuinstallation meines BananaPi mit ioBroker + Gedöns jetzt Probleme auftreten weis ich nicht genau. Auch kann ich nicht mehr sagen, Welche Geräte-IDs vorher vergeben waren.
                      Was das hub4 seinsoll - keine Anhung.

                      Falls Bedarf besteht, unterstütze ich gerne weiter.

                      MfG
                      Stefan

                      derAlff 1 Reply Last reply Reply Quote 0
                      • derAlff
                        derAlff Developer @Stefan Falt last edited by

                        @stefan-falt lösche den Adapter bitte nochmal. Hast du von GitHub oder aus dem stable Repository installiert?

                        Stefan Falt 1 Reply Last reply Reply Quote 0
                        • Homoran
                          Homoran Global Moderator Administrators @Stefan Falt last edited by

                          @derAlff
                          @stefan-falt sagte in Victron-Energy Adapter - will nicht - doppelte Geräte-ID?:

                          ich bin mir zu 99 % sicher diesen Adapter benutzt zu haben haben, allerdings von GitHub? installiert.

                          klingt für mich, dass es diesmal aus latest kommt

                          1 Reply Last reply Reply Quote 0
                          • Stefan Falt
                            Stefan Falt @derAlff last edited by Stefan Falt

                            @deralff
                            Als er noch ging, habe ich ihn aus GitHub instaliert. Diesmal aber über die Adapter Funktionalität über die ioBroker Adapter.
                            Ich bin aber noch auf Arbeit, mache ich dann Abends ... und werde Berichten.

                            derAlff 1 Reply Last reply Reply Quote 0
                            • derAlff
                              derAlff Developer @Stefan Falt last edited by derAlff

                              @stefan-falt dann installier ihn bitte nochmal von GitHub. Dort war die letzte Änderung vor ca. einem Monat.
                              Aus dem Stable ist der Adapter schon etwas älter.

                              Kannst du mir bei Gelegenheit die Konstellation deiner Anlage mitteilen 😅?

                              Stefan Falt 1 Reply Last reply Reply Quote 0
                              • Stefan Falt
                                Stefan Falt @derAlff last edited by Stefan Falt

                                @deralff
                                Hallo,
                                ich habe den vorhandenen VE Adapter gelöscht und über Github neu installiert (https://github.com/derAlff/ioBroker.ve).
                                Das Problem besteht unverändert.
                                Ich möchte nochmal erwähnen, dass das schon mal funktioniert hat, bevor ich meinen BananaPi neu aufgesetzt habe.

                                Meine Konstellation:

                                • Multiplus 2 GX 70-50 mit EM24 Zähler und einer DIY Batterie 280Ah mit Seplos 200A BMS.
                                • ioBroker
                                • ein SolarLog Base (nirgens eingetragen)
                                • Schüko SGI10K WR (nur vom SolarLog üser S0 gezählt)
                                • SolPlanet ASW3000S-S (nirgens eingetragen)

                                MfG
                                Stefan

                                host.bananapim5
	2023-09-01 19:06:43.872	info	Restart adapter system.adapter.ve.0 because enabled
host.bananapim5
	2023-09-01 19:06:43.871	error	instance system.adapter.ve.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
ve.0
	2023-09-01 19:06:43.293	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
ve.0
	2023-09-01 19:06:43.290	info	terminating
ve.0
	2023-09-01 19:06:43.288	info	Unload adapter...
ve.0
	2023-09-01 19:06:43.282	error	Modbus exception 10: Unknown error
ve.0
	2023-09-01 19:06:43.281	error	Error: Modbus exception 10: Unknown error at ModbusRTU._onReceive (/opt/iobroker/node_modules/modbus-serial/index.js:370:21) at TcpPort.emit (node:events:514:28) at Socket.<anonymous> (/opt/iobroker/node_modules/modbus-serial/ports/tcpport.js:94:24) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
ve.0
	2023-09-01 19:06:43.280	error	unhandled promise rejection: Modbus exception 10: Unknown error
ve.0
	2023-09-01 19:06:43.278	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
ve.0
	2023-09-01 19:06:43.236	error	Modbus exception 10: Unknown error
ve.0
	2023-09-01 19:06:43.235	error	Error: Modbus exception 10: Unknown error at ModbusRTU._onReceive (/opt/iobroker/node_modules/modbus-serial/index.js:370:21) at TcpPort.emit (node:events:514:28) at Socket.<anonymous> (/opt/iobroker/node_modules/modbus-serial/ports/tcpport.js:94:24) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
ve.0
	2023-09-01 19:06:43.234	error	unhandled promise rejection: Modbus exception 10: Unknown error
ve.0
	2023-09-01 19:06:43.233	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
ve.0
	2023-09-01 19:06:43.231	error	Modbus exception 10: Unknown error
ve.0
	2023-09-01 19:06:43.230	error	Error: Modbus exception 10: Unknown error at ModbusRTU._onReceive (/opt/iobroker/node_modules/modbus-serial/index.js:370:21) at TcpPort.emit (node:events:514:28) at Socket.<anonymous> (/opt/iobroker/node_modules/modbus-serial/ports/tcpport.js:94:24) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
ve.0
	2023-09-01 19:06:43.229	error	unhandled promise rejection: Modbus exception 10: Unknown error
ve.0
	2023-09-01 19:06:43.228	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
ve.0
	2023-09-01 19:06:43.226	error	Modbus exception 10: Unknown error
ve.0
	2023-09-01 19:06:43.225	error	Error: Modbus exception 10: Unknown error at ModbusRTU._onReceive (/opt/iobroker/node_modules/modbus-serial/index.js:370:21) at TcpPort.emit (node:events:514:28) at Socket.<anonymous> (/opt/iobroker/node_modules/modbus-serial/ports/tcpport.js:94:24) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
ve.0
	2023-09-01 19:06:43.224	error	unhandled promise rejection: Modbus exception 10: Unknown error
ve.0
	2023-09-01 19:06:43.223	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
ve.0
	2023-09-01 19:06:43.221	error	Modbus exception 10: Unknown error
ve.0
	2023-09-01 19:06:43.220	error	Error: Modbus exception 10: Unknown error at ModbusRTU._onReceive (/opt/iobroker/node_modules/modbus-serial/index.js:370:21) at TcpPort.emit (node:events:514:28) at Socket.<anonymous> (/opt/iobroker/node_modules/modbus-serial/ports/tcpport.js:94:24) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
ve.0
	2023-09-01 19:06:43.219	error	unhandled promise rejection: Modbus exception 10: Unknown error
ve.0
	2023-09-01 19:06:43.218	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
ve.0
	2023-09-01 19:06:43.216	error	Modbus exception 10: Unknown error
ve.0
	2023-09-01 19:06:43.215	error	Error: Modbus exception 10: Unknown error at ModbusRTU._onReceive (/opt/iobroker/node_modules/modbus-serial/index.js:370:21) at TcpPort.emit (node:events:514:28) at Socket.<anonymous> (/opt/iobroker/node_modules/modbus-serial/ports/tcpport.js:94:24) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
ve.0
	2023-09-01 19:06:43.214	error	unhandled promise rejection: Modbus exception 10: Unknown error
ve.0
	2023-09-01 19:06:43.213	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
ve.0
	2023-09-01 19:06:43.211	error	Modbus exception 10: Unknown error
ve.0
	2023-09-01 19:06:43.210	error	Error: Modbus exception 10: Unknown error at ModbusRTU._onReceive (/opt/iobroker/node_modules/modbus-serial/index.js:370:21) at TcpPort.emit (node:events:514:28) at Socket.<anonymous> (/opt/iobroker/node_modules/modbus-serial/ports/tcpport.js:94:24) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
ve.0
	2023-09-01 19:06:43.209	error	unhandled promise rejection: Modbus exception 10: Unknown error
ve.0
	2023-09-01 19:06:43.208	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
ve.0
	2023-09-01 19:06:43.207	error	Modbus exception 10: Unknown error
ve.0
	2023-09-01 19:06:43.206	error	Error: Modbus exception 10: Unknown error at ModbusRTU._onReceive (/opt/iobroker/node_modules/modbus-serial/index.js:370:21) at TcpPort.emit (node:events:514:28) at Socket.<anonymous> (/opt/iobroker/node_modules/modbus-serial/ports/tcpport.js:94:24) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
ve.0
	2023-09-01 19:06:43.204	error	unhandled promise rejection: Modbus exception 10: Unknown error
ve.0
	2023-09-01 19:06:43.203	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
ve.0
	2023-09-01 19:06:43.201	error	Modbus exception 10: Unknown error
ve.0
	2023-09-01 19:06:43.200	error	Error: Modbus exception 10: Unknown error at ModbusRTU._onReceive (/opt/iobroker/node_modules/modbus-serial/index.js:370:21) at TcpPort.emit (node:events:514:28) at Socket.<anonymous> (/opt/iobroker/node_modules/modbus-serial/ports/tcpport.js:94:24) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
ve.0
	2023-09-01 19:06:43.199	error	unhandled promise rejection: Modbus exception 10: Unknown error
ve.0
	2023-09-01 19:06:43.198	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
ve.0
	2023-09-01 19:06:43.196	error	Modbus exception 10: Unknown error
ve.0
	2023-09-01 19:06:43.195	error	Error: Modbus exception 10: Unknown error at ModbusRTU._onReceive (/opt/iobroker/node_modules/modbus-serial/index.js:370:21) at TcpPort.emit (node:events:514:28) at Socket.<anonymous> (/opt/iobroker/node_modules/modbus-serial/ports/tcpport.js:94:24) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
ve.0
	2023-09-01 19:06:43.193	error	unhandled promise rejection: Modbus exception 10: Unknown error
ve.0
	2023-09-01 19:06:43.192	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
ve.0
	2023-09-01 19:06:43.190	error	Modbus exception 10: Unknown error
ve.0
	2023-09-01 19:06:43.188	error	Error: Modbus exception 10: Unknown error at ModbusRTU._onReceive (/opt/iobroker/node_modules/modbus-serial/index.js:370:21) at TcpPort.emit (node:events:514:28) at Socket.<anonymous> (/opt/iobroker/node_modules/modbus-serial/ports/tcpport.js:94:24) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
ve.0
	2023-09-01 19:06:43.186	error	unhandled promise rejection: Modbus exception 10: Unknown error
ve.0
	2023-09-01 19:06:43.184	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
ve.0
	2023-09-01 19:06:43.181	error	Modbus exception 10: Unknown error
ve.0
	2023-09-01 19:06:43.180	error	Error: Modbus exception 10: Unknown error at ModbusRTU._onReceive (/opt/iobroker/node_modules/modbus-serial/index.js:370:21) at TcpPort.emit (node:events:514:28) at Socket.<anonymous> (/opt/iobroker/node_modules/modbus-serial/ports/tcpport.js:94:24) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
ve.0
	2023-09-01 19:06:43.177	error	unhandled promise rejection: Modbus exception 10: Unknown error
ve.0
	2023-09-01 19:06:43.176	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
admin.0
	2023-09-01 19:06:42.130	info	Adapter rating updated
smartmeter.0
	2023-09-01 19:06:41.396	info	Received 10 values, 3 updated
ve.0
	2023-09-01 19:06:38.051	info	Number of PV-Inverters: 0
ve.0
	2023-09-01 19:06:38.049	info	config port: 502
ve.0
	2023-09-01 19:06:38.048	info	config IP: 192.168.178.44
ve.0
	2023-09-01 19:06:37.985	info	starting. Version 0.3.1 (non-npm: derAlff/ioBroker.ve#584088cddf3318ede48554ed97414f5ff79f460e) in /opt/iobroker/node_modules/iobroker.ve, node: v18.17.1, js-controller: 4.0.24
host.bananapim5
	2023-09-01 19:06:35.119	info	instance system.adapter.ve.0 started with pid 17719
host.bananapim5
	2023-09-01 19:06:32.585	info	instance system.adapter.ve.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
host.bananapim5
	2023-09-01 19:06:32.057	info	stopInstance system.adapter.ve.0 send kill signal
ve.0
	2023-09-01 19:06:32.009	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
ve.0
	2023-09-01 19:06:32.007	info	terminating
ve.0
	2023-09-01 19:06:32.006	info	Unload adapter...
ve.0
	2023-09-01 19:06:32.002	info	Got terminate signal TERMINATE_YOURSELF
host.bananapim5
	2023-09-01 19:06:31.992	info	stopInstance system.adapter.ve.0 (force=false, process=true)
smartmeter.0
	2023-09-01 19:06:28.044	info	Received 10 values, 3 updated
smartmeter.0
	2023-09-01 19:06:16.866	info	Received 10 values, 1 updated
smartmeter.0
	2023-09-01 19:06:03.515	info	Received 10 values, 1 updated
ve.0
	2023-09-01 19:06:01.882	info	Number of PV-Inverters: 0
ve.0
	2023-09-01 19:06:01.880	info	config port: 502
ve.0
	2023-09-01 19:06:01.878	info	config IP:
ve.0
	2023-09-01 19:06:01.812	info	starting. Version 0.3.1 (non-npm: derAlff/ioBroker.ve#584088cddf3318ede48554ed97414f5ff79f460e) in /opt/iobroker/node_modules/iobroker.ve, node: v18.17.1, js-controller: 4.0.24
host.bananapim5
	2023-09-01 19:05:58.930	info	instance system.adapter.ve.0 started with pid 17702
host.bananapim5
	2023-09-01 19:05:56.941	info	iobroker exit 0
                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post

                                Support us

                                ioBroker
                                Community Adapters
                                Donate

                                543
                                Online

                                31.9k
                                Users

                                80.1k
                                Topics

                                1.3m
                                Posts

                                3
                                50
                                3201
                                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