Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Sonos Adapter probleme

    NEWS

    • Monatsrückblick - April 2025

    • Minor js-controller 7.0.7 Update in latest repo

    • Save The Date: ioBroker@Smart Living Forum Solingen, 14.06.

    Sonos Adapter probleme

    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      Dominik_neu @Thomas Braun last edited by Dominik_neu

      2024-05-30 14:19:47.130 - info: host.raspberrypi instance system.adapter.sonos.0 started with pid 6092
      2024-05-30 14:19:49.125 - info: sonos.0 (6092) starting. Version 3.0.0 in /opt/iobroker/node_modules/iobroker.sonos, node: v18.14.2, js-controller: 5.0.19
      2024-05-30 14:19:49.931 - error: sonos.0 (6092) Cannot write file coverImage/192_168_20_12.png: sonos is not an object of type "meta"
      2024-05-30 14:19:49.946 - error: sonos.0 (6092) 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().
      2024-05-30 14:19:49.946 - error: sonos.0 (6092) unhandled promise rejection: sonos is not an object of type "meta"
      2024-05-30 14:19:49.948 - error: sonos.0 (6092) Error: sonos is not an object of type "meta"
      at ObjectsInRedisClient.validateMetaObject (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:587:39)
      at runNextTicks (node:internal/process/task_queues:60:5)
      at process.processImmediate (node:internal/timers:447:9)
      at async ObjectsInRedisClient.writeFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:821:13)
      2024-05-30 14:19:49.949 - error: sonos.0 (6092) sonos is not an object of type "meta"
      2024-05-30 14:19:49.952 - error: sonos.0 (6092) Cannot write file coverImage/192_168_20_10.png: sonos is not an object of type "meta"
      2024-05-30 14:19:49.956 - info: sonos.0 (6092) terminating
      2024-05-30 14:19:49.966 - info: sonos.0 (6092) terminating
      2024-05-30 14:19:49.968 - warn: sonos.0 (6092) Terminated (UNCAUGHT_EXCEPTION): Without reason
      2024-05-30 14:19:49.989 - error: sonos.0 (6092) 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().
      2024-05-30 14:19:49.991 - error: sonos.0 (6092) unhandled promise rejection: sonos is not an object of type "meta"
      2024-05-30 14:19:49.992 - error: sonos.0 (6092) Error: sonos is not an object of type "meta"
      at ObjectsInRedisClient.validateMetaObject (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:587:39)
      at runNextTicks (node:internal/process/task_queues:60:5)
      at process.processImmediate (node:internal/timers:447:9)
      at async ObjectsInRedisClient.writeFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:821:13)
      2024-05-30 14:19:49.992 - error: sonos.0 (6092) sonos is not an object of type "meta"
      2024-05-30 14:19:50.470 - info: sonos.0 (6092) terminating
      2024-05-30 14:19:50.533 - error: host.raspberrypi instance system.adapter.sonos.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
      2024-05-30 14:19:50.533 - info: host.raspberrypi Restart adapter system.adapter.sonos.0 because enabled
      2024-05-30 14:20:20.597 - info: host.raspberrypi instance system.adapter.sonos.0 started with pid 6108
      2024-05-30 14:20:22.958 - info: sonos.0 (6108) starting. Version 3.0.0 in /opt/iobroker/node_modules/iobroker.sonos, node: v18.14.2, js-controller: 5.0.19
      2024-05-30 14:20:24.038 - error: sonos.0 (6108) Cannot write file coverImage/192_168_20_11.png: sonos is not an object of type "meta"
      2024-05-30 14:20:24.056 - error: sonos.0 (6108) 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().
      2024-05-30 14:20:24.057 - error: sonos.0 (6108) unhandled promise rejection: sonos is not an object of type "meta"
      2024-05-30 14:20:24.059 - error: sonos.0 (6108) Error: sonos is not an object of type "meta"
      at ObjectsInRedisClient.validateMetaObject (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:587:39)
      at runNextTicks (node:internal/process/task_queues:60:5)
      at process.processImmediate (node:internal/timers:447:9)
      at async ObjectsInRedisClient.writeFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:821:13)
      2024-05-30 14:20:24.060 - error: sonos.0 (6108) sonos is not an object of type "meta"
      2024-05-30 14:20:24.062 - error: sonos.0 (6108) Cannot write file coverImage/192_168_20_10.png: sonos is not an object of type "meta"
      2024-05-30 14:20:24.064 - error: sonos.0 (6108) Cannot write file coverImage/192_168_20_12.png: sonos is not an object of type "meta"
      2024-05-30 14:20:24.068 - info: sonos.0 (6108) terminating
      2024-05-30 14:20:24.077 - info: sonos.0 (6108) terminating
      2024-05-30 14:20:24.078 - warn: sonos.0 (6108) Terminated (UNCAUGHT_EXCEPTION): Without reason
      2024-05-30 14:20:24.094 - error: sonos.0 (6108) 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().
      2024-05-30 14:20:24.096 - error: sonos.0 (6108) unhandled promise rejection: sonos is not an object of type "meta"
      2024-05-30 14:20:24.096 - error: sonos.0 (6108) Error: sonos is not an object of type "meta"
      at ObjectsInRedisClient.validateMetaObject (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:587:39)
      at runNextTicks (node:internal/process/task_queues:60:5)
      at process.processImmediate (node:internal/timers:447:9)
      at async ObjectsInRedisClient.writeFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:821:13)
      2024-05-30 14:20:24.097 - error: sonos.0 (6108) sonos is not an object of type "meta"
      2024-05-30 14:20:24.103 - error: sonos.0 (6108) 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().
      2024-05-30 14:20:24.103 - error: sonos.0 (6108) unhandled promise rejection: sonos is not an object of type "meta"
      2024-05-30 14:20:24.106 - error: sonos.0 (6108) Error: sonos is not an object of type "meta"
      at ObjectsInRedisClient.validateMetaObject (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:587:39)
      at runNextTicks (node:internal/process/task_queues:60:5)
      at process.processImmediate (node:internal/timers:447:9)
      at async ObjectsInRedisClient.writeFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:821:13)
      2024-05-30 14:20:24.106 - error: sonos.0 (6108) sonos is not an object of type "meta"
      2024-05-30 14:20:24.580 - info: sonos.0 (6108) terminating
      2024-05-30 14:20:24.650 - error: host.raspberrypi instance system.adapter.sonos.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
      2024-05-30 14:20:24.651 - info: host.raspberrypi Restart adapter system.adapter.sonos.0 because enabled
      2024-05-30 14:20:54.766 - info: host.raspberrypi instance system.adapter.sonos.0 started with pid 6123
      2024-05-30 14:20:57.156 - info: sonos.0 (6123) starting. Version 3.0.0 in /opt/iobroker/node_modules/iobroker.sonos, node: v18.14.2, js-controller: 5.0.19
      2024-05-30 14:20:58.345 - error: sonos.0 (6123) Cannot write file coverImage/192_168_20_11.png: sonos is not an object of type "meta"
      2024-05-30 14:20:58.355 - error: sonos.0 (6123) Cannot write file coverImage/192_168_20_12.png: sonos is not an object of type "meta"
      2024-05-30 14:20:58.373 - error: sonos.0 (6123) 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().
      2024-05-30 14:20:58.375 - error: sonos.0 (6123) unhandled promise rejection: sonos is not an object of type "meta"
      2024-05-30 14:20:58.377 - error: sonos.0 (6123) Error: sonos is not an object of type "meta"
      at ObjectsInRedisClient.validateMetaObject (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:587:39)
      at runNextTicks (node:internal/process/task_queues:60:5)
      at process.processImmediate (node:internal/timers:447:9)
      at async ObjectsInRedisClient.writeFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:821:13)
      2024-05-30 14:20:58.378 - error: sonos.0 (6123) sonos is not an object of type "meta"
      2024-05-30 14:20:58.384 - error: sonos.0 (6123) Cannot write file coverImage/192_168_20_10.png: sonos is not an object of type "meta"
      2024-05-30 14:20:58.388 - error: sonos.0 (6123) 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().
      2024-05-30 14:20:58.390 - error: sonos.0 (6123) unhandled promise rejection: sonos is not an object of type "meta"
      2024-05-30 14:20:58.394 - error: sonos.0 (6123) Error: sonos is not an object of type "meta"
      at ObjectsInRedisClient.validateMetaObject (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:591:35)
      at ObjectsInRedisClient.writeFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:821:24)
      at AdapterClass.writeFile (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:4816:73)
      at /opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/tools.js:2022:16
      at new Promise ()
      at AdapterClass.writeFileAsync (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/tools.js:2021:16)
      at takeSonosState (/opt/iobroker/node_modules/iobroker.sonos/main.js:1456:31)
      at processSonosEvents (/opt/iobroker/node_modules/iobroker.sonos/main.js:1693:17)
      at SonosSystem. (/opt/iobroker/node_modules/iobroker.sonos/main.js:2105:13)
      at SonosSystem.emit (node:events:513:28)
      2024-05-30 14:20:58.395 - error: sonos.0 (6123) sonos is not an object of type "meta"
      2024-05-30 14:20:58.399 - info: sonos.0 (6123) terminating
      2024-05-30 14:20:58.412 - info: sonos.0 (6123) terminating
      2024-05-30 14:20:58.413 - warn: sonos.0 (6123) Terminated (UNCAUGHT_EXCEPTION): Without reason
      2024-05-30 14:20:58.437 - error: sonos.0 (6123) 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().
      2024-05-30 14:20:58.437 - error: sonos.0 (6123) unhandled promise rejection: sonos is not an object of type "meta"
      2024-05-30 14:20:58.438 - error: sonos.0 (6123) Error: sonos is not an object of type "meta"
      at ObjectsInRedisClient.validateMetaObject (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:587:39)
      at runNextTicks (node:internal/process/task_queues:60:5)
      at process.processImmediate (node:internal/timers:447:9)
      at async ObjectsInRedisClient.writeFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:821:13)
      2024-05-30 14:20:58.439 - error: sonos.0 (6123) sonos is not an object of type "meta"
      2024-05-30 14:20:58.916 - info: sonos.0 (6123) terminating
      2024-05-30 14:20:58.993 - error: host.raspberrypi instance system.adapter.sonos.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
      2024-05-30 14:20:58.994 - info: host.raspberrypi Restart adapter system.adapter.sonos.0 because enabled
      2024-05-30 14:20:58.994 - warn: host.raspberrypi Do not restart adapter system.adapter.sonos.0 because restart loop detected
      2024-05-30 14:25:18.683 - warn: admin.0 (5545) sonos has an invalid jsonConfig: [{"instancePath":"/items/devicesTab/items/_sendto","schemaPath":"#/definitions/sendToProps/additionalProperties","keyword":"additionalProperties","params":{"additionalProperty":"timeout"},"message":"must NOT have additional properties"},{"instancePath":"/items/devicesTab","schemaPath":"#/properties/items/patternProperties/%5E.%2B/allOf/8/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"},{"instancePath":"","schemaPath":"#/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"}]
      2024-05-30 14:25:25.881 - info: admin.0 (5545) ==> Connected system.user.admin from ::ffff:192.168.50.50
      2024-05-30 14:26:19.956 - info: admin.0 (5545) <== Disconnect system.user.admin from ::ffff:192.168.50.50 javascript
      
      
      1 Reply Last reply Reply Quote 0
      • S
        SmartHomie @Dominik_neu last edited by

        @dominik_neu Hänge mich hier mal ran. Habe den Sonos Adapter neu installiert da ich immer viele Warnungen/Abstürze von dem Adapter erhalten habe. Jetzt geht aber leider gar nichts mehr und die Instanz geht auf rot.
        Habe auch die Meldung "Restart loop detected". Ein iob stop und iob fix haben nichts gebracht.

        2024-06-02 11:45:05.138  - warn: admin.0 (1193178) sonos has an invalid jsonConfig: [{"instancePath":"/items/devicesTab/items/_sendto","schemaPath":"#/definitions/sendToProps/additionalProperties","keyword":"additionalProperties","params":{"additionalProperty":"timeout"},"message":"must NOT have additional properties"},{"instancePath":"/items/devicesTab","schemaPath":"#/properties/items/patternProperties/%5E.%2B/allOf/8/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"},{"instancePath":"","schemaPath":"#/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"}]
        2024-06-02 11:48:06.599  - info: host.ioBroker2 instance system.adapter.sonos.0 started with pid 1196483
        2024-06-02 11:48:09.964  - info: sonos.0 (1196483) starting. Version 3.0.0 in /opt/iobroker/node_modules/iobroker.sonos, node: v18.20.2, js-controller: 5.0.19
        2024-06-02 11:48:11.252  - error: sonos.0 (1196483) 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().
        2024-06-02 11:48:11.255  - error: sonos.0 (1196483) unhandled promise rejection: Cannot read properties of undefined (reading 'id')
        2024-06-02 11:48:11.259  - error: sonos.0 (1196483) TypeError: Cannot read properties of undefined (reading 'id')
            at syncConfig (/opt/iobroker/node_modules/iobroker.sonos/main.js:2029:71)
        2024-06-02 11:48:11.261  - error: sonos.0 (1196483) Cannot read properties of undefined (reading 'id')
        2024-06-02 11:48:11.276  - info: sonos.0 (1196483) terminating
        2024-06-02 11:48:11.279  - info: sonos.0 (1196483) terminating
        2024-06-02 11:48:11.281  - warn: sonos.0 (1196483) Terminated (UNCAUGHT_EXCEPTION): Without reason
        2024-06-02 11:48:11.787  - info: sonos.0 (1196483) terminating
        2024-06-02 11:48:12.037  - error: host.ioBroker2 instance system.adapter.sonos.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
        2024-06-02 11:48:12.038  - info: host.ioBroker2 Restart adapter system.adapter.sonos.0 because enabled
        2024-06-02 11:48:34.343  - info: connector-local-control.0 (1194295) receive server message from 192.168.178.56: 32100: {"msgType":"Heartbeat","mac":"f008d179f228","deviceType":"02000001","token":"37412C478E0FBEAB","data":{"currentState":1,"numberOfDevices":1,"RSSI":-43}}
        2024-06-02 11:48:34.345  - info: connector-local-control.0 (1194295) Heartbeat
        2024-06-02 11:48:42.260  - info: host.ioBroker2 instance system.adapter.sonos.0 started with pid 1196660
        2024-06-02 11:48:45.467  - info: sonos.0 (1196660) starting. Version 3.0.0 in /opt/iobroker/node_modules/iobroker.sonos, node: v18.20.2, js-controller: 5.0.19
        2024-06-02 11:48:46.671  - error: sonos.0 (1196660) 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().
        2024-06-02 11:48:46.672  - error: sonos.0 (1196660) unhandled promise rejection: Cannot read properties of undefined (reading 'id')
        2024-06-02 11:48:46.675  - error: sonos.0 (1196660) TypeError: Cannot read properties of undefined (reading 'id')
            at syncConfig (/opt/iobroker/node_modules/iobroker.sonos/main.js:2029:71)
        2024-06-02 11:48:46.677  - error: sonos.0 (1196660) Cannot read properties of undefined (reading 'id')
        2024-06-02 11:48:46.692  - info: sonos.0 (1196660) terminating
        2024-06-02 11:48:46.693  - info: sonos.0 (1196660) terminating
        2024-06-02 11:48:46.695  - warn: sonos.0 (1196660) Terminated (UNCAUGHT_EXCEPTION): Without reason
        2024-06-02 11:48:47.199  - info: sonos.0 (1196660) terminating
        2024-06-02 11:48:47.402  - error: host.ioBroker2 instance system.adapter.sonos.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
        2024-06-02 11:48:47.402  - info: host.ioBroker2 Restart adapter system.adapter.sonos.0 because enabled
        2024-06-02 11:49:17.682  - info: host.ioBroker2 instance system.adapter.sonos.0 started with pid 1196804
        2024-06-02 11:49:20.994  - info: sonos.0 (1196804) starting. Version 3.0.0 in /opt/iobroker/node_modules/iobroker.sonos, node: v18.20.2, js-controller: 5.0.19
        2024-06-02 11:49:22.232  - error: sonos.0 (1196804) 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().
        2024-06-02 11:49:22.234  - error: sonos.0 (1196804) unhandled promise rejection: Cannot read properties of undefined (reading 'id')
        2024-06-02 11:49:22.238  - error: sonos.0 (1196804) TypeError: Cannot read properties of undefined (reading 'id')
            at syncConfig (/opt/iobroker/node_modules/iobroker.sonos/main.js:2029:71)
        2024-06-02 11:49:22.240  - error: sonos.0 (1196804) Cannot read properties of undefined (reading 'id')
        2024-06-02 11:49:22.254  - info: sonos.0 (1196804) terminating
        2024-06-02 11:49:22.256  - info: sonos.0 (1196804) terminating
        2024-06-02 11:49:22.259  - warn: sonos.0 (1196804) Terminated (UNCAUGHT_EXCEPTION): Without reason
        2024-06-02 11:49:22.764  - info: sonos.0 (1196804) terminating
        2024-06-02 11:49:23.034  - error: host.ioBroker2 instance system.adapter.sonos.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
        2024-06-02 11:49:23.035  - info: host.ioBroker2 Restart adapter system.adapter.sonos.0 because enabled
        2024-06-02 11:49:23.035  - warn: host.ioBroker2 Do not restart adapter system.adapter.sonos.0 because restart loop detected```
        Thomas Braun 1 Reply Last reply Reply Quote 0
        • Thomas Braun
          Thomas Braun Most Active @SmartHomie last edited by Thomas Braun

          Hier startet der Adapter zwar, meckert aber einiges an:

          2024-06-02 12:05:36.075  - warn: admin.0 (817993) sonos has an invalid jsonConfig: [{"instancePath":"/items/devicesTab/items/_sendto","schemaPath":"#/definitions/sendToProps/additionalProperties","keyword":"additionalProperties","params":{"additionalProperty":"timeout"},"message":"must NOT have additional properties"},{"instancePath":"/items/devicesTab","schemaPath":"#/properties/items/patternProperties/%5E.%2B/allOf/8/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"},{"instancePath":"","schemaPath":"#/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"}]
          2024-06-02 12:05:36.587  - info: sonos.0 (829438) starting. Version 3.0.0 in /opt/iobroker/node_modules/iobroker.sonos, node: v20.14.0, js-controller: 6.0.1-alpha.0-20240529-9dbeeb628
          2024-06-02 12:05:36.691  - info: sonos.0 (829438) Method "createDevice" is deprecated and will be removed in js-controller 7, use "extendObject/setObjectNotExists" instead
          2024-06-02 12:05:36.793  - info: sonos.0 (829438) Method "createChannel" is deprecated and will be removed in js-controller 7, use "extendObject/setObjectNotExists" instead
          2024-06-02 12:05:36.803  - info: sonos.0 (829438) Method "createState" is deprecated and will be removed in js-controller 7, use "extendObject/setObjectNotExists" instead
          2024-06-02 12:05:36.827  - info: sonos.0 (829438) Method "createState" is deprecated and will be removed in js-controller 7, use "extendObject/setObjectNotExists" instead
          2024-06-02 12:05:36.847  - info: sonos.0 (829438) Method "createState" is deprecated and will be removed in js-controller 7, use "extendObject/setObjectNotExists" instead
          2024-06-02 12:05:36.865  - info: sonos.0 (829438) Method "createState" is deprecated and will be removed in js-controller 7, use "extendObject/setObjectNotExists" instead
          2024-06-02 12:05:36.884  - info: sonos.0 (829438) Method "createState" is deprecated and will be removed in js-controller 7, use "extendObject/setObjectNotExists" instead
          2024-06-02 12:05:36.906  - info: sonos.0 (829438) Method "createState" is deprecated and will be removed in js-controller 7, use "extendObject/setObjectNotExists" instead
          
          

          Das ganze mit nodejs@20.

          mcm1957 1 Reply Last reply Reply Quote 0
          • S
            SmartHomie @Dominik_neu last edited by

            @dominik_neu und, Problem gelöst? Keine Ahnung ob der Entwickler des Sonos Adapters das hier im Forum mitliest.

            M 1 Reply Last reply Reply Quote 0
            • M
              mameier1234 @SmartHomie last edited by

              Ich hatte die selben Meldungen ..

              Lösung: Instanz UND Adapter löschen und neu einrichten. Nur die Instanz löschen und wieder anlegen hat es nicht gebracht.

              haus-automatisierung S 2 Replies Last reply Reply Quote 2
              • haus-automatisierung
                haus-automatisierung Developer Most Active @mameier1234 last edited by

                @mameier1234 Dann gibt es wohl eine neue Version einer Abhängigkeit, welche das Problem behebt.

                Wäre sinnvoll wenn der Entwickler eine neue Version freigibt damit das Update automatisch passiert

                1 Reply Last reply Reply Quote 0
                • mcm1957
                  mcm1957 @Thomas Braun last edited by

                  @thomas-braun said in Sonos Adapter probleme:

                  Hier startet der Adapter zwar, meckert aber einiges an:

                  2024-06-02 12:05:36.075  - warn: admin.0 (817993) sonos has an invalid jsonConfig: [{"instancePath":"/items/devicesTab/items/_sendto","schemaPath":"#/definitions/sendToProps/additionalProperties","keyword":"additionalProperties","params":{"additionalProperty":"timeout"},"message":"must NOT have additional properties"},{"instancePath":"/items/devicesTab","schemaPath":"#/properties/items/patternProperties/%5E.%2B/allOf/8/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"},{"instancePath":"","schemaPath":"#/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"}]
                  2024-06-02 12:05:36.587  - info: sonos.0 (829438) starting. Version 3.0.0 in /opt/iobroker/node_modules/iobroker.sonos, node: v20.14.0, js-controller: 6.0.1-alpha.0-20240529-9dbeeb628
                  2024-06-02 12:05:36.691  - info: sonos.0 (829438) Method "createDevice" is deprecated and will be removed in js-controller 7, use "extendObject/setObjectNotExists" instead
                  2024-06-02 12:05:36.793  - info: sonos.0 (829438) Method "createChannel" is deprecated and will be removed in js-controller 7, use "extendObject/setObjectNotExists" instead
                  2024-06-02 12:05:36.803  - info: sonos.0 (829438) Method "createState" is deprecated and will be removed in js-controller 7, use "extendObject/setObjectNotExists" instead
                  2024-06-02 12:05:36.827  - info: sonos.0 (829438) Method "createState" is deprecated and will be removed in js-controller 7, use "extendObject/setObjectNotExists" instead
                  2024-06-02 12:05:36.847  - info: sonos.0 (829438) Method "createState" is deprecated and will be removed in js-controller 7, use "extendObject/setObjectNotExists" instead
                  2024-06-02 12:05:36.865  - info: sonos.0 (829438) Method "createState" is deprecated and will be removed in js-controller 7, use "extendObject/setObjectNotExists" instead
                  2024-06-02 12:05:36.884  - info: sonos.0 (829438) Method "createState" is deprecated and will be removed in js-controller 7, use "extendObject/setObjectNotExists" instead
                  2024-06-02 12:05:36.906  - info: sonos.0 (829438) Method "createState" is deprecated and will be removed in js-controller 7, use "extendObject/setObjectNotExists" instead
                  
                  

                  Das ganze mit nodejs@20.

                  Du hast wahrscheinlich js-controller 6 installiert. Mit js-controller 6 werden diese Methoden deprecated funktionieren aber weiter. Ergo bitte nur ein Issue im Aapzter Repo eröffnen wenn es noch nicht existiert.

                  Thomas Braun 1 Reply Last reply Reply Quote 0
                  • Thomas Braun
                    Thomas Braun Most Active @mcm1957 last edited by

                    @mcm1957

                    Schon läääääängst passiert:

                    https://github.com/ioBroker/ioBroker.sonos/issues/238

                    Grothesk242 created this issue in ioBroker/ioBroker.sonos

                    open Adapter needs some polish #238

                    1 Reply Last reply Reply Quote 0
                    • S
                      SmartHomie @mameier1234 last edited by

                      @mameier1234 DANKKEEE. Das hat bei mir jetzt auch funktioniert. 👍

                      1 Reply Last reply Reply Quote 0
                      • S
                        steffensammet last edited by steffensammet

                        Hat jemand eine Idee für Docker ? Da hat Instanz & Adapter löschen bisher leider nichts gebracht 😞

                        docker official image - v9.1.2
                        admin: v6.17.14
                        js-controller: 5.0.19
                        Node.js: v18.20.3
                        NPM: 10.8.1

                        Habe ich vielleicht ein Problem mit den Ports ??

                        sonos.0
                        2024-06-30 12:10:16.455	debug	Process channel: sonos.0.root.192_168_178_88
                        
                        sonos.0
                        2024-06-30 12:10:16.408	debug	Process channel: sonos.0.root.192_168_178_87
                        
                        sonos.0
                        2024-06-30 12:10:16.358	debug	Process channel: sonos.0.root.192_168_178_86
                        
                        sonos.0
                        2024-06-30 12:10:16.307	debug	Process channel: sonos.0.root.192_168_178_89
                        
                        sonos.0
                        2024-06-30 12:10:16.307	debug	Channels of root: [{"type":"channel","common":{"role":"media.music","name":"Sonos Play:1 Terrasse"},"native":{"ip":"192.168.178.89"},"from":"system.adapter.sonos.0","user":"system.user.admin","ts":1719742183531,"_id":"sonos.0.root.192_168_178_89","acl":{"object":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}},{"type":"channel","common":{"role":"media.music","name":"Sonos AMP Badezimmer"},"native":{"ip":"192.168.178.86"},"from":"system.adapter.sonos.0","user":"system.user.admin","ts":1719742183595,"_id":"sonos.0.root.192_168_178_86","acl":{"object":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}},{"type":"channel","common":{"role":"media.music","name":"Sonos AMP Hobbyraum"},"native":{"ip":"192.168.178.87"},"from":"system.adapter.sonos.0","user":"system.user.admin","ts":1719742183855,"_id":"sonos.0.root.192_168_178_87","acl":{"object":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}},{"type":"channel","common":{"role":"media.music","name":"Sonos AMP Hobbyraum"},"native":{"ip":"192.168.178.88"},"from":"system.adapter.sonos.0","user":"system.user.admin","ts":1719742184125,"_id":"sonos.0.root.192_168_178_88","acl":{"object":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}}]
                        
                        sonos.0
                        2024-06-30 12:10:16.257	debug	Initialize known devices: [{"type":"device","common":{"name":"root"},"native":{},"from":"system.adapter.sonos.0","user":"system.user.admin","ts":1719739575452,"_id":"sonos.0.root","acl":{"object":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}}]
                        
                        sonos.0
                        2024-06-30 12:10:16.164	debug	Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
                        
                        sonos.0
                        2024-06-30 12:10:16.140	info	starting. Version 3.0.0 in /opt/iobroker/node_modules/iobroker.sonos, node: v18.20.3, js-controller: 5.0.19
                        
                        sonos.0
                        2024-06-30 12:10:16.021	debug	States connected to redis: 127.0.0.1:9000
                        
                        sonos.0
                        2024-06-30 12:10:15.918	debug	States create User PubSub Client
                        
                        sonos.0
                        2024-06-30 12:10:15.917	debug	States create System PubSub Client
                        
                        sonos.0
                        2024-06-30 12:10:15.884	debug	Redis States: Use Redis connection: 127.0.0.1:9000
                        
                        sonos.0
                        2024-06-30 12:10:15.826	debug	Objects connected to redis: 127.0.0.1:9001
                        
                        sonos.0
                        2024-06-30 12:10:15.822	debug	Objects client initialize lua scripts
                        
                        sonos.0
                        2024-06-30 12:10:15.722	debug	Objects create User PubSub Client
                        
                        sonos.0
                        2024-06-30 12:10:15.722	debug	Objects create System PubSub Client
                        
                        sonos.0
                        2024-06-30 12:10:15.720	debug	Objects client ready ... initialize now
                        
                        sonos.0
                        2024-06-30 12:10:15.671	debug	Redis Objects: Use Redis connection: 127.0.0.1:9001
                        
                        S 1 Reply Last reply Reply Quote 0
                        • S
                          steffensammet @steffensammet last edited by

                          tatsächlich .... ein Problem mit den Ports ..... 🙂

                          R 1 Reply Last reply Reply Quote 0
                          • R
                            road_runner31 @steffensammet last edited by

                            @steffensammet Welche Ports werden denn benötigt? Muss ich die explizit freigeben?
                            Danke für eine kurze Info.. 🙂

                            S 1 Reply Last reply Reply Quote 0
                            • S
                              steffensammet @road_runner31 last edited by

                              @road_runner31

                              laut meinem Log war es 9000 und 9001;
                              in der Realität habe ich den Container aber von Host zu einer Bridge umgezogen und hatte somit alle Ports verfügbar.

                              Ich hoffe dies hilft dir weiter.
                              Es halt komisch ist, bei Home Assistant funktioniert es "out-of-the-box" ... 😞

                              Friedhofsblond 1 Reply Last reply Reply Quote 0
                              • Friedhofsblond
                                Friedhofsblond @steffensammet last edited by

                                Moin,
                                irgendwie habe ich Ladehemmung 😊
                                Ich wollte den IObroker als Sonos-API-Server nutzen.
                                (wollte per HUE-Taster und Webhook einen Sonos-One steuern)
                                Ich dachte das geht mit dem Sonos-Adapter?
                                Habe die Adapter Web und Sonos installiert und upgedatet.
                                Dann zwei Speaker eingetragen - wird auch alles ausgelesen - keine errors im Log.
                                Nun wollte ich per http einen Befehl senden z.B. volume 20 - also 20% Lautstärke.

                                "http://192.168.115.29:5005/Wohnzimmer/volume/20"

                                Schmeiß ich das einfach so in irgendeinen Browser - irgendwie steh ich auf dem Schlauch.

                                Danke für einen Denkanstoß

                                Friedhofsblond 1 Reply Last reply Reply Quote 0
                                • Friedhofsblond
                                  Friedhofsblond @Friedhofsblond last edited by

                                  Moin,
                                  Habe den Api-Server testweise erstmal auf einem Raspi-Z installiert.
                                  Soweit läuft das, alle Speaker werden erkannt (auch mit neuer Firmware).
                                  Wie installiere ich den Api-Server nun richtig auf dem iob ?
                                  Ich werde den wohl hauptsächlich extern nutzen und im homey webooks versenden. Aber eine Integration/kontrolle im iob wäre schön.
                                  Grüsse

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

                                  Support us

                                  ioBroker
                                  Community Adapters
                                  Donate
                                  FAQ Cloud / IOT
                                  HowTo: Node.js-Update
                                  HowTo: Backup/Restore
                                  Downloads
                                  BLOG

                                  563
                                  Online

                                  31.6k
                                  Users

                                  79.4k
                                  Topics

                                  1.3m
                                  Posts

                                  9
                                  17
                                  848
                                  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