Skip to content
  • Home
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Skripten / Logik
  4. Blockly
  5. [gelöst]mit Mediola Gateway TV über IR einschalten

NEWS

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    18
    1
    774

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    18
    1
    6.2k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    1.5k

[gelöst]mit Mediola Gateway TV über IR einschalten

Scheduled Pinned Locked Moved Solved Blockly
blockly
30 Posts 6 Posters 1.1k Views 4 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • SRo769S Offline
    SRo769S Offline
    SRo769
    wrote on last edited by
    #6

    worüber wird der Fernseher denn abgeschaltet?

    1 Reply Last reply
    0
    • J Offline
      J Offline
      jwedenig
      Most Active
      wrote on last edited by jwedenig
      #7

      Bildschirmfoto 2019-10-15 um 09.26.41.png

      Über den IP Befehl des Samsung Adapters, und "ein"mit dem http Befehl, welcher ein IR Signal an mein Mediola Gateway sendet, da man ja leider den Samsung Fernseher nicht anders einschalten kann mangels Netzwerkverfügbarkeit

      1 Reply Last reply
      0
      • SRo769S Offline
        SRo769S Offline
        SRo769
        wrote on last edited by
        #8

        letztlich meckert das script nur über den Fehler "TypeError [ERR_UNESCAPED_CHARACTERS]: Request path contains unescaped characters" - d.h., der kann den Netzwerkpfad aufgrund eines Fehlers nicht auflösen bzw. die Aktion auslösen.
        Hast du auch den aus Blockly herauskopierten Pfad im Browser getestet?

        Zusätzlich ist der Datenpunkt "MainPowerZone" noch falsch definiert. Er wird mit einer Zahl beschrieben, ist vielleicht aber als Bool o.ä. ausgelegt.

        J 1 Reply Last reply
        0
        • SRo769S SRo769

          letztlich meckert das script nur über den Fehler "TypeError [ERR_UNESCAPED_CHARACTERS]: Request path contains unescaped characters" - d.h., der kann den Netzwerkpfad aufgrund eines Fehlers nicht auflösen bzw. die Aktion auslösen.
          Hast du auch den aus Blockly herauskopierten Pfad im Browser getestet?

          Zusätzlich ist der Datenpunkt "MainPowerZone" noch falsch definiert. Er wird mit einer Zahl beschrieben, ist vielleicht aber als Bool o.ä. ausgelegt.

          J Offline
          J Offline
          jwedenig
          Most Active
          wrote on last edited by
          #9

          @SRo769

          ja, im Browser funktioniert der Pfad

          1 Reply Last reply
          0
          • J Offline
            J Offline
            jwedenig
            Most Active
            wrote on last edited by
            #10

            ja, stimmt, Power zone wird mit true/false definiert, ist aber scheinbar egal, weil der DENON ja funktioniert

            J 1 Reply Last reply
            0
            • J jwedenig

              ja, stimmt, Power zone wird mit true/false definiert, ist aber scheinbar egal, weil der DENON ja funktioniert

              J Offline
              J Offline
              jwedenig
              Most Active
              wrote on last edited by
              #11

              habs jetzt geändert:

              Bildschirmfoto 2019-10-15 um 09.46.53.png

              1 Reply Last reply
              0
              • J Offline
                J Offline
                jwedenig
                Most Active
                wrote on last edited by
                #12

                aktualisiertes Log:

                undefined2019-10-15 09:48:21.095 - info: javascript.1 Stop script script.js.Weldscripts.Alexa_Fernseher_ein
                2019-10-15 09:48:21.100 - info: javascript.0 Stop script script.js.Weldscripts.Alexa_Fernseher_ein
                2019-10-15 09:48:21.129 - info: javascript.0 Start javascript script.js.Weldscripts.Alexa_Fernseher_ein
                2019-10-15 09:48:21.146 - info: javascript.0 script.js.Weldscripts.Alexa_Fernseher_ein: registered 1 subscription and 0 schedules
                2019-10-15 09:48:47.833 - warn: javascript.0 Wrong type of denon.0.zoneMain.powerZone: "string". Please fix, while deprecated and will not work in next versions.
                2019-10-15 09:48:47.840 - warn: javascript.0 at setState (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1258:20)
                2019-10-15 09:48:47.841 - warn: javascript.0 at Object. (script.js.Weldscripts.Alexa_Fernseher_ein:9:5)
                2019-10-15 09:48:47.841 - warn: javascript.0 at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:963:38)
                2019-10-15 09:48:47.841 - warn: javascript.0 at Object.stateChange (/opt/iobroker/node_modules/iobroker.javascript/main.js:364:25)
                2019-10-15 09:48:47.841 - warn: javascript.0 at Object.change (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3706:37)
                2019-10-15 09:48:47.842 - warn: javascript.0 at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInMemClient.js:52:30)
                2019-10-15 09:48:47.842 - warn: javascript.0 at Socket.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
                2019-10-15 09:48:47.842 - warn: javascript.0 at Socket.onevent (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:270:10)
                2019-10-15 09:48:47.842 - warn: javascript.0 at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:228:12)
                2019-10-15 09:48:47.842 - warn: javascript.0 at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
                2019-10-15 09:48:47.843 - warn: javascript.0 at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
                2019-10-15 09:48:47.843 - warn: javascript.0 at Manager.ondecoded (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:332:8)
                2019-10-15 09:48:47.843 - warn: javascript.0 at Decoder. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
                2019-10-15 09:48:47.843 - warn: javascript.0 at Decoder.Emitter.emit (/opt/iobroker/node_modules/component-emitter/index.js:134:20)
                2019-10-15 09:48:47.843 - warn: javascript.0 at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:246:12)
                2019-10-15 09:48:47.843 - warn: javascript.0 at Manager.ondata (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:322:16)
                2019-10-15 09:48:47.844 - warn: javascript.0 at Socket. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
                2019-10-15 09:48:47.844 - warn: javascript.0 at Socket.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20)
                2019-10-15 09:48:47.844 - warn: javascript.0 at Socket.onPacket (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:451:14)
                2019-10-15 09:48:47.844 - warn: javascript.0 at WS. (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:268:10)
                2019-10-15 09:48:47.844 - warn: javascript.0 at WS.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20)
                2019-10-15 09:48:47.845 - warn: javascript.0 at WS.Transport.onPacket (/opt/iobroker/node_modules/engine.io-client/lib/transport.js:145:8)
                2019-10-15 09:48:47.845 - warn: javascript.0 at WS.Transport.onData (/opt/iobroker/node_modules/engine.io-client/lib/transport.js:137:8)
                2019-10-15 09:48:47.845 - warn: javascript.0 at WebSocket.ws.onmessage (/opt/iobroker/node_modules/engine.io-client/lib/transports/websocket.js:146:10)
                2019-10-15 09:48:47.845 - warn: javascript.0 at WebSocket.onMessage (/opt/iobroker/node_modules/ws/lib/WebSocket.js:442:14)
                2019-10-15 09:48:47.845 - warn: javascript.0 at WebSocket.emit (events.js:198:13)
                2019-10-15 09:48:47.845 - warn: javascript.0 at Receiver.ontext (/opt/iobroker/node_modules/ws/lib/WebSocket.js:841:10)
                2019-10-15 09:48:47.846 - warn: javascript.0 at /opt/iobroker/node_modules/ws/lib/Receiver.js:536:18
                2019-10-15 09:48:47.846 - warn: javascript.0 at Receiver.applyExtensions (/opt/iobroker/node_modules/ws/lib/Receiver.js:371:5)
                2019-10-15 09:48:47.846 - warn: javascript.0 at /opt/iobroker/node_modules/ws/lib/Receiver.js:508:14
                2019-10-15 09:48:47.846 - warn: javascript.0 at Receiver.flush (/opt/iobroker/node_modules/ws/lib/Receiver.js:347:3)
                2019-10-15 09:48:47.846 - warn: javascript.0 at Receiver.finish (/opt/iobroker/node_modules/ws/lib/Receiver.js:541:12)
                2019-10-15 09:48:47.847 - warn: javascript.0 at Receiver.expectHandler (/opt/iobroker/node_modules/ws/lib/Receiver.js:499:31)
                2019-10-15 09:48:47.847 - warn: javascript.0 at Receiver.add (/opt/iobroker/node_modules/ws/lib/Receiver.js:103:24)
                2019-10-15 09:48:47.847 - warn: javascript.0 at Socket.realHandler (/opt/iobroker/node_modules/ws/lib/WebSocket.js:825:20)
                2019-10-15 09:48:47.847 - warn: javascript.0 at Socket.emit (events.js:198:13)
                2019-10-15 09:48:47.847 - warn: javascript.0 at addChunk (_stream_readable.js:288:12)
                2019-10-15 09:48:47.847 - warn: javascript.0 at readableAddChunk (_stream_readable.js:269:11)
                2019-10-15 09:48:47.848 - warn: javascript.0 at Socket.Readable.push (_stream_readable.js:224:10)
                2019-10-15 09:48:47.848 - warn: javascript.0 at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)
                2019-10-15 09:48:47.852 - error: javascript.0 script.js.Weldscripts.Alexa_Fernseher_ein: TypeError [ERR_UNESCAPED_CHARACTERS]: Request path contains unescaped characters
                2019-10-15 09:49:11.101 - warn: javascript.0 Wrong type of denon.0.zoneMain.powerZone: "string". Please fix, while deprecated and will not work in next versions.
                2019-10-15 09:49:11.109 - warn: javascript.0 at setState (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1258:20)
                2019-10-15 09:49:11.110 - warn: javascript.0 at Object. (script.js.Weldscripts.Alexa_Fernseher_ein:13:5)
                2019-10-15 09:49:11.110 - warn: javascript.0 at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:963:38)
                2019-10-15 09:49:11.110 - warn: javascript.0 at Object.stateChange (/opt/iobroker/node_modules/iobroker.javascript/main.js:364:25)
                2019-10-15 09:49:11.110 - warn: javascript.0 at Object.change (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3706:37)
                2019-10-15 09:49:11.110 - warn: javascript.0 at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInMemClient.js:52:30)
                2019-10-15 09:49:11.111 - warn: javascript.0 at Socket.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
                2019-10-15 09:49:11.111 - warn: javascript.0 at Socket.onevent (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:270:10)
                2019-10-15 09:49:11.111 - warn: javascript.0 at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:228:12)
                2019-10-15 09:49:11.111 - warn: javascript.0 at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
                2019-10-15 09:49:11.111 - warn: javascript.0 at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
                2019-10-15 09:49:11.112 - warn: javascript.0 at Manager.ondecoded (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:332:8)
                2019-10-15 09:49:11.112 - warn: javascript.0 at Decoder. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
                2019-10-15 09:49:11.112 - warn: javascript.0 at Decoder.Emitter.emit (/opt/iobroker/node_modules/component-emitter/index.js:134:20)
                2019-10-15 09:49:11.112 - warn: javascript.0 at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:246:12)
                2019-10-15 09:49:11.112 - warn: javascript.0 at Manager.ondata (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:322:16)
                2019-10-15 09:49:11.113 - warn: javascript.0 at Socket. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
                2019-10-15 09:49:11.113 - warn: javascript.0 at Socket.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20)
                2019-10-15 09:49:11.113 - warn: javascript.0 at Socket.onPacket (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:451:14)
                2019-10-15 09:49:11.113 - warn: javascript.0 at WS. (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:268:10)
                2019-10-15 09:49:11.113 - warn: javascript.0 at WS.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20)
                2019-10-15 09:49:11.113 - warn: javascript.0 at WS.Transport.onPacket (/opt/iobroker/node_modules/engine.io-client/lib/transport.js:145:8)
                2019-10-15 09:49:11.114 - warn: javascript.0 at WS.Transport.onData (/opt/iobroker/node_modules/engine.io-client/lib/transport.js:137:8)
                2019-10-15 09:49:11.114 - warn: javascript.0 at WebSocket.ws.onmessage (/opt/iobroker/node_modules/engine.io-client/lib/transports/websocket.js:146:10)
                2019-10-15 09:49:11.114 - warn: javascript.0 at WebSocket.onMessage (/opt/iobroker/node_modules/ws/lib/WebSocket.js:442:14)
                2019-10-15 09:49:11.114 - warn: javascript.0 at WebSocket.emit (events.js:198:13)
                2019-10-15 09:49:11.114 - warn: javascript.0 at Receiver.ontext (/opt/iobroker/node_modules/ws/lib/WebSocket.js:841:10)
                2019-10-15 09:49:11.115 - warn: javascript.0 at /opt/iobroker/node_modules/ws/lib/Receiver.js:536:18
                2019-10-15 09:49:11.115 - warn: javascript.0 at Receiver.applyExtensions (/opt/iobroker/node_modules/ws/lib/Receiver.js:371:5)
                2019-10-15 09:49:11.115 - warn: javascript.0 at /opt/iobroker/node_modules/ws/lib/Receiver.js:508:14
                2019-10-15 09:49:11.115 - warn: javascript.0 at Receiver.flush (/opt/iobroker/node_modules/ws/lib/Receiver.js:347:3)
                2019-10-15 09:49:11.115 - warn: javascript.0 at Receiver.finish (/opt/iobroker/node_modules/ws/lib/Receiver.js:541:12)
                2019-10-15 09:49:11.115 - warn: javascript.0 at Receiver.expectHandler (/opt/iobroker/node_modules/ws/lib/Receiver.js:499:31)
                2019-10-15 09:49:11.116 - warn: javascript.0 at Receiver.add (/opt/iobroker/node_modules/ws/lib/Receiver.js:103:24)
                2019-10-15 09:49:11.116 - warn: javascript.0 at Socket.realHandler (/opt/iobroker/node_modules/ws/lib/WebSocket.js:825:20)
                2019-10-15 09:49:11.116 - warn: javascript.0 at Socket.emit (events.js:198:13)
                2019-10-15 09:49:11.116 - warn: javascript.0 at addChunk (_stream_readable.js:288:12)
                2019-10-15 09:49:11.116 - warn: javascript.0 at readableAddChunk (_stream_readable.js:269:11)
                2019-10-15 09:49:11.117 - warn: javascript.0 at Socket.Readable.push (_stream_readable.js:224:10)
                2019-10-15 09:49:11.117 - warn: javascript.0 at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)
                2019-10-15 09:49:11.117 - warn: javascript.0 Wrong type of samsung.0.Power.off: "number". Please fix, while deprecated and will not work in next versions.
                2019-10-15 09:49:11.123 - warn: javascript.0 at setState (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1258:20)
                2019-10-15 09:49:11.124 - warn: javascript.0 at Object. (script.js.Weldscripts.Alexa_Fernseher_ein:14:5)
                2019-10-15 09:49:11.124 - warn: javascript.0 at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:963:38)
                2019-10-15 09:49:11.124 - warn: javascript.0 at Object.stateChange (/opt/iobroker/node_modules/iobroker.javascript/main.js:364:25)
                2019-10-15 09:49:11.124 - warn: javascript.0 at Object.change (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3706:37)
                2019-10-15 09:49:11.124 - warn: javascript.0 at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInMemClient.js:52:30)
                2019-10-15 09:49:11.125 - warn: javascript.0 at Socket.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
                2019-10-15 09:49:11.125 - warn: javascript.0 at Socket.onevent (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:270:10)
                2019-10-15 09:49:11.125 - warn: javascript.0 at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:228:12)
                2019-10-15 09:49:11.125 - warn: javascript.0 at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
                2019-10-15 09:49:11.125 - warn: javascript.0 at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
                2019-10-15 09:49:11.126 - warn: javascript.0 at Manager.ondecoded (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:332:8)
                2019-10-15 09:49:11.126 - warn: javascript.0 at Decoder. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
                2019-10-15 09:49:11.126 - warn: javascript.0 at Decoder.Emitter.emit (/opt/iobroker/node_modules/component-emitter/index.js:134:20)
                2019-10-15 09:49:11.126 - warn: javascript.0 at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:246:12)
                2019-10-15 09:49:11.126 - warn: javascript.0 at Manager.ondata (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:322:16)
                2019-10-15 09:49:11.127 - warn: javascript.0 at Socket. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
                2019-10-15 09:49:11.127 - warn: javascript.0 at Socket.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20)
                2019-10-15 09:49:11.127 - warn: javascript.0 at Socket.onPacket (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:451:14)
                2019-10-15 09:49:11.127 - warn: javascript.0 at WS. (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:268:10)
                2019-10-15 09:49:11.127 - warn: javascript.0 at WS.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20)
                2019-10-15 09:49:11.128 - warn: javascript.0 at WS.Transport.onPacket (/opt/iobroker/node_modules/engine.io-client/lib/transport.js:145:8)
                2019-10-15 09:49:11.128 - warn: javascript.0 at WS.Transport.onData (/opt/iobroker/node_modules/engine.io-client/lib/transport.js:137:8)
                2019-10-15 09:49:11.128 - warn: javascript.0 at WebSocket.ws.onmessage (/opt/iobroker/node_modules/engine.io-client/lib/transports/websocket.js:146:10)
                2019-10-15 09:49:11.128 - warn: javascript.0 at WebSocket.onMessage (/opt/iobroker/node_modules/ws/lib/WebSocket.js:442:14)
                2019-10-15 09:49:11.128 - warn: javascript.0 at WebSocket.emit (events.js:198:13)
                2019-10-15 09:49:11.129 - warn: javascript.0 at Receiver.ontext (/opt/iobroker/node_modules/ws/lib/WebSocket.js:841:10)
                2019-10-15 09:49:11.129 - warn: javascript.0 at /opt/iobroker/node_modules/ws/lib/Receiver.js:536:18
                2019-10-15 09:49:11.129 - warn: javascript.0 at Receiver.applyExtensions (/opt/iobroker/node_modules/ws/lib/Receiver.js:371:5)
                2019-10-15 09:49:11.129 - warn: javascript.0 at /opt/iobroker/node_modules/ws/lib/Receiver.js:508:14
                2019-10-15 09:49:11.129 - warn: javascript.0 at Receiver.flush (/opt/iobroker/node_modules/ws/lib/Receiver.js:347:3)
                2019-10-15 09:49:11.129 - warn: javascript.0 at Receiver.finish (/opt/iobroker/node_modules/ws/lib/Receiver.js:541:12)
                2019-10-15 09:49:11.130 - warn: javascript.0 at Receiver.expectHandler (/opt/iobroker/node_modules/ws/lib/Receiver.js:499:31)
                2019-10-15 09:49:11.130 - warn: javascript.0 at Receiver.add (/opt/iobroker/node_modules/ws/lib/Receiver.js:103:24)
                2019-10-15 09:49:11.130 - warn: javascript.0 at Socket.realHandler (/opt/iobroker/node_modules/ws/lib/WebSocket.js:825:20)
                2019-10-15 09:49:11.130 - warn: javascript.0 at Socket.emit (events.js:198:13)
                2019-10-15 09:49:11.130 - warn: javascript.0 at addChunk (_stream_readable.js:288:12)
                2019-10-15 09:49:11.131 - warn: javascript.0 at readableAddChunk (_stream_readable.js:269:11)
                2019-10-15 09:49:11.131 - warn: javascript.0 at Socket.Readable.push (_stream_readable.js:224:10)
                2019-10-15 09:49:11.131 - warn: javascript.0 at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)
                2019-10-15 09:49:11.166 - error: samsung.0 Empty commands will not be excecuted.
                
                
                1 Reply Last reply
                0
                • UweRLPU Offline
                  UweRLPU Offline
                  UweRLP
                  wrote on last edited by
                  #13

                  Du benutzt Texte als true/false mußt aber unter Logik den Baustein wahr/unwahr nutzen. Vermutlich ist der Text bei select input "TV" auch nicht richtig, was ist select input für ein Objekt?

                  1 Reply Last reply
                  0
                  • UweRLPU Offline
                    UweRLPU Offline
                    UweRLP
                    wrote on last edited by
                    #14

                    Hier mein Blocky zum Ein-/Auschalten meiner Anlage. Ich mußte es leider in zwei Bilder aufteilen...
                    MeinBlockly_Teil1.jpg
                    MeinBlockly_Teil2.jpg

                    Vielleicht hilft es dir, habe dazu noch ein paar Kommentare eingefügt.

                    1 Reply Last reply
                    0
                    • J Offline
                      J Offline
                      jwedenig
                      Most Active
                      wrote on last edited by
                      #15

                      Mein Denon reagiert auf "0"und "1" als auch auf "true" und False"
                      das Problem ist dass der "request Url" Befehl nicht funktioniert.
                      Mhhh, Scheibenkleister

                      UweRLPU 1 Reply Last reply
                      0
                      • J jwedenig

                        Mein Denon reagiert auf "0"und "1" als auch auf "true" und False"
                        das Problem ist dass der "request Url" Befehl nicht funktioniert.
                        Mhhh, Scheibenkleister

                        UweRLPU Offline
                        UweRLPU Offline
                        UweRLP
                        wrote on last edited by UweRLP
                        #16

                        @jwedenig Vermute mal zum einschalten des Fensehers? Hat der TV immer die selbe also feste IP Adresse? War der TV zuvor vom Strom getrennt, kann sein das die Url zu früh nach dem Stromeinschalten abgesetzt wurde. Als Alternative zur Url, kann das Mediola Gateway IR senden oder hast du eine Harmony Fernbedienung mit Hub? Könntest dann den TV damit einschalten.

                        J 1 Reply Last reply
                        0
                        • UweRLPU UweRLP

                          @jwedenig Vermute mal zum einschalten des Fensehers? Hat der TV immer die selbe also feste IP Adresse? War der TV zuvor vom Strom getrennt, kann sein das die Url zu früh nach dem Stromeinschalten abgesetzt wurde. Als Alternative zur Url, kann das Mediola Gateway IR senden oder hast du eine Harmony Fernbedienung mit Hub? Könntest dann den TV damit einschalten.

                          J Offline
                          J Offline
                          jwedenig
                          Most Active
                          wrote on last edited by
                          #17

                          @UweRLP
                          Der Fernseher ist immer in Standby

                          Das abfeuern im Browser funktioniert tadellos .
                          Das Problem ist das Skript!
                          Glaube ich halt

                          J 1 Reply Last reply
                          0
                          • J jwedenig

                            @UweRLP
                            Der Fernseher ist immer in Standby

                            Das abfeuern im Browser funktioniert tadellos .
                            Das Problem ist das Skript!
                            Glaube ich halt

                            J Offline
                            J Offline
                            jwedenig
                            Most Active
                            wrote on last edited by
                            #18

                            Wie soll das Mediola als Trigger IR senden, es gibt doch keinen Mediola Adapter für IObroker, oder?

                            1 Reply Last reply
                            0
                            • UweRLPU Offline
                              UweRLPU Offline
                              UweRLP
                              wrote on last edited by
                              #19

                              Ups, bin davon ausgegangen das es einen Mediola Adapter gibt, weis es aber nicht, sorry.
                              Aber es gibt doch einen Samsung Adapter besteht da nicht die Mölglichkeit den TV einzuschalten?

                              BBTownB J 2 Replies Last reply
                              0
                              • UweRLPU UweRLP

                                Ups, bin davon ausgegangen das es einen Mediola Adapter gibt, weis es aber nicht, sorry.
                                Aber es gibt doch einen Samsung Adapter besteht da nicht die Mölglichkeit den TV einzuschalten?

                                BBTownB Offline
                                BBTownB Offline
                                BBTown
                                wrote on last edited by BBTown
                                #20

                                @UweRLP sagte in Samsung Fernseher schalten:

                                Ups, bin davon ausgegangen das es einen Mediola Adapter gibt, weis es aber nicht, sorry.
                                Aber es gibt doch einen Samsung Adapter besteht da nicht die Mölglichkeit den TV einzuschalten?

                                kommen die Datenpunkte nicht genau von diesem Adapter? (samsung.0)

                                @jwedenig was passiert denn bei "Power.off=1" ?

                                ioBroker auf NUC (VM debian v13 (Trixie ), node v22.22.2 npm v10.9.4, js-controller v7.1.1 jsonl/jsonl / HomeMatic CCU-2 (Wired und Funk) / Philips HUE / echo.DOT / Broadlink RM pro / SONOS

                                1 Reply Last reply
                                0
                                • UweRLPU UweRLP

                                  Ups, bin davon ausgegangen das es einen Mediola Adapter gibt, weis es aber nicht, sorry.
                                  Aber es gibt doch einen Samsung Adapter besteht da nicht die Mölglichkeit den TV einzuschalten?

                                  J Offline
                                  J Offline
                                  jwedenig
                                  Most Active
                                  wrote on last edited by
                                  #21

                                  @UweRLP
                                  nein, weil ja der Samsung erst im Netzwerk erreichbar ist, wenn er eingeschaltet ist, deswegen ja der Umweg über Mediola.
                                  Hier nochmals das Log

                                  undefined2019-10-15 10:49:36.978 - info: javascript.0 Stop script script.js.Weldscripts.Alexa_Fernseher_ein1
                                  2019-10-15 10:49:52.603 - info: javascript.0 script.js.Weldscripts.Alexa_Fernseher_ein: request: http://192.168.1.223/command?code=19082600000300220404660469008A01A5008A008D008A2DDD00010101020202020201010102020202020201020202020202010201010101010103&XC_FNC=Send2

                                  2019-10-15 10:49:52.604 - warn: javascript.0 Wrong type of denon.0.zoneMain.powerZone: "string". Please fix, while deprecated and will not work in next versions.
                                  2019-10-15 10:49:52.608 - warn: javascript.0 at setState (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1258:20)
                                  2019-10-15 10:49:52.608 - warn: javascript.0 at Object. (script.js.Weldscripts.Alexa_Fernseher_ein:11:5)
                                  2019-10-15 10:49:52.608 - warn: javascript.0 at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:963:38)
                                  2019-10-15 10:49:52.608 - warn: javascript.0 at Object.stateChange (/opt/iobroker/node_modules/iobroker.javascript/main.js:364:25)
                                  2019-10-15 10:49:52.608 - warn: javascript.0 at Object.change (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3706:37)
                                  2019-10-15 10:49:52.608 - warn: javascript.0 at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInMemClient.js:52:30)
                                  2019-10-15 10:49:52.608 - warn: javascript.0 at Socket.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
                                  2019-10-15 10:49:52.609 - warn: javascript.0 at Socket.onevent (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:270:10)
                                  2019-10-15 10:49:52.609 - warn: javascript.0 at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:228:12)
                                  2019-10-15 10:49:52.609 - warn: javascript.0 at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
                                  2019-10-15 10:49:52.609 - warn: javascript.0 at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
                                  2019-10-15 10:49:52.609 - warn: javascript.0 at Manager.ondecoded (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:332:8)
                                  2019-10-15 10:49:52.609 - warn: javascript.0 at Decoder. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
                                  2019-10-15 10:49:52.612 - warn: javascript.0 at Decoder.Emitter.emit (/opt/iobroker/node_modules/component-emitter/index.js:134:20)
                                  2019-10-15 10:49:52.612 - warn: javascript.0 at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:246:12)
                                  2019-10-15 10:49:52.612 - warn: javascript.0 at Manager.ondata (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:322:16)
                                  2019-10-15 10:49:52.613 - warn: javascript.0 at Socket. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
                                  2019-10-15 10:49:52.613 - warn: javascript.0 at Socket.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20)
                                  2019-10-15 10:49:52.613 - warn: javascript.0 at Socket.onPacket (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:451:14)
                                  2019-10-15 10:49:52.613 - warn: javascript.0 at WS. (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:268:10)
                                  2019-10-15 10:49:52.613 - warn: javascript.0 at WS.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20)
                                  2019-10-15 10:49:52.613 - warn: javascript.0 at WS.Transport.onPacket (/opt/iobroker/node_modules/engine.io-client/lib/transport.js:145:8)
                                  2019-10-15 10:49:52.613 - warn: javascript.0 at WS.Transport.onData (/opt/iobroker/node_modules/engine.io-client/lib/transport.js:137:8)
                                  2019-10-15 10:49:52.613 - warn: javascript.0 at WebSocket.ws.onmessage (/opt/iobroker/node_modules/engine.io-client/lib/transports/websocket.js:146:10)
                                  2019-10-15 10:49:52.613 - warn: javascript.0 at WebSocket.onMessage (/opt/iobroker/node_modules/ws/lib/WebSocket.js:442:14)
                                  2019-10-15 10:49:52.613 - warn: javascript.0 at WebSocket.emit (events.js:198:13)
                                  2019-10-15 10:49:52.613 - warn: javascript.0 at Receiver.ontext (/opt/iobroker/node_modules/ws/lib/WebSocket.js:841:10)
                                  2019-10-15 10:49:52.614 - warn: javascript.0 at /opt/iobroker/node_modules/ws/lib/Receiver.js:536:18
                                  2019-10-15 10:49:52.614 - warn: javascript.0 at Receiver.applyExtensions (/opt/iobroker/node_modules/ws/lib/Receiver.js:371:5)
                                  2019-10-15 10:49:52.614 - warn: javascript.0 at /opt/iobroker/node_modules/ws/lib/Receiver.js:508:14
                                  2019-10-15 10:49:52.614 - warn: javascript.0 at Receiver.flush (/opt/iobroker/node_modules/ws/lib/Receiver.js:347:3)
                                  2019-10-15 10:49:52.614 - warn: javascript.0 at Receiver.finish (/opt/iobroker/node_modules/ws/lib/Receiver.js:541:12)
                                  2019-10-15 10:49:52.614 - warn: javascript.0 at Receiver.expectHandler (/opt/iobroker/node_modules/ws/lib/Receiver.js:499:31)
                                  2019-10-15 10:49:52.614 - warn: javascript.0 at Receiver.add (/opt/iobroker/node_modules/ws/lib/Receiver.js:103:24)
                                  2019-10-15 10:49:52.614 - warn: javascript.0 at Socket.realHandler (/opt/iobroker/node_modules/ws/lib/WebSocket.js:825:20)
                                  2019-10-15 10:49:52.614 - warn: javascript.0 at Socket.emit (events.js:198:13)
                                  2019-10-15 10:49:52.614 - warn: javascript.0 at addChunk (_stream_readable.js:288:12)
                                  2019-10-15 10:49:52.614 - warn: javascript.0 at readableAddChunk (_stream_readable.js:269:11)
                                  2019-10-15 10:49:52.614 - warn: javascript.0 at Socket.Readable.push (_stream_readable.js:224:10)
                                  2019-10-15 10:49:52.615 - warn: javascript.0 at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)
                                  2019-10-15 10:49:52.616 - error: javascript.0 script.js.Weldscripts.Alexa_Fernseher_ein: TypeError [ERR_UNESCAPED_CHARACTERS]: Request path contains unescaped characters
                                  
                                  

                                  Das Problem ist glaube ich das hier:

                                  javascript.0 2019-10-15 10:49:52.616 error script.js.Weldscripts.Alexa_Fernseher_ein: TypeError [ERR_UNESCAPED_CHARACTERS]: Request path contains unescaped characters

                                  UweRLPU 1 Reply Last reply
                                  0
                                  • J jwedenig

                                    @UweRLP
                                    nein, weil ja der Samsung erst im Netzwerk erreichbar ist, wenn er eingeschaltet ist, deswegen ja der Umweg über Mediola.
                                    Hier nochmals das Log

                                    undefined2019-10-15 10:49:36.978 - info: javascript.0 Stop script script.js.Weldscripts.Alexa_Fernseher_ein1
                                    2019-10-15 10:49:52.603 - info: javascript.0 script.js.Weldscripts.Alexa_Fernseher_ein: request: http://192.168.1.223/command?code=19082600000300220404660469008A01A5008A008D008A2DDD00010101020202020201010102020202020201020202020202010201010101010103&XC_FNC=Send2

                                    2019-10-15 10:49:52.604 - warn: javascript.0 Wrong type of denon.0.zoneMain.powerZone: "string". Please fix, while deprecated and will not work in next versions.
                                    2019-10-15 10:49:52.608 - warn: javascript.0 at setState (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1258:20)
                                    2019-10-15 10:49:52.608 - warn: javascript.0 at Object. (script.js.Weldscripts.Alexa_Fernseher_ein:11:5)
                                    2019-10-15 10:49:52.608 - warn: javascript.0 at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:963:38)
                                    2019-10-15 10:49:52.608 - warn: javascript.0 at Object.stateChange (/opt/iobroker/node_modules/iobroker.javascript/main.js:364:25)
                                    2019-10-15 10:49:52.608 - warn: javascript.0 at Object.change (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3706:37)
                                    2019-10-15 10:49:52.608 - warn: javascript.0 at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInMemClient.js:52:30)
                                    2019-10-15 10:49:52.608 - warn: javascript.0 at Socket.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
                                    2019-10-15 10:49:52.609 - warn: javascript.0 at Socket.onevent (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:270:10)
                                    2019-10-15 10:49:52.609 - warn: javascript.0 at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:228:12)
                                    2019-10-15 10:49:52.609 - warn: javascript.0 at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
                                    2019-10-15 10:49:52.609 - warn: javascript.0 at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
                                    2019-10-15 10:49:52.609 - warn: javascript.0 at Manager.ondecoded (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:332:8)
                                    2019-10-15 10:49:52.609 - warn: javascript.0 at Decoder. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
                                    2019-10-15 10:49:52.612 - warn: javascript.0 at Decoder.Emitter.emit (/opt/iobroker/node_modules/component-emitter/index.js:134:20)
                                    2019-10-15 10:49:52.612 - warn: javascript.0 at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:246:12)
                                    2019-10-15 10:49:52.612 - warn: javascript.0 at Manager.ondata (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:322:16)
                                    2019-10-15 10:49:52.613 - warn: javascript.0 at Socket. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
                                    2019-10-15 10:49:52.613 - warn: javascript.0 at Socket.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20)
                                    2019-10-15 10:49:52.613 - warn: javascript.0 at Socket.onPacket (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:451:14)
                                    2019-10-15 10:49:52.613 - warn: javascript.0 at WS. (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:268:10)
                                    2019-10-15 10:49:52.613 - warn: javascript.0 at WS.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20)
                                    2019-10-15 10:49:52.613 - warn: javascript.0 at WS.Transport.onPacket (/opt/iobroker/node_modules/engine.io-client/lib/transport.js:145:8)
                                    2019-10-15 10:49:52.613 - warn: javascript.0 at WS.Transport.onData (/opt/iobroker/node_modules/engine.io-client/lib/transport.js:137:8)
                                    2019-10-15 10:49:52.613 - warn: javascript.0 at WebSocket.ws.onmessage (/opt/iobroker/node_modules/engine.io-client/lib/transports/websocket.js:146:10)
                                    2019-10-15 10:49:52.613 - warn: javascript.0 at WebSocket.onMessage (/opt/iobroker/node_modules/ws/lib/WebSocket.js:442:14)
                                    2019-10-15 10:49:52.613 - warn: javascript.0 at WebSocket.emit (events.js:198:13)
                                    2019-10-15 10:49:52.613 - warn: javascript.0 at Receiver.ontext (/opt/iobroker/node_modules/ws/lib/WebSocket.js:841:10)
                                    2019-10-15 10:49:52.614 - warn: javascript.0 at /opt/iobroker/node_modules/ws/lib/Receiver.js:536:18
                                    2019-10-15 10:49:52.614 - warn: javascript.0 at Receiver.applyExtensions (/opt/iobroker/node_modules/ws/lib/Receiver.js:371:5)
                                    2019-10-15 10:49:52.614 - warn: javascript.0 at /opt/iobroker/node_modules/ws/lib/Receiver.js:508:14
                                    2019-10-15 10:49:52.614 - warn: javascript.0 at Receiver.flush (/opt/iobroker/node_modules/ws/lib/Receiver.js:347:3)
                                    2019-10-15 10:49:52.614 - warn: javascript.0 at Receiver.finish (/opt/iobroker/node_modules/ws/lib/Receiver.js:541:12)
                                    2019-10-15 10:49:52.614 - warn: javascript.0 at Receiver.expectHandler (/opt/iobroker/node_modules/ws/lib/Receiver.js:499:31)
                                    2019-10-15 10:49:52.614 - warn: javascript.0 at Receiver.add (/opt/iobroker/node_modules/ws/lib/Receiver.js:103:24)
                                    2019-10-15 10:49:52.614 - warn: javascript.0 at Socket.realHandler (/opt/iobroker/node_modules/ws/lib/WebSocket.js:825:20)
                                    2019-10-15 10:49:52.614 - warn: javascript.0 at Socket.emit (events.js:198:13)
                                    2019-10-15 10:49:52.614 - warn: javascript.0 at addChunk (_stream_readable.js:288:12)
                                    2019-10-15 10:49:52.614 - warn: javascript.0 at readableAddChunk (_stream_readable.js:269:11)
                                    2019-10-15 10:49:52.614 - warn: javascript.0 at Socket.Readable.push (_stream_readable.js:224:10)
                                    2019-10-15 10:49:52.615 - warn: javascript.0 at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)
                                    2019-10-15 10:49:52.616 - error: javascript.0 script.js.Weldscripts.Alexa_Fernseher_ein: TypeError [ERR_UNESCAPED_CHARACTERS]: Request path contains unescaped characters
                                    
                                    

                                    Das Problem ist glaube ich das hier:

                                    javascript.0 2019-10-15 10:49:52.616 error script.js.Weldscripts.Alexa_Fernseher_ein: TypeError [ERR_UNESCAPED_CHARACTERS]: Request path contains unescaped characters

                                    UweRLPU Offline
                                    UweRLPU Offline
                                    UweRLP
                                    wrote on last edited by
                                    #22

                                    @jwedenig Ähm, habe jetzt den Faden verloren. Wenn du im Browser den TV per Url einschalten kannst dann ist der TV auch im Netzwerk erreichbar. Was hat jetzt Mediola damit zu tun? Irgenwie fehlen hier noch Infos die verheimlicht werden :-)

                                    J 1 Reply Last reply
                                    0
                                    • UweRLPU UweRLP

                                      @jwedenig Ähm, habe jetzt den Faden verloren. Wenn du im Browser den TV per Url einschalten kannst dann ist der TV auch im Netzwerk erreichbar. Was hat jetzt Mediola damit zu tun? Irgenwie fehlen hier noch Infos die verheimlicht werden :-)

                                      J Offline
                                      J Offline
                                      jwedenig
                                      Most Active
                                      wrote on last edited by
                                      #23

                                      @UweRLP
                                      Nein, mit der Url feuere ich ja nur einen IR Befehl für Mediola ab, und dann wird der Fernseher eingeschaltet

                                      J 1 Reply Last reply
                                      0
                                      • J jwedenig

                                        @UweRLP
                                        Nein, mit der Url feuere ich ja nur einen IR Befehl für Mediola ab, und dann wird der Fernseher eingeschaltet

                                        J Offline
                                        J Offline
                                        jwedenig
                                        Most Active
                                        wrote on last edited by
                                        #24

                                        http://192.168.1.223/command?code=19082600000300220404660469008A01A5008A008D008A2DDD00010101020202020201010102020202020201020202020202010201010101010103&XC_FNC=Send2

                                        1 Reply Last reply
                                        0
                                        • J Offline
                                          J Offline
                                          jwedenig
                                          Most Active
                                          wrote on last edited by
                                          #25

                                          http://192.168.2.223/command?code=19082600000300220404660469008A01A5008A008D008A2DDD00010101020202020201010102020202020201020202020202010201010101010103&XC_FNC=Send2

                                          1 Reply Last reply
                                          0

                                          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                                          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                                          With your input, this post could be even better 💗

                                          Register Login
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          619

                                          Online

                                          32.8k

                                          Users

                                          82.7k

                                          Topics

                                          1.3m

                                          Posts
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Home
                                          • Recent
                                          • Tags
                                          • Unread 0
                                          • Categories
                                          • Unreplied
                                          • Popular
                                          • GitHub
                                          • Docu
                                          • Hilfe