Navigation

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

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

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

    Quarksack

    @Quarksack

    0
    Reputation
    14
    Profile views
    10
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    Quarksack Follow

    Latest posts made by Quarksack

    • RE: [iot-Aktion] Andere Probleme mit dem iot-Adapter bzw der Nutzung

      Lösung für IFTTT, :mrgreen:

      mein IOBroker läuft bei mir auf einem Synology im Docker. Heute Nacht hat mein Synology sich geupdatet. Dadurch wird Docker immer mit neu gestartet.

      Anscheinend brachte das die Lösung. Dadurch dass die Instanz von IOBroker neu gestartet wurde hat sich alles bei mir Sauber verbunden und die API Key wurden auch sauber erstellt. :roll:

      Grüße

      Quarksack
      2824_unbenannt.jpg

      posted in ioBroker Allgemein
      Quarksack
      Quarksack
    • RE: [iot-Aktion] Andere Probleme mit dem iot-Adapter bzw der Nutzung

      Hallo Leute,

      evtl. könnt Ihr mir weiterhelfen. Bei mir läuft alles soweit. Allerdings funktioniert die Sache mit IFTTT nicht so ganz.

      Wenn ich auf "Neuen Service-URL-Schlüsse Abrufen" klicke passiert nichts.

      Das Log sieht dann wie folgt aus.

      iot.0	2019-01-01 21:01:04.898	info	Connection changed: connect
      iot.0	2019-01-01 21:01:02.481	error	Cannot read URL key: Not exists
      iot.0	2019-01-01 21:01:02.261	info	Connecting with xxxxxx.iot.eu-west-1.amazonaws.com
      iot.0	2019-01-01 21:01:02.206	info	starting. Version 0.2.2 in /opt/iobroker/node_modules/iobroker.iot, node: v6.13.1
      
      

      Grüße

      Quarksack
      2824_unbenannt.png

      posted in ioBroker Allgemein
      Quarksack
      Quarksack
    • RE: Iobroker und Broadlink pro

      @4-real:

      Danke für den Tipp mit dem Reset. Werde ich heute Abend gleich mal durchführen.

      Ich hatte die Geräte mit der APP auf dem BL angelernt. Ich dachte das der Adapter die Geräte dann ausliest.

      Grüßla

      posted in ioBroker Allgemein
      Quarksack
      Quarksack
    • RE: Iobroker und Broadlink pro

      Moin moin Zusammen,

      da ich auch schon durch so ziemlich jeden Broadlink2.0 Thread durchforstet habe und noch keine Lösung gefunden haben, schreib ich hier mal mein Problem.

      Der BL2.0 Adapter findet meinen BL (warum auch immer zweimal). Allerdings werden keinerlei angelernten Geräte angezeigt. Siehe Screenshot.

      2824_controller.jpg

      Kann mir wer weiterhelfen?

      Viele Grüße

      posted in ioBroker Allgemein
      Quarksack
      Quarksack
    • RE: [Aufruf] deConz Adapter Testen 1.1.2

      Wooohoooo…

      Jetzt gehts. Danke für die Hilfe.

      Grüße

      Quarksack

      posted in Tester
      Quarksack
      Quarksack
    • RE: [Aufruf] deConz Adapter Testen 1.1.2

      Kaum macht man richtig schon bekommt man auch das richtige Log.

      host.RackStation	2017-12-27 22:05:01.436	error	instance system.adapter.deconz.0 terminated with code 0 (OK)
      deconz.0	2017-12-27 22:05:01.388	info	terminating
      deconz.0	2017-12-27 22:05:00.880	error	at readableAddChunk (_stream_readable.js:176:18)
      deconz.0	2017-12-27 22:05:00.880	error	at Socket.emit (events.js:188:7)
      deconz.0	2017-12-27 22:05:00.880	error	at emitOne (events.js:96:13)
      deconz.0	2017-12-27 22:05:00.880	error	at Socket.socketOnData (_http_client.js:363:20)
      deconz.0	2017-12-27 22:05:00.880	error	at HTTPParser.parserOnHeadersComplete (_http_common.js:99:23)
      deconz.0	2017-12-27 22:05:00.880	error	at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:474:21)
      deconz.0	2017-12-27 22:05:00.880	error	at ClientRequest.emit (events.js:188:7)
      deconz.0	2017-12-27 22:05:00.880	error	at emitOne (events.js:96:13)
      deconz.0	2017-12-27 22:05:00.880	error	at ClientRequest.g (events.js:292:16)
      deconz.0	2017-12-27 22:05:00.880	error	at ClientRequest.response (/opt/iobroker/node_modules/ws/lib/WebSocket.js:719:15)
      deconz.0	2017-12-27 22:05:00.880	error	Error: unexpected server response (404)
      deconz.0	2017-12-27 22:05:00.879	error	uncaught exception: unexpected server response (404)
      deconz.0	2017-12-27 22:04:50.915	debug	getAllSensors: {"1":{"config":{"on":true,"reachable":false},"ep":1,"etag":"c35a1d9b238acee3b6426c0973955cb0","manufacturername":"IKEA of Sweden","modelid":"TRADFRI bulb E27 W opal 1000lm","name":"TRA
      deconz.0	2017-12-27 22:04:50.878	debug	API version: 1.0.0
      deconz.0	2017-12-27 22:04:50.811	info	starting. Version 0.1.1 in /opt/iobroker/node_modules/iobroker.deconz, node: v6.12.2
      deconz.0	2017-12-27 22:04:50.763	debug	statesDB connected
      deconz.0	2017-12-27 22:04:50.700	debug	objectDB connected
      host.RackStation	2017-12-27 22:04:48.887	info	instance system.adapter.deconz.0 started with pid 909
      host.RackStation	2017-12-27 22:04:18.875	info	Restart adapter system.adapter.deconz.0 because enabled
      host.RackStation	2017-12-27 22:04:18.875	error	instance system.adapter.deconz.0 terminated with code 0 (OK)
      deconz.0	2017-12-27 22:04:18.855	info	terminating
      deconz.0	2017-12-27 22:04:18.297	error	at readableAddChunk (_stream_readable.js:176:18)
      deconz.0	2017-12-27 22:04:18.297	error	at Socket.emit (events.js:188:7)
      deconz.0	2017-12-27 22:04:18.297	error	at emitOne (events.js:96:13)
      deconz.0	2017-12-27 22:04:18.297	error	at Socket.socketOnData (_http_client.js:363:20)
      deconz.0	2017-12-27 22:04:18.297	error	at HTTPParser.parserOnHeadersComplete (_http_common.js:99:23)
      deconz.0	2017-12-27 22:04:18.297	error	at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:474:21)
      deconz.0	2017-12-27 22:04:18.297	error	at ClientRequest.emit (events.js:188:7)
      deconz.0	2017-12-27 22:04:18.297	error	at emitOne (events.js:96:13)
      deconz.0	2017-12-27 22:04:18.297	error	at ClientRequest.g (events.js:292:16)
      deconz.0	2017-12-27 22:04:18.297	error	at ClientRequest.response (/opt/iobroker/node_modules/ws/lib/WebSocket.js:719:15)
      deconz.0	2017-12-27 22:04:18.297	error	Error: unexpected server response (404)
      deconz.0	2017-12-27 22:04:18.297	error	uncaught exception: unexpected server response (404)
      deconz.0	2017-12-27 22:04:08.335	debug	getAllSensors: {"1":{"config":{"on":true,"reachable":false},"ep":1,"etag":"c35a1d9b238acee3b6426c0973955cb0","manufacturername":"IKEA of Sweden","modelid":"TRADFRI bulb E27 W opal 1000lm","name":"TRA
      deconz.0	2017-12-27 22:04:08.292	debug	API version: 1.0.0
      deconz.0	2017-12-27 22:04:08.228	info	starting. Version 0.1.1 in /opt/iobroker/node_modules/iobroker.deconz, node: v6.12.2
      

      2824_iobroker.jpg

      posted in Tester
      Quarksack
      Quarksack
    • RE: [Aufruf] deConz Adapter Testen 1.1.2

      @Jey Cee:

      @Quarksack:

      Doch leider startet der Adapter andauernd neu. Hier das Log.: `

      Kannst du bitte mal den http://www.iobroker.net/docu/?page_id=14&lang=de#Experten-Modus auf "debug" stellen, damit mehr Informationen Sichtbar sind. Und dann das Log hier Einfügen. `

      Vielleicht noch als Info im Einsatz ist das Raspbee Gateway mit Raspbian Stretch.

      host.RackStation	2017-12-27 14:23:55.286	info	Restart adapter system.adapter.deconz.0 because enabled
      host.RackStation	2017-12-27 14:23:55.285	error	instance system.adapter.deconz.0 terminated with code 0 (OK)
      deconz.0	2017-12-27 14:23:54.582	error	Error: unexpected server response (404) at ClientRequest.response (/opt/iobroker/node_modules/ws/lib/WebSocket.js:719:15) at ClientRequest.g (events.js:292:16) at emitOne (events.js:96:13)
      deconz.0	2017-12-27 14:23:54.581	error	uncaught exception: unexpected server response (404)
      deconz.0	2017-12-27 14:23:44.576	info	starting. Version 0.1.1 in /opt/iobroker/node_modules/iobroker.deconz, node: v6.12.2
      host.RackStation	2017-12-27 14:23:42.603	info	instance system.adapter.deconz.0 started with pid 839
      host.RackStation	2017-12-27 13:23:12.590	info	Restart adapter system.adapter.deconz.0 because enabled
      host.RackStation	2017-12-27 13:23:12.590	error	instance system.adapter.deconz.0 terminated with code 0 (OK)
      deconz.0	2017-12-27 13:23:12.570	info	terminating
      deconz.0	2017-12-27 13:23:12.063	error	at readableAddChunk (_stream_readable.js:176:18)
      deconz.0	2017-12-27 13:23:12.063	error	at Socket.emit (events.js:188:7)
      deconz.0	2017-12-27 13:23:12.063	error	at emitOne (events.js:96:13)
      deconz.0	2017-12-27 13:23:12.063	error	at Socket.socketOnData (_http_client.js:363:20)
      deconz.0	2017-12-27 13:23:12.063	error	at HTTPParser.parserOnHeadersComplete (_http_common.js:99:23)
      deconz.0	2017-12-27 13:23:12.063	error	at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:474:21)
      deconz.0	2017-12-27 13:23:12.063	error	at ClientRequest.emit (events.js:188:7)
      deconz.0	2017-12-27 13:23:12.063	error	at emitOne (events.js:96:13)
      deconz.0	2017-12-27 13:23:12.063	error	at ClientRequest.g (events.js:292:16)
      deconz.0	2017-12-27 13:23:12.063	error	at ClientRequest.response (/opt/iobroker/node_modules/ws/lib/WebSocket.js:719:15)
      deconz.0	2017-12-27 13:23:12.063	error	Error: unexpected server response (404)
      deconz.0	2017-12-27 13:23:12.061	error	uncaught exception: unexpected server response (404)
      deconz.0	2017-12-27 13:23:01.985	info	starting. Version 0.1.1 in /opt/iobroker/node_modules/iobroker.deconz, node: v6.12.2
      host.RackStation	2017-12-27 13:23:00.080	info	instance system.adapter.deconz.0 started with pid 829
      host.RackStation	2017-12-27 13:22:30.069	info	Restart adapter system.adapter.deconz.0 because enabled
      host.RackStation	2017-12-27 13:22:30.069	error	instance system.adapter.deconz.0 terminated with code 0 (OK)
      deconz.0	2017-12-27 13:22:30.049	info	terminating
      deconz.0	2017-12-27 13:22:29.541	error	at readableAddChunk (_stream_readable.js:176:18)
      deconz.0	2017-12-27 13:22:29.541	error	at Socket.emit (events.js:188:7)
      deconz.0	2017-12-27 13:22:29.541	error	at emitOne (events.js:96:13)
      deconz.0	2017-12-27 13:22:29.541	error	at Socket.socketOnData (_http_client.js:363:20)
      deconz.0	2017-12-27 13:22:29.541	error	at HTTPParser.parserOnHeadersComplete (_http_common.js:99:23)
      deconz.0	2017-12-27 13:22:29.541	error	at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:474:21)
      deconz.0	2017-12-27 13:22:29.541	error	at ClientRequest.emit (events.js:188:7)
      deconz.0	2017-12-27 13:22:29.541	error	at emitOne (events.js:96:13)
      deconz.0	2017-12-27 13:22:29.541	error	at ClientRequest.g (events.js:292:16)
      deconz.0	2017-12-27 13:22:29.541	error	at ClientRequest.response (/opt/iobroker/node_modules/ws/lib/WebSocket.js:719:15)
      deconz.0	2017-12-27 13:22:29.541	error	Error: unexpected server response (404)
      deconz.0	2017-12-27 13:22:29.539	error	uncaught exception: unexpected server response (404)
      deconz.0	2017-12-27 13:22:19.461	info	starting. Version 0.1.1 in /opt/iobroker/node_modules/iobroker.deconz, node: v6.12.2
      host.RackStation	2017-12-27 13:22:17.567	info	instance system.adapter.deconz.0 started with pid 819
      hm-rpc.2	2017-12-27 13:21:57.296	info	xmlrpc -> 0 devices
      hm-rpc.2	2017-12-27 13:21:57.290	info	xmlrpc <- listDevices ["hm-rpc.2"]
      host.RackStation	2017-12-27 13:21:47.555	info	Restart adapter system.adapter.deconz.0 because enabled
      host.RackStation	2017-12-27 13:21:47.554	error	instance system.adapter.deconz.0 terminated with code 0 (OK)
      deconz.0	2017-12-27 13:21:47.532	info	terminating
      deconz.0	2017-12-27 13:21:47.024	error	at readableAddChunk (_stream_readable.js:176:18)
      deconz.0	2017-12-27 13:21:47.024	error	at Socket.emit (events.js:188:7)
      deconz.0	2017-12-27 13:21:47.024	error	at emitOne (events.js:96:13)
      deconz.0	2017-12-27 13:21:47.024	error	at Socket.socketOnData (_http_client.js:363:20)
      deconz.0	2017-12-27 13:21:47.024	error	at HTTPParser.parserOnHeadersComplete (_http_common.js:99:23)
      deconz.0	2017-12-27 13:21:47.024	error	at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:474:21)
      deconz.0	2017-12-27 13:21:47.024	error	at ClientRequest.emit (events.js:188:7)
      deconz.0	2017-12-27 13:21:47.024	error	at emitOne (events.js:96:13)
      deconz.0	2017-12-27 13:21:47.024	error	at ClientRequest.g (events.js:292:16)
      deconz.0	2017-12-27 13:21:47.024	error	at ClientRequest.response (/opt/iobroker/node_modules/ws/lib/WebSocket.js:719:15)
      deconz.0	2017-12-27 13:21:47.024	error	Error: unexpected server response (404)
      deconz.0	2017-12-27 13:21:47.022	error	uncaught exception: unexpected server response (404)
      hm-rpc.0	2017-12-27 13:21:43.888	info	Connected
      hm-rpc.0	2017-12-27 13:21:43.887	info	new CUxD devices/channels after filter: 0
      hm-rpc.0	2017-12-27 13:21:43.873	info	binrpc -> listDevices 28
      hm-rpc.0	2017-12-27 13:21:43.395	info	Disconnected
      deconz.0	2017-12-27 13:21:36.945	info	starting. Version 0.1.1 in /opt/iobroker/node_modules/iobroker.deconz, node: v6.12.2
      host.RackStation	2017-12-27 13:21:35.009	info	instance system.adapter.deconz.0 started with pid 809
      
      
      posted in Tester
      Quarksack
      Quarksack
    • RE: [Aufruf] deConz Adapter Testen 1.1.2

      Mahlzeit,

      wird gemacht. Bin grad auf Arbeit aber heute Abend kommt das Log.

      Grüße

      posted in Tester
      Quarksack
      Quarksack
    • RE: [Aufruf] deConz Adapter Testen 1.1.2

      Tachov,

      bei mir hat die Installation des Adapters ohne Probleme geklappt auch der API-Key habe ich ohne Problme bekommen.

      Doch leider startet der Adapter andauernd neu. Hier das Log.:

      deconz.0	2017-12-26 13:55:47.576	info	starting. Version 0.1.1 in /opt/iobroker/node_modules/iobroker.deconz, node: v6.12.2
      host.RackStation	2017-12-26 13:55:45.585	info	instance system.adapter.deconz.0 started with pid 1053
      host.RackStation	2017-12-26 12:55:43.687	info	Restart adapter system.adapter.deconz.0 because enabled
      host.RackStation	2017-12-26 12:55:43.686	error	instance system.adapter.deconz.0 terminated with code 0 (OK)
      deconz.0	2017-12-26 12:55:43.667	info	terminating
      deconz.0	2017-12-26 12:55:43.159	error	at readableAddChunk (_stream_readable.js:176:18)
      deconz.0	2017-12-26 12:55:43.159	error	at Socket.emit (events.js:188:7)
      deconz.0	2017-12-26 12:55:43.159	error	at emitOne (events.js:96:13)
      deconz.0	2017-12-26 12:55:43.159	error	at Socket.socketOnData (_http_client.js:363:20)
      deconz.0	2017-12-26 12:55:43.159	error	at HTTPParser.parserOnHeadersComplete (_http_common.js:99:23)
      deconz.0	2017-12-26 12:55:43.159	error	at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:474:21)
      deconz.0	2017-12-26 12:55:43.159	error	at ClientRequest.emit (events.js:188:7)
      deconz.0	2017-12-26 12:55:43.159	error	at emitOne (events.js:96:13)
      deconz.0	2017-12-26 12:55:43.159	error	at ClientRequest.g (events.js:292:16)
      deconz.0	2017-12-26 12:55:43.159	error	at ClientRequest.response (/opt/iobroker/node_modules/ws/lib/WebSocket.js:719:15)
      deconz.0	2017-12-26 12:55:43.159	error	Error: unexpected server response (404)
      deconz.0	2017-12-26 12:55:43.156	error	uncaught exception: unexpected server response (404)
      
      posted in Tester
      Quarksack
      Quarksack
    • Fehler in TR-064

      Hallo Gemeinde,

      leider schaffe ich es nicht den TR-064 online zu Bringgen.

      Im Log erscheint

      host.RackStation	2017-06-06 19:15:09.507	error	instance system.adapter.tr-064.0 terminated with code 1 ()
      

      Wenn man im Terminal "node node_modules/iobroker.tr-064/tr-064.js –logs --force" eingibt kommt

      /opt/iobroker/node_modules/soef/soef.js:1253                                    
          fns.adapter = fns.adapter(options);                                         
                            ^                                                         
      
      TypeError: fns.adapter is not a function                                        
          at Object.exports.Adapter (/opt/iobroker/node_modules/soef/soef.js:1253:23) 
          at Object. <anonymous>(/opt/iobroker/node_modules/iobroker.tr-064/tr-064.js:14:20)                                                                          
          at Module._compile (module.js:570:32)                                       
          at Object.Module._extensions..js (module.js:579:10)                         
          at Module.load (module.js:487:32)                                           
          at tryModuleLoad (module.js:446:12)                                         
          at Function.Module._load (module.js:438:3)                                  
          at Module.runMain (module.js:604:10)                                        
          at run (bootstrap_node.js:390:7)                                            
          at startup (bootstrap_node.js:150:9)</anonymous>
      

      Ich habe den IOBroker über Docker auf einer Synology frisch installiert. Kann mir jemand evtl. weiterhelfen?

      Danke

      Quarksack

      posted in Error/Bug
      Quarksack
      Quarksack
    Community
    Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
    The ioBroker Community 2014-2023
    logo