Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. RPC Adapter 1.14.27 logeinträge für CUXD RPC Instanz

    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

    UNSOLVED RPC Adapter 1.14.27 logeinträge für CUXD RPC Instanz

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

      Hi,

      habe gerade mal den RPC Adapter auf Version 1.14.27 gebracht.

      Jetzt macht die RPC Instanz für CUXD ständig einen neustart und im log kommen diese Einträge:

      2021-01-10 13:25:31.476  - info: host.iobroker instance system.adapter.hm-rpc.1 started with pid 23406
      2021-01-10 13:25:32.249  - info: hm-rpc.1 (23406) starting. Version 1.14.27 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v12.19.0, js-controller: 3.1.6
      2021-01-10 13:25:32.330  - info: hm-rpc.1 (23406) binrpc server is trying to listen on 192.168.178.18:8701
      2021-01-10 13:25:32.331  - info: hm-rpc.1 (23406) binrpc client is trying to connect to 192.168.178.8:8701/ with ["xmlrpc_bin://192.168.178.18:8701","iobroker:hm-rpc.1"]
      2021-01-10 13:25:32.376  - info: hm-rpc.1 (23406) binrpc -> listDevices 18
      2021-01-10 13:25:32.417  - info: hm-rpc.1 (23406) new CUxD devices/channels after filter: 0
      2021-01-10 13:25:32.417  - info: hm-rpc.1 (23406) Connected
      2021-01-10 13:27:02.430  - error: hm-rpc.1 (23406) uncaught exception: argument 'obj' must be type number, string, boolean or object
      2021-01-10 13:27:02.431  - error: hm-rpc.1 (23406) TypeError: argument 'obj' must be type number, string, boolean or object
          at Object.encodeData (/opt/iobroker/node_modules/binrpc/lib/protocol.js:69:19)
          at Object.encodeArray (/opt/iobroker/node_modules/binrpc/lib/protocol.js:156:44)
          at Object.encodeData (/opt/iobroker/node_modules/binrpc/lib/protocol.js:90:32)
          at Object.encodeResponse (/opt/iobroker/node_modules/binrpc/lib/protocol.js:52:25)
          at /opt/iobroker/node_modules/binrpc/lib/server.js:83:41
          at Server.<anonymous> (/opt/iobroker/node_modules/iobroker.hm-rpc/main.js:924:9)
          at Server.emit (events.js:314:20)
          at Server.handleCall (/opt/iobroker/node_modules/binrpc/lib/server.js:82:24)
          at Socket.<anonymous> (/opt/iobroker/node_modules/binrpc/lib/server.js:59:22)
          at Socket.emit (events.js:314:20)
      2021-01-10 13:27:02.432  - info: hm-rpc.1 (23406) binrpc -> 192.168.178.8:8701/ init ["xmlrpc_bin://192.168.178.18:8701",""]
      2021-01-10 13:27:02.435  - info: hm-rpc.1 (23406) Disconnected
      2021-01-10 13:27:02.441  - info: hm-rpc.1 (23406) terminating
      2021-01-10 13:27:02.442  - info: hm-rpc.1 (23406) Terminated (NO_ERROR): Without reason
      2021-01-10 13:27:02.964  - info: host.iobroker instance system.adapter.hm-rpc.1 terminated with code 0 (NO_ERROR)
      

      Liegt das an meiner Config oder ist das ein Bug im Adapter?

      EDIT: Gibt auch schon ein issue von einem anderen User dazu: Issue

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

      Support us

      ioBroker
      Community Adapters
      Donate

      632
      Online

      31.9k
      Users

      80.1k
      Topics

      1.3m
      Posts

      cuxd error rpc upgrade
      1
      1
      60
      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