Neuer ioBroker-Blog online: Monatsrückblick März/April 2026

[jwedenig]

Hi!
Habe alles nach Anleitung gemacht, die Geräte wurden erkannt doch leider bleibt der Adapter gelb! Woran kann es liegen?
Ich wollte mir so Lohan Lampen mit GU 10 Fassung kaufen, oder hat wer eine andere Idee welche GU 10 LEDs in Farbe es gibt, welche mit einem anderen Adapter laufen würden? (günstig sollte es sein)
Vielen Dank
Jürgen

undefined2019-11-15 09:09:03.814 - info: host.raspberrypi object change system.adapter.tuya.0
2019-11-15 09:09:03.840 - info: host.raspberrypi instance system.adapter.tuya.0 started with pid 6478
2019-11-15 09:09:06.188 - error: host.raspberrypi instance system.adapter.tuya.0 terminated with code 7 (Adapter already running)
2019-11-15 09:09:06.189 - info: host.raspberrypi Restart adapter system.adapter.tuya.0 because enabled
2019-11-15 09:09:23.903 - info: tuya.0 SSL-Proxy ready to receive requests
2019-11-15 09:09:36.220 - info: host.raspberrypi instance system.adapter.tuya.0 started with pid 7197
2019-11-15 09:09:38.000 - error: host.raspberrypi instance system.adapter.tuya.0 terminated with code 7 (Adapter already running)
2019-11-15 09:09:38.001 - info: host.raspberrypi Restart adapter system.adapter.tuya.0 because enabled
2019-11-15 09:10:08.027 - info: host.raspberrypi instance system.adapter.tuya.0 started with pid 7912
2019-11-15 09:10:09.758 - error: host.raspberrypi instance system.adapter.tuya.0 terminated with code 7 (Adapter already running)
2019-11-15 09:10:09.759 - info: host.raspberrypi Restart adapter system.adapter.tuya.0 because enabled
2019-11-15 09:10:39.786 - info: host.raspberrypi instance system.adapter.tuya.0 started with pid 8622
2019-11-15 09:10:41.544 - error: host.raspberrypi instance system.adapter.tuya.0 terminated with code 7 (Adapter already running)
2019-11-15 09:10:41.544 - info: host.raspberrypi Restart adapter system.adapter.tuya.0 because enabled
2019-11-15 09:11:05.873 - error: tuya.0 SSL-Proxy ERROR: Error: socket hang up
2019-11-15 09:11:05.875 - error: tuya.0 Error: socket hang up
at TLSSocket.onSocketClose (_tls_wrap.js:764:23)
at TLSSocket.emit (events.js:203:15)
at _handle.close (net.js:606:12)
at Socket.done (_tls_wrap.js:388:7)
at Object.onceWrapper (events.js:286:20)
at Socket.emit (events.js:198:13)
at TCP._handle.close (net.js:606:12)
2019-11-15 09:11:05.895 - error: tuya.0 SSL-Proxy ERROR: Error: socket hang up
2019-11-15 09:11:05.896 - error: tuya.0 Error: socket hang up
at TLSSocket.onSocketClose (_tls_wrap.js:764:23)
at TLSSocket.emit (events.js:203:15)
at _handle.close (net.js:606:12)
at Socket.done (_tls_wrap.js:388:7)
at Object.onceWrapper (events.js:286:20)
at Socket.emit (events.js:198:13)
at TCP._handle.close (net.js:606:12)
2019-11-15 09:11:05.899 - error: tuya.0 SSL-Proxy ERROR: Error: socket hang up
2019-11-15 09:11:05.900 - error: tuya.0 Error: socket hang up
at TLSSocket.onSocketClose (_tls_wrap.js:764:23)
at TLSSocket.emit (events.js:203:15)
at _handle.close (net.js:606:12)
at Socket.done (_tls_wrap.js:388:7)
at Object.onceWrapper (events.js:286:20)
at Socket.emit (events.js:198:13)
at TCP._handle.close (net.js:606:12)
2019-11-15 09:11:05.969 - error: tuya.0 SSL-Proxy ERROR: Error: socket hang up
2019-11-15 09:11:05.970 - error: tuya.0 Error: socket hang up
at TLSSocket.onSocketClose (_tls_wrap.js:764:23)
at TLSSocket.emit (events.js:203:15)
at _handle.close (net.js:606:12)
at Socket.done (_tls_wrap.js:388:7)
at Object.onceWrapper (events.js:286:20)
at Socket.emit (events.js:198:13)
at TCP._handle.close (net.js:606:12)
2019-11-15 09:11:05.972 - error: tuya.0 SSL-Proxy ERROR: Error: socket hang up
2019-11-15 09:11:05.973 - error: tuya.0 Error: socket hang up
at TLSSocket.onSocketClose (_tls_wrap.js:764:23)
at TLSSocket.emit (events.js:203:15)
at _handle.close (net.js:606:12)
at Socket.done (_tls_wrap.js:388:7)
at Object.onceWrapper (events.js:286:20)
at Socket.emit (events.js:198:13)
at TCP._handle.close (net.js:606:12)
2019-11-15 09:11:06.046 - error: tuya.0 SSL-Proxy ERROR: Error: socket hang up
2019-11-15 09:11:06.047 - error: tuya.0 Error: socket hang up
at TLSSocket.onSocketClose (_tls_wrap.js:764:23)
at TLSSocket.emit (events.js:203:15)
at _handle.close (net.js:606:12)
at Socket.done (_tls_wrap.js:388:7)
at Object.onceWrapper (events.js:286:20)
at Socket.emit (events.js:198:13)
at TCP._handle.close (net.js:606:12)
2019-11-15 09:11:06.216 - error: tuya.0 SSL-Proxy ERROR: Error: socket hang up
2019-11-15 09:11:06.217 - error: tuya.0 Error: socket hang up
at TLSSocket.onSocketClose (_tls_wrap.js:764:23)
at TLSSocket.emit (events.js:203:15)
at _handle.close (net.js:606:12)
at Socket.done (_tls_wrap.js:388:7)
at Object.onceWrapper (events.js:286:20)
at Socket.emit (events.js:198:13)
at TCP._handle.close (net.js:606:12)
2019-11-15 09:11:06.282 - error: tuya.0 SSL-Proxy ERROR: Error: socket hang up
2019-11-15 09:11:06.283 - error: tuya.0 Error: socket hang up
at TLSSocket.onSocketClose (_tls_wrap.js:764:23)
at TLSSocket.emit (events.js:203:15)
at _handle.close (net.js:606:12)
at Socket.done (_tls_wrap.js:388:7)
at Object.onceWrapper (events.js:286:20)
at Socket.emit (events.js:198:13)
at TCP._handle.close (net.js:606:12)
2019-11-15 09:11:11.558 - info: host.raspberrypi instance system.adapter.tuya.0 started with pid 9331
2019-11-15 09:11:13.346 - error: tuya.0 SSL-Proxy ERROR: Error: socket hang up
2019-11-15 09:11:13.347 - error: tuya.0 Error: socket hang up
at TLSSocket.onSocketClose (_tls_wrap.js:764:23)
at TLSSocket.emit (events.js:203:15)
at _handle.close (net.js:606:12)
at Socket.done (_tls_wrap.js:388:7)
at Object.onceWrapper (events.js:286:20)
at Socket.emit (events.js:198:13)
at TCP._handle.close (net.js:606:12)
2019-11-15 09:11:13.353 - error: host.raspberrypi instance system.adapter.tuya.0 terminated with code 7 (Adapter already running)
2019-11-15 09:11:13.354 - info: host.raspberrypi Restart adapter system.adapter.tuya.0 because enabled
2019-11-15 09:11:13.399 - error: tuya.0 SSL-Proxy ERROR: Error: socket hang up
2019-11-15 09:11:13.400 - error: tuya.0 Error: socket hang up
at TLSSocket.onSocketClose (_tls_wrap.js:764:23)
at TLSSocket.emit (events.js:203:15)
at _handle.close (net.js:606:12)
at Socket.done (_tls_wrap.js:388:7)
at Object.onceWrapper (events.js:286:20)
at Socket.emit (events.js:198:13)
at TCP._handle.close (net.js:606:12)
2019-11-15 09:11:14.097 - info: tuya.0 05052560dc4f22d6ba0a Init with IP=192.168.1.68, Key=54b4b3dc89c8d6e5, Version=3.3
2019-11-15 09:11:14.110 - info: tuya.0 05052560dc4f22d45277 Init with IP=192.168.1.233, Key=acad14d74b7ade3e, Version=3.3
2019-11-15 09:11:14.115 - info: tuya.0 05052560dc4f22d45277 Init with IP=192.168.1.233, Key=acad14d74b7ade3e, Version=3.3
2019-11-15 09:11:14.127 - info: tuya.0 05052560dc4f22d6ba0a Init with IP=192.168.1.68, Key=54b4b3dc89c8d6e5, Version=3.3
2019-11-15 09:11:40.299 - info: host.raspberrypi object change system.adapter.tuya.0
2019-11-15 09:11:41.507 - info: host.raspberrypi object change system.adapter.tuya.0
2019-11-15 09:11:41.539 - info: host.raspberrypi instance system.adapter.tuya.0 started with pid 10055
2019-11-15 09:11:43.292 - error: host.raspberrypi instance system.adapter.tuya.0 terminated with code 7 (Adapter already running)
2019-11-15 09:11:43.293 - info: host.raspberrypi Restart adapter system.adapter.tuya.0 because enabled

[jwedenig]

@jwedenig

[Cliff]

Hänge mich hier einmal ran weil es am Besten passt.
Bei mir läuft der aktuelle Tuya Adapter im Grunde. Ich habe eine (messende) WLan- Steckdose in dem System. Diese wurde erkannt und funktioniert.
Leider 'stürzt' mir der Tuya- Adapter täglich ab (Wird gelb).

Im Log ist folgendes (Durchaus mehrfach über den Tag) zu sehen:

tuya.0 2019-12-16 09:34:04.635 warn 14271317a4cf12a09e93 error on get: Error: No connection has been made to the device.
tuya.0 2019-12-16 09:33:41.973 error 14271317a4cf12a09e93: Error: connection timed out
tuya.0 2019-12-16 09:33:04.631 warn 14271317a4cf12a09e93 error on get: Error: No connection has been made to the device.
tuya.0 2019-12-16 09:32:04.627 warn 14271317a4cf12a09e93 error on get: Error: No connection has been made to the device.
tuya.0 2019-12-16 09:31:04.622 warn 14271317a4cf12a09e93 error on get: Error: No connection has been made to the device.

Ich vermute eine dieser Unterbrechungen bringt den Adapter zum Absturz.
Die Steckdose ist übrigens max. 5m von der Fritzbox entfernt.

Wenn man versucht den Tuya- Adapter aus IoBroker heraus zu restarten kommt folgendes in einer Endlosschleife:

host.rock64 2019-12-16 17:35:24.680 info Restart adapter system.adapter.tuya.0 because enabled
host.rock64 2019-12-16 17:35:24.679 error instance system.adapter.tuya.0 terminated with code 7 (Adapter already running)
host.rock64 2019-12-16 17:35:21.796 info instance system.adapter.tuya.0 started with pid 14613
host.rock64 2019-12-16 17:34:51.675 info Restart adapter system.adapter.tuya.0 because enabled
host.rock64 2019-12-16 17:34:51.674 error instance system.adapter.tuya.0 terminated with code 7 (Adapter already running)
host.rock64 2019-12-16 17:34:49.150 info instance system.adapter.tuya.0 started with pid 13799
host.rock64 2019-12-16 17:34:19.101 info Restart adapter system.adapter.tuya.0 because enabled
host.rock64 2019-12-16 17:34:19.101 error instance system.adapter.tuya.0 terminated with code 7 (Adapter already running)
host.rock64 2019-12-16 17:34:16.496 info instance system.adapter.tuya.0 started with pid 12968
host.rock64 2019-12-16 17:34:16.452 info object change system.adapter.tuya.0

Einzige Abhillfe:
Neustart des Rechners (Hier Rock64). Dann ist der Adapter sofort wieder 'grün'

[Cliff]

So,
ist beschlossen: Tuya fliegt raus und wird durch TpLink ersetzt.
Es nervt jeden Tag den Rechner neustarten zu müssen...