Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. [gelöst] Plötzlich Probleme mit ModBus Adapter

    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

    [gelöst] Plötzlich Probleme mit ModBus Adapter

    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      n3ucr0n last edited by n3ucr0n

      Hallo alle zusammen,

      ich nutze zum Auslesen meiner PV-Anlage den Modbus Adapter.
      Seit einem Monat läuft das Ganze problemlos.

      Seit Samstagabend +- 23:30 Uhr läuft jedoch nichts mehr und ich verstehe nicht warum.
      Es wurde nichts geändert, installiert, geupdated oder ähnliches. Wir waren nicht mal zu Hause als die Probleme angefangen haben.
      Vielleicht kann mir jemand helfen.

      Fehlerbeschreibung:
      Der Adapter wechselt dauerhaft von Grün auf Gelb.
      Keine Datenpunkte werden mehr aktualisiert.

      System:
      Proxmox 8.2.2 mit Ubuntu auf einem Intel NUC
      JS-Controller 5.0.19
      NPM 9.2.0
      Node JS 18.13.0
      Modbus Adapter Version 6.1.0

      Hardware:
      Wechselrichter: SOFAR ME3000-SP
      Modbus Konverter: Waveshare RS485 TO ETH (Dieser hier: https://botland.de/konverter-usb-uart-rs232-rs485/15133-rs485-konverter-ethernet-cortex-m0-waveshare-16529-5904422377816.html)

      Konfiguration:
      Modbus Konverter:


      8fbc0877-b439-4463-828e-ef4b397d82a0-image.png

      Modbus Adapter Konfiguration:


      a692a801-2f12-4828-bdb2-c31c8a79e765-image.png
      3f37c4ce-862c-4f1f-b2aa-896e8e01b4b3-image.png

      Auszug aus dem Protokoll (Adapter auf Silly):

      2024-06-17 08:08:33.091 - info: admin.0 (354) ==> Connected system.user.admin from ::ffff:192.168.178.148
2024-06-17 08:08:48.606 - info: host.ioBroker "system.adapter.modbus.0" enabled
2024-06-17 08:08:48.873 - info: host.ioBroker instance system.adapter.modbus.0 started with pid 76061
2024-06-17 08:08:49.216 - debug: modbus.0 (76061) Redis Objects: Use Redis connection: 127.0.0.1:9001
2024-06-17 08:08:49.254 - debug: modbus.0 (76061) Objects client ready ... initialize now
2024-06-17 08:08:49.255 - debug: modbus.0 (76061) Objects create System PubSub Client
2024-06-17 08:08:49.255 - debug: modbus.0 (76061) Objects create User PubSub Client
2024-06-17 08:08:49.335 - debug: modbus.0 (76061) Objects client initialize lua scripts
2024-06-17 08:08:49.338 - debug: modbus.0 (76061) Objects connected to redis: 127.0.0.1:9001
2024-06-17 08:08:49.339 - silly: modbus.0 (76061) redis psubscribe cfg.o.system.user.*
2024-06-17 08:08:49.386 - silly: modbus.0 (76061) redis psubscribe cfg.o.enum.*
2024-06-17 08:08:49.386 - silly: modbus.0 (76061) objectDB connected
2024-06-17 08:08:49.387 - debug: modbus.0 (76061) Redis States: Use Redis connection: 127.0.0.1:9000
2024-06-17 08:08:49.412 - debug: modbus.0 (76061) States create System PubSub Client
2024-06-17 08:08:49.412 - debug: modbus.0 (76061) States create User PubSub Client
2024-06-17 08:08:49.496 - debug: modbus.0 (76061) States connected to redis: 127.0.0.1:9000
2024-06-17 08:08:49.496 - silly: modbus.0 (76061) statesDB connected
2024-06-17 08:08:49.526 - debug: modbus.0 (76061) Plugin sentry Initialize Plugin (enabled=true)
2024-06-17 08:08:49.615 - info: modbus.0 (76061) starting. Version 6.1.0 in /opt/iobroker/node_modules/iobroker.modbus, node: v18.13.0, js-controller: 5.0.19
2024-06-17 08:08:49.646 - silly: modbus.0 (76061) States system redis pmessage system.adapter.modbus.0.logLevel/system.adapter.modbus.0.logLevel:{"val":"silly","ack":true,"ts":1718604529643,"q":0,"from":"system.adapter.modbus.0","lc":1718604040841}
2024-06-17 08:08:49.739 - debug: modbus.0 (76061) Initialize Objects for disInputs: []
2024-06-17 08:08:49.739 - debug: modbus.0 (76061) Initialize Objects for coils: []
2024-06-17 08:08:49.739 - debug: modbus.0 (76061) Initialize Objects for inputRegs: []
2024-06-17 08:08:49.739 - debug: modbus.0 (76061) Initialize Objects for holdingRegs: [{"_address":525,"deviceId":1,"name":"Charge/Discha rge power","description":"Aktuelle Ladung & Entladung Batterie","unit":"W","type":"int16be","len":1,"factor":1,"offset":0,"formula":"x * 10","role":"value","room":"","poll":true,"wp":"","cw":"","isScale":"","address":525,"id":"holdingRegisters.1.525_Charge/Discha_rge_power"},{"_address":528,"deviceId":1,"name":"The residual capacity of battery","description":"Batterieladung","unit":"%","type":"uint16be","len":1,"factor":1,"offset":0,"formula":"","role":"value","room":"","poll":true,"wp":"","cw":false,"isScale":"","address":528,"id":"holdingRegisters.1.528_The_residual_capacity_of_battery"},{"_address":530,"deviceId":1,"name":"Feed in/out power","description":"Aktueller Netzbezug","unit":"W","type":"int16be","len":1,"factor":1,"offset":0,"formula":"x * -10","role":"value","room":"","poll":true,"wp":"","cw":"","isScale":"","address":530,"id":"holdingRegisters.1.530_Feed_in/out_power"},{"_address":531,"deviceId":1,"name":"The power of the load","description":"Aktueller Hausverbrauch","unit":"W","type":"uint16be","len":1,"factor":1,"offset":0,"formula":"x * 10","role":"value","room":"","poll":true,"wp":"","cw":"","isScale":"","address":531,"id":"holdingRegisters.1.531_The_power_of_the_load"},{"_address":532,"deviceId":1,"name":"Input/Output power","description":"keine ahnng","unit":"","type":"int16be","len":1,"factor":1,"offset":0,"formula":"","role":"value","room":"","poll":true,"wp":"","cw":"","isScale":"","address":532,"id":"holdingRegisters.1.532_Input/Output_power"},{"_address":533,"deviceId":1,"name":"The power of generation","description":"Aktuelle Erzeugung Solaranlage","unit":"W","type":"int16be","len":1,"factor":1,"offset":0,"formula":"x *-10","role":"value","room":"","poll":true,"wp":"","cw":"","isScale":"","address":533,"id":"holdingRegisters.1.533_The_power_of_generation"},{"_address":535,"deviceId":1,"name":"EPS output power","description":"Aktueller Verbrauch Notstrom","unit":"W","type":"uint16be","len":1,"factor":1,"offset":0,"formula":"x / 10","role":"value","room":"","poll":true,"wp":"","cw":"","isScale":"","address":535,"id":"holdingRegisters.1.535_EPS_output_power"},{"_address":536,"deviceId":1,"name":"Generation of one day","description":"Erzeugung heute","unit":"kWh","type":"uint16be","len":1,"factor":1,"offset":0,"formula":"x / 100","role":"value","room":"","poll":true,"wp":"","cw":"","isScale":"","address":536,"id":"holdingRegisters.1.536_Generation_of_one_day"},{"_address":537,"deviceId":1,"name":"The power sell to grid of today","description":"Einspeisung heute","unit":"kWh","type":"uint16be","len":1,"factor":1,"offset":0,"formula":"x / 100","role":"value","room":"","poll":true,"wp":"","cw":"","isScale":"","address":537,"id":"holdingRegisters.1.537_The_power_sell_to_grid_of_today"},{"_address":538,"deviceId":1,"name":"The power buy from grid of today","description":"Netzbezug heute","unit":"kWh","type":"uint16be","len":1,"factor":1,"offset":0,"formula":"x / 100","role":"value","room":"","poll":true,"wp":"","cw":"","isScale":"","address":538,"id":"holdingRegisters.1.538_The_power_buy_from_grid_of_today"},{"_address":539,"deviceId":1,"name":"Today consumption of the load","description":"Hausverbrauch heute","unit":"kWh","type":"uint16be","len":1,"factor":1,"offset":0,"formula":"x / 100","role":"value","room":"","poll":true,"wp":"","cw":"","isScale":"","address":539,"id":"holdingRegisters.1.539_Today_consumption_of_the_load"}]
2024-06-17 08:08:49.740 - debug: modbus.0 (76061) Add holdingRegisters.1.525_Charge/Discha_rge_power: {"_id":"holdingRegisters.1.525_Charge/Discha_rge_power","type":"state","common":{"name":"Aktuelle Ladung & Entladung Batterie","role":"value","type":"number","read":true,"write":true,"def":0,"unit":"W"},"native":{"regType":"holdingRegs","address":525,"deviceId":1,"type":"int16be","len":1,"offset":0,"factor":1,"poll":true}}
2024-06-17 08:08:49.740 - debug: modbus.0 (76061) Add holdingRegisters.1.528_The_residual_capacity_of_battery: {"_id":"holdingRegisters.1.528_The_residual_capacity_of_battery","type":"state","common":{"name":"Batterieladung","role":"value","type":"number","read":true,"write":true,"def":0,"unit":"%"},"native":{"regType":"holdingRegs","address":528,"deviceId":1,"type":"uint16be","len":1,"offset":0,"factor":1,"poll":true}}
2024-06-17 08:08:49.740 - debug: modbus.0 (76061) Add holdingRegisters.1.530_Feed_in/out_power: {"_id":"holdingRegisters.1.530_Feed_in/out_power","type":"state","common":{"name":"Aktueller Netzbezug","role":"value","type":"number","read":true,"write":true,"def":0,"unit":"W"},"native":{"regType":"holdingRegs","address":530,"deviceId":1,"type":"int16be","len":1,"offset":0,"factor":1,"poll":true}}
2024-06-17 08:08:49.740 - debug: modbus.0 (76061) Add holdingRegisters.1.531_The_power_of_the_load: {"_id":"holdingRegisters.1.531_The_power_of_the_load","type":"state","common":{"name":"Aktueller Hausverbrauch","role":"value","type":"number","read":true,"write":true,"def":0,"unit":"W"},"native":{"regType":"holdingRegs","address":531,"deviceId":1,"type":"uint16be","len":1,"offset":0,"factor":1,"poll":true}}
2024-06-17 08:08:49.740 - debug: modbus.0 (76061) Add holdingRegisters.1.532_Input/Output_power: {"_id":"holdingRegisters.1.532_Input/Output_power","type":"state","common":{"name":"keine ahnng","role":"value","type":"number","read":true,"write":true,"def":0,"unit":""},"native":{"regType":"holdingRegs","address":532,"deviceId":1,"type":"int16be","len":1,"offset":0,"factor":1,"poll":true}}
2024-06-17 08:08:49.740 - debug: modbus.0 (76061) Add holdingRegisters.1.533_The_power_of_generation: {"_id":"holdingRegisters.1.533_The_power_of_generation","type":"state","common":{"name":"Aktuelle Erzeugung Solaranlage","role":"value","type":"number","read":true,"write":true,"def":0,"unit":"W"},"native":{"regType":"holdingRegs","address":533,"deviceId":1,"type":"int16be","len":1,"offset":0,"factor":1,"poll":true}}
2024-06-17 08:08:49.740 - debug: modbus.0 (76061) Add holdingRegisters.1.535_EPS_output_power: {"_id":"holdingRegisters.1.535_EPS_output_power","type":"state","common":{"name":"Aktueller Verbrauch Notstrom","role":"value","type":"number","read":true,"write":true,"def":0,"unit":"W"},"native":{"regType":"holdingRegs","address":535,"deviceId":1,"type":"uint16be","len":1,"offset":0,"factor":1,"poll":true}}
2024-06-17 08:08:49.740 - debug: modbus.0 (76061) Add holdingRegisters.1.536_Generation_of_one_day: {"_id":"holdingRegisters.1.536_Generation_of_one_day","type":"state","common":{"name":"Erzeugung heute","role":"value","type":"number","read":true,"write":true,"def":0,"unit":"kWh"},"native":{"regType":"holdingRegs","address":536,"deviceId":1,"type":"uint16be","len":1,"offset":0,"factor":1,"poll":true}}
2024-06-17 08:08:49.740 - debug: modbus.0 (76061) Add holdingRegisters.1.537_The_power_sell_to_grid_of_today: {"_id":"holdingRegisters.1.537_The_power_sell_to_grid_of_today","type":"state","common":{"name":"Einspeisung heute","role":"value","type":"number","read":true,"write":true,"def":0,"unit":"kWh"},"native":{"regType":"holdingRegs","address":537,"deviceId":1,"type":"uint16be","len":1,"offset":0,"factor":1,"poll":true}}
2024-06-17 08:08:49.740 - debug: modbus.0 (76061) Add holdingRegisters.1.538_The_power_buy_from_grid_of_today: {"_id":"holdingRegisters.1.538_The_power_buy_from_grid_of_today","type":"state","common":{"name":"Netzbezug heute","role":"value","type":"number","read":true,"write":true,"def":0,"unit":"kWh"},"native":{"regType":"holdingRegs","address":538,"deviceId":1,"type":"uint16be","len":1,"offset":0,"factor":1,"poll":true}}
2024-06-17 08:08:49.740 - debug: modbus.0 (76061) Add holdingRegisters.1.539_Today_consumption_of_the_load: {"_id":"holdingRegisters.1.539_Today_consumption_of_the_load","type":"state","common":{"name":"Hausverbrauch heute","role":"value","type":"number","read":true,"write":true,"def":0,"unit":"kWh"},"native":{"regType":"holdingRegs","address":539,"deviceId":1,"type":"uint16be","len":1,"offset":0,"factor":1,"poll":true}}
2024-06-17 08:08:49.907 - info: modbus.0 (76061) Connected to slave
2024-06-17 08:08:49.908 - debug: modbus.0 (76061) [DevID_1] Poll start ---------------------
2024-06-17 08:08:49.908 - debug: modbus.0 (76061) Initialization of scale factors done!
2024-06-17 08:08:49.908 - debug: modbus.0 (76061) [DevID_1/holdingRegs] Poll address 525 - 15 registers
2024-06-17 08:08:49.909 - debug: modbus.0 (76061) Sending pdu to the socket.
2024-06-17 08:08:49.910 - silly: modbus.0 (76061) Keepalive is disabled!
2024-06-17 08:08:49.912 - silly: modbus.0 (76061) States user redis pmessage modbus.0.*/modbus.0.info.connection:{"val":false,"ack":true,"ts":1718604529910,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1718604503573}
2024-06-17 08:08:49.912 - silly: modbus.0 (76061) States user redis pmessage modbus.0.*/modbus.0.info.connection:{"val":true,"ack":true,"ts":1718604529911,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1718604529911}
2024-06-17 08:08:50.909 - warn: modbus.0 (76061) Error: undefined
2024-06-17 08:08:50.909 - error: modbus.0 (76061) Request timed out.
2024-06-17 08:08:50.909 - error: modbus.0 (76061) Client in error state.
2024-06-17 08:08:50.910 - warn: modbus.0 (76061) Poll error count: 1 code: {"err":"timeout","timeout":1000}
2024-06-17 08:08:50.910 - debug: modbus.0 (76061) Socket closed with error
2024-06-17 08:08:50.910 - debug: modbus.0 (76061) Clearing timeout of the current request.
2024-06-17 08:08:50.910 - debug: modbus.0 (76061) Cleaning up request fifo.
2024-06-17 08:08:50.953 - silly: modbus.0 (76061) States user redis pmessage modbus.0.*/modbus.0.info.connection:{"val":false,"ack":true,"ts":1718604530951,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1718604530951}
2024-06-17 08:08:51.910 - debug: modbus.0 (76061) Closing client on purpose.
2024-06-17 08:08:51.910 - info: modbus.0 (76061) Disconnected from slave 192.168.178.5
2024-06-17 08:08:51.913 - silly: modbus.0 (76061) States user redis pmessage modbus.0.*/modbus.0.info.connection:{"val":false,"ack":true,"ts":1718604531912,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1718604530951}
2024-06-17 08:08:53.419 - info: modbus.0 (76061) Connected to slave
2024-06-17 08:08:53.419 - debug: modbus.0 (76061) [DevID_1] Poll start ---------------------
2024-06-17 08:08:53.419 - debug: modbus.0 (76061) [DevID_1/holdingRegs] Poll address 525 - 15 registers
2024-06-17 08:08:53.420 - debug: modbus.0 (76061) Sending pdu to the socket.
2024-06-17 08:08:53.420 - silly: modbus.0 (76061) Keepalive is disabled!
2024-06-17 08:08:53.422 - silly: modbus.0 (76061) States user redis pmessage modbus.0.*/modbus.0.info.connection:{"val":true,"ack":true,"ts":1718604533421,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1718604533421}
2024-06-17 08:08:54.421 - warn: modbus.0 (76061) Error: undefined
2024-06-17 08:08:54.421 - error: modbus.0 (76061) Request timed out.
2024-06-17 08:08:54.421 - error: modbus.0 (76061) Client in error state.
2024-06-17 08:08:54.421 - warn: modbus.0 (76061) Poll error count: 2 code: {"err":"timeout","timeout":1000}
2024-06-17 08:08:54.422 - debug: modbus.0 (76061) Socket closed with error
2024-06-17 08:08:54.422 - debug: modbus.0 (76061) Clearing timeout of the current request.
2024-06-17 08:08:54.422 - debug: modbus.0 (76061) Cleaning up request fifo.
2024-06-17 08:08:54.465 - silly: modbus.0 (76061) States user redis pmessage modbus.0.*/modbus.0.info.connection:{"val":false,"ack":true,"ts":1718604534463,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1718604534463}
2024-06-17 08:08:55.421 - debug: modbus.0 (76061) Closing client on purpose.
2024-06-17 08:08:55.421 - info: modbus.0 (76061) Disconnected from slave 192.168.178.5
2024-06-17 08:08:55.423 - silly: modbus.0 (76061) States user redis pmessage modbus.0.*/modbus.0.info.connection:{"val":false,"ack":true,"ts":1718604535422,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1718604534463}
2024-06-17 08:08:56.924 - info: modbus.0 (76061) Connected to slave
2024-06-17 08:08:56.924 - debug: modbus.0 (76061) [DevID_1] Poll start ---------------------
2024-06-17 08:08:56.924 - debug: modbus.0 (76061) [DevID_1/holdingRegs] Poll address 525 - 15 registers
2024-06-17 08:08:56.925 - debug: modbus.0 (76061) Sending pdu to the socket.
2024-06-17 08:08:56.925 - silly: modbus.0 (76061) Keepalive is disabled!
2024-06-17 08:08:57.017 - silly: modbus.0 (76061) States user redis pmessage modbus.0.*/modbus.0.info.connection:{"val":true,"ack":true,"ts":1718604537008,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1718604537008}
2024-06-17 08:08:57.925 - warn: modbus.0 (76061) Error: undefined
2024-06-17 08:08:57.925 - error: modbus.0 (76061) Request timed out.
2024-06-17 08:08:57.925 - error: modbus.0 (76061) Client in error state.
2024-06-17 08:08:57.925 - warn: modbus.0 (76061) Poll error count: 3 code: {"err":"timeout","timeout":1000}
2024-06-17 08:08:57.926 - debug: modbus.0 (76061) Socket closed with error
2024-06-17 08:08:57.926 - debug: modbus.0 (76061) Clearing timeout of the current request.
2024-06-17 08:08:57.926 - debug: modbus.0 (76061) Cleaning up request fifo.
2024-06-17 08:08:57.969 - silly: modbus.0 (76061) States user redis pmessage modbus.0.*/modbus.0.info.connection:{"val":false,"ack":true,"ts":1718604537968,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1718604537968}
2024-06-17 08:08:58.925 - debug: modbus.0 (76061) Closing client on purpose.
2024-06-17 08:08:58.926 - info: modbus.0 (76061) Disconnected from slave 192.168.178.5
2024-06-17 08:08:58.928 - silly: modbus.0 (76061) States user redis pmessage modbus.0.*/modbus.0.info.connection:{"val":false,"ack":true,"ts":1718604538927,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1718604537968}
2024-06-17 08:09:00.427 - info: modbus.0 (76061) Connected to slave
2024-06-17 08:09:00.427 - debug: modbus.0 (76061) [DevID_1] Poll start ---------------------
2024-06-17 08:09:00.427 - debug: modbus.0 (76061) [DevID_1/holdingRegs] Poll address 525 - 15 registers
2024-06-17 08:09:00.428 - debug: modbus.0 (76061) Sending pdu to the socket.
2024-06-17 08:09:00.428 - silly: modbus.0 (76061) Keepalive is disabled!
2024-06-17 08:09:00.435 - silly: modbus.0 (76061) States user redis pmessage modbus.0.*/modbus.0.info.connection:{"val":true,"ack":true,"ts":1718604540432,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1718604540432}
2024-06-17 08:09:01.428 - warn: modbus.0 (76061) Error: undefined
2024-06-17 08:09:01.429 - error: modbus.0 (76061) Request timed out.
2024-06-17 08:09:01.429 - error: modbus.0 (76061) Client in error state.
2024-06-17 08:09:01.429 - warn: modbus.0 (76061) Poll error count: 4 code: {"err":"timeout","timeout":1000}
2024-06-17 08:09:01.429 - debug: modbus.0 (76061) Socket closed with error
2024-06-17 08:09:01.429 - debug: modbus.0 (76061) Clearing timeout of the current request.
2024-06-17 08:09:01.429 - debug: modbus.0 (76061) Cleaning up request fifo.
2024-06-17 08:09:01.432 - silly: modbus.0 (76061) States user redis pmessage modbus.0.*/modbus.0.info.connection:{"val":false,"ack":true,"ts":1718604541430,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1718604541430}
2024-06-17 08:09:02.200 - info: host.ioBroker "system.adapter.modbus.0" disabled
2024-06-17 08:09:02.200 - info: host.ioBroker stopInstance system.adapter.modbus.0 (force=false, process=true)
2024-06-17 08:09:02.202 - silly: modbus.0 (76061) States system redis pmessage system.adapter.modbus.0.sigKill/system.adapter.modbus.0.sigKill:{"val":-1,"ack":false,"ts":1718604542201,"q":0,"from":"system.host.ioBroker","lc":1718604542201}
2024-06-17 08:09:02.202 - info: modbus.0 (76061) Got terminate signal TERMINATE_YOURSELF
2024-06-17 08:09:02.203 - debug: modbus.0 (76061) Closing client on purpose.
2024-06-17 08:09:02.203 - info: modbus.0 (76061) terminating
2024-06-17 08:09:02.203 - debug: modbus.0 (76061) Plugin sentry destroyed
2024-06-17 08:09:02.203 - info: modbus.0 (76061) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2024-06-17 08:09:02.206 - silly: modbus.0 (76061) States user redis pmessage modbus.0.*/modbus.0.info.connection:{"val":false,"ack":true,"ts":1718604542205,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1718604541430}
2024-06-17 08:09:02.297 - info: host.ioBroker stopInstance system.adapter.modbus.0 send kill signal
2024-06-17 08:09:02.703 - info: modbus.0 (76061) terminating
2024-06-17 08:09:02.766 - info: host.ioBroker instance system.adapter.modbus.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)

      Da diese Konfiguration bis zum Zeitpunkt X problemlos funktioniert hat bin ich etwas ratlos, was zu den Fehlern führt.
      Kann jemand etwas mit der Fehlermeldung im Log anfangen bzw. mich bei der Behebung unterstützen?

      Danke!

      Homoran JLeg 2 Replies Last reply Reply Quote 0
      • Homoran
        Homoran Global Moderator Administrators @n3ucr0n last edited by

        @n3ucr0n sagte in Plötzlich Probleme mit ModBus Adapter:

        Client in error state.

        ist ein Hinweis auf ein Problem außerhalb von ioBroker

        N 1 Reply Last reply Reply Quote 0
        • N
          n3ucr0n @Homoran last edited by

          @homoran
          Alles klar, danke für den Hinweis:

          Um für mich die Fehlerquellen "außerhalb vom ioBroker" zu definieren, folgendes wären Punkte:

          • Konfiguration des Konverters und Adapters fehlerhaft (kann ich das ausschließen, da es bereits funktioniert hat!?)
          • Hardwaredefekt des Konverters
          • Hardwaredefekt am Kabel zwischen Konverter und Switch (kann ich das ausschließen, da ich via IP noch auf den Konverter komme?)
          • Hardwaredefekt am Kabel zwischen Wechselrichter und Konverter

          Gibt es noch weitere Punkte die ich checken sollte?

          Danke!

          Latzi 1 Reply Last reply Reply Quote 0
          • Latzi
            Latzi @n3ucr0n last edited by

            @n3ucr0n
            timeout vom Modbus-Adapter höher stellen, 1 sek ist sportlich 😉

            N 1 Reply Last reply Reply Quote 0
            • N
              n3ucr0n @Latzi last edited by

              @latzi Habe die Zeiten mal auf 10 Sekunden erhöht.

              Selbige Fehler nur eben nicht mehr im Sekundentakt 😊

              Latzi 1 Reply Last reply Reply Quote 0
              • Latzi
                Latzi @n3ucr0n last edited by

                @n3ucr0n
                schade, Versuch war´s wert.

                1 Reply Last reply Reply Quote 0
                • JLeg
                  JLeg @n3ucr0n last edited by

                  @n3ucr0n hast du den Waveshare-Adapter mal stromlos gemacht? Ich benutze ein ähnliches Teil, ab und zuhängt sich das leider schonmal auf...

                  N 1 Reply Last reply Reply Quote 0
                  • N
                    n3ucr0n @JLeg last edited by

                    @jleg Ja, ich habe es mal für einige Sekunden vom Strom getrennt.

                    Leider gleiches Problem.

                    W 1 Reply Last reply Reply Quote 0
                    • W
                      warp735 @n3ucr0n last edited by

                      @n3ucr0n
                      Hat der WR n Update gefahren?

                      N 1 Reply Last reply Reply Quote 0
                      • N
                        n3ucr0n @warp735 last edited by

                        @warp735 Das weiß ich leider nicht - Aber selbst bei einem WR Update dürften sich doch die Register nicht ändern!?

                        Homoran W 2 Replies Last reply Reply Quote 0
                        • Homoran
                          Homoran Global Moderator Administrators @n3ucr0n last edited by

                          @n3ucr0n sagte in Plötzlich Probleme mit ModBus Adapter:

                          Aber selbst bei einem WR Update dürften sich doch die Register nicht ändern!?

                          aber der Client braucht dann ggf. einen reboot

                          N 1 Reply Last reply Reply Quote 0
                          • W
                            warp735 @n3ucr0n last edited by

                            @n3ucr0n sagte in Plötzlich Probleme mit ModBus Adapter:

                            doch die Register nicht ändern

                            Warum nicht...?! Hatte ich erst gestern. BMS Update vom Akku gefahren und Modbus ging garnix mehr. Bin dann wieder zurück auf die alte Version

                            1 Reply Last reply Reply Quote 0
                            • N
                              n3ucr0n @Homoran last edited by

                              @homoran

                              Reboot war die Lösung. Allerdings ein Reboot des Wechselrichters!

                              Durch den Akku der mit dran hängt geht der nicht "von alleine" aus.
                              Habe grade mal die Verbindung zum Zählerschrank und zum Akku getrennt, neu hochgefahren, Daten laufen wieder.

                              Danke für die Unterstützung!

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

                                @n3ucr0n sagte in Plötzlich Probleme mit ModBus Adapter:

                                Reboot war die Lösung. Allerdings ein Reboot des Wechselrichters!

                                Natürlich Wechselrichter. Da sitzt doch der Modbus Client drin.

                                N 1 Reply Last reply Reply Quote 0
                                • N
                                  n3ucr0n @Homoran last edited by

                                  @homoran
                                  Ja auf die Idee war ich nicht gekommen - habe immer den Konverter neu gestartet aber an die Quelle habe ich dummerweise nicht gedacht. Manchmal hat man nicht nur nen Brett sondern einen Wald vor dem Kopf.

                                  Danke für die Axt 😁

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

                                    @n3ucr0n sagte in [gelöst] Plötzlich Probleme mit ModBus Adapter:

                                    habe immer den Konverter neu gestartet

                                    wäre auch noch mögl7ch gewesen, aber nach dem zweiten Mal ohne Veränderung.....😁

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

                                    Support us

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

                                    807
                                    Online

                                    31.9k
                                    Users

                                    80.2k
                                    Topics

                                    1.3m
                                    Posts

                                    5
                                    16
                                    503
                                    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