Skip to content
  • Home
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. SPH 10000TL-BH-UP Wechselrichter über Modbus auslesen

NEWS

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    18
    1
    651

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    18
    1
    5.7k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    1.5k

SPH 10000TL-BH-UP Wechselrichter über Modbus auslesen

Scheduled Pinned Locked Moved ioBroker Allgemein
5 Posts 3 Posters 1.2k Views 4 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • 2 Offline
    2 Offline
    2hot4you
    wrote on last edited by
    #1

    Hallo Zusammen,

    vielleicht hat ja jemand bereits einen Growatt WR SPH 10000 über Modbus ausgelesen. Bei mir will es nicht klappen.
    Ich habe bereits diverse Modbus Energiezähler über den Modbus Adapter problemlos laufen.
    Für das zweiten Modbus Gateway habe ich eine weitere Instanz vom Adapter installiert.

    Zur Adapter Konfiguration:
    Modbus1.png

    modbus4.png

    Gateway:
    modbus2.png

    modbus3.png

    Wechselrichter:
    modbus5.png
    Das Gateway ist am Port 485-3 angeschlossen.

    Ich habe auch die Ports 458-1 und 2 ausprobiert, gleicher Effekt.
    Auch mit den Modbus Einstellungen im Wechselrichter habe ich gespielt.

    modbus6.png
    In einem andren Forum hatte ich gelesen, dass der Modbus Modus auf VPP gestellt werden sollte, aber auch in dieser Einstellung kein Erfolg

    Auszug vom LOG

    modbus.1
    2024-06-02 12:37:33.710	info	Disconnected from slave 192.168.30.50
    modbus.1
    2024-06-02 12:37:32.711	warn	[1] Poll error count: 1 code: {"err":"timeout","timeout":5000}
    modbus.1
    2024-06-02 12:37:32.710	error	Client in error state.
    modbus.1
    2024-06-02 12:37:32.710	error	Request timed out.
    modbus.1
    2024-06-02 12:37:32.710	warn	Error: undefined
    modbus.1
    2024-06-02 12:37:27.709	info	Connected to slave
    modbus.1
    2024-06-02 12:37:27.415	info	starting. Version 6.2.3 in /opt/iobroker/node_modules/iobroker.modbus, node: v20.13.1, js-controller: 5.0.19
    modbus.1
    2024-06-02 12:37:23.694	info	terminating
    modbus.1
    2024-06-02 12:37:23.194	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    modbus.1
    2024-06-02 12:37:23.194	info	terminating
    modbus.1
    2024-06-02 12:37:23.193	info	Got terminate signal TERMINATE_YOURSELF
    

    Das Gateway zeigt auch kurz an, dass zum Adapter einer Verbindung aufgebaut wird.

    Jemand ne Idee ?

    Gruß Michael

    wendy2702W 1 Reply Last reply
    0
    • 2 2hot4you

      Hallo Zusammen,

      vielleicht hat ja jemand bereits einen Growatt WR SPH 10000 über Modbus ausgelesen. Bei mir will es nicht klappen.
      Ich habe bereits diverse Modbus Energiezähler über den Modbus Adapter problemlos laufen.
      Für das zweiten Modbus Gateway habe ich eine weitere Instanz vom Adapter installiert.

      Zur Adapter Konfiguration:
      Modbus1.png

      modbus4.png

      Gateway:
      modbus2.png

      modbus3.png

      Wechselrichter:
      modbus5.png
      Das Gateway ist am Port 485-3 angeschlossen.

      Ich habe auch die Ports 458-1 und 2 ausprobiert, gleicher Effekt.
      Auch mit den Modbus Einstellungen im Wechselrichter habe ich gespielt.

      modbus6.png
      In einem andren Forum hatte ich gelesen, dass der Modbus Modus auf VPP gestellt werden sollte, aber auch in dieser Einstellung kein Erfolg

      Auszug vom LOG

      modbus.1
      2024-06-02 12:37:33.710	info	Disconnected from slave 192.168.30.50
      modbus.1
      2024-06-02 12:37:32.711	warn	[1] Poll error count: 1 code: {"err":"timeout","timeout":5000}
      modbus.1
      2024-06-02 12:37:32.710	error	Client in error state.
      modbus.1
      2024-06-02 12:37:32.710	error	Request timed out.
      modbus.1
      2024-06-02 12:37:32.710	warn	Error: undefined
      modbus.1
      2024-06-02 12:37:27.709	info	Connected to slave
      modbus.1
      2024-06-02 12:37:27.415	info	starting. Version 6.2.3 in /opt/iobroker/node_modules/iobroker.modbus, node: v20.13.1, js-controller: 5.0.19
      modbus.1
      2024-06-02 12:37:23.694	info	terminating
      modbus.1
      2024-06-02 12:37:23.194	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      modbus.1
      2024-06-02 12:37:23.194	info	terminating
      modbus.1
      2024-06-02 12:37:23.193	info	Got terminate signal TERMINATE_YOURSELF
      

      Das Gateway zeigt auch kurz an, dass zum Adapter einer Verbindung aufgebaut wird.

      Jemand ne Idee ?

      Gruß Michael

      wendy2702W Offline
      wendy2702W Offline
      wendy2702
      wrote on last edited by wendy2702
      #2

      @2hot4you du hast im Adapter und im US Riot die Umwandlung TCPtoRTU aktiv.

      Geht aber nur an einer Stelle. Ich würde im IOB auf TCP stellen und die Wandlung im US dingsbums machen lassen.

      Loggen für die Instanz auf Debug stellen und das log dann mal Posten.

      Bitte keine Fragen per PN, die gehören ins Forum!

      Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

      2 1 Reply Last reply
      0
      • wendy2702W wendy2702

        @2hot4you du hast im Adapter und im US Riot die Umwandlung TCPtoRTU aktiv.

        Geht aber nur an einer Stelle. Ich würde im IOB auf TCP stellen und die Wandlung im US dingsbums machen lassen.

        Loggen für die Instanz auf Debug stellen und das log dann mal Posten.

        2 Offline
        2 Offline
        2hot4you
        wrote on last edited by 2hot4you
        #3

        @wendy2702

        anbei das aktuelle LOG File. Ich habe den Adapter auf TCP umgestellt. Da ich nur ein Endgerät abfrage, habe ich auf den MODBUS kein Widerstand parallelgeschaltet.

        
        
        modbus.1
        2024-06-02 23:21:11.977	info	Disconnected from slave 192.168.30.50
        
        modbus.1
        2024-06-02 23:21:11.977	debug	Closing client on purpose.
        
        modbus.1
        2024-06-02 23:21:10.978	debug	Cleaning up request fifo.
        
        modbus.1
        2024-06-02 23:21:10.978	debug	Clearing timeout of the current request.
        
        modbus.1
        2024-06-02 23:21:10.978	debug	Socket closed with error
        
        modbus.1
        2024-06-02 23:21:10.978	warn	[1] Poll error count: 3 code: {"err":"timeout","timeout":5000}
        
        modbus.1
        2024-06-02 23:21:10.977	error	Client in error state.
        
        modbus.1
        2024-06-02 23:21:10.977	error	Request timed out.
        
        modbus.1
        2024-06-02 23:21:10.977	warn	Error: undefined
        
        modbus.1
        2024-06-02 23:21:05.977	debug	[DevID_1/inputRegs] Poll address 12 - 1 registers
        
        modbus.1
        2024-06-02 23:21:05.976	debug	[DevID_1] Poll start ---------------------
        
        modbus.1
        2024-06-02 23:21:05.976	info	Connected to slave 192.168.30.50
        
        modbus.1
        2024-06-02 23:20:05.973	info	Disconnected from slave 192.168.30.50
        
        modbus.1
        2024-06-02 23:20:05.973	debug	Closing client on purpose.
        
        modbus.1
        2024-06-02 23:20:04.974	debug	Cleaning up request fifo.
        
        modbus.1
        2024-06-02 23:20:04.973	debug	Clearing timeout of the current request.
        
        modbus.1
        2024-06-02 23:20:04.973	debug	Socket closed with error
        
        modbus.1
        2024-06-02 23:20:04.973	warn	[1] Poll error count: 2 code: {"err":"timeout","timeout":5000}
        
        modbus.1
        2024-06-02 23:20:04.973	error	Client in error state.
        
        modbus.1
        2024-06-02 23:20:04.972	error	Request timed out.
        
        modbus.1
        2024-06-02 23:20:04.972	warn	Error: undefined
        
        modbus.1
        2024-06-02 23:19:59.971	debug	[DevID_1/inputRegs] Poll address 12 - 1 registers
        
        modbus.1
        2024-06-02 23:19:59.971	debug	[DevID_1] Poll start ---------------------
        
        modbus.1
        2024-06-02 23:19:59.970	info	Connected to slave 192.168.30.50
        
        modbus.1
        2024-06-02 23:18:59.969	info	Disconnected from slave 192.168.30.50
        
        modbus.1
        2024-06-02 23:18:59.969	debug	Closing client on purpose.
        
        modbus.1
        2024-06-02 23:18:58.969	debug	Cleaning up request fifo.
        
        modbus.1
        2024-06-02 23:18:58.969	debug	Clearing timeout of the current request.
        
        modbus.1
        2024-06-02 23:18:58.969	debug	Socket closed with error
        
        modbus.1
        2024-06-02 23:18:58.969	warn	[1] Poll error count: 1 code: {"err":"timeout","timeout":5000}
        
        modbus.1
        2024-06-02 23:18:58.968	error	Client in error state.
        
        modbus.1
        2024-06-02 23:18:58.968	error	Request timed out.
        
        modbus.1
        2024-06-02 23:18:58.968	warn	Error: undefined
        
        modbus.1
        2024-06-02 23:18:53.966	debug	[DevID_1/inputRegs] Poll address 12 - 1 registers
        
        modbus.1
        2024-06-02 23:18:53.966	debug	Initialization of scale factors done!
        
        modbus.1
        2024-06-02 23:18:53.965	debug	[DevID_1] Poll start ---------------------
        
        modbus.1
        2024-06-02 23:18:53.965	info	Connected to slave 192.168.30.50
        
        modbus.1
        2024-06-02 23:18:53.793	debug	Initialize Objects for holdingRegs: []
        
        modbus.1
        2024-06-02 23:18:53.793	debug	Add inputRegisters.30013Output_Power: {"_id":"inputRegisters.30013Output_Power","type":"state","common":{"name":"","role":"value","type":"number","read":true,"write":false,"def":0,"unit":"W"},"native":{"regType":"inputRegs","address":12,"deviceId":1,"type":"uint16be","len":1,"offset":0,"factor":0.1}}
        
        modbus.1
        2024-06-02 23:18:53.793	debug	Initialize Objects for inputRegs: [{"_address":"30013","name":"Output Power","description":"","unit":"W","type":"uint16be","len":1,"factor":0.1,"offset":0,"formula":"","role":"value","room":"","cw":"","isScale":"","address":12,"deviceId":1,"id":"inputRegisters.30013Output_Power"}]
        
        modbus.1
        2024-06-02 23:18:53.793	debug	Initialize Objects for coils: []
        
        modbus.1
        2024-06-02 23:18:53.793	debug	Initialize Objects for disInputs: []
        
        modbus.1
        2024-06-02 23:18:53.689	info	starting. Version 6.2.3 in /opt/iobroker/node_modules/iobroker.modbus, node: v20.13.1, js-controller: 5.0.19
        
        modbus.1
        2024-06-02 23:18:53.513	debug	Plugin sentry Initialize Plugin (enabled=true)
        
        
        wendy2702W 1 Reply Last reply
        0
        • 2 2hot4you

          @wendy2702

          anbei das aktuelle LOG File. Ich habe den Adapter auf TCP umgestellt. Da ich nur ein Endgerät abfrage, habe ich auf den MODBUS kein Widerstand parallelgeschaltet.

          
          
          modbus.1
          2024-06-02 23:21:11.977	info	Disconnected from slave 192.168.30.50
          
          modbus.1
          2024-06-02 23:21:11.977	debug	Closing client on purpose.
          
          modbus.1
          2024-06-02 23:21:10.978	debug	Cleaning up request fifo.
          
          modbus.1
          2024-06-02 23:21:10.978	debug	Clearing timeout of the current request.
          
          modbus.1
          2024-06-02 23:21:10.978	debug	Socket closed with error
          
          modbus.1
          2024-06-02 23:21:10.978	warn	[1] Poll error count: 3 code: {"err":"timeout","timeout":5000}
          
          modbus.1
          2024-06-02 23:21:10.977	error	Client in error state.
          
          modbus.1
          2024-06-02 23:21:10.977	error	Request timed out.
          
          modbus.1
          2024-06-02 23:21:10.977	warn	Error: undefined
          
          modbus.1
          2024-06-02 23:21:05.977	debug	[DevID_1/inputRegs] Poll address 12 - 1 registers
          
          modbus.1
          2024-06-02 23:21:05.976	debug	[DevID_1] Poll start ---------------------
          
          modbus.1
          2024-06-02 23:21:05.976	info	Connected to slave 192.168.30.50
          
          modbus.1
          2024-06-02 23:20:05.973	info	Disconnected from slave 192.168.30.50
          
          modbus.1
          2024-06-02 23:20:05.973	debug	Closing client on purpose.
          
          modbus.1
          2024-06-02 23:20:04.974	debug	Cleaning up request fifo.
          
          modbus.1
          2024-06-02 23:20:04.973	debug	Clearing timeout of the current request.
          
          modbus.1
          2024-06-02 23:20:04.973	debug	Socket closed with error
          
          modbus.1
          2024-06-02 23:20:04.973	warn	[1] Poll error count: 2 code: {"err":"timeout","timeout":5000}
          
          modbus.1
          2024-06-02 23:20:04.973	error	Client in error state.
          
          modbus.1
          2024-06-02 23:20:04.972	error	Request timed out.
          
          modbus.1
          2024-06-02 23:20:04.972	warn	Error: undefined
          
          modbus.1
          2024-06-02 23:19:59.971	debug	[DevID_1/inputRegs] Poll address 12 - 1 registers
          
          modbus.1
          2024-06-02 23:19:59.971	debug	[DevID_1] Poll start ---------------------
          
          modbus.1
          2024-06-02 23:19:59.970	info	Connected to slave 192.168.30.50
          
          modbus.1
          2024-06-02 23:18:59.969	info	Disconnected from slave 192.168.30.50
          
          modbus.1
          2024-06-02 23:18:59.969	debug	Closing client on purpose.
          
          modbus.1
          2024-06-02 23:18:58.969	debug	Cleaning up request fifo.
          
          modbus.1
          2024-06-02 23:18:58.969	debug	Clearing timeout of the current request.
          
          modbus.1
          2024-06-02 23:18:58.969	debug	Socket closed with error
          
          modbus.1
          2024-06-02 23:18:58.969	warn	[1] Poll error count: 1 code: {"err":"timeout","timeout":5000}
          
          modbus.1
          2024-06-02 23:18:58.968	error	Client in error state.
          
          modbus.1
          2024-06-02 23:18:58.968	error	Request timed out.
          
          modbus.1
          2024-06-02 23:18:58.968	warn	Error: undefined
          
          modbus.1
          2024-06-02 23:18:53.966	debug	[DevID_1/inputRegs] Poll address 12 - 1 registers
          
          modbus.1
          2024-06-02 23:18:53.966	debug	Initialization of scale factors done!
          
          modbus.1
          2024-06-02 23:18:53.965	debug	[DevID_1] Poll start ---------------------
          
          modbus.1
          2024-06-02 23:18:53.965	info	Connected to slave 192.168.30.50
          
          modbus.1
          2024-06-02 23:18:53.793	debug	Initialize Objects for holdingRegs: []
          
          modbus.1
          2024-06-02 23:18:53.793	debug	Add inputRegisters.30013Output_Power: {"_id":"inputRegisters.30013Output_Power","type":"state","common":{"name":"","role":"value","type":"number","read":true,"write":false,"def":0,"unit":"W"},"native":{"regType":"inputRegs","address":12,"deviceId":1,"type":"uint16be","len":1,"offset":0,"factor":0.1}}
          
          modbus.1
          2024-06-02 23:18:53.793	debug	Initialize Objects for inputRegs: [{"_address":"30013","name":"Output Power","description":"","unit":"W","type":"uint16be","len":1,"factor":0.1,"offset":0,"formula":"","role":"value","room":"","cw":"","isScale":"","address":12,"deviceId":1,"id":"inputRegisters.30013Output_Power"}]
          
          modbus.1
          2024-06-02 23:18:53.793	debug	Initialize Objects for coils: []
          
          modbus.1
          2024-06-02 23:18:53.793	debug	Initialize Objects for disInputs: []
          
          modbus.1
          2024-06-02 23:18:53.689	info	starting. Version 6.2.3 in /opt/iobroker/node_modules/iobroker.modbus, node: v20.13.1, js-controller: 5.0.19
          
          modbus.1
          2024-06-02 23:18:53.513	debug	Plugin sentry Initialize Plugin (enabled=true)
          
          
          wendy2702W Offline
          wendy2702W Offline
          wendy2702
          wrote on last edited by
          #4

          @2hot4you Kennst du das :

          https://www.photovoltaikforum.com/thread/192228-growatt-sph-modbus-rtu-rj45-pinout-und-register-beschreibung/

          Bitte keine Fragen per PN, die gehören ins Forum!

          Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

          1 Reply Last reply
          0
          • rayman2302R Offline
            rayman2302R Offline
            rayman2302
            wrote on last edited by
            #5

            Guten Abend alle zusammen. Gibt es in der Thematik noch ein bißchen Support? Stehe gerade exakt an der gleichen Stelle und weiß echt nicht mehr weiter.

            Genau die gleichen Fehlermeldungen.

            Beste Grüße und noch ein gesundes neues Jahr, Tobi

            1 Reply Last reply
            0

            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

            With your input, this post could be even better 💗

            Register Login
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            Support us

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

            460

            Online

            32.7k

            Users

            82.6k

            Topics

            1.3m

            Posts
            Community
            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
            ioBroker Community 2014-2025
            logo
            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Home
            • Recent
            • Tags
            • Unread 0
            • Categories
            • Unreplied
            • Popular
            • GitHub
            • Docu
            • Hilfe