Skip to content
  • 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
Logo
  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. Test Adapter OpenKNX 0.6.x

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.1k
  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    1.8k
  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.0k

Test Adapter OpenKNX 0.6.x

Scheduled Pinned Locked Moved Tester
577 Posts 72 Posters 161.2k Views 71 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.
  • A Automatisierer 0

    @killroy2
    Hier eine Zusatzinfo zu Problem mit dem HVAC-Modus DPT20.102:

    Ich habe auf die neuerste Version V0.5.2 des Adapters umgestellt.
    Der Fehler tritt weiterhin auf.
    Der Datenpunkt hat das Attribut: "autoread": true

    Vielleicht hilft das weiter.

    H Do not disturb
    H Do not disturb
    Hansi1234
    wrote on last edited by Hansi1234
    #479

    Guten Morgen zusammen.

    Ich habe folgende Fehlermeldungen im Log. Kann mir hier jemand helfen?

    [error] 3/5/2023, 7:47:39 AM.672 KNXUltimate-KNXEngine: Sending KNX packet: Send UDP Catch error: Not running object seqCounter:undefined

    EDIT:
    Falsches Forum. Sorry. Ich erstelle ein Tread im Node-Red Abteil. Danke

    1 Reply Last reply
    0
    • M Offline
      M Offline
      mpl1338
      wrote on last edited by
      #480

      kann der Adapter Telegramme auf den Bus bestätigen? Ich habe etliche GAs die nur für IOBroker zwecke senden. Kann der Apadpter diese bestätigen? Ich habe sehr viele wiederholende Telegramme und würde dieses verhalten gerne abstellen.

      K 1 Reply Last reply
      0
      • 123brokerei1 Offline
        123brokerei1 Offline
        123brokerei
        wrote on last edited by 123brokerei
        #481

        Hallo,

        ich habe leider ständige Verbindungsabbrüche. Hat mir im Zusammenhang mit dem Log jemand einen Tipp?

        023-03-08 10:22:21.846 - info: openknx.0 (3126) starting. Version 0.2.5 in /opt/iobroker/node_modules/iobroker.openknx, node: v16.19.0, js-controller: 4.0.24
2023-03-08 10:22:21.858 - info: openknx.0 (3126) Connecting to knx gateway: xxx.xxx.xxx.xx:3671 with phy. Adr: 1.1.1 minimum send delay: 50 ms debug level: debug
2023-03-08 10:22:21.859 - info: openknx.0 (3126) /opt/iobroker/node_modules/iobroker.js-controller
2023-03-08 10:22:21.925 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:23:21.927 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:23:24.927 - warn: openknx.0 (3126) [warn] 2023-03-08 09:23:24.927 connection timed out, retrying...
2023-03-08 10:23:27.928 - warn: openknx.0 (3126) [warn] 2023-03-08 09:23:27.928 connection timed out, retrying...
2023-03-08 10:23:33.931 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:23:33.939 - info: openknx.0 (3126) Connected!
2023-03-08 10:23:33.990 - info: openknx.0 (3126) Found 0 valid KNX objects of 2 objects in adapter.
2023-03-08 10:25:34.942 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:25:34.944 - warn: openknx.0 (3126) timed out waiting for CONNECTIONSTATE_RESPONSE
2023-03-08 10:25:37.167 - warn: openknx.0 (2311) Connection lost
2023-03-08 10:25:37.169 - warn: openknx.0 (2311) Could not perform strict object check of state openknx.0.info.connection: DB closed
2023-03-08 10:25:37.169 - warn: openknx.0 (2311) get state error: Connection is closed.
2023-03-08 10:25:37.944 - warn: openknx.0 (3126) [warn] 2023-03-08 09:25:37.944 connection timed out, retrying...
2023-03-08 10:25:37.948 - info: openknx.0 (3126) Connected!
2023-03-08 10:25:39.686 - info: openknx.0 (3126) [info] 2023-03-08 09:25:39.686 empty internal fsm queue due to inbound_DISCONNECT_REQUEST:
2023-03-08 10:25:39.686 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:25:40.169 - warn: openknx.0 (2311) [warn] 2023-03-08 09:25:40.169 connection timed out, retrying...
2023-03-08 10:25:42.688 - warn: openknx.0 (3126) [warn] 2023-03-08 09:25:42.687 connection timed out, retrying...
2023-03-08 10:25:43.170 - warn: openknx.0 (2311) [warn] 2023-03-08 09:25:43.170 connection timed out, retrying...
2023-03-08 10:25:45.687 - warn: openknx.0 (3126) [warn] 2023-03-08 09:25:45.687 connection timed out, retrying...
2023-03-08 10:25:51.689 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:25:54.691 - warn: openknx.0 (3126) [warn] 2023-03-08 09:25:54.691 connection timed out, retrying...
2023-03-08 10:25:57.692 - warn: openknx.0 (3126) [warn] 2023-03-08 09:25:57.692 connection timed out, retrying...
2023-03-08 10:26:06.694 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:26:09.695 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:09.695 connection timed out, retrying...
2023-03-08 10:26:12.696 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:12.696 connection timed out, retrying...
2023-03-08 10:26:12.698 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:26:37.950 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:37.950 Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
2023-03-08 10:26:38.951 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:26:38.952 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:38.952 Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
2023-03-08 10:26:38.952 - warn: openknx.0 (3126) timed out waiting for CONNECTIONSTATE_RESPONSE
2023-03-08 10:26:41.952 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:41.952 connection timed out, retrying...
2023-03-08 10:26:41.953 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:41.953 Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
2023-03-08 10:26:44.953 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:44.953 connection timed out, retrying...
2023-03-08 10:26:44.954 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:44.954 Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
2023-03-08 10:26:56.955 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:26:56.957 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:56.956 Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
2023-03-08 10:26:59.957 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:59.957 connection timed out, retrying...
2023-03-08 10:26:59.958 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:59.958 Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
2023-03-08 10:27:02.958 - warn: openknx.0 (3126) [warn] 2023-03-08 09:27:02.958 connection timed out, retrying...
2023-03-08 10:27:02.959 - warn: openknx.0 (3126) [warn] 2023-03-08 09:27:02.959 Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
2023-03-08 10:27:17.961 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:27:17.964 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:28:17.965 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:28:20.967 - warn: openknx.0 (3126) [warn] 2023-03-08 09:28:20.967 connection timed out, retrying...
2023-03-08 10:28:22.293 - info: openknx.0 (3126) [info] 2023-03-08 09:28:22.293 empty internal fsm queue due to inbound_DISCONNECT_REQUEST:
2023-03-08 10:28:23.967 - warn: openknx.0 (3126) [warn] 2023-03-08 09:28:23.967 connection timed out, retrying...
2023-03-08 10:28:41.969 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:28:44.971 - warn: openknx.0 (3126) [warn] 2023-03-08 09:28:44.971 connection timed out, retrying...
2023-03-08 10:28:44.974 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:28:44.976 - info: openknx.0 (3126) Connected!
2023-03-08 10:28:44.979 - info: openknx.0 (3126) Connected!
2023-03-08 10:30:46.170 - warn: openknx.0 (2311) Connection lost
2023-03-08 10:30:46.172 - warn: openknx.0 (2311) Could not perform strict object check of state openknx.0.info.connection: DB closed
2023-03-08 10:30:46.172 - warn: openknx.0 (2311) get state error: Connection is closed.
2023-03-08 10:30:49.171 - warn: openknx.0 (2311) [warn] 2023-03-08 09:30:49.171 connection timed out, retrying...
2023-03-08 10:30:52.172 - warn: openknx.0 (2311) [warn] 2023-03-08 09:30:52.172 connection timed out, retrying...
2023-03-08 10:31:11.099 - info: openknx.0 (3126) [info] 2023-03-08 09:31:11.099 empty internal fsm queue due to inbound_DISCONNECT_REQUEST:
2023-03-08 10:31:11.100 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:31:11.104 - info: openknx.0 (3126) Connected!
2023-03-08 10:31:45.981 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:31:45.982 - warn: openknx.0 (3126) timed out waiting for CONNECTIONSTATE_RESPONSE
2023-03-08 10:31:48.982 - warn: openknx.0 (3126) [warn] 2023-03-08 09:31:48.982 connection timed out, retrying...
2023-03-08 10:31:48.987 - info: openknx.0 (3126) Connected!
2023-03-08 10:34:49.994 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:34:49.995 - warn: openknx.0 (3126) timed out waiting for CONNECTIONSTATE_RESPONSE
2023-03-08 10:34:52.995 - warn: openknx.0 (3126) [warn] 2023-03-08 09:34:52.995 connection timed out, retrying...
2023-03-08 10:34:55.996 - warn: openknx.0 (3126) [warn] 2023-03-08 09:34:55.996 connection timed out, retrying...
2023-03-08 10:35:01.997 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:35:02.003 - info: openknx.0 (3126) Connected!
2023-03-08 10:35:55.174 - warn: openknx.0 (2311) Connection lost
2023-03-08 10:35:55.175 - warn: openknx.0 (2311) Could not perform strict object check of state openknx.0.info.connection: DB closed
2023-03-08 10:35:55.176 - warn: openknx.0 (2311) get state error: Connection is closed.
2023-03-08 10:35:58.175 - warn: openknx.0 (2311) [warn] 2023-03-08 09:35:58.175 connection timed out, retrying...
2023-03-08 10:36:01.176 - warn: openknx.0 (2311) [warn] 2023-03-08 09:36:01.176 connection timed out, retrying...
        123brokerei1 K 2 Replies Last reply
        0
        • 123brokerei1 123brokerei

          Hallo,

          ich habe leider ständige Verbindungsabbrüche. Hat mir im Zusammenhang mit dem Log jemand einen Tipp?

          023-03-08 10:22:21.846 - info: openknx.0 (3126) starting. Version 0.2.5 in /opt/iobroker/node_modules/iobroker.openknx, node: v16.19.0, js-controller: 4.0.24
2023-03-08 10:22:21.858 - info: openknx.0 (3126) Connecting to knx gateway: xxx.xxx.xxx.xx:3671 with phy. Adr: 1.1.1 minimum send delay: 50 ms debug level: debug
2023-03-08 10:22:21.859 - info: openknx.0 (3126) /opt/iobroker/node_modules/iobroker.js-controller
2023-03-08 10:22:21.925 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:23:21.927 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:23:24.927 - warn: openknx.0 (3126) [warn] 2023-03-08 09:23:24.927 connection timed out, retrying...
2023-03-08 10:23:27.928 - warn: openknx.0 (3126) [warn] 2023-03-08 09:23:27.928 connection timed out, retrying...
2023-03-08 10:23:33.931 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:23:33.939 - info: openknx.0 (3126) Connected!
2023-03-08 10:23:33.990 - info: openknx.0 (3126) Found 0 valid KNX objects of 2 objects in adapter.
2023-03-08 10:25:34.942 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:25:34.944 - warn: openknx.0 (3126) timed out waiting for CONNECTIONSTATE_RESPONSE
2023-03-08 10:25:37.167 - warn: openknx.0 (2311) Connection lost
2023-03-08 10:25:37.169 - warn: openknx.0 (2311) Could not perform strict object check of state openknx.0.info.connection: DB closed
2023-03-08 10:25:37.169 - warn: openknx.0 (2311) get state error: Connection is closed.
2023-03-08 10:25:37.944 - warn: openknx.0 (3126) [warn] 2023-03-08 09:25:37.944 connection timed out, retrying...
2023-03-08 10:25:37.948 - info: openknx.0 (3126) Connected!
2023-03-08 10:25:39.686 - info: openknx.0 (3126) [info] 2023-03-08 09:25:39.686 empty internal fsm queue due to inbound_DISCONNECT_REQUEST:
2023-03-08 10:25:39.686 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:25:40.169 - warn: openknx.0 (2311) [warn] 2023-03-08 09:25:40.169 connection timed out, retrying...
2023-03-08 10:25:42.688 - warn: openknx.0 (3126) [warn] 2023-03-08 09:25:42.687 connection timed out, retrying...
2023-03-08 10:25:43.170 - warn: openknx.0 (2311) [warn] 2023-03-08 09:25:43.170 connection timed out, retrying...
2023-03-08 10:25:45.687 - warn: openknx.0 (3126) [warn] 2023-03-08 09:25:45.687 connection timed out, retrying...
2023-03-08 10:25:51.689 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:25:54.691 - warn: openknx.0 (3126) [warn] 2023-03-08 09:25:54.691 connection timed out, retrying...
2023-03-08 10:25:57.692 - warn: openknx.0 (3126) [warn] 2023-03-08 09:25:57.692 connection timed out, retrying...
2023-03-08 10:26:06.694 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:26:09.695 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:09.695 connection timed out, retrying...
2023-03-08 10:26:12.696 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:12.696 connection timed out, retrying...
2023-03-08 10:26:12.698 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:26:37.950 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:37.950 Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
2023-03-08 10:26:38.951 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:26:38.952 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:38.952 Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
2023-03-08 10:26:38.952 - warn: openknx.0 (3126) timed out waiting for CONNECTIONSTATE_RESPONSE
2023-03-08 10:26:41.952 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:41.952 connection timed out, retrying...
2023-03-08 10:26:41.953 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:41.953 Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
2023-03-08 10:26:44.953 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:44.953 connection timed out, retrying...
2023-03-08 10:26:44.954 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:44.954 Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
2023-03-08 10:26:56.955 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:26:56.957 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:56.956 Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
2023-03-08 10:26:59.957 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:59.957 connection timed out, retrying...
2023-03-08 10:26:59.958 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:59.958 Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
2023-03-08 10:27:02.958 - warn: openknx.0 (3126) [warn] 2023-03-08 09:27:02.958 connection timed out, retrying...
2023-03-08 10:27:02.959 - warn: openknx.0 (3126) [warn] 2023-03-08 09:27:02.959 Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
2023-03-08 10:27:17.961 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:27:17.964 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:28:17.965 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:28:20.967 - warn: openknx.0 (3126) [warn] 2023-03-08 09:28:20.967 connection timed out, retrying...
2023-03-08 10:28:22.293 - info: openknx.0 (3126) [info] 2023-03-08 09:28:22.293 empty internal fsm queue due to inbound_DISCONNECT_REQUEST:
2023-03-08 10:28:23.967 - warn: openknx.0 (3126) [warn] 2023-03-08 09:28:23.967 connection timed out, retrying...
2023-03-08 10:28:41.969 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:28:44.971 - warn: openknx.0 (3126) [warn] 2023-03-08 09:28:44.971 connection timed out, retrying...
2023-03-08 10:28:44.974 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:28:44.976 - info: openknx.0 (3126) Connected!
2023-03-08 10:28:44.979 - info: openknx.0 (3126) Connected!
2023-03-08 10:30:46.170 - warn: openknx.0 (2311) Connection lost
2023-03-08 10:30:46.172 - warn: openknx.0 (2311) Could not perform strict object check of state openknx.0.info.connection: DB closed
2023-03-08 10:30:46.172 - warn: openknx.0 (2311) get state error: Connection is closed.
2023-03-08 10:30:49.171 - warn: openknx.0 (2311) [warn] 2023-03-08 09:30:49.171 connection timed out, retrying...
2023-03-08 10:30:52.172 - warn: openknx.0 (2311) [warn] 2023-03-08 09:30:52.172 connection timed out, retrying...
2023-03-08 10:31:11.099 - info: openknx.0 (3126) [info] 2023-03-08 09:31:11.099 empty internal fsm queue due to inbound_DISCONNECT_REQUEST:
2023-03-08 10:31:11.100 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:31:11.104 - info: openknx.0 (3126) Connected!
2023-03-08 10:31:45.981 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:31:45.982 - warn: openknx.0 (3126) timed out waiting for CONNECTIONSTATE_RESPONSE
2023-03-08 10:31:48.982 - warn: openknx.0 (3126) [warn] 2023-03-08 09:31:48.982 connection timed out, retrying...
2023-03-08 10:31:48.987 - info: openknx.0 (3126) Connected!
2023-03-08 10:34:49.994 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:34:49.995 - warn: openknx.0 (3126) timed out waiting for CONNECTIONSTATE_RESPONSE
2023-03-08 10:34:52.995 - warn: openknx.0 (3126) [warn] 2023-03-08 09:34:52.995 connection timed out, retrying...
2023-03-08 10:34:55.996 - warn: openknx.0 (3126) [warn] 2023-03-08 09:34:55.996 connection timed out, retrying...
2023-03-08 10:35:01.997 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:35:02.003 - info: openknx.0 (3126) Connected!
2023-03-08 10:35:55.174 - warn: openknx.0 (2311) Connection lost
2023-03-08 10:35:55.175 - warn: openknx.0 (2311) Could not perform strict object check of state openknx.0.info.connection: DB closed
2023-03-08 10:35:55.176 - warn: openknx.0 (2311) get state error: Connection is closed.
2023-03-08 10:35:58.175 - warn: openknx.0 (2311) [warn] 2023-03-08 09:35:58.175 connection timed out, retrying...
2023-03-08 10:36:01.176 - warn: openknx.0 (2311) [warn] 2023-03-08 09:36:01.176 connection timed out, retrying...
          123brokerei1 Offline
          123brokerei1 Offline
          123brokerei
          wrote on last edited by
          #482

          @123brokerei Kleine Ergänzung: ich verwende den MDT Router SCN-IP100.03 mit der Applikation ohne KNX Secure...

          1 Reply Last reply
          0
          • M mpl1338

            kann der Adapter Telegramme auf den Bus bestätigen? Ich habe etliche GAs die nur für IOBroker zwecke senden. Kann der Apadpter diese bestätigen? Ich habe sehr viele wiederholende Telegramme und würde dieses verhalten gerne abstellen.

            K Offline
            K Offline
            killroy2
            wrote on last edited by killroy2
            #483

            @mpl1338
            Ich fürchte das ist nicht möglich. Die IP Gateways sind relativ einfach gestrickt und leiten die Anfragen von einem Netz ins andere weiter. Ich kenne da keine Stelle wo das Protokoll sowas zulassen würde.

            1 Reply Last reply
            1
            • A Automatisierer 0

              Problem mit HVAC-Mode:

              Ich habe die folgende Fehlermeldung im Log:

              openknx.0
	2023-03-01 22:44:47.874	warn	[warn] "2023-03-01T21:44:47.874Z" 'DPT1.fromBuffer: buf should be 1 byte (got 2 bytes)' 2
openknx.0
	2023-03-01 22:44:47.695	warn	[warn] "2023-03-01T21:44:47.695Z" 'DPT1.fromBuffer: buf should be 1 byte (got 2 bytes)' 2
openknx.0
	2023-03-01 22:44:47.645	warn	[warn] "2023-03-01T21:44:47.645Z" 'DPT1.fromBuffer: buf should be 1 byte (got 2 bytes)' 2
openknx.0
	2023-03-01 22:44:47.592	warn	[warn] "2023-03-01T21:44:47.592Z" 'DPT1.fromBuffer: buf should be 1 byte (got 2 bytes)' 2
openknx.0
	2023-03-01 22:44:47.269	warn	[warn] "2023-03-01T21:44:47.269Z" 'DPT1.fromBuffer: buf should be 1 byte (got 2 bytes)' 2
openknx.0
	2023-03-01 22:44:46.822	warn	[warn] "2023-03-01T21:44:46.822Z" 'DPT1.fromBuffer: buf should be 1 byte (got 2 bytes)' 2

              Der Datenpunt sieht folgendermaßen aus:

              {
  "_id": "openknx.0.Heizung_und_Temp_(HZ).Gar__Wkst_.HZ_-_GH_-_El_Radiator_Beide_-_Betriebsartvorwahl_(Komfort_Nacht_Frost)",
  "type": "state",
  "common": {
    "desc": "Basetype: 1-byte",
    "name": "HZ - GH - El.Radiator Beide - Betriebsartvorwahl (Komfort/Nacht/Frost)",
    "read": true,
    "role": "state",
    "type": "number",
    "write": true
  },
  "native": {
    "address": "6/4/35",
    "answer_groupValueResponse": false,
    "autoread": true,
    "bitlength": 8,
    "dpt": "DPT20.102",
    "valuetype": "basic"
  },
  "from": "system.adapter.openknx.0",
  "user": "system.user.admin",
  "ts": 1677706626491,
  "acl": {
    "object": 1636,
    "state": 1636,
    "owner": "system.user.admin",
    "ownerGroup": "system.group.administrator"
  }
}

              Hier die Projektierung in der ETS:

              fehler.jpg

              Frage:
              Wo ist das Problem ?
              Was ist falsch?

              K Offline
              K Offline
              killroy2
              wrote on last edited by
              #484

              @automatisierer-0 said in Test Adapter OpenKNX 0.2.x:

              Frage:
              Wo ist das Problem ?
              Was ist falsch?

              Die Zuordnung passt nicht, oben kommt eine DPT1 konfigurierte Nachricht, unten ist ein DPT20

              1 Reply Last reply
              1
              • A Automatisierer 0

                Es verwirrt mich:
                Nach dem erfolgreichen einlesen des XML Files kann man nur rechts unten den Button CLOSE drücken.
                Ich hätte mir eigentlich erwartet, dass ich den Button "SAVE" oder "SAVE AND CLOSE" drücken muss.

                K Offline
                K Offline
                killroy2
                wrote on last edited by
                #485

                @automatisierer-0 said in Test Adapter OpenKNX 0.2.x:

                Es verwirrt mich:
                Nach dem erfolgreichen einlesen des XML Files kann man nur rechts unten den Button CLOSE drücken.
                Ich hätte mir eigentlich erwartet, dass ich den Button "SAVE" oder "SAVE AND CLOSE" drücken muss.

                die Buttons sind zB für die Checkboxen, der Importdialog speichert immer und startet den Adapter neu.
                Ich ändere die Beschriftung damit es eindeutig wird.

                1 Reply Last reply
                1
                • S Sam 0

                  Hi, kann mir villeicht jemand sagen ob es möglich ist zwischen Leseanfrage und Schreibtelegramme zu unterscheiden?

                  K Offline
                  K Offline
                  killroy2
                  wrote on last edited by
                  #486

                  @sam-0 Du meinst zwischen groupValueResponse und write? Nein, diese Information wird nicht nach oben weitergegeben.

                  1 Reply Last reply
                  1
                  • 123brokerei1 123brokerei

                    Hallo,

                    ich habe leider ständige Verbindungsabbrüche. Hat mir im Zusammenhang mit dem Log jemand einen Tipp?

                    023-03-08 10:22:21.846 - info: openknx.0 (3126) starting. Version 0.2.5 in /opt/iobroker/node_modules/iobroker.openknx, node: v16.19.0, js-controller: 4.0.24
2023-03-08 10:22:21.858 - info: openknx.0 (3126) Connecting to knx gateway: xxx.xxx.xxx.xx:3671 with phy. Adr: 1.1.1 minimum send delay: 50 ms debug level: debug
2023-03-08 10:22:21.859 - info: openknx.0 (3126) /opt/iobroker/node_modules/iobroker.js-controller
2023-03-08 10:22:21.925 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:23:21.927 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:23:24.927 - warn: openknx.0 (3126) [warn] 2023-03-08 09:23:24.927 connection timed out, retrying...
2023-03-08 10:23:27.928 - warn: openknx.0 (3126) [warn] 2023-03-08 09:23:27.928 connection timed out, retrying...
2023-03-08 10:23:33.931 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:23:33.939 - info: openknx.0 (3126) Connected!
2023-03-08 10:23:33.990 - info: openknx.0 (3126) Found 0 valid KNX objects of 2 objects in adapter.
2023-03-08 10:25:34.942 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:25:34.944 - warn: openknx.0 (3126) timed out waiting for CONNECTIONSTATE_RESPONSE
2023-03-08 10:25:37.167 - warn: openknx.0 (2311) Connection lost
2023-03-08 10:25:37.169 - warn: openknx.0 (2311) Could not perform strict object check of state openknx.0.info.connection: DB closed
2023-03-08 10:25:37.169 - warn: openknx.0 (2311) get state error: Connection is closed.
2023-03-08 10:25:37.944 - warn: openknx.0 (3126) [warn] 2023-03-08 09:25:37.944 connection timed out, retrying...
2023-03-08 10:25:37.948 - info: openknx.0 (3126) Connected!
2023-03-08 10:25:39.686 - info: openknx.0 (3126) [info] 2023-03-08 09:25:39.686 empty internal fsm queue due to inbound_DISCONNECT_REQUEST:
2023-03-08 10:25:39.686 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:25:40.169 - warn: openknx.0 (2311) [warn] 2023-03-08 09:25:40.169 connection timed out, retrying...
2023-03-08 10:25:42.688 - warn: openknx.0 (3126) [warn] 2023-03-08 09:25:42.687 connection timed out, retrying...
2023-03-08 10:25:43.170 - warn: openknx.0 (2311) [warn] 2023-03-08 09:25:43.170 connection timed out, retrying...
2023-03-08 10:25:45.687 - warn: openknx.0 (3126) [warn] 2023-03-08 09:25:45.687 connection timed out, retrying...
2023-03-08 10:25:51.689 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:25:54.691 - warn: openknx.0 (3126) [warn] 2023-03-08 09:25:54.691 connection timed out, retrying...
2023-03-08 10:25:57.692 - warn: openknx.0 (3126) [warn] 2023-03-08 09:25:57.692 connection timed out, retrying...
2023-03-08 10:26:06.694 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:26:09.695 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:09.695 connection timed out, retrying...
2023-03-08 10:26:12.696 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:12.696 connection timed out, retrying...
2023-03-08 10:26:12.698 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:26:37.950 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:37.950 Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
2023-03-08 10:26:38.951 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:26:38.952 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:38.952 Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
2023-03-08 10:26:38.952 - warn: openknx.0 (3126) timed out waiting for CONNECTIONSTATE_RESPONSE
2023-03-08 10:26:41.952 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:41.952 connection timed out, retrying...
2023-03-08 10:26:41.953 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:41.953 Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
2023-03-08 10:26:44.953 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:44.953 connection timed out, retrying...
2023-03-08 10:26:44.954 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:44.954 Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
2023-03-08 10:26:56.955 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:26:56.957 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:56.956 Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
2023-03-08 10:26:59.957 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:59.957 connection timed out, retrying...
2023-03-08 10:26:59.958 - warn: openknx.0 (3126) [warn] 2023-03-08 09:26:59.958 Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
2023-03-08 10:27:02.958 - warn: openknx.0 (3126) [warn] 2023-03-08 09:27:02.958 connection timed out, retrying...
2023-03-08 10:27:02.959 - warn: openknx.0 (3126) [warn] 2023-03-08 09:27:02.959 Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
2023-03-08 10:27:17.961 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:27:17.964 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:28:17.965 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:28:20.967 - warn: openknx.0 (3126) [warn] 2023-03-08 09:28:20.967 connection timed out, retrying...
2023-03-08 10:28:22.293 - info: openknx.0 (3126) [info] 2023-03-08 09:28:22.293 empty internal fsm queue due to inbound_DISCONNECT_REQUEST:
2023-03-08 10:28:23.967 - warn: openknx.0 (3126) [warn] 2023-03-08 09:28:23.967 connection timed out, retrying...
2023-03-08 10:28:41.969 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:28:44.971 - warn: openknx.0 (3126) [warn] 2023-03-08 09:28:44.971 connection timed out, retrying...
2023-03-08 10:28:44.974 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:28:44.976 - info: openknx.0 (3126) Connected!
2023-03-08 10:28:44.979 - info: openknx.0 (3126) Connected!
2023-03-08 10:30:46.170 - warn: openknx.0 (2311) Connection lost
2023-03-08 10:30:46.172 - warn: openknx.0 (2311) Could not perform strict object check of state openknx.0.info.connection: DB closed
2023-03-08 10:30:46.172 - warn: openknx.0 (2311) get state error: Connection is closed.
2023-03-08 10:30:49.171 - warn: openknx.0 (2311) [warn] 2023-03-08 09:30:49.171 connection timed out, retrying...
2023-03-08 10:30:52.172 - warn: openknx.0 (2311) [warn] 2023-03-08 09:30:52.172 connection timed out, retrying...
2023-03-08 10:31:11.099 - info: openknx.0 (3126) [info] 2023-03-08 09:31:11.099 empty internal fsm queue due to inbound_DISCONNECT_REQUEST:
2023-03-08 10:31:11.100 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:31:11.104 - info: openknx.0 (3126) Connected!
2023-03-08 10:31:45.981 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:31:45.982 - warn: openknx.0 (3126) timed out waiting for CONNECTIONSTATE_RESPONSE
2023-03-08 10:31:48.982 - warn: openknx.0 (3126) [warn] 2023-03-08 09:31:48.982 connection timed out, retrying...
2023-03-08 10:31:48.987 - info: openknx.0 (3126) Connected!
2023-03-08 10:34:49.994 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:34:49.995 - warn: openknx.0 (3126) timed out waiting for CONNECTIONSTATE_RESPONSE
2023-03-08 10:34:52.995 - warn: openknx.0 (3126) [warn] 2023-03-08 09:34:52.995 connection timed out, retrying...
2023-03-08 10:34:55.996 - warn: openknx.0 (3126) [warn] 2023-03-08 09:34:55.996 connection timed out, retrying...
2023-03-08 10:35:01.997 - warn: openknx.0 (3126) Connection lost
2023-03-08 10:35:02.003 - info: openknx.0 (3126) Connected!
2023-03-08 10:35:55.174 - warn: openknx.0 (2311) Connection lost
2023-03-08 10:35:55.175 - warn: openknx.0 (2311) Could not perform strict object check of state openknx.0.info.connection: DB closed
2023-03-08 10:35:55.176 - warn: openknx.0 (2311) get state error: Connection is closed.
2023-03-08 10:35:58.175 - warn: openknx.0 (2311) [warn] 2023-03-08 09:35:58.175 connection timed out, retrying...
2023-03-08 10:36:01.176 - warn: openknx.0 (2311) [warn] 2023-03-08 09:36:01.176 connection timed out, retrying...
                    K Offline
                    K Offline
                    killroy2
                    wrote on last edited by
                    #487

                    @123brokerei said in Test Adapter OpenKNX 0.2.x:

                    get state error: Connection is closed.

                    evtl hängt es mit dem js controller zusammen:
                    https://github.com/iobroker-community-adapters/ioBroker.ical/issues/214

                    T 123brokerei1 2 Replies Last reply
                    1
                    • K killroy2

                      @123brokerei said in Test Adapter OpenKNX 0.2.x:

                      get state error: Connection is closed.

                      evtl hängt es mit dem js controller zusammen:
                      https://github.com/iobroker-community-adapters/ioBroker.ical/issues/214

                      T Offline
                      T Offline
                      Tontechniker
                      wrote on last edited by
                      #488

                      @killroy2 Hallo! Habe Dir gerade eine Spende über Paypal geschickt!
                      Ich habe die 0.5.2 heute nochmal neu heruntergeladen. Ist es gewollt, dass alle Texte in der Instanz-Einstellung in Englisch sind, außer "IMPORT ETS XML UND SPEICHERN"? Nur eine "kleine Ungereimtheit"?!
                      Gruß
                      Hans

                      K 1 Reply Last reply
                      0
                      • T Tontechniker

                        @killroy2 Hallo! Habe Dir gerade eine Spende über Paypal geschickt!
                        Ich habe die 0.5.2 heute nochmal neu heruntergeladen. Ist es gewollt, dass alle Texte in der Instanz-Einstellung in Englisch sind, außer "IMPORT ETS XML UND SPEICHERN"? Nur eine "kleine Ungereimtheit"?!
                        Gruß
                        Hans

                        K Offline
                        K Offline
                        killroy2
                        wrote on last edited by
                        #489

                        @tontechniker Herzlichen Dank für deine Spende!
                        Ich mache gerade eine Überarbeitung vom Admin Menü, deswegen kann es sein dass die aktuellsten Quellen nicht mehr ganz ausgereift sind.

                        Die 0.5.2 Version ist jetzt ins stable Repository gewandert und wird demnächst für alle sichtbar sein.

                        1 Reply Last reply
                        1
                        • K killroy2

                          @123brokerei said in Test Adapter OpenKNX 0.2.x:

                          get state error: Connection is closed.

                          evtl hängt es mit dem js controller zusammen:
                          https://github.com/iobroker-community-adapters/ioBroker.ical/issues/214

                          123brokerei1 Offline
                          123brokerei1 Offline
                          123brokerei
                          wrote on last edited by 123brokerei
                          #490

                          @killroy2 ich weiß nicht. Die Meldung ist von 2021 und kam seither nicht mehr auf. Mein JS-Controller ist eigentlich aktuell. Mit node red (knx ultimate) bekomme ich eine stabile Tunnelverbindung hin. Dort kann ich den Tunnel direkt angeben. Geht das im Adapter auch irgendwie? Im Log wird als physikalische Adresse 1.1.1 angezeigt, was bei mir nicht passen würde. Würde sehr gerne im ioBroker bleiben und nicht zusätzlich node red verwenden müssen.

                          S 1 Reply Last reply
                          0
                          • 123brokerei1 123brokerei

                            @killroy2 ich weiß nicht. Die Meldung ist von 2021 und kam seither nicht mehr auf. Mein JS-Controller ist eigentlich aktuell. Mit node red (knx ultimate) bekomme ich eine stabile Tunnelverbindung hin. Dort kann ich den Tunnel direkt angeben. Geht das im Adapter auch irgendwie? Im Log wird als physikalische Adresse 1.1.1 angezeigt, was bei mir nicht passen würde. Würde sehr gerne im ioBroker bleiben und nicht zusätzlich node red verwenden müssen.

                            S Offline
                            S Offline
                            socke85
                            wrote on last edited by
                            #491

                            Ich habe heute nodejs und auch openkx geupdatet alles aktuell leider bekomme ich den Adapter nicht mehr zum laufen, habe auch schon ältere Versionen probiert.

                            Das log erzählt mir:

                            ost.Jarvis
2023-03-14 21:59:03.543	error	instance system.adapter.openknx.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.Jarvis
2023-03-14 21:59:03.543	error	Caught by controller[0]: }
host.Jarvis
2023-03-14 21:59:03.543	error	Caught by controller[0]: ]
host.Jarvis
2023-03-14 21:59:03.543	error	Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.openknx/main.js'
host.Jarvis
2023-03-14 21:59:03.543	error	Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.openknx/lib/knx/index.js',
host.Jarvis
2023-03-14 21:59:03.543	error	Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.openknx/lib/knx/src/Connection.js',
host.Jarvis
2023-03-14 21:59:03.543	error	Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.openknx/lib/knx/src/KnxProtocol.js',
host.Jarvis
2023-03-14 21:59:03.543	error	Caught by controller[0]: requireStack: [
host.Jarvis
2023-03-14 21:59:03.543	error	Caught by controller[0]: code: 'MODULE_NOT_FOUND',
host.Jarvis
2023-03-14 21:59:03.543	error	Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1057:19) {
host.Jarvis
2023-03-14 21:59:03.543	error	Caught by controller[0]: at Function.Module._load (node:internal/modules/cjs/loader:868:12)
host.Jarvis
2023-03-14 21:59:03.543	error	Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1033:32)
host.Jarvis
2023-03-14 21:59:03.543	error	Caught by controller[0]: at Object.Module._extensions..js (node:internal/modules/cjs/loader:1209:10)
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1155:14)
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.openknx/lib/knx/src/KnxProtocol.js:8:16)
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: at require (node:internal/modules/cjs/helpers:103:18)
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1057:19)
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: at Function.Module._load (node:internal/modules/cjs/loader:833:27)
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: at Function.Module._resolveFilename (node:internal/modules/cjs/loader:985:15)
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.openknx/main.js
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.openknx/lib/knx/index.js
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.openknx/lib/knx/src/Connection.js
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.openknx/lib/knx/src/KnxProtocol.js
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: Require stack:
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: Error: Cannot find module 'binary-parser'
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: ^
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: throw err;
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: node:internal/modules/cjs/loader:988
host.Jarvis
2023-03-14 21:58:57.808	error	instance system.adapter.openknx.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.Jarvis
2023-03-14 21:58:57.808	error	Caught by controller[0]: }
host.Jarvis
2023-03-14 21:58:57.808	error	Caught by controller[0]: ]
host.Jarvis
2023-03-14 21:58:57.807	error	Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.openknx/main.js'
host.Jarvis
2023-03-14 21:58:57.807	error	Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.openknx/lib/knx/index.js',
host.Jarvis
2023-03-14 21:58:57.807	error	Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.openknx/lib/knx/src/Connection.js',
host.Jarvis
2023-03-14 21:58:57.807	error	Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.openknx/lib/knx/src/KnxProtocol.js',
host.Jarvis
2023-03-14 21:58:57.807	error	Caught by controller[0]: requireStack: [

                            Habt ihr eine Idee woran es liegen kann?

                            F 1 Reply Last reply
                            0
                            • N Offline
                              N Offline
                              netfriend
                              wrote on last edited by
                              #492

                              Hallo,

                              ich habe meinen openKNX-Adapter in den letzten Tagen von 0.1.22 (die seit langer Zeit stabil lief) auf die aktuelle 0.5.2 aktualisiert.
                              Soweit hat alles gut funktioniert - herzlichen Dank an alle Beteiligten, vor allem @killroy2

                              Mir ist lediglich aufgefallen, dass nun Werte als Dezimaltrennzeichen ein Komma verwenden, vorher war es ein Punkt.
                              Ist das so gewollt? Kann man das irgendwo einstellen?

                              K andreaskosA 2 Replies Last reply
                              0
                              • N netfriend

                                Hallo,

                                ich habe meinen openKNX-Adapter in den letzten Tagen von 0.1.22 (die seit langer Zeit stabil lief) auf die aktuelle 0.5.2 aktualisiert.
                                Soweit hat alles gut funktioniert - herzlichen Dank an alle Beteiligten, vor allem @killroy2

                                Mir ist lediglich aufgefallen, dass nun Werte als Dezimaltrennzeichen ein Komma verwenden, vorher war es ein Punkt.
                                Ist das so gewollt? Kann man das irgendwo einstellen?

                                K Offline
                                K Offline
                                killroy2
                                wrote on last edited by
                                #493

                                @netfriend Sowas ist nicht bewusst eingebaut worden, kannst du ein Beispiel geben wo du sowas siehst?

                                T 1 Reply Last reply
                                1
                                • N Offline
                                  N Offline
                                  netfriend
                                  wrote on last edited by
                                  #494

                                  Ja, kann ich.

                                  z.B. DPT 9.001
                                  0.5.2
                                  5b659424-a587-4933-8f3d-321778850a0d-image.png
                                  01.22
                                  ef04d435-d252-44f4-80c3-8cabbc7ebaab-image.png

                                  Das selbe auch mit DPT9.005 oder DPT9.007 ...

                                  oder DPT14.076 bzw. DPT14
                                  e168a314-0746-490a-af4e-3d67c48aa882-image.png

                                  Kann es sein, dass das eine allgemeine Systemeinstellung ist? Ich frage, weil ich das ganze Raspi OS neu aufgesetzt habe.

                                  Ansonsten habe ich das selbe KNX-GA-Adressen.xml verwendet wie vorher auch.

                                  1 Reply Last reply
                                  0
                                  • N netfriend

                                    Hallo,

                                    ich habe meinen openKNX-Adapter in den letzten Tagen von 0.1.22 (die seit langer Zeit stabil lief) auf die aktuelle 0.5.2 aktualisiert.
                                    Soweit hat alles gut funktioniert - herzlichen Dank an alle Beteiligten, vor allem @killroy2

                                    Mir ist lediglich aufgefallen, dass nun Werte als Dezimaltrennzeichen ein Komma verwenden, vorher war es ein Punkt.
                                    Ist das so gewollt? Kann man das irgendwo einstellen?

                                    andreaskosA Offline
                                    andreaskosA Offline
                                    andreaskos
                                    wrote on last edited by
                                    #495

                                    @netfriend
                                    Das ist eine systemweite Einstellung. Siehe Screenshot:
                                    screenshot.jpg

                                    LG
                                    Andreas

                                    N 1 Reply Last reply
                                    1
                                    • andreaskosA andreaskos

                                      @netfriend
                                      Das ist eine systemweite Einstellung. Siehe Screenshot:
                                      screenshot.jpg

                                      LG
                                      Andreas

                                      N Offline
                                      N Offline
                                      netfriend
                                      wrote on last edited by
                                      #496

                                      @andreaskos

                                      Super, vielen Dank.
                                      Das war's - geändert und iobroker neugestartet und jetzt passt's wieder. ..und ich habe gesucht und gesucht und den Wald vor lauter Bäumen nicht gesehen.

                                      1 Reply Last reply
                                      0
                                      • S socke85

                                        Ich habe heute nodejs und auch openkx geupdatet alles aktuell leider bekomme ich den Adapter nicht mehr zum laufen, habe auch schon ältere Versionen probiert.

                                        Das log erzählt mir:

                                        ost.Jarvis
2023-03-14 21:59:03.543	error	instance system.adapter.openknx.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.Jarvis
2023-03-14 21:59:03.543	error	Caught by controller[0]: }
host.Jarvis
2023-03-14 21:59:03.543	error	Caught by controller[0]: ]
host.Jarvis
2023-03-14 21:59:03.543	error	Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.openknx/main.js'
host.Jarvis
2023-03-14 21:59:03.543	error	Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.openknx/lib/knx/index.js',
host.Jarvis
2023-03-14 21:59:03.543	error	Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.openknx/lib/knx/src/Connection.js',
host.Jarvis
2023-03-14 21:59:03.543	error	Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.openknx/lib/knx/src/KnxProtocol.js',
host.Jarvis
2023-03-14 21:59:03.543	error	Caught by controller[0]: requireStack: [
host.Jarvis
2023-03-14 21:59:03.543	error	Caught by controller[0]: code: 'MODULE_NOT_FOUND',
host.Jarvis
2023-03-14 21:59:03.543	error	Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1057:19) {
host.Jarvis
2023-03-14 21:59:03.543	error	Caught by controller[0]: at Function.Module._load (node:internal/modules/cjs/loader:868:12)
host.Jarvis
2023-03-14 21:59:03.543	error	Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1033:32)
host.Jarvis
2023-03-14 21:59:03.543	error	Caught by controller[0]: at Object.Module._extensions..js (node:internal/modules/cjs/loader:1209:10)
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1155:14)
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.openknx/lib/knx/src/KnxProtocol.js:8:16)
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: at require (node:internal/modules/cjs/helpers:103:18)
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1057:19)
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: at Function.Module._load (node:internal/modules/cjs/loader:833:27)
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: at Function.Module._resolveFilename (node:internal/modules/cjs/loader:985:15)
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.openknx/main.js
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.openknx/lib/knx/index.js
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.openknx/lib/knx/src/Connection.js
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.openknx/lib/knx/src/KnxProtocol.js
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: Require stack:
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: Error: Cannot find module 'binary-parser'
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: ^
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: throw err;
host.Jarvis
2023-03-14 21:59:03.542	error	Caught by controller[0]: node:internal/modules/cjs/loader:988
host.Jarvis
2023-03-14 21:58:57.808	error	instance system.adapter.openknx.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.Jarvis
2023-03-14 21:58:57.808	error	Caught by controller[0]: }
host.Jarvis
2023-03-14 21:58:57.808	error	Caught by controller[0]: ]
host.Jarvis
2023-03-14 21:58:57.807	error	Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.openknx/main.js'
host.Jarvis
2023-03-14 21:58:57.807	error	Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.openknx/lib/knx/index.js',
host.Jarvis
2023-03-14 21:58:57.807	error	Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.openknx/lib/knx/src/Connection.js',
host.Jarvis
2023-03-14 21:58:57.807	error	Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.openknx/lib/knx/src/KnxProtocol.js',
host.Jarvis
2023-03-14 21:58:57.807	error	Caught by controller[0]: requireStack: [

                                        Habt ihr eine Idee woran es liegen kann?

                                        F Offline
                                        F Offline
                                        Finkinho
                                        wrote on last edited by
                                        #497

                                        @socke85 ich habe den gleichen Fehler. Konntest du schon eine Lösung finden? Danke

                                        1 Reply Last reply
                                        0
                                        • K killroy2

                                          @netfriend Sowas ist nicht bewusst eingebaut worden, kannst du ein Beispiel geben wo du sowas siehst?

                                          T Offline
                                          T Offline
                                          Tontechniker
                                          wrote on last edited by Tontechniker
                                          #498

                                          @killroy2 Bei mir funktioniert die 0.5.3 seit ca. 3 Monaten (seit sie im GIT steht) ohne Beanstandung!
                                          Gruß
                                          Hans

                                          1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes

                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          604

                                          Online

                                          32.4k

                                          Users

                                          81.4k

                                          Topics

                                          1.3m

                                          Posts
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Login
                                          • Don't have an account? Register
                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Recent
                                          • Tags
                                          • Unread 0
                                          • Categories
                                          • Unreplied
                                          • Popular
                                          • GitHub
                                          • Docu
                                          • Hilfe