Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Skripten / Logik
    4. Bose Soundtouch steuern

    NEWS

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Bose Soundtouch steuern

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

      Hallo Leute.

      Es gibt zwei neue Versionen auf Github:

      • 0.0.10 - erster Versuch von multi-room (zone) playEverywhere
      [https://github.com/SwedishChef1/iobroke … ball/zones](https://github.com/SwedishChef1/iobroker.bosesoundtouch/tarball/zones)
      
      Einfach den Status 'playEverywhere' im Master-Adapter auf TRUE setzen
      
      • 0.1.1 - now playing: neuer Status 'art' (URL zum aktuellen Song/Album/Radiosender-Bild, falls vorhanden)

        https://github.com/SwedishChef1/iobroke … all/master

      Sobald playEverywhere grob funktioniert (bitte um euer Feedback, ich konnte das mit nur einer Box nicht wirklich testen), werde ich das auf 'master' mergen.

      1 Reply Last reply Reply Quote 0
      • N
        Nanouk last edited by

        Hallo und schönen 3 Advent euch allen.

        Wie kann ich die playEverywhere Version installieren?

        Ich bekomme immer 404 Fehler.

        Wie muss der Link aussehen um es im Admin zu installieren?

        Grüße,

        Nanouk

        1 Reply Last reply Reply Quote 0
        • SwedishChef
          SwedishChef last edited by

          Hallo Nanouk,

          Sorry, ich hab die links einfach aus dem Browser kopiert. Sind in meinem vorigen Post korrigiert.

          1 Reply Last reply Reply Quote 0
          • apollon77
            apollon77 last edited by

            Wann stellst DU den Adapter den mal auf npm und ins ioBroker repo? Also für "latest" ist er allemal stabil genug!! das macht dann einiges einfacher

            1 Reply Last reply Reply Quote 0
            • SwedishChef
              SwedishChef last edited by

              @apollon77:

              Wann stellst DU den Adapter den mal auf npm und ins ioBroker repo? Also für "latest" ist er allemal stabil genug!! das macht dann einiges einfacher `
              Was ist hier zu tun? Brauche hier Unterstützung, soll ja auch das repo laut einem GitHub issue auf ioBroker.bosesoundtouch (großes B) umbenennen. Möchte nichts kaputt machen…

              1 Reply Last reply Reply Quote 0
              • apollon77
                apollon77 last edited by

                Ok,

                1.) Umbenennen: alles committen, lokal löschen, bei Github umbenennen, neu lokal auschecken

                2.) npm … https://docs.npmjs.com/getting-started/ ... m-packages

                3.) Repo: https://github.com/ioBroker/ioBroker.re ... positories

                das github ioBroker.repositories forken auf Github, auschecken, Deinen Adapter eintragen (nimm einen der anderen als Blaupause), alphabetisch einsortieren und am besten erstmal nur ins "Latest" file. Dann Pull-Request stellen.

                Vorher checke nochmal deine io-package.json (Authors sollte korrekt gefüllt sein) und package.json das da alles passt.

                Und (falls nicht gemacht) Testing travis-ci.org/appveyor bei dir aktivieren

                1 Reply Last reply Reply Quote 0
                • apollon77
                  apollon77 last edited by

                  Ansonsten noch eine Idee: Macht es sinn die "presets" regelmäßig neu einzulesen? Einmal am Tag oder so?

                  Ich habe gestern bei mir was geändert und ioBroker kennt immer noch die Alten infos … Klar Adapter-Restart löst es, aber vllt so ein "Einmal am Tag" (oder in h konfigurierbar) wäre vllt sinnvoll.

                  Ingo

                  1 Reply Last reply Reply Quote 0
                  • D
                    der_Auge last edited by

                    Hallo zusammen,

                    erst einmal ein Dank an den Entwickler und die Unterstützer.

                    Habe mir den Adapter auch über Github installiert.

                    Folgendes steht im LOG:

                    ! 2017-12-18 07:21:01.699 - [32minfo[39m: iobroker url "https://github.com/SwedishChef1/iobroke … all/master" --debug
                    ! 2017-12-18 07:21:02.412 - [32minfo[39m: iobroker install https://github.com/SwedishChef1/iobroke ... all/master
                    ! 2017-12-18 07:21:02.626 - [32minfo[39m: iobroker npm install https://github.com/SwedishChef1/iobroke ... all/master --production --prefix "/opt/iobroker" (System call)
                    ! 2017-12-18 07:21:36.255 - [32minfo[39m: iobroker npm WARN addRemoteGit Error: not found: gitnpm WARN addRemoteGit at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:14:12)
                    ! npm WARN addRemoteGit at F (/usr/lib/node_modules/npm/node_modules/which/which.js:69:19)
                    ! npm WARN addRemoteGit at E (/usr/lib/node_modules/npm/node_modules/which/which.js:81:29)
                    ! npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/which.js:90:16
                    ! npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:44:5
                    ! npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/access.js:8:5
                    ! npm WARN addRemoteGit at FSReqWrap.oncomplete (fs.js:123:15)
                    ! npm WARN addRemoteGit git://github.com/noopkat/browser-serialport.git#api-updates resetting remote /root/.npm/_git-remotes/git-github-com-noopkat-browser-serialport-git-api-updates-0f82caf3 because of error: { Error: not found: git
                    ! npm WARN addRemoteGit at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:14:12)
                    ! npm WARN addRemoteGit at F (/usr/lib/node_modules/npm/node_modules/which/which.js:69:19)
                    ! npm WARN addRemoteGit
                    ! 2017-12-18 07:21:36.268 - [32minfo[39m: iobroker at E (/usr/lib/node_modules/npm/node_modules/which/which.js:81:29)npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/which.js:90:16
                    ! npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:44:5
                    ! npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/access.js:8:5
                    ! npm WARN addRemoteGit at FSReqWrap.oncomplete (fs.js:123:15) code: 'ENOGIT' }
                    ! npm WARN addRemoteGit Error: not found: git
                    ! npm WARN addRemoteGit at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:14:12)
                    ! npm WARN addRemoteGit at F (/usr/lib/node_modules/npm/node_modules/which/which.js:69:19)
                    ! npm WARN addRemoteGit at E (/usr/lib/node_modules/npm/node_modules/which/which.js:81:29)
                    ! npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/which.js:90:16
                    ! npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:44:5
                    ! npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/access.js:8:5
                    ! npm WARN addRemoteGit at FSReqWrap.oncomplete (fs.js:123:15)
                    ! npm WARN addRemoteGit git://github.com/noopkat/js-stk500v1.git#avrgirl resetting remote /root/.npm/_git-remotes/git-github-com-noopkat-js-stk500v1-git-avrgirl-31bc3a47 because of error: { Error: not found: git
                    ! npm WARN addRemoteGit at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:14:12)
                    ! npm WARN addRemoteGit at F (/usr/lib/node_modules/npm/node_modules/which/which.js:69:19)
                    ! npm WARN addRemoteGit at E (/usr/lib/node_modules/npm/node_modules/which/which.js:81:29)
                    ! npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/which.js:90:16
                    ! npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:44:5
                    ! npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/access.js:8:5
                    ! npm WARN addRemoteGit at FSReqWrap.oncomplete (fs.js:123:15) code: 'ENOGIT' }
                    ! 2017-12-18 07:21:36.299 - [32minfo[39m: iobroker npm ERR! git clone --template=/root/.npm/_git-remotes/_templates --mirror git://github.com/noopkat/browser-serialport.git /root/.npm/_git-remotes/git-github-com-noopkat-browser-serialport-git-api-updates-0f82caf3: undefinednpm ERR! git clone --template=/root/.npm/_git-remotes/_templates --mirror git://github.com/noopkat/browser-serialport.git /root/.npm/_git-remotes/git-github-com-noopkat-browser-serialport-git-api-updates-0f82caf3: undefined
                    ! 2017-12-18 07:21:36.349 - [32minfo[39m: iobroker npm ERR! git clone --template=/root/.npm/_git-remotes/_templates --mirror git://github.com/noopkat/js-stk500v1.git /root/.npm/_git-remotes/git-github-com-noopkat-js-stk500v1-git-avrgirl-31bc3a47: undefinednpm ERR! git clone --template=/root/.npm/_git-remotes/_templates --mirror git://github.com/noopkat/js-stk500v1.git /root/.npm/_git-remotes/git-github-com-noopkat-js-stk500v1-git-avrgirl-31bc3a47: undefined
                    ! 2017-12-18 07:22:00.040 - [32minfo[39m: host.NUC instance system.adapter.dwd.0 started with pid 21593
                    ! 2017-12-18 07:22:01.713 - [32minfo[39m: dwd.0 starting. Version 2.2.1 in /opt/iobroker/node_modules/iobroker.dwd, node: v6.12.0
                    ! 2017-12-18 07:22:02.853 - [32minfo[39m: host.NUC instance system.adapter.dwd.0 terminated with code 0 (OK)
                    ! 2017-12-18 07:22:04.552 - [32minfo[39m: iobroker > usb@1.3.1 install /opt/iobroker/node_modules/usb
                    ! > node-pre-gyp install --fallback-to-build
                    ! 2017-12-18 07:22:06.288 - [32minfo[39m: iobroker node-pre-gyp
                    ! 2017-12-18 07:22:06.289 - [32minfo[39m: iobroker
                    ! 2017-12-18 07:22:06.293 - [32minfo[39m: iobroker ERR! Tried to download(404): https://github.com/tessel/node-usb/rele ... x64.tar.gz node-pre-gyp ERR! Pre-built binaries not found for usb@1.3.1 and node@6.12.0 (node-v48 ABI, glibc) (falling back to source compile with node-gyp)
                    ! 2017-12-18 07:22:08.628 - [32minfo[39m: iobroker make: Verzeichnis „/opt/iobroker/node_modules/usb/build“ wird betreten
                    ! 2017-12-18 07:22:08.631 - [32minfo[39m: iobroker CC(target) Release/obj.target/libusb/libusb/libusb/core.o
                    ! 2017-12-18 07:22:09.380 - [32minfo[39m: iobroker CC(target) Release/obj.target/libusb/libusb/libusb/descriptor.o
                    ! 2017-12-18 07:22:10.033 - [32minfo[39m: iobroker CC(target) Release/obj.target/libusb/libusb/libusb/hotplug.o
                    ! 2017-12-18 07:22:10.286 - [32minfo[39m: iobroker CC(target) Release/obj.target/libusb/libusb/libusb/io.o
                    ! 2017-12-18 07:22:10.944 - [32minfo[39m: iobroker CC(target) Release/obj.target/libusb/libusb/libusb/strerror.o
                    ! 2017-12-18 07:22:11.093 - [32minfo[39m: iobroker CC(target) Release/obj.target/libusb/libusb/libusb/sync.o
                    ! 2017-12-18 07:22:11.308 - [32minfo[39m: iobroker CC(target) Release/obj.target/libusb/libusb/libusb/os/poll_posix.o
                    ! 2017-12-18 07:22:11.439 - [32minfo[39m: iobroker CC(target) Release/obj.target/libusb/libusb/libusb/os/threads_posix.o
                    ! 2017-12-18 07:22:11.546 - [32minfo[39m: iobroker CC(target) Release/obj.target/libusb/libusb/libusb/os/linux_usbfs.o
                    ! 2017-12-18 07:22:12.938 - [32minfo[39m: iobroker CC(target) Release/obj.target/libusb/libusb/libusb/os/linux_udev.o
                    ! 2017-12-18 07:22:13.031 - [32minfo[39m: iobroker ../libusb/libusb/os/linux_udev.c:40:21: fatal error: libudev.h: Datei oder Verzeichnis nicht gefundencompilation terminated.
                    ! 2017-12-18 07:22:13.037 - [32minfo[39m: iobroker libusb.target.mk:133: die Regel für Ziel „Release/obj.target/libusb/libusb/libusb/os/linux_udev.o“ scheitertemake: Verzeichnis „/opt/iobroker/node_modules/usb/build“ wird verlassen
                    ! make: *** [Release/obj.target/libusb/libusb/libusb/os/linux_udev.o] Fehler 1
                    ! 2017-12-18 07:22:13.042 - [32minfo[39m: iobroker gyp
                    ! 2017-12-18 07:22:13.046 - [32minfo[39m: iobroker ERR! build error
                    ! 2017-12-18 07:22:13.052 - [32minfo[39m: iobroker gyp
                    ! 2017-12-18 07:22:13.053 - [32minfo[39m: iobroker ERR! stack
                    ! 2017-12-18 07:22:13.056 - [32minfo[39m: iobroker Error: make failed with exit code: 2gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
                    ! gyp ERR! stack at emitTwo (events.js:106:13)
                    ! 2017-12-18 07:22:13.057 - [32minfo[39m: iobroker gyp ERR! stack
                    ! 2017-12-18 07:22:13.058 - [32minfo[39m: iobroker at ChildProcess.emit (events.js:191:7)gyp
                    ! 2017-12-18 07:22:13.059 - [32minfo[39m: iobroker ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)
                    ! 2017-12-18 07:22:13.064 - [32minfo[39m: iobroker gyp ERR! System Linux 4.4.0-101-genericgyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "–fallback-to-build" "--module=/opt/iobroker/node_modules/usb/src/binding/usb_bindings.node" "--module_name=usb_bindings" "--module_path=/opt/iobroker/node_modules/usb/src/binding"
                    ! gyp ERR! cwd /opt/iobroker/node_modules/usb
                    ! 2017-12-18 07:22:13.069 - [32minfo[39m: iobroker gyp ERR! node -v v6.12.0gyp ERR! node-gyp -v v3.4.0
                    ! gyp ERR! not ok
                    ! 2017-12-18 07:22:13.085 - [32minfo[39m: iobroker node-pre-gyp ERR! build error node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/opt/iobroker/node_modules/usb/src/binding/usb_bindings.node --module_name=usb_bindings --module_path=/opt/iobroker/node_modules/usb/src/binding' (1)
                    ! node-pre-gyp ERR! stack at ChildProcess. <anonymous>(/opt/iobroker/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
                    ! node-pre-gyp ERR! stack at emitTwo (events.js:106:13)
                    ! node-pre-gyp ERR! stack at ChildProcess.emit (events.js:191:7)
                    ! node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:920:16)
                    ! node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:230:5)
                    ! node-pre-gyp ERR! System Linux 4.4.0-101-generic
                    ! node-pre-gyp
                    ! 2017-12-18 07:22:13.092 - [32minfo[39m: iobroker ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
                    ! 2017-12-18 07:22:13.096 - [32minfo[39m: iobroker node-pre-gyp ERR! cwd /opt/iobroker/node_modules/usbnode-pre-gyp ERR! node -v v6.12.0
                    ! node-pre-gyp ERR! node-pre-gyp -v v0.6.39
                    ! node-pre-gyp ERR! not ok
                    ! Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/opt/iobroker/node_modules/usb/src/binding/usb_bindings.node --module_name=usb_bindings --module_path=/opt/iobroker/node_modules/usb/src/binding' (1)
                    ! 2017-12-18 07:22:13.135 - [32minfo[39m: iobroker > mdns@2.3.4 install /opt/iobroker/node_modules/mdns
                    ! > node-gyp rebuild
                    ! 2017-12-18 07:22:14.595 - [32minfo[39m: iobroker make: Verzeichnis „/opt/iobroker/node_modules/mdns/build“ wird betreten
                    ! 2017-12-18 07:22:14.606 - [32minfo[39m: iobroker CXX(target) Release/obj.target/dns_sd_bindings/src/dns_sd.o
                    ! 2017-12-18 07:22:14.852 - [32minfo[39m: iobroker In file included from ../src/dns_sd.cpp:1:0:../src/mdns.hpp:32:20: fatal error: dns_sd.h: Datei oder Verzeichnis nicht gefunden
                    ! compilation terminated.
                    ! 2017-12-18 07:22:14.855 - [32minfo[39m: iobroker dns_sd_bindings.target.mk:152: die Regel für Ziel „Release/obj.target/dns_sd_bindings/src/dns_sd.o“ scheitertemake: Verzeichnis „/opt/iobroker/node_modules/mdns/build“ wird verlassen
                    ! make: *** [Release/obj.target/dns_sd_bindings/src/dns_sd.o] Fehler 1
                    ! 2017-12-18 07:22:14.863 - [32minfo[39m: iobroker gyp
                    ! 2017-12-18 07:22:14.866 - [32minfo[39m: iobroker ERR! build error
                    ! 2017-12-18 07:22:14.878 - [32minfo[39m: iobroker gyp ERR! stack Error: make failed with exit code: 2gyp ERR! stack
                    ! 2017-12-18 07:22:14.885 - [32minfo[39m: iobroker at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)gyp ERR! stack at emitTwo (events.js:106:13)
                    ! gyp ERR! stack at ChildProcess.emit (events.js:191:7)
                    ! gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)
                    ! gyp ERR! System Linux 4.4.0-101-generic
                    ! gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
                    ! gyp ERR! cwd /opt/iobroker/node_modules/mdns
                    ! gyp ERR! node -v v6.12.0
                    ! gyp ERR! node-gyp -v v3.4.0
                    ! gyp ERR! not ok
                    ! > serialport@4.0.7 install /opt/iobroker/node_modules/serialport
                    ! > node-pre-gyp install –fallback-to-build
                    ! 2017-12-18 07:22:18.445 - [32minfo[39m: iobroker [serialport] Success: "/opt/iobroker/node_modules/serialport/build/Release/serialport.node" is installed via remote
                    ! 2017-12-18 07:22:30.111 - [32minfo[39m: iobroker iobroker.core@1.0.0 /opt/iobroker├── async@2.6.0 extraneous
                    ! ├── awty@0.1.0 extraneous
                    ! ├── chip.avr.avr109@1.1.0 extraneous
                    ! ├── colors@1.1.2 extraneous
                    ! ├─┬ iobroker.bosesoundtouch@0.1.0
                    ! │ ├── es6-promise@4.1.1
                    ! │ ├── string-format@0.5.0
                    ! │ ├─┬ ws@3.3.3
                    ! │ │ ├── async-limiter@1.0.0
                    ! │ │ └── ultron@1.1.1
                    ! │ └─┬ xml2js@0.4.19
                    ! │ ├── sax@1.2.4
                    ! │ └── xmlbuilder@9.0.4
                    ! ├── serialport@4.0.7 extraneous
                    ! └── stk500-v2@1.0.2 extraneous
                    ! 2017-12-18 07:22:30.118 - [32minfo[39m: iobroker npm WARN optional SKIPPING OPTIONAL DEPENDENCY: xpc-connection@~0.1.4 (node_modules/iobroker.radar/node_modules/noble/node_modules/xpc-connection):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for xpc-connection@0.1.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
                    ! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: browser-serialport@git://github.com/noopkat/browser-serialport.git#api-updates (node_modules/avrgirl-arduino/node_modules/browser-serialport):
                    ! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: not found: git
                    ! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: stk500@git://github.com/noopkat/js-stk500v1.git#avrgirl (node_modules/avrgirl-arduino/node_modules/stk500):
                    ! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: not found: git
                    ! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: usb@1.3.1 (node_modules/usb):
                    ! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: usb@1.3.1 install: node-pre-gyp install –fallback-to-build
                    ! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
                    ! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: mdns@2.3.4 (node_modules/mdns):
                    ! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: mdns@2.3.4 install: node-gyp rebuild
                    ! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
                    ! 2017-12-18 07:22:30.226 - [32minfo[39m: iobroker got /opt/iobroker/node_modules/iobroker.bosesoundtouch/admin
                    ! 2017-12-18 07:22:30.264 - [32minfo[39m: iobroker upload [2] bosesoundtouch.admin /opt/iobroker/node_modules/iobroker.bosesoundtouch/admin/words.js words.js application/javascript
                    ! 2017-12-18 07:22:30.341 - [32minfo[39m: iobroker upload [1] bosesoundtouch.admin /opt/iobroker/node_modules/iobroker.bosesoundtouch/admin/index.html index.html text/html
                    ! 2017-12-18 07:22:30.418 - [32minfo[39m: iobroker upload [0] bosesoundtouch.admin /opt/iobroker/node_modules/iobroker.bosesoundtouch/admin/bosesoundtouch.png bosesoundtouch.png image/png
                    ! 2017-12-18 07:22:30.533 - [32minfo[39m: iobroker exit 0
                    ! 2017-12-18 07:22:31.035 - [32minfo[39m: host.NUC Update repository "online" under "https://raw.githubusercontent.com/ioBro … -dist.json"[/spoiler]</anonymous>

                    Nach der Installation sind mir noch ein paar Kleinigkeiten aufgefallen.

                    Adapter-Seite:

                    • es fehle das kleine und das große Bild bei MousOver

                    • in der Beschreibung steht noch die Infos aus der Vorlage (Template)

                    Ansonsten bin ich Begeistert.

                    Nun werde ich einen weiteren Nutzer von ioBroker überzeugen können

                    Frage: Zum umschalten unter Objekte -> presents > key die Zahl 1 oder 2 oder…. eintragen?

                    Gruß

                    Jürgen

                    1 Reply Last reply Reply Quote 0
                    • M
                      Master77 last edited by

                      Hi

                      Als Datenpunkt musst du Key auswählen und als Wert im Widget dann PRESET_1 beispielsweise eintragen.

                      Gesendet von meinem HUAWEI NXT-L29 mit Tapatalk

                      1 Reply Last reply Reply Quote 0
                      • apollon77
                        apollon77 last edited by

                        Alle aktuell möglichen "Key"-Werte sind auf der Github REDME.md aufgelistet

                        1 Reply Last reply Reply Quote 0
                        • D
                          der_Auge last edited by

                          @apollon77:

                          Alle aktuell möglichen "Key"-Werte sind auf der Github REDME.md aufgelistet `

                          Super

                          nun habe ich es gefunden

                          key
                          
                          One of the following keys to send:
                          
                          PLAY 
                          PAUSE 
                          STOP 
                          PREV_TRACK 
                          NEXT_TRACK 
                          THUMBS_UP 
                          THUMBS_DOWN 
                          BOOKMARK 
                          POWER 
                          MUTE 
                          VOLUME_UP 
                          VOLUME_DOWN 
                          PRESET_1 
                          PRESET_2 
                          PRESET_3 
                          PRESET_4 
                          PRESET_5 
                          PRESET_6 
                          AUX_INPUT 
                          SHUFFLE_OFF 
                          SHUFFLE_ON 
                          REPEAT_OFF 
                          REPEAT_ONE 
                          REPEAT_ALL 
                          PLAY_PAUSE 
                          ADD_FAVORITE 
                          REMOVE_FAVORITE 
                          INVALID_KEY
                          
                          
                          1 Reply Last reply Reply Quote 0
                          • K
                            kekel last edited by

                            Hallo zusammen,

                            ich muss jetzt unbedingt ein ganz großes Lob an alle Beteiligten aussprechen.

                            Ich hatte gestern den Gedanken, dass es doch schön wäre wenn meine Soundtouch-Geräte aufs Wort gehorchen würden … und stelle fest, Super, das gibt es ja schon.

                            Danke!

                            Besonders faszinierend finde ich die zukünftige Möglichkeit von PlayEverywhere (MultiRoom). Ganz hervorragend wäre es, wenn man dabei noch Gruppen bilden könnte.

                            Frei nach dem Motto "Alle" ... also wirklich alle oder z.B "Wohnzimmer" ... also nur die Geräte im Wohnzimmer.

                            Ich wünsche euch schöne und geruhsame Feiertage.

                            1 Reply Last reply Reply Quote 0
                            • apollon77
                              apollon77 last edited by

                              @SwedishChef: siehe Github Pull-Request: Damit tut Testing dann. Musst nur noch im package.json den Author korrigieren 😉

                              Und sobald Du es auch npm hast kann ich auch Discovery Adapter releasen wo das Soundtouch Erkennung drin ist

                              1 Reply Last reply Reply Quote 0
                              • D
                                der_Auge last edited by

                                Super Sache

                                mein Zwischenstand im VIS
                                3361_image_2017-12-19_at_19.36.32.jpeg

                                nun müsste ich die Tasten (die über dem Bild liegen) noch transparent werden. :?:

                                Gruß

                                Jürgen

                                1 Reply Last reply Reply Quote 0
                                • SwedishChef
                                  SwedishChef last edited by

                                  Hallo an alle, die mir helfen können:

                                  'npm publish' liefert folgendes:

                                  ! 0 info it worked if it ends with ok
                                  ! 1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
                                  ! 1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
                                  ! 1 verbose cli 'publish' ]
                                  ! 2 info using npm@5.4.2
                                  ! 3 info using node@v8.7.0
                                  ! 4 verbose npm-session e37bebc5daa4975e
                                  ! 5 verbose publish [ '.' ]
                                  ! 6 info lifecycle ioBroker.bosesoundtouch@0.1.2~prepublish: ioBroker.bosesoundtouch@0.1.2
                                  ! 7 info lifecycle ioBroker.bosesoundtouch@0.1.2~prepare: ioBroker.bosesoundtouch@0.1.2
                                  ! 8 info lifecycle ioBroker.bosesoundtouch@0.1.2~prepublishOnly: ioBroker.bosesoundtouch@0.1.2
                                  ! 9 info lifecycle ioBroker.bosesoundtouch@0.1.2~prepack: ioBroker.bosesoundtouch@0.1.2
                                  ! 10 info lifecycle ioBroker.bosesoundtouch@0.1.2~postpack: ioBroker.bosesoundtouch@0.1.2
                                  ! 11 verbose getPublishConfig undefined
                                  ! 12 silly mapToRegistry name ioBroker.bosesoundtouch
                                  ! 13 silly mapToRegistry using default registry
                                  ! 14 silly mapToRegistry registry https://registry.npmjs.org/
                                  ! 15 silly mapToRegistry data { type: 'tag',
                                  ! 15 silly mapToRegistry registry: true,
                                  ! 15 silly mapToRegistry where: undefined,
                                  ! 15 silly mapToRegistry raw: 'ioBroker.bosesoundtouch',
                                  ! 15 silly mapToRegistry name: 'ioBroker.bosesoundtouch',
                                  ! 15 silly mapToRegistry escapedName: 'ioBroker.bosesoundtouch',
                                  ! 15 silly mapToRegistry scope: undefined,
                                  ! 15 silly mapToRegistry rawSpec: '',
                                  ! 15 silly mapToRegistry saveSpec: null,
                                  ! 15 silly mapToRegistry fetchSpec: 'latest',
                                  ! 15 silly mapToRegistry gitRange: undefined,
                                  ! 15 silly mapToRegistry gitCommittish: undefined,
                                  ! 15 silly mapToRegistry hosted: undefined }
                                  ! 16 silly mapToRegistry uri https://registry.npmjs.org/ioBroker.bosesoundtouch
                                  ! 17 verbose publish registryBase https://registry.npmjs.org/
                                  ! 18 silly publish uploading C:\Temp\npm-13924-69337115\tmp\fromDir-4370ad97\package.tgz
                                  ! 19 verbose request uri https://registry.npmjs.org/ioBroker.bosesoundtouch
                                  ! 20 verbose request sending authorization for write operation
                                  ! 21 info attempt registry request try #1 at 16:29:46
                                  ! 22 verbose request using bearer token for auth
                                  ! 23 verbose request id 0cdceb557cee2578
                                  ! 24 http request PUT https://registry.npmjs.org/ioBroker.bosesoundtouch
                                  ! 25 http 400 https://registry.npmjs.org/ioBroker.bosesoundtouch
                                  ! 26 verbose headers { 'content-type': 'application/json',
                                  ! 26 verbose headers 'cache-control': 'max-age=300',
                                  ! 26 verbose headers 'content-length': '67',
                                  ! 26 verbose headers 'accept-ranges': 'bytes',
                                  ! 26 verbose headers date: 'Fri, 22 Dec 2017 15:29:46 GMT',
                                  ! 26 verbose headers via: '1.1 varnish',
                                  ! 26 verbose headers connection: 'keep-alive',
                                  ! 26 verbose headers 'x-served-by': 'cache-hhn1527-HHN',
                                  ! 26 verbose headers 'x-cache': 'MISS',
                                  ! 26 verbose headers 'x-cache-hits': '0',
                                  ! 26 verbose headers 'x-timer': 'S1513956586.701662,VS0,VE781',
                                  ! 26 verbose headers vary: 'Accept-Encoding, Accept' }
                                  ! 27 error publish Failed PUT 400
                                  ! 28 verbose stack Error: "ioBroker.bosesoundtouch" is invalid for new packages : ioBroker.bosesoundtouch
                                  ! 28 verbose stack at makeError (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-registry-client\lib\request.js:314:12)
                                  ! 28 verbose stack at RegClient. <anonymous>(C:\Program Files\nodejs\node_modules\npm\node_modules\npm-registry-client\lib\request.js:302:14)
                                  ! 28 verbose stack at Request._callback (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-registry-client\lib\request.js:216:14)
                                  ! 28 verbose stack at Request.self.callback (C:\Program Files\nodejs\node_modules\npm\node_modules\request\request.js:188:22)
                                  ! 28 verbose stack at emitTwo (events.js:125:13)
                                  ! 28 verbose stack at Request.emit (events.js:213:7)
                                  ! 28 verbose stack at Request. <anonymous>(C:\Program Files\nodejs\node_modules\npm\node_modules\request\request.js:1171:10)
                                  ! 28 verbose stack at emitOne (events.js:115:13)
                                  ! 28 verbose stack at Request.emit (events.js:210:7)
                                  ! 28 verbose stack at IncomingMessage. <anonymous>(C:\Program Files\nodejs\node_modules\npm\node_modules\request\request.js:1091:12)
                                  ! 28 verbose stack at Object.onceWrapper (events.js:314:30)
                                  ! 28 verbose stack at emitNone (events.js:110:20)
                                  ! 28 verbose stack at IncomingMessage.emit (events.js:207:7)
                                  ! 28 verbose stack at endReadableNT (_stream_readable.js:1057:12)
                                  ! 28 verbose stack at _combinedTickCallback (internal/process/next_tick.js:138:11)
                                  ! 28 verbose stack at process._tickCallback (internal/process/next_tick.js:180:9)
                                  ! 29 verbose statusCode 400
                                  ! 30 verbose pkgid ioBroker.bosesoundtouch
                                  ! 31 verbose cwd D:\Documents\JavaScript\ioBroker.bosesoundtouch
                                  ! 32 verbose Windows_NT 10.0.16299
                                  ! 33 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "publish"
                                  ! 34 verbose node v8.7.0
                                  ! 35 verbose npm v5.4.2
                                  ! 36 error code E400
                                  ! 37 error "ioBroker.bosesoundtouch" is invalid for new packages : ioBroker.bosesoundtouch
                                  ! 38 verbose exit [ 1, true ]</anonymous></anonymous></anonymous>
                                  Zuvor hatte ich schon einmal V0.1.1 erfolgreich published, allerdings noch fehlerhaft mit 'iobroker.bosesoundtouch' als Paketname. Also 'npm –force unpublish' -> name korrigiert (ioBroker.bosesoundtouch) -> version hoch auf 0.1.2 -> und dann das ;(

                                  Wie komme ich aus dem Schlamassel wieder raus?

                                  Danke schon mal im Voraus.

                                  1 Reply Last reply Reply Quote 0
                                  • apollon77
                                    apollon77 last edited by

                                    Nur das GitHub repo muss ioBroker sein. Das npm Paket hat „iobroker“ im Namen. Das ist schon korrekt so. Also in per Package.json muss es kleingeschrieben sein

                                    1 Reply Last reply Reply Quote 0
                                    • D
                                      der_Auge last edited by

                                      Guten Morgen

                                      nach Softwareupdate auf eine Sound10 funktionieren die Programmtasten nicht mehr

                                      Habe mal die Taste 1 abgehängt

                                      ! [{"tpl":"tplJquiRadioList","data":{"oid":"bosesoundtouch.0.key","g_fixed":false,"g_visibility":false,"g_css_font_text":true,"g_css_background":false,"g_css_shadow_padding":false,"g_css_border":false,"g_gestures":false,"g_signals":false,"visibility-cond":"==","visibility-val":1,"visibility-groups-action":"hide","values":"PRESET_1","texts":"1","signals-cond-0":"==","signals-val-0":true,"signals-icon-0":"/vis/signals/lowbattery.png","signals-icon-size-0":0,"signals-blink-0":false,"signals-horz-0":0,"signals-vert-0":0,"signals-hide-edit-0":false,"signals-cond-1":"==","signals-val-1":true,"signals-icon-1":"/vis/signals/lowbattery.png","signals-icon-size-1":0,"signals-blink-1":false,"signals-horz-1":0,"signals-vert-1":0,"signals-hide-edit-1":false,"signals-cond-2":"==","signals-val-2":true,"signals-icon-2":"/vis/signals/lowbattery.png","signals-icon-size-2":0,"signals-blink-2":false,"signals-horz-2":0,"signals-vert-2":0,"signals-hide-edit-2":false,"g_last_change":false,"lc-type":"last-change","lc-is-interval":true,"lc-is-moment":false,"lc-format":"","lc-position-vert":"top","lc-position-horz":"right","lc-offset-vert":0,"lc-offset-horz":0,"lc-font-size":"12px","lc-font-family":"","lc-font-style":"","lc-bkg-color":"","lc-color":"","lc-border-width":"0","lc-border-style":"","lc-border-color":"","lc-border-radius":10,"lc-zindex":0},"style":{"left":"448px","top":"364px","width":"50px","height":"50px","z-index":"4"},"widgetSet":"jqui"}]

                                      Geht euch das auch so?

                                      Es läuft die Version 0.1.0

                                      Gruß

                                      Jürgen

                                      1 Reply Last reply Reply Quote 0
                                      • SwedishChef
                                        SwedishChef last edited by

                                        V0.1.3 ist als npm Paket verfügbar und auch der pull request im ioBroker.repositories für den ersten offiziellen Release.

                                        Wie sind die ersten Erfahrungen mit play everywhere am zones branch?

                                        Gesendet von meinem A0001 mit Tapatalk

                                        1 Reply Last reply Reply Quote 0
                                        • apollon77
                                          apollon77 last edited by

                                          Kann bitte auch mal jemand Discovery vom github installieren und schauen ob böse (außer bei mir) korrekt gefunden wird? 😉

                                          Mehrere Zonen und so kann ich leider nicht testen. Hab auch nur ein Gerät 😉

                                          1 Reply Last reply Reply Quote 0
                                          • D
                                            der_Auge last edited by

                                            @SwedishChef:

                                            V0.1.3 ist als npm Paket verfügbar und auch der pull request im ioBroker.repositories für den ersten offiziellen Release.

                                            Wie sind die ersten Erfahrungen mit play everywhere am zones branch? `
                                            bekomme ich leider nicht angezeigt

                                            ich lade den Verwahrungsort von "http://download.iobroker.net/sources-dist-latest.json" herunter

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            1.1k
                                            Online

                                            31.6k
                                            Users

                                            79.6k
                                            Topics

                                            1.3m
                                            Posts

                                            36
                                            286
                                            62045
                                            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