Navigation

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

    NEWS

    • Neues Video "KI im Smart Home" - ioBroker plus n8n

    • Neues Video über Aliase, virtuelle Geräte und Kategorien

    • Wir empfehlen: Node.js 22.x

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

    DreDaPro

    @DreDaPro

    0
    Reputation
    7
    Profile views
    2
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    DreDaPro Follow

    Latest posts made by DreDaPro

    • RE: Loxone Instanz stützt bei der Verbindung ab

      @thomas-braun said in Loxone Instanz stützt bei der Verbindung ab:

      Warum fischst du den Adapter aus dem github und installierst das nicht ordentlich aus einem Repo?

      Hi Thomas,

      danke für deine Antwort.
      natürlich habe ich es zuerst aus dem Repo genommen. Hab versucht die Instanzen neu zu installieren oder den ganzen Adapter neu. Am Ende hab ich es versucht schon von Github aus.... aber da genau das gleiche..

      posted in ioBroker Allgemein
      DreDaPro
      DreDaPro
    • Loxone Instanz stützt bei der Verbindung ab

      bei einer neuen Installation von IoBroker stürzt die Loxone Instanz bei der Verbindung mit Loxone ab.

      Plattform: linux
      Betriebssystem: linux
      Architektur: x64
      CPUs: 2
      Geschwindigkeit: 2096 MHz
      Modell: AMD Opteron 63xx class CPU
      RAM: 1.9 GB
      System-Betriebszeit: 22:34:13
      Node.js: v16.19.0
      time: 1675192113721
      timeOffset: -60
      Adapter-Anzahl: 457
      NPM: v8.19.3
      Datenträgergröße: 490.6 GB
      Freier Festplattenspeicher: 474.8 GB
      Betriebszeit: 00:01:34
      Aktive Instanzen: 10
      Pfad: /opt/iobroker/
      aktiv:

      host.IoBroker
      2023-01-31 20:08:31.193	error	instance system.adapter.loxone.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
      host.IoBroker
      2023-01-31 20:08:31.193	error	Caught by controller[2]: at processTicksAndRejections (node:internal/process/task_queues:78:11)
      host.IoBroker
      2023-01-31 20:08:31.193	error	Caught by controller[2]: at flush (/opt/iobroker/node_modules/q/q.js:125:13)
      host.IoBroker
      2023-01-31 20:08:31.193	error	Caught by controller[2]: at runSingle (/opt/iobroker/node_modules/q/q.js:137:13)
      host.IoBroker
      2023-01-31 20:08:31.193	error	Caught by controller[2]: at /opt/iobroker/node_modules/q/q.js:624:44
      host.IoBroker
      2023-01-31 20:08:31.192	error	Caught by controller[2]: at Promise.promise.promiseDispatch (/opt/iobroker/node_modules/q/q.js:808:41)
      host.IoBroker
      2023-01-31 20:08:31.192	error	Caught by controller[2]: at Promise.when (/opt/iobroker/node_modules/q/q.js:1142:31)
      host.IoBroker
      2023-01-31 20:08:31.192	error	Caught by controller[2]: at /opt/iobroker/node_modules/q/q.js:890:30
      host.IoBroker
      2023-01-31 20:08:31.192	error	Caught by controller[2]: at _rejected (/opt/iobroker/node_modules/q/q.js:864:24)
      host.IoBroker
      2023-01-31 20:08:31.192	error	Caught by controller[2]: at _handleBadAuthResponse (/opt/iobroker/node_modules/lxcommunicator/modules/WebSocket.js:336:14)
      host.IoBroker
      2023-01-31 20:08:31.192	error	Caught by controller[2]: TypeError: Cannot read properties of undefined (reading '_setAuthenticating')
      host.IoBroker
      2023-01-31 20:08:31.192	error	Caught by controller[1]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
      host.IoBroker
      2023-01-31 20:08:31.191	error	Caught by controller[0]: WebSocket: socket failed! WS Close Code: 1006
      
      loxone.0
      2023-01-31 20:08:30.627	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
      
      loxone.0
      2023-01-31 20:08:30.625	info	terminating
      
      loxone.0
      2023-01-31 20:08:30.600	error	Cannot read properties of undefined (reading '_setAuthenticating')
      
      loxone.0
      2023-01-31 20:08:30.600	error	TypeError: Cannot read properties of undefined (reading '_setAuthenticating') at _handleBadAuthResponse (/opt/iobroker/node_modules/lxcommunicator/modules/WebSocket.js:336:14) at _rejected (/opt/iobroker/node_modules/q/q.js:864:24) at /opt/iobroker/node_modules/q/q.js:890:30 at Promise.when (/opt/iobroker/node_modules/q/q.js:1142:31) at Promise.promise.promiseDispatch (/opt/iobroker/node_modules/q/q.js:808:41) at /opt/iobroker/node_modules/q/q.js:624:44 at runSingle (/opt/iobroker/node_modules/q/q.js:137:13) at flush (/opt/iobroker/node_modules/q/q.js:125:13) at processTicksAndRejections (node:internal/process/task_queues:78:11)
      
      loxone.0
      2023-01-31 20:08:30.599	error	unhandled promise rejection: Cannot read properties of undefined (reading '_setAuthenticating')
      
      loxone.0
      2023-01-31 20:08:30.598	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      
      loxone.0
      2023-01-31 20:08:30.588	error	Couldn't open socket
      
      loxone.0
      2023-01-31 20:08:30.431	info	Trying to connect
      
      loxone.0
      2023-01-31 20:08:30.344	info	starting. Version 3.0.0 (non-npm: UncleSamSwiss/ioBroker.loxone#0d354f53ef9516762a6f8af492e625be8bff309d) in /opt/iobroker/node_modules/iobroker.loxone, node: v16.19.0, js-controller: 4.0.24
      
      

      MOD EDIT: LOG IN CODE TAGS </> GESETZT

      posted in ioBroker Allgemein
      DreDaPro
      DreDaPro
    Community
    Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
    The ioBroker Community 2014-2023
    logo