@eisbaeeer
Ich finde das ein sehr schönes Projekt. Woher hast du das Gehäuse? Und da müsste ja dann eigentlich noch Platz für einen Voc Sensor sein, oder?

Hallo,

vor einigen Jahren habe ich hier mit Hilfe des Forums, das Dahua Event Script in ioBroker zum Laufen gebracht sowie ein Blockly geschrieben, dass mir beim Klingeln ein Bild verschickt. Das hat bis vor kurzem (10.3) auch hervorragend funktioniert. Ohne dass ich bewusst was geändert habe, kommt das Bild mittlerweile mit knapp 2minuten Verzögerung via Telegram an, obwohl das Log mir sagt, dass das Bild sofort weggeschickt wurde.

Anbei erstmal das Script

const DigestFetch = require('digest-fetch');
const net = require('net');
const fs = require('fs');
const path = require('path');
const md5 = require('md5');
const mqtt = require('mqtt');

/**
* Class to abstract a dahua doorbell.
*
* On instantiation it automatically connects with the doorbell, logs in and
* subscribes to all events.
*
* When an event is received, it forwards it to the MQTT broker so other systems
* can received those events. This behavior is very generic, users need to listen
* to those MQTT messages and create their own integrations using something like
* node-red for instance.
*
* In time this could be used to create a more user-friendly integration in home assistant,
* but a doorbell is a complicated device and I don't know enough yet to decide how such
* integration would look.
*/

class DahuaVTO {
  deviceType;
  serialNumber;

  /**
   * {Number} requestId
   *
   * Our Request / Response ID that must be in all requests and initated by us.
   * This number auto-increments every time we send a message. Once we've logged in, every
   * response contains the request id of which it's a response of, se it could be used to
   * match responses with requests.
   *
   * I haven't bothered to do so because ,for what I saw, we only care about response order
   * for the initial setup, and we do that on request at a time.
   *
   * If we ever make requests in parallel and we need to associate response to each request,
   * we could use this. For not, it's just an auto-incremental number.
   * */

  requestId = 0;

  // Session ID will be returned after successful login
  /**
   * {Number} sessionId
   *
   * When we try to log in on the doorbell we get a sessionId. From that point on every message
   * we send over the socket needs to have include the sessionID for the doorbell to recognize us.
   */
  sessionId = 0;

  // Will be set after the login, but we initialize to 60s because it's a reasonable default
  /**
   * {Number} keepAliveInterval
   *
   * The number of seconds we have to space our keepAlive messages so the doorbell doesn't close
   * the connection.
   */
  keepAliveInterval = 60;

  /**
   * The ID returned by the `setInterval` call.
   * We keep a reference in case we want to cancel it (maybe in case of failure?)
   */
  _keepAliveTimer;

  /**
   * TCP socket to communicate with the doorbell external unit.
   */
  doorbellSocket;

  /**
   * MQTT client to publish (and maybe receive) messages.
   */
  mqttClient;

  constructor() {
    this.dahua_host = "192.168.178.10";
    this.dahua_username = "admin";
    this.dahua_password = "password";
    this.mqtt_broker_host = "192.168.x.y";
    this.mqtt_broker_port = "1883";
    this.mqtt_broker_username = "admin";
    this.mqtt_broker_password = "admin";
    this.mqtt_broker_topic_prefix = "DahuaVTO";
    this.digestClient =  new DigestFetch(
      this.dahua_username,
      this.dahua_password
    );

    this.getDeviceDetails().then(({ deviceType, serialNumber }) => {
      this.deviceType = deviceType;
      this.serialNumber = serialNumber;
      this.start();
    });
  }

  /**
   * Starts the app by:
   *    - Opening a TCP socket to the doorbell
   *    - Connecting to the MQTT broker
   *    - Authenticating with the doorbell and subscribing to events.
   */
  start() {
    this.setupDoorbellSocket();
    this.setupMQTT();
    this.initLogin();
  }

  /**
   * Makes a request to the doorbell using digest auth to retrieve the device's information.
   *
   * The information is returned in plain text (not JSON) that we have to parse.
   * For now I think we only care about device type and serial number, which can be
   * used to disambiguate in case we have more than one doorbell.
   */
  async getDeviceDetails() {
    return this.digestClient
      .fetch(
        `http://${this.dahua_host}/cgi-bin/magicBox.cgi?action=getSystemInfo`
      )
      .then((r) => r.text())
      .then((text) => {
        const deviceDetails = text
          .trim()
          .split('\n')
          .reduce((obj, str) => {
            const [key, val] = str.split('=');
            obj[key] = val.trim();
            return obj;
          }, {});
        return deviceDetails;
      });
  }

  /**
   * Saves a snapshot of the doorbells image into the given directory (defaults to /tmp/).
   *
   * By default the file is named with a simple timestamp of the current time (YYYY-MM-DD-H-M-S.jpg)
   *
   */
  saveSnapshot(p = '/tmp/') {
    let now = new Date();
    let dateStr = `${now.getFullYear()}-${
      now.getMonth() + 1
    }-${now.getDate()}-${now.getHours()}-${now.getMinutes()}-${now.getSeconds()}`;
    let destination = path.join(p, `DoorBell_${dateStr}.jpg`);
    this.digestClient
      .fetch(`http://${this.dahua_host}/cgi-bin/snapshot.cgi`)
      .then((r) => {
        return r.buffer();
      })
      .then((buf) => {
        fs.writeFile(destination, buf, 'binary', function (err) {
          if (err) {
            log('Error saving snapshot to disk', err);
          } else {
            log('Snapshot saved');
          }
        });
      });
  }

  /**
   * Creates the TCP socket connection with the doorbell on port 5000.
   *
   * Setups the listener for when we receive data over that socket
   *
   * Also setups other listeners for logging purposes mostly.
   *
   * If something goes wrong, we close everything and try to start over again.
   */
  setupDoorbellSocket() {
    let socket = new net.Socket({ readable: true, writable: true });
    socket.on('end', function () {
      log('Doorbell socket ended');
    });
    socket.on('close', function () {
     log('Doorbell socket closed');
      clearInterval(this._keepAliveTimer);
    });
    socket.on('data', this.receive.bind(this));
    socket.on('error', function (e) {
      log('Doorbell socket error', e);
      this.doorbellSocket.destroy(); // destroy the socket
      this.mqttClient.end(true); // End the mqtt connection right away.
      clearInterval(this._keepAliveTimer); // Stop sending keepalive requests
      this.start(); // Start over again.
    });
    this.doorbellSocket = socket.connect({ port: 5000, host: this.dahua_host });
  }

  /**
   * Configure an initialize the MQTT client.
   *
   * It configures the "Last Will and Testament" (LWT), which is the message send to MQTT
   * if this client gets disconnected in an ungraceful way (e.g. a fatal error).
   *
   * It also adds listeners that right now are only used for logging.
   */
  setupMQTT() {
    this.mqttClient = mqtt.connect({
      host: this.mqtt_broker_host,
      port: this.mqtt_broker_port,
      username: this.mqtt_broker_username,
      password: this.mqtt_broker_password,
      will: {
        topic: `${this.mqtt_broker_topic_prefix}/lwt`,
        payload: 'connected',
        qos: 1,
      },
    });
    this.mqttClient.on('disconnect', function (packet) {
      log('MQTTDisconnect', packet);
    });
    this.mqttClient.on('message', function (topic, message, packet) {
      log('MQTTMessage', { topic, message, packet });
    });
  }

  /**
   * Publishes to MQTT an event with the given name and payload.
   * @param {string} name
   * @param {object} payload
   */
  publishToMQTT(name, payload) {
    let message = JSON.stringify(payload);
    this.mqttClient.publish(
      `${this.mqtt_broker_topic_prefix}/${name}/Event`,
      message
    );
  }

  /**
   * Sends a message with the given data to the doorbell's outside unit using the TCP socket.
   * @param {string} data
   *
   * This is a fairly low level way of communication, so let's dive in.
   *
   * We write binary to the socket, so we have to use buffers.
   *
   * The first 32 bytes of the message are the header.
   * After the header we concat the actual message, which is a JSON string.
   * The header has some bits that are fixed and others that are the length of the message that will
   * come after.
   *
   * I didn't reverse-engineered this myself but it works. Take it as gospel as I did.
   */
  send(data) {
    let json = JSON.stringify(data);
    let buf = Buffer.alloc(32);
    let offset = buf.writeUInt32BE(0x20000000);
    offset = buf.writeUInt32BE(0x44484950, offset);
    offset = buf.writeDoubleBE(0, offset);
    offset = buf.writeUInt32LE(json.length, offset);
    offset = buf.writeUInt32LE(0, offset);
    offset = buf.writeUInt32LE(json.length, offset);
    offset = buf.writeUInt32LE(0, offset);
    buf = Buffer.concat([buf, Buffer.from(json)]);
    this.requestId += 1;
    this.doorbellSocket.write(buf);
  }

  /**
   * Handles received messages from the TCP socket.
   * @param {Buffer} buf
   *
   * The received messages are binary. Once discarded the first 32 bytes (the header),
   * the rest of the message is parsed as as a JSON string.
   *
   * The header contains the length of the received response in bytes 16..20 and the expected
   * length of the response in bytes 24..28 in case we need it, but I haven't found a
   * reason to. Perhaps responses might be sent in several chunks? So far it doesn't seem to be
   * the case.
   *
   * Since we always make requests in the exact same order, we know the first two responses are
   * for the authentication.
   * Subsequent responses can be either events or keepalive responses.
   */
receive(buf) {
  let str = buf.slice(32).toString();
    try {
      let obj = JSON.parse(str);
    if (this.requestId === 1) {
      this.handleFirstLoginPayload(obj);
    } else if (this.requestId === 2) {
      this.handleSecondLoginPayload(obj);
    } else if (obj.method === 'client.notifyEventStream') {
      this.handleEvents(obj.params.eventList);
    } else {
      this.handleGenericPayload(obj);
    }
  } catch (e) {
    log("Failed to parse incoming message", e);
  }
}

  /**
   * Sends the initial login request.
   * Note that does not include any password.
   * The response to this request will be negative but that is expected, it will contain the
   * necessary information to login.
   */
  initLogin() {
    this.send({
      id: 10000,
      magic: '0x1234',
      method: 'global.login',
      params: {
        clientType: '',
        ipAddr: '(null)',
        loginType: 'Direct',
        password: '',
        userName: this.dahua_username,
      },
      session: 0,
    });
  }

  /**
   * Handles the response to the initial login request.
   *
   * The response contains a session ID, a realm and a random, which in combination with
   * the username and the password are used to generate an MD5 password that is used
   * for logging in.
   *
   * @param {object} payload
   */
  handleFirstLoginPayload({ session, params: { random, realm } }) {
    this.sessionId = session;
    let randomHash = this.genMD5Hash(random, realm);
    this.send({
      id: 10000, // I assume this ID a high number just because we have to send something.
      magic: '0x1234', // No idea what this is
      method: 'global.login',
      session: this.sessionId,
      params: {
        userName: this.dahua_username,
        password: randomHash,
        clientType: '',
        ipAddr: '(null)',
        loginType: 'Direct',
        authorityType: 'Default',
      },
    });
  }

  /**
   * Handles the response to the second (and last) response to login request.
   *
   * If successful, any subsequent message that includes the session id will be accepted for
   * as long as the socket is not closed.
   *
   * To prevent the socket from closing we send a keepalive message every so often.
   *
   * Also now that we're authenticated we subscribe to all events fired by the doorbell.
   */
  handleSecondLoginPayload(obj) {
    if (obj.result) {
      log('Logging to Dahua Doorbell successful');
      this.keepAliveInterval = obj.params.keepAliveInterval - 5;
      this.attachEventManager();
      this.keepConnectionAlive();
    } else {
      log('Failed to login. Response was: ', obj);
    }
  }

  /**
   * Handles any response not handled by any other method. I believe only keepalive responses
   * will end up here, but added some logging just in case.
   *
   * For now keepalive events are published to MQTT, but I don't see a good reason for that.
   */
  handleGenericPayload(obj) {
    if (
      obj.result === true &&
      obj.params &&
      Object.hasOwnProperty.call(obj.params, 'timeout')
    ) {
      log('Publish KeepAlive event');
      this.publishToMQTT('keepAlive', {
        deviceType: this.deviceType,
        serialNumber: this.serialNumber,
      });
    } else {
      log(
        'handleGenericPayload# Cannot handle received payload',
        obj
      );
    }
  }

  /**
   * Generates a MD5 digest of the username, password, realms and random to send as
   * password when logging in.
   * @param {*} random
   * @param {*} realm
   */
  genMD5Hash(random, realm) {
    const base_credentials = `${this.dahua_username}:${realm}:${this.dahua_password}`;
    const pwddb_hash = md5(base_credentials).toUpperCase();
    const base_pass = `${this.dahua_username}:${random}:${pwddb_hash}`;
    return md5(base_pass).toUpperCase();
  }

  /**
   * Sends the message to subscribe to all dorbell events.
   */
  attachEventManager() {
    this.send({
      id: this.requestId,
      magic: '0x1234',
      method: 'eventManager.attach',
      params: {
        codes: ['All'],
      },
      session: this.sessionId,
    });
  }

  /**
   * Handles the events sent by the doorbell.
   *
   * It just publishes those events along with some information of the device firing them
   * to MQTT
   */
  handleEvents(events) {
    events.forEach((event) => {
      log(`Publish event ${event.Code} to MQTT`);
      this.publishToMQTT(event.Code, {
        Action: event.eventAction,
        Data: event.Data,
        deviceType: this.deviceType,
        serialNumber: this.serialNumber,
      });
    });
  }

  /**
   * Sets up a function to be called periodically to keep the socket open by sending
   * keepalive messages.
   * @param {Number} delay (in seconds)
   */
  keepConnectionAlive(delay) {
    this._keepAliveTimer = setInterval(() => {
      let keepAlivePayload = {
        method: 'global.keepAlive',
        magic: '0x1234',
        params: {
          timeout: delay,
          active: true,
        },
        id: this.requestId,
        session: this.sessionId,
      };

      this.send(keepAlivePayload);
    }, this.keepAliveInterval * 1000);
  }

  /**
   * Remotely triggers the relay 1 (e.g. to open an electric gate).
   *
   * In my VTO 2202 F this also triggers the voice announcing the the door has been opened.
   */
  openDoor() {
    return this.digestClient
      .fetch(
        `http://${this.dahua_host}/cgi-bin/accessControl.cgi?action=openDoor&channel=1&UserID=101&Type=Remote`
      )
      .then((r) => {
        if (r.ok) {
          log('Door relay triggered');
        } else {
          log('Error triggering the door relay', e);
        }
      })
      .catch(e => log('Connection error triggering the door relay',e));
  }

  // requestMissedCallsLog() {
  //   this.send({
  //     id: this.requestId,
  //     magic: '0x1234',
  //     method: 'RecordFinder.factory.create',
  //     params: {
  //       name: 'VideoTalkMissedLog',
  //     },
  //     session: this.sessionId,
  //   });
  // }

  // requestMissedCallsLog2(findToken) {
  //   this.send({
  //     id: this.requestId,
  //     magic: '0x1234',
  //     method: 'RecordFinder.startFind',
  //     object: findToken,
  //     params: { condition: null },
  //     session: this.sessionId,
  //   });
  // }

  // requestMissedCallsLog3(findToken) {
  //   this.send({
  //     id: this.requestId,
  //     magic: '0x1234',
  //     method: 'RecordFinder.doFind',
  //     object: findToken,
  //     params: { count: 3 }, // Number of calls to show
  //     session: this.sessionId,
  //   });
  // }
};

exports.default = DahuaVTO;

new DahuaVTO();

dann das blockly

Spoiler

Hier die fehlerhaften Logs und was auch beim klingeln kommt:

2025-03-13 18:21:33.335 - error: javascript.0 (26445) script.js.common.Dahua.DahuaEvent: SyntaxError: Unexpected non-whitespace character after JSON at position 238
2025-03-13 18:21:33.336 - error: javascript.0 (26445) at JSON.parse ()
2025-03-13 18:21:33.336 - error: javascript.0 (26445) at DahuaVTO.receive (script.js.common.Dahua.DahuaEvent:285:20)
2025-03-13 18:21:33.336 - error: javascript.0 (26445) at Socket.emit (node:events:518:28)
2025-03-13 18:21:33.336 - error: javascript.0 (26445) at Socket.emit (node:domain:489:12)
2025-03-13 18:21:33.336 - error: javascript.0 (26445) at addChunk (node:internal/streams/readable:561:12)
2025-03-13 18:21:33.336 - error: javascript.0 (26445) at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
2025-03-13 18:21:33.336 - error: javascript.0 (26445) at Socket.Readable.push (node:internal/streams/readable:392:5)
2025-03-13 18:21:33.336 - error: javascript.0 (26445) at TCP.onStreamRead (node:internal/stream_base_commons:191:23)
2025-03-13 18:21:33.537 - error: host.iobroker Caught by controller[0]: SyntaxError: Unexpected non-whitespace character after JSON at position 238
2025-03-13 18:21:33.538 - error: host.iobroker Caught by controller[0]: at JSON.parse ()
2025-03-13 18:21:33.538 - error: host.iobroker Caught by controller[0]: at DahuaVTO.receive (script.js.common.Dahua.DahuaEvent:286:20)
2025-03-13 18:21:33.538 - error: host.iobroker Caught by controller[0]: at Socket.emit (node:events:518:28)
2025-03-13 18:21:33.538 - error: host.iobroker Caught by controller[0]: at Socket.emit (node:domain:489:12)
2025-03-13 18:21:33.538 - error: host.iobroker Caught by controller[0]: at addChunk (node:internal/streams/readable:561:12)
2025-03-13 18:21:33.538 - error: host.iobroker Caught by controller[0]: at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
2025-03-13 18:21:33.538 - error: host.iobroker Caught by controller[0]: at Socket.Readable.push (node:internal/streams/readable:392:5)
2025-03-13 18:21:33.538 - error: host.iobroker Caught by controller[0]: at TCP.onStreamRead (node:internal/stream_base_commons:191:23)
2025-03-13 18:21:33.538 - error: host.iobroker instance system.adapter.javascript.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
2025-03-13 18:21:33.538 - info: host.iobroker Restart adapter system.adapter.javascript.0 because enabled

script.js.common.Dahua.DahuaEvent: clearInterval() => not found
script.js.common.Dahua.DahuaEvent: Unknown severity level "[object Object]" by log of [handleGenericPayload# Cannot handle received payload]

wie beschrieben, ich kann mich nicht erinnern, dass ich was in den vergangenen 10 Tagen geändert hätte, aber es nervt halt, dass das Bild zu spät ankommt.

Bin für jede Idee zu haben....

@Glasfaser
habe jetzt die Beta installiert und auch die Befehle aus dem Thread hier wiederholt. Leider lässt sich die Admin Instanz immer noch nicht aktivieren.
Ich habe mal iobroker via SSH komplett neu aufgesetzt, da funktionierte dann die weboberfläche. Ich vermute mal, dass irgendeine Datei zerschossen ist.

sehe gerade in dem beta container eine neue Fehlermeldung

2023/12/22 12:53:53	stdout	}
2023/12/22 12:53:53	stdout	  port: 42010
2023/12/22 12:53:53	stdout	  address: '192.168.178.52',
2023/12/22 12:53:53	stdout	  syscall: 'listen',
2023/12/22 12:53:53	stdout	  errno: -99,
2023/12/22 12:53:53	stdout	  code: 'EADDRNOTAVAIL',
2023/12/22 12:53:53	stdout	    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
2023/12/22 12:53:53	stdout	    at doListen (node:net:2014:7)
2023/12/22 12:53:53	stdout	    at listenInCluster (node:net:1865:12)
2023/12/22 12:53:53	stdout	    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
2023/12/22 12:53:53	stdout	Error: listen EADDRNOTAVAIL: address not available 192.168.178.52:42010
2023/12/22 12:53:21	stdout	

Edit: habe jetzt einen neuen Container mit latest erzeugt und einen neuen Pfad hergestellt. Backup vom Novmeber konnte ich einspielen. Interessanterweise vom Dezember nicht (hatte 3 und 12.12 getestet). Da ist der Restore-vorgang abgebrochen.

@glasfaser

hmm ich frage mich eher, was dazu geführt hat, dass es zerschossen ist?!
Ich versuche morgen mal die beta...

@glasfaser

das geht nicht:

The execution of this command is blocked as your ioBroker is running inside a Doc
ker container!                                                                   
For more details see ioBroker Docker image docs (https://docs.buanet.de/iobroker-
docker-image/docs/) or use the maintenance script 'maintenance --help'.          

@glasfaser

status

root@iobroker:/opt/iobroker# iobroker status                                     
iobroker is running on this host.                                                
                                                                                 
                                                                                 
Objects type: jsonl                                                              
States  type: jsonl

diag

Skript v.2023-10-10

*** BASE SYSTEM ***
Hardware Vendor : Synology
Kernel          : x86_64
Userland        : amd64
Docker          : v9.0.1
Virtualization  : Docker
Kernel          : x86_64
Userland        : amd64

Systemuptime and Load:
 23:32:02 up 11:12,  0 user,  load average: 3.03, 4.81, 5.30
CPU threads: 2


*** Time and Time Zones ***
Thu Dec 21 22:32:02 UTC 2023
Thu Dec 21 23:32:02 CET 2023
CET +0100
Etc/UTC

*** User and Groups ***
root
/root
root

*** X-Server-Setup ***
X-Server:       false
Desktop:
Terminal:


*** MEMORY ***
               total        used        free      shared  buff/cache   available
Mem:             18G        3.9G        285M        646M         15G         14G
Swap:            13G         70M         13G
Total:           32G        3.9G         13G

        17836 M total memory
         3700 M used memory
         7854 M active memory
         8766 M inactive memory
          272 M free memory
           49 M buffer memory
        14766 M swap cache
        12749 M total swap
           66 M used swap
        12683 M free swap

*** FILESYSTEM ***
Filesystem     Type   Size  Used Avail Use% Mounted on
/dev/md2       btrfs  3.5T  1.8T  1.8T  51% /
tmpfs          tmpfs   64M     0   64M   0% /dev
tmpfs          tmpfs  8.8G     0  8.8G   0% /sys/fs/cgroup
shm            tmpfs   64M     0   64M   0% /dev/shm
/dev/md2       btrfs  3.5T  1.8T  1.8T  51% /opt/iobroker
/dev/md2       btrfs  3.5T  1.8T  1.8T  51% /etc/hosts
tmpfs          tmpfs  8.8G     0  8.8G   0% /proc/acpi
tmpfs          tmpfs  8.8G     0  8.8G   0% /proc/scsi
tmpfs          tmpfs  8.8G     0  8.8G   0% /sys/firmware

Messages concerning ext4 filesystem in dmesg:
sudo: unable to resolve host iobroker: Name or service not known

Show mounted filesystems \(real ones only\):
TARGET             SOURCE
                                                   FSTYPE OPTIONS
/                  /dev/md2[/@syno/@docker/btrfs/subvolumes/769fca532000df7bd06a6
b2495878a45410548fa1233ac9d0718b1a3aabf31d4]       btrfs  rw,nodev,relatime,ssd,s
ynoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvoli
d=2143,subvol=/@syno/@docker/btrfs/subvolumes/769fca532000df7bd06a6b2495878a45410
548fa1233ac9d0718b1a3aabf31d4
|-/opt/iobroker    /dev/md2[/@syno/docker/iobroker]
                                                   btrfs  rw,nodev,relatime,ssd,s
ynoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvoli
d=260,subvol=/@syno/docker
|-/etc/resolv.conf /dev/md2[/@syno/@docker/containers/bff6048aa927721b34e64ac2831
6ab5dd0572f9b10fecd32a7151e936c569f30/resolv.conf] btrfs  rw,nodev,relatime,ssd,s
ynoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvoli
d=257,subvol=/@syno
|-/etc/hostname    /dev/md2[/@syno/@docker/containers/bff6048aa927721b34e64ac2831
6ab5dd0572f9b10fecd32a7151e936c569f30/hostname]    btrfs  rw,nodev,relatime,ssd,s
ynoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvoli
d=257,subvol=/@syno
`-/etc/hosts       /dev/md2[/@syno/@docker/containers/bff6048aa927721b34e64ac2831
6ab5dd0572f9b10fecd32a7151e936c569f30/hosts]       btrfs  rw,nodev,relatime,ssd,s
ynoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,syno_allocator,subvoli
d=257,subvol=/@syno

Files in neuralgic directories:

/var:
sudo: unable to resolve host iobroker: Name or service not known
34M     /var/
32M     /var/lib
19M     /var/lib/apt/lists
19M     /var/lib/apt
13M     /var/lib/dpkg



/opt/iobroker/backups:
522M    /opt/iobroker/backups/

/opt/iobroker/iobroker-data:
428M    /opt/iobroker/iobroker-data/
226M    /opt/iobroker/iobroker-data/files
142M    /opt/iobroker/iobroker-data/backup-objects
67M     /opt/iobroker/iobroker-data/files/javascript.admin
48M     /opt/iobroker/iobroker-data/files/javascript.admin/static

The five largest files in iobroker-data are:
33M     /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.1797d034.js.ma
p
21M     /opt/iobroker/iobroker-data/files/web.admin/static/js/main.aaea95f8.js.ma
p
20M     /opt/iobroker/iobroker-data/objects.jsonl
16M     /opt/iobroker/iobroker-data/states.jsonl
12M     /opt/iobroker/iobroker-data/objects.json.migrated

USB-Devices by-id:
USB-Sticks -  Avoid direct links to /dev/* in your adapter setups, please always
prefer the links 'by-id':

find: '/dev/serial/by-id/': No such file or directory

*** NodeJS-Installation ***

/usr/bin/nodejs         v18.19.0
/usr/bin/node           v18.19.0
/usr/bin/npm            10.2.3
/usr/bin/npx            10.2.3
/usr/bin/corepack       0.22.0


nodejs:
  Installed: 18.19.0-1nodesource1
  Candidate: 18.19.0-1nodesource1
  Version table:
 *** 18.19.0-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
        100 /var/lib/dpkg/status
     18.18.2-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.18.1-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.18.0-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.17.1-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.17.0-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.16.1-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.16.0-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.15.0-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.14.2-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.14.1-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.14.0-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.13.0+dfsg1-1 500
        500 http://deb.debian.org/debian bookworm/main amd64 Packages
     18.13.0-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.12.0-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.11.0-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.10.0-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.9.1-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.9.0-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.8.0-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.7.0-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.6.0-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.5.0-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.4.0-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.3.0-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.2.0-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.1.0-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
     18.0.0-1nodesource1 500
        500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages

Temp directories causing npm8 problem: 0
No problems detected

Errors in npm tree:

*** ioBroker-Installation ***

ioBroker Status
iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Core adapters versions
js-controller:  5.0.17
admin:          6.12.0
javascript:     7.1.6

Adapters from github:   0

Adapter State
  system.adapter.admin.0                  : admin                 : iobroker
                            -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.alexa2.0                 : alexa2                : iobroker
                            -  enabled
+ system.adapter.backitup.0               : backitup              : iobroker
                            -  enabled
+ system.adapter.cloud.0                  : cloud                 : iobroker
                            -  enabled
+ system.adapter.discovery.0              : discovery             : iobroker
                            -  enabled
  system.adapter.ecovacs-deebot.0         : ecovacs-deebot        : iobroker
                            - disabled
  system.adapter.flot.0                   : flot                  : iobroker
                            -  enabled
+ system.adapter.gruenbeck.0              : gruenbeck             : iobroker
                            -  enabled
+ system.adapter.hm-rega.0                : hm-rega               : iobroker
                            -  enabled
+ system.adapter.hm-rpc.0                 : hm-rpc                : iobroker
                            -  enabled, port: 0
+ system.adapter.info.0                   : info                  : iobroker
                            -  enabled
+ system.adapter.iot.0                    : iot                   : iobroker
                            -  enabled
+ system.adapter.javascript.0             : javascript            : iobroker
                            -  enabled
  system.adapter.mqtt-client.0            : mqtt-client           : iobroker
                            - disabled, port: 1883
+ system.adapter.mqtt.0                   : mqtt                  : iobroker
                            -  enabled, port: 1883, bind: 192.168.178.52
  system.adapter.openweathermap.0         : openweathermap        : iobroker
                            -  enabled
+ system.adapter.panasonic-comfort-cloud.0: panasonic-comfort-cloud: iobroker
                             -  enabled
+ system.adapter.ping.0                   : ping                  : iobroker
                            -  enabled
+ system.adapter.scenes.0                 : scenes                : iobroker
                            -  enabled
+ system.adapter.smartcontrol.0           : smartcontrol          : iobroker
                            -  enabled
+ system.adapter.sony-bravia.0            : sony-bravia           : iobroker
                            -  enabled
+ system.adapter.sql.0                    : sql                   : iobroker
                            -  enabled, port: 3307
+ system.adapter.telegram.0               : telegram              : iobroker
                            -  enabled, port: 8443, bind: 0.0.0.0
+ system.adapter.terminal.0               : terminal              : iobroker
                            -  enabled, port: 8088, bind: 0.0.0.0, run as: admin
+ system.adapter.vesync.0                 : vesync                : iobroker
                            -  enabled
  system.adapter.vis.0                    : vis                   : iobroker
                            -  enabled
+ system.adapter.web.0                    : web                   : iobroker
                            -  enabled, port: 8082, bind: 192.168.178.52, run as:
 admin
+ system.adapter.whatsapp-cmb.0           : whatsapp-cmb          : iobroker
                            -  enabled
+ system.adapter.zigbee.0                 : zigbee                : iobroker
                            -  enabled, port: tcp://192.168.178.5:6638

+ instance is alive

Enabled adapters with bindings
  system.adapter.admin.0                  : admin                 : iobroker
                            -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.hm-rpc.0                 : hm-rpc                : iobroker
                            -  enabled, port: 0
+ system.adapter.mqtt.0                   : mqtt                  : iobroker
                            -  enabled, port: 1883, bind: 192.168.178.52
+ system.adapter.sql.0                    : sql                   : iobroker
                            -  enabled, port: 3307
+ system.adapter.telegram.0               : telegram              : iobroker
                            -  enabled, port: 8443, bind: 0.0.0.0
+ system.adapter.terminal.0               : terminal              : iobroker
                            -  enabled, port: 8088, bind: 0.0.0.0, run as: admin
+ system.adapter.web.0                    : web                   : iobroker
                            -  enabled, port: 8082, bind: 192.168.178.52, run as:
 admin
+ system.adapter.zigbee.0                 : zigbee                : iobroker
                            -  enabled, port: tcp://192.168.178.5:6638

ioBroker-Repositories
stable        : http://download.iobroker.net/sources-dist.json
beta          : http://download.iobroker.net/sources-dist-latest.json
pana          : https://github.com/marc2016/ioBroker.panasonic-comfort-cloud

Active repo(s): stable

Installed ioBroker-Instances
Used repository: stable
Adapter    "admin"        : 6.12.0   , installed 6.12.0
Adapter    "alexa2"       : 3.26.3   , installed 3.26.3
Adapter    "backitup"     : 2.8.7    , installed 2.8.7
Adapter    "cloud"        : 4.4.1    , installed 4.4.1
Adapter    "discovery"    : 4.2.0    , installed 4.2.0
Adapter    "ecovacs-deebot": 1.4.13  , installed 1.4.13
Adapter    "flot"         : 1.12.0   , installed 1.12.0
Adapter    "gruenbeck"    : 0.0.42   , installed 0.0.42
Adapter    "hm-rega"      : 4.0.0    , installed 4.0.0
Adapter    "hm-rpc"       : 1.15.19  , installed 1.15.19
Adapter    "info"         : 2.0.0    , installed 2.0.0
Adapter    "iot"          : 2.0.11   , installed 2.0.11
Adapter    "javascript"   : 7.1.6    , installed 7.1.6
Controller "js-controller": 5.0.17   , installed 5.0.17
Adapter    "mqtt"         : 5.1.0    , installed 5.1.0
Adapter    "mqtt-client"  : 1.7.0    , installed 1.7.0
Adapter    "openweathermap": 0.4.5   , installed 0.4.5
Adapter    "panasonic-comfort-cloud": 2.2.4, installed 2.2.4
Adapter    "ping"         : 1.6.2    , installed 1.6.2
Adapter    "scenes"       : 2.3.9    , installed 2.3.9
Adapter    "simple-api"   : 2.7.2    , installed 2.7.2
Adapter    "smartcontrol" : 2.0.1    , installed 2.0.1
Adapter    "socketio"     : 6.6.0    , installed 6.6.0
Adapter    "sony-bravia"  : 1.0.9    , installed 1.0.9
Adapter    "sql"          : 2.2.0    , installed 2.2.0
Adapter    "telegram"     : 3.0.0    , installed 3.0.0
Adapter    "terminal"     : 1.0.0    , installed 1.0.0
Adapter    "vesync"       : 0.0.3    , installed 0.0.3
Adapter    "vis"          : 1.5.4    , installed 1.5.4
Adapter    "vis-hqwidgets": 1.4.0    , installed 1.4.0
Adapter    "weatherunderground": 3.6.0, installed 3.6.0
Adapter    "web"          : 6.1.10   , installed 6.1.10
Adapter    "whatsapp-cmb" : 0.2.3    , installed 0.2.3
Adapter    "ws"           : 2.5.8    , installed 2.5.8
Adapter    "zigbee"       : 1.8.24   , installed 1.8.24

Objects and States
Please stand by - This may take a while
Objects:        11169
States:         9270

*** OS-Repositories and Updates ***
sudo: unable to resolve host iobroker: Name or service not known
sudo: unable to resolve host iobroker: Name or service not known
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian bookworm-updates InRelease
Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease
Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
Reading package lists...
Pending Updates: 0

*** Listening Ports ***
sudo: unable to resolve host iobroker: Name or service not known
       3482043    -              Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       U
ser       Inode      PID/Program name
tcp        0      0 192.168.178.52:42010    0.0.0.0:*               LISTEN      1
000       4662589    -
tcp        0      0 192.168.178.52:1883     0.0.0.0:*               LISTEN      1
000       4665719    -
tcp        0      0 0.0.0.0:6011            0.0.0.0:*               LISTEN      2
54178     119443     -
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      0
          48335      -
tcp        0      0 0.0.0.0:6012            0.0.0.0:*               LISTEN      2
54178     120432     -
tcp        0      0 0.0.0.0:892             0.0.0.0:*               LISTEN      0
          27010      -
tcp        0      0 0.0.0.0:445             0.0.0.0:*               LISTEN      0
          56007      -
tcp        0      0 127.0.0.1:512           0.0.0.0:*               LISTEN      0
          128944     -
tcp        0      0 127.0.0.1:161           0.0.0.0:*               LISTEN      0
          67992      -
tcp        0      0 0.0.0.0:2049            0.0.0.0:*               LISTEN      0
          41443      -
tcp        0      0 0.0.0.0:6690            0.0.0.0:*               LISTEN      0
          161086     -
tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1
000       4657587    -
tcp        0      0 192.168.178.52:49160    0.0.0.0:*               LISTEN      0
          124425     -
tcp        0      0 0.0.0.0:5000            0.0.0.0:*               LISTEN      0
          48329      -
tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1
000       4657541    -
tcp        0      0 0.0.0.0:5001            0.0.0.0:*               LISTEN      0
          48331      -
tcp        0      0 0.0.0.0:3306            0.0.0.0:*               LISTEN      0
          3480800    -
tcp        0      0 0.0.0.0:3307            0.0.0.0:*               LISTEN      6
6         103720     -
tcp        0      0 0.0.0.0:139             0.0.0.0:*               LISTEN      0
          56008      -
tcp        0      0 0.0.0.0:5357            0.0.0.0:*               LISTEN      0
          56614      -
tcp        0      0 0.0.0.0:4045            0.0.0.0:*               LISTEN      0
          41466      -
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      0
          22626      -
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      0
          48333      -
tcp        0      0 192.168.178.52:50001    0.0.0.0:*               LISTEN      0
          121254     -
tcp        0      0 192.168.178.52:8082     0.0.0.0:*               LISTEN      1
000       4670898    -
tcp        0      0 0.0.0.0:5010            0.0.0.0:*               LISTEN      0
          3482369    -
tcp        0      0 0.0.0.0:50002           0.0.0.0:*               LISTEN      0
          121541     -
tcp        0      0 192.168.178.52:49170    0.0.0.0:*               LISTEN      2
54178     119223     -
tcp        0      0 127.0.0.1:915           0.0.0.0:*               LISTEN      0
          108377     -
tcp        0      0 0.0.0.0:662             0.0.0.0:*               LISTEN      0
          27879      -
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0
          24612      -
tcp        0      0 0.0.0.0:3000            0.0.0.0:*               LISTEN      0

tcp        0      0 0.0.0.0:8888            0.0.0.0:*               LISTEN      0
          3479802    -
tcp        0      0 127.0.0.1:33304         0.0.0.0:*               LISTEN      0
          183457     -
tcp        0      0 127.0.0.1:5432          0.0.0.0:*               LISTEN      5
5         102861     -
tcp        0      0 127.0.0.1:18617         0.0.0.0:*               LISTEN      0
          124469     -
tcp6       0      0 :::443                  :::*                    LISTEN      0
          48336      -
tcp6       0      0 :::892                  :::*                    LISTEN      0
          27016      -
tcp6       0      0 :::3261                 :::*                    LISTEN      0
          70512      -
tcp6       0      0 :::445                  :::*                    LISTEN      0
          56005      -
tcp6       0      0 :::5566                 :::*                    LISTEN      0
          95836      -
tcp6       0      0 :::3263                 :::*                    LISTEN      0
          70510      -
tcp6       0      0 :::3264                 :::*                    LISTEN      0
          70514      -
tcp6       0      0 :::3265                 :::*                    LISTEN      0
          71938      -
tcp6       0      0 :::2049                 :::*                    LISTEN      0
          41456      -
tcp6       0      0 :::6690                 :::*                    LISTEN      0
          161087     -
tcp6       0      0 :::5000                 :::*                    LISTEN      0
          48330      -
tcp6       0      0 :::5001                 :::*                    LISTEN      0
          48332      -
tcp6       0      0 :::3306                 :::*                    LISTEN      0
          3480805    -
tcp6       0      0 :::139                  :::*                    LISTEN      0
          56006      -
tcp6       0      0 :::5357                 :::*                    LISTEN      0
          56615      -
tcp6       0      0 :::4045                 :::*                    LISTEN      0
          41468      -
tcp6       0      0 :::111                  :::*                    LISTEN      0
          22629      -
tcp6       0      0 :::80                   :::*                    LISTEN      0
          48334      -
tcp6       0      0 :::5010                 :::*                    LISTEN      0
          3482374    -
tcp6       0      0 :::662                  :::*                    LISTEN      0
          27883      -
tcp6       0      0 :::22                   :::*                    LISTEN      0
          24614      -
tcp6       0      0 :::8088                 :::*                    LISTEN      1
000       4671410    -
tcp6       0      0 :::3000                 :::*                    LISTEN      0
          3482048    -
tcp6       0      0 :::8888                 :::*                    LISTEN      0
          3479807    -
udp        0      0 0.0.0.0:9997            0.0.0.0:*                           0
          23392      -
udp        0      0 0.0.0.0:9998            0.0.0.0:*                           0
          23391      -
udp        0      0 0.0.0.0:9999            0.0.0.0:*                           0
          23390      -
udp        0      0 127.0.0.1:59233         0.0.0.0:*                           0
          121255     -
udp        0      0 0.0.0.0:43647           0.0.0.0:*                           0
          182180     -
udp        0      0 0.0.0.0:47990           0.0.0.0:*                           0
          2993018    -
udp        0      0 0.0.0.0:64921           0.0.0.0:*                           0
          22625      -
udp        0      0 127.0.0.1:48677         0.0.0.0:*                           0
          124426     -
udp        0      0 0.0.0.0:68              0.0.0.0:*                           0
          23331      -
udp        0      0 0.0.0.0:68              0.0.0.0:*                           0
          23828      -
udp        0      0 0.0.0.0:111             0.0.0.0:*                           0
          21135      -
udp        0      0 192.168.178.255:137     0.0.0.0:*                           0
          2993100    -
udp        0      0 192.168.178.52:137      0.0.0.0:*                           0
          2993099    -
udp        0      0 0.0.0.0:137             0.0.0.0:*                           0
          2993064    -
udp        0      0 192.168.178.255:138     0.0.0.0:*                           0
          2993102    -
udp        0      0 192.168.178.52:138      0.0.0.0:*                           0
          2993101    -
udp        0      0 0.0.0.0:138             0.0.0.0:*                           0
          2993065    -
udp        0      0 127.0.0.1:161           0.0.0.0:*                           0
          67991      -
udp        0      0 0.0.0.0:662             0.0.0.0:*                           0
          27877      -
udp        0      0 127.0.0.1:676           0.0.0.0:*                           0
          27170      -
udp        0      0 0.0.0.0:892             0.0.0.0:*                           0
          27007      -
udp        0      0 127.0.0.1:33734         0.0.0.0:*                           2
54178     119224     -
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           0
          124428     -
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           0
          121257     -
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           2
54178     119226     -
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           0
          48805      -
udp        0      0 0.0.0.0:2049            0.0.0.0:*                           0
          41455      -
udp        0      0 0.0.0.0:3702            0.0.0.0:*                           9
9         55753      -
udp        0      0 0.0.0.0:4045            0.0.0.0:*                           0
          41465      -
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           0
          2993016    -
udp        0      0 192.168.178.52:55900    0.0.0.0:*                           2
54178     119225     -
udp        0      0 192.168.178.52:55901    0.0.0.0:*                           0
          121256     -
udp        0      0 192.168.178.52:55902    0.0.0.0:*                           0
          124427     -
udp6       0      0 :::111                  :::*                                0
          22627      -
udp6       0      0 :::662                  :::*                                0
          27881      -
udp6       0      0 :::892                  :::*                                0
          27013      -
udp6       0      0 :::2049                 :::*                                0
          41457      -
udp6       0      0 :::36027                :::*                                0
          2993019    -
udp6       0      0 :::3702                 :::*                                9
9         55755      -
udp6       0      0 :::4045                 :::*                                0
          41467      -
udp6       0      0 :::5353                 :::*                                0
          2993017    -
udp6       0      0 :::56733                :::*                                0
          22628      -

*** Log File - Last 25 Lines ***

2023-12-21 23:28:57.304  - info: javascript.0 (292) script.js.common.Dahua.DahuaE
vent: Publish KeepAlive event
2023-12-21 23:28:59.755  - info: javascript.0 (292) script.js.common.Dahua.DahuaE
vent: Publish event VideoMotion to MQTT
2023-12-21 23:28:59.937  - info: javascript.0 (292) script.js.common.Dahua.DahuaE
vent: Publish event SIPRegisterResult to MQTT
2023-12-21 23:29:00.960  - info: javascript.0 (292) script.js.common.Dahua.DahuaE
vent: Publish event SIPRegisterResult to MQTT
2023-12-21 23:29:04.186  - info: javascript.0 (292) script.js.common.Dahua.DahuaE
vent: Publish event VideoMotion to MQTT
2023-12-21 23:29:04.667  - info: javascript.0 (292) script.js.common.Dahua.DahuaE
vent: Publish event VideoMotion to MQTT
2023-12-21 23:29:11.185  - info: javascript.0 (292) script.js.common.Dahua.DahuaE
vent: Publish event VideoMotion to MQTT
2023-12-21 23:29:52.303  - info: javascript.0 (292) script.js.common.Dahua.DahuaE
vent: Publish KeepAlive event
2023-12-21 23:29:57.935  - info: javascript.0 (292) script.js.common.Dahua.DahuaE
vent: Publish event SIPRegisterResult to MQTT
2023-12-21 23:29:58.957  - info: javascript.0 (292) script.js.common.Dahua.DahuaE
vent: Publish event SIPRegisterResult to MQTT
2023-12-21 23:30:24.172  - info: javascript.0 (292) script.js.common.Dahua.DahuaE
vent: Publish event VideoMotion to MQTT
2023-12-21 23:30:31.183  - info: javascript.0 (292) script.js.common.Dahua.DahuaE
vent: Publish event VideoMotion to MQTT
2023-12-21 23:30:47.302  - info: javascript.0 (292) script.js.common.Dahua.DahuaE
vent: Publish KeepAlive event
2023-12-21 23:30:55.933  - info: javascript.0 (292) script.js.common.Dahua.DahuaE
vent: Publish event SIPRegisterResult to MQTT
2023-12-21 23:30:56.954  - info: javascript.0 (292) script.js.common.Dahua.DahuaE
vent: Publish event SIPRegisterResult to MQTT
2023-12-21 23:31:11.304  - info: javascript.0 (292) script.js.common.Dahua.DahuaE
vent: Publish event VideoMotion to MQTT
2023-12-21 23:31:16.183  - info: javascript.0 (292) script.js.common.Dahua.DahuaE
vent: Publish event VideoMotion to MQTT
2023-12-21 23:31:37.254  - info: panasonic-comfort-cloud.0 (917) state panasonic-
comfort-cloud.0.info.connection changed: true (ack = true)
2023-12-21 23:31:42.320  - info: javascript.0 (292) script.js.common.Dahua.DahuaE
vent: Publish KeepAlive event
2023-12-21 23:31:43.280  - info: javascript.0 (292) script.js.common.Dahua.DahuaE
vent: Publish event VideoMotion to MQTT
2023-12-21 23:31:53.932  - info: javascript.0 (292) script.js.common.Dahua.DahuaE
vent: Publish event SIPRegisterResult to MQTT
2023-12-21 23:31:54.954  - info: javascript.0 (292) script.js.common.Dahua.DahuaE
vent: Publish event SIPRegisterResult to MQTT
2023-12-21 23:31:56.301  - info: javascript.0 (292) script.js.common.Dahua.DahuaE
vent: Publish event NTPAdjustTime to MQTT
2023-12-21 23:31:59.182  - info: javascript.0 (292) script.js.common.Dahua.DahuaE
vent: Publish event VideoMotion to MQTT
2023-12-21 23:32:37.301  - info: javascript.0 (292) script.js.common.Dahua.DahuaE
vent: Publish KeepAlive event

============ Mark until here for C&P =============

Summary

======================= SUMMARY =======================
                        v.2023-10-10


model name      : Intel(R) Celeron(R) J4025 CPU @ 2.00GHz
Kernel          : x86_64
Userland        : amd64
Docker          : v9.0.1

Installation:           Docker
Kernel:                 x86_64
Userland:               amd64
Timezone:               Etc/UTC
User-ID:                0
X-Server:               false


Pending OS-Updates:     0
Pending iob updates:    0

Nodejs-Installation:    /usr/bin/nodejs         v18.19.0
                        /usr/bin/node           v18.19.0
                        /usr/bin/npm            10.2.3
                        /usr/bin/npx            10.2.3
                        /usr/bin/corepack       0.22.0

Recommended versions are nodejs  and npm
Your nodejs installation is correct

MEMORY:
               total        used        free      shared  buff/cache   available
Mem:             18G        4.0G        308M        646M         15G         14G
Swap:            13G         70M         13G
Total:           32G        4.0G         13G

Active iob-Instances:   24
Active repo(s): stable

ioBroker Core:          js-controller           5.0.17
                        admin                   6.12.0

ioBroker Status:        iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Status admin and web instance:
  system.adapter.admin.0                  : admin                 : iobroker
                            -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.web.0                    : web                   : iobroker
                            -  enabled, port: 8082, bind: 192.168.178.52, run as:
 admin

Objects:                11169
States:                 9270

Size of iob-Database:

20M     /opt/iobroker/iobroker-data/objects.jsonl
12M     /opt/iobroker/iobroker-data/objects.json.migrated
12M     /opt/iobroker/iobroker-data/objects.json.bak.migrated
17M     /opt/iobroker/iobroker-data/states.jsonl
1.4M    /opt/iobroker/iobroker-data/states.json.migrated
1.4M    /opt/iobroker/iobroker-data/states.json.bak.migrated



=================== END OF SUMMARY ====================

@glasfaser

naja ich habe natürlich nicht wild rumgeschossen, sondern schon geschaut was sinn macht. Die sudo Befehle haben im bash bei mir aber noch nie funktioniert:

oot@iobroker:/opt/iobroker# sudo -H -u iobroker npm install iobroker.js-controll
er                                                                               
sudo: unable to resolve host iobroker: Name or service not known                 
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ idealTree:iobroker: sill idealTree buil
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠦ idealTree:iobroker: sill idealTree buil
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil
(⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠧ idealTree:iobroker: sill idealTree buil

removed 97 packages in 29s

143 packages are looking for funding
  run `npm fund` for details

@glasfaser

Danke für die Unterstützung, aber wo gebe ich den sudo Befehl ein? Wenn ich im Docker das Terminal öffne , dann bekomme ich folgende Meldung:

sudo: unable to resolve host iobroker: Name or service not known

removed 97 packages in 29s

143 packages are looking for funding
  run `npm fund` for details

Wenn ich dann den Container neustarte, kommt dieselbe Fehlermeldung.

Hallo zusammen,

ich nutze schon seit einiger Zeit ioBroker im Container Manager auf eine Synology mit DSM v.7. Bis vor einiger Zeit hat auch alles sehr gut funktioniert. Von Zeit zu Zeit habe ich mich in die Admin Oberfläche eingewählt und geschaut, welche Updates es gibt, etc. Das letzte Mal habe ich das wohl Anfang Oktober gemacht. Heute wollte ich mich wieder einloggen, um nach einem spezifischen Adapter zu suchen (Tesla), aber die Oberfläche öffnete sich nicht "ERR_CONNECTION_REFUSED"

Dann bin ich den Container gegangen und habe im Terminal mit list instances nach geschaut und gesehen, dass alle meine Instanzen laufen - deshalb ist mir das nicht aufgefallen - außer die admin.0 Instanz. Die ist auf enabled und mit bind 0.0.0.0

Habe dann das image im Container Manager aktualisiert, sämtliche iob Befehle, die hier im Forum zu finden waren, aber leider läuft die Instanz Admin immer noch nicht.
Wenn ich den Container starte, dann bekomme ich auch eine Fehlermeldung mit der ich aber bislang noch nichts anfangen konnte:

2023/12/21 22:39:26,stdout,================================== > LOG REDIRECT system.adapter.admin.0 => false [system.adapter.admin.0.logging]

2023/12/21 22:39:26,stdout,================================== > LOG REDIRECT system.adapter.admin.0 => false [Process stopped]

2023/12/21 22:39:26,stdout,

2023/12/21 22:39:26,stdout,Node.js v18.19.0

2023/12/21 22:39:26,stdout,

2023/12/21 22:39:26,stdout,}

2023/12/21 22:39:26,stdout,  ]

2023/12/21 22:39:26,stdout,    '/opt/iobroker/node_modules/iobroker.admin/main.js'

2023/12/21 22:39:26,stdout,"    '/opt/iobroker/node_modules/iobroker.admin/lib/web.js',
"
2023/12/21 22:39:26,stdout,"    '/opt/iobroker/node_modules/mime/index.js',
"
2023/12/21 22:39:26,stdout,  requireStack: [

2023/12/21 22:39:26,stdout,"  code: 'MODULE_NOT_FOUND',
"
2023/12/21 22:39:26,stdout,    at Module.require (node:internal/modules/cjs/loader:1225:19) {

2023/12/21 22:39:26,stdout,    at Module._load (node:internal/modules/cjs/loader:1013:12)

2023/12/21 22:39:26,stdout,    at Module.load (node:internal/modules/cjs/loader:1197:32)

2023/12/21 22:39:26,stdout,    at Module._extensions..js (node:internal/modules/cjs/loader:1414:10)

2023/12/21 22:39:26,stdout,    at Module._compile (node:internal/modules/cjs/loader:1356:14)

2023/12/21 22:39:26,stdout,    at Object.<anonymous> (/opt/iobroker/node_modules/mime/index.js:3:12)

2023/12/21 22:39:26,stdout,    at require (node:internal/modules/helpers:177:18)

2023/12/21 22:39:26,stdout,    at Module.require (node:internal/modules/cjs/loader:1225:19)

2023/12/21 22:39:26,stdout,    at Module._load (node:internal/modules/cjs/loader:975:27)

2023/12/21 22:39:26,stdout,    at Module._resolveFilename (node:internal/modules/cjs/loader:1134:15)

2023/12/21 22:39:26,stdout,- /opt/iobroker/node_modules/iobroker.admin/main.js

2023/12/21 22:39:26,stdout,- /opt/iobroker/node_modules/iobroker.admin/lib/web.js

2023/12/21 22:39:26,stdout,- /opt/iobroker/node_modules/mime/index.js

2023/12/21 22:39:26,stdout,Require stack:

2023/12/21 22:39:26,stdout,Error: Cannot find module './Mime'

2023/12/21 22:39:26,stdout,

2023/12/21 22:39:26,stdout,  ^

2023/12/21 22:39:26,stdout,  throw err;

2023/12/21 22:39:26,stdout,node:internal/modules/cjs/loader:1137

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.panasonic-comfort-cloud.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.vesync.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.gruenbeck.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.smartcontrol.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.ecovacs-deebot.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.vis.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.terminal.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.web.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.iot.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.cloud.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.backitup.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.info.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.discovery.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.ping.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.zigbee.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.openweathermap.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.sony-bravia.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.mqtt-client.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.mqtt.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.alexa2.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.hm-rega.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.hm-rpc.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.sql.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.telegram.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.javascript.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.scenes.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.whatsapp-cmb.0" for host "iobroker"

2023/12/21 22:39:25,stdout,host.iobroker check instance "system.adapter.admin.0" for host "iobroker"

2023/12/21 22:39:22,stdout,##### #### ### ## # iobroker.js-controller log output # ## ### #### #####

2023/12/21 22:39:22,stdout, 

2023/12/21 22:39:22,stdout,Starting ioBroker... 

2023/12/21 22:39:22,stdout, 

2023/12/21 22:39:22,stdout,--------------------------------------------------------------------------------

2023/12/21 22:39:22,stdout,-----                    Step 5 of 5: ioBroker startup                     -----

2023/12/21 22:39:22,stdout,--------------------------------------------------------------------------------

2023/12/21 22:39:22,stdout, 

2023/12/21 22:39:22,stdout, 

2023/12/21 22:39:22,stdout,For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs/).

2023/12/21 22:39:22,stdout,Some adapters have special requirements/ settings which can be activated by the use of environment variables.

2023/12/21 22:39:22,stdout, 

2023/12/21 22:39:22,stdout,--------------------------------------------------------------------------------

2023/12/21 22:39:22,stdout,-----                Step 4 of 5: Applying special settings                -----

2023/12/21 22:39:22,stdout,--------------------------------------------------------------------------------

2023/12/21 22:39:22,stdout, 

2023/12/21 22:39:22,stdout,No action required.

2023/12/21 22:39:22,stdout,Hostname in ioBroker matches the hostname of this container.

2023/12/21 22:38:56,stdout, 

2023/12/21 22:38:56,stdout,Checking Database connection... Done.

2023/12/21 22:38:44,stdout, 

2023/12/21 22:38:43,stdout,(Re)setting permissions (This might take a while! Please be patient!)... Done.

2023/12/21 22:38:41,stdout, 

2023/12/21 22:38:41,stdout,--------------------------------------------------------------------------------

2023/12/21 22:38:41,stdout,-----             Step 3 of 5: Checking ioBroker installation              -----

2023/12/21 22:38:41,stdout,--------------------------------------------------------------------------------

2023/12/21 22:38:41,stdout, 

2023/12/21 22:38:41,stdout,Existing installation of ioBroker detected in "/opt/iobroker".

2023/12/21 22:38:40,stdout, 

2023/12/21 22:38:40,stdout,--------------------------------------------------------------------------------

2023/12/21 22:38:40,stdout,-----             Step 2 of 5: Detecting ioBroker installation             -----

2023/12/21 22:38:40,stdout,--------------------------------------------------------------------------------

2023/12/21 22:38:40,stdout, 

2023/12/21 22:38:40,stdout,This is not the first run of this container. Skipping first run preparation.

2023/12/21 22:38:40,stdout, 

2023/12/21 22:38:40,stdout,--------------------------------------------------------------------------------

2023/12/21 22:38:40,stdout,-----                   Step 1 of 5: Preparing container                   -----

2023/12/21 22:38:40,stdout,--------------------------------------------------------------------------------

2023/12/21 22:38:40,stdout, 

2023/12/21 22:38:40,stdout,--------------------------------------------------------------------------------

2023/12/21 22:38:40,stdout,-----                    SETUID:              1000                         -----

2023/12/21 22:38:40,stdout,-----                    SETGID:              1000                         -----

2023/12/21 22:38:40,stdout,-----                        Environment Variables                         -----

2023/12/21 22:38:40,stdout,-----                                                                      -----

2023/12/21 22:38:40,stdout,-----                    npm:                 10.2.3                       -----

2023/12/21 22:38:39,stdout,-----                    node:                v18.19.0                     -----

2023/12/21 22:38:39,stdout,-----                    build:               2023-12-19T23:44:44+00:00    -----

2023/12/21 22:38:39,stdout,-----                    image:               v9.0.1                       -----

2023/12/21 22:38:39,stdout,-----                          Version Information                         -----

2023/12/21 22:38:39,stdout,-----                                                                      -----

2023/12/21 22:38:39,stdout,-----                    hostname:            iobroker                     -----

2023/12/21 22:38:39,stdout,-----                    arch:                x86_64                       -----

2023/12/21 22:38:39,stdout,-----                          System Information                          -----

2023/12/21 22:38:39,stdout,--------------------------------------------------------------------------------

2023/12/21 22:38:39,stdout, 

2023/12/21 22:38:39,stdout,--------------------------------------------------------------------------------

2023/12/21 22:38:39,stdout,-----                          Please be patient!                          -----

2023/12/21 22:38:39,stdout,-----                    Startupscript is now running!                     -----

2023/12/21 22:38:39,stdout,-----              Welcome to your ioBroker Docker container!              -----

2023/12/21 22:38:39,stdout,-----                                                                      -----

2023/12/21 22:38:39,stdout,----- ╚═╝  ╚═════╝  ╚═════╝  ╚═╝  ╚═╝  ╚═════╝  ╚═╝  ╚═╝ ╚══════╝ ╚═╝  ╚═╝ -----

2023/12/21 22:38:39,stdout,----- ██║ ╚██████╔╝ ██████╔╝ ██║  ██║ ╚██████╔╝ ██║  ██╗ ███████╗ ██║  ██║ -----

2023/12/21 22:38:39,stdout,----- ██║ ██║   ██║ ██╔══██╗ ██╔══██╗ ██║   ██║ ██╔═██╗  ██╔══╝   ██╔══██╗ -----

2023/12/21 22:38:39,stdout,----- ██║ ██║   ██║ ██████╔╝ ██████╔╝ ██║   ██║ █████╔╝  █████╗   ██████╔╝ -----

2023/12/21 22:38:39,stdout,----- ██║ ██╔═══██╗ ██╔══██╗ ██╔══██╗ ██╔═══██╗ ██║ ██╔╝ ██╔════╝ ██╔══██╗ -----

2023/12/21 22:38:39,stdout,----- ██╗  ██████╗  ██████╗  ██████╗   ██████╗  ██╗  ██╗ ███████╗ ██████╗  -----

2023/12/21 22:38:39,stdout,-----                                                                      -----

2023/12/21 22:38:39,stdout,--------------------------------------------------------------------------------

2023/12/21 22:38:39,stdout,-------------------------     2023-12-21 22:38:39      -------------------------

2023/12/21 22:38:39,stdout,--------------------------------------------------------------------------------

Jemand eine Idee, was ich noch versuchen könnte?

@dimaiv
funktioniert dieser nur über USB? Was ist da alles dabei bzw. welche weitere Hardware benötigt man, um diesen zu betreiben?

Hallo zusammen,

ich habe das Problem, dass der ikea tradfri LED Treiber (ICPSHC24-10EU-IL-1) immer wieder die Verbindung zum Gateway verliert. Ich muss ihn dann immer wieder neu anlernen. Wenn die Geräte an ihrem Ort sind, dann hat der tradfri eine Verbindungsstärke von rund 50. Ich habe dazu jetzt nichts spezifisches im Netz gefunden (Tradfri und CC2652P).

Ideen?