Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. discoma

    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

    D
    • Profile
    • Following 0
    • Followers 0
    • Topics 0
    • Posts 1
    • Best 0
    • Groups 0

    discoma

    @discoma

    0
    Reputation
    8
    Profile views
    1
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    discoma Follow

    Latest posts made by discoma

    • RE: RSCP an E3DC keine Verbindung

      @chris71

      Ich erhalte ebenfalls keine Daten vom E3DC sondern nur diese Meldungen:

      e3dc-rscp.0
      	2023-08-01 15:42:04.157	warn	Received data type NONE with data length = 11 - tagCode 0x800000
      e3dc-rscp.0
      	2023-08-01 15:42:04.146	warn	Received data type NONE with data length = 11 - tagCode 0x800000
      e3dc-rscp.0
      	2023-08-01 15:42:04.134	warn	Received data type NONE with data length = 11 - tagCode 0x800000
      e3dc-rscp.0
      	2023-08-01 15:42:04.121	warn	Received data type NONE with data length = 11 - tagCode 0x800000
      e3dc-rscp.0
      	2023-08-01 15:42:04.108	warn	Received data type NONE with data length = 11 - tagCode 0x800000
      e3dc-rscp.0
      	2023-08-01 15:42:04.094	warn	Received data type ERROR: RSCP_ERR_ACCESS_DENIED (2) - tag TAG_EMS_STATUS (0x1800040)
      e3dc-rscp.0
      	2023-08-01 15:42:04.093	warn	Received data type ERROR: RSCP_ERR_ACCESS_DENIED (2) - tag TAG_EMS_ALIVE (0x1850000)
      e3dc-rscp.0
      	2023-08-01 15:42:04.093	warn	Received data type ERROR: RSCP_ERR_ACCESS_DENIED (2) - tag TAG_EMS_MODE (0x1800011)
      e3dc-rscp.0
      	2023-08-01 15:42:04.092	warn	Received data type ERROR: RSCP_ERR_ACCESS_DENIED (2) - tag TAG_EMS_POWER_ADD (0x1800005)
      e3dc-rscp.0
      	2023-08-01 15:42:04.091	warn	Received data type ERROR: RSCP_ERR_ACCESS_DENIED (2) - tag TAG_EMS_POWER_GRID (0x1800004)
      e3dc-rscp.0
      	2023-08-01 15:42:04.090	warn	Received data type ERROR: RSCP_ERR_ACCESS_DENIED (2) - tag TAG_EMS_POWER_HOME (0x1800003)
      e3dc-rscp.0
      	2023-08-01 15:42:04.090	warn	Received data type ERROR: RSCP_ERR_ACCESS_DENIED (2) - tag TAG_EMS_POWER_BAT (0x1800002)
      e3dc-rscp.0
      	2023-08-01 15:42:04.089	warn	Received data type ERROR: RSCP_ERR_ACCESS_DENIED (2) - tag TAG_EMS_POWER_PV (0x1800001)
      node-red.0
      	2023-08-01 15:41:56.734	error	1 Aug 15:41:56 - [error] [modbus-read:E3DCauslesen] Error: Timed out at /opt/iobroker/iobroker-data/node-red/node_modules/node-red-contrib-modbus/modbus/maps/core/core/modbus-client-core.js:79:156
      node-red.0
      	2023-08-01 15:41:56.731	warn	1 Aug 15:41:56 - [warn] [modbus-read:E3DCauslesen] Modbus Failure On State sending Get More About It By Logging 1 Aug 15:41:56 - [warn] [modbus-client:E3DC ] Client -> fsm broken state after failed Get More About It By Logging TCP@192.168.178.58:5033 default Unit-Id: 1
      node-red.0
      	2023-08-01 15:41:56.729	warn	1 Aug 15:41:56 - [warn] [modbus-client:E3DC ] Client -> fsm failed state after sending Get More About It By Logging TCP@192.168.178.58:5033 default Unit-Id: 1 
      

      Die Verbindung in der Instanz scheint in Ordnung zu sein:
      2023-08-01_-1.png

      In Node-Red sieht es wie folgt aus:
      2023-08-01_-2.png

      Kann jemand weiterhelfen?

      posted in Einsteigerfragen
      D
      discoma
    Community
    Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
    The ioBroker Community 2014-2023
    logo