Tuya will nicht

[oFbEQnpoLKKl6mbY5e13]

@hausbaer

Bitte poste die Meldungen vom Start des Tuya-Adapters im Debug-Modus. Bitte kein Screenshot, sondern den blanken Text direkt aus der Datei iobroker.current.log unter /op/iobroker/log oder zumindest aus dem Admin. Bittte den Text dann in CodeTags einfassen (</>).

[arteck]

@hausbaer das ist kein Fehler sondern ein warning..steht da auch .. und soll dem Entwickler signalisieren dass das Object falsch ist ..

das hat zuerst nix mit deinem Fehler zu tun..

[Hausbaer]

Hier mal der Log:

2022-03-02 07:58:32.240  - info: host.raspi-iobroker instance system.adapter.tuya.0 started with pid 4366
2022-03-02 07:58:33.913  - debug: tuya.0 (4366) Redis Objects: Use Redis connection: 0.0.0.0:9001
2022-03-02 07:58:34.010  - debug: tuya.0 (4366) Objects client ready ... initialize now
2022-03-02 07:58:34.029  - debug: tuya.0 (4366) Objects create System PubSub Client
2022-03-02 07:58:34.031  - debug: tuya.0 (4366) Objects create User PubSub Client
2022-03-02 07:58:34.196  - debug: tuya.0 (4366) Objects client initialize lua scripts
2022-03-02 07:58:34.202  - debug: tuya.0 (4366) Objects connected to redis: 0.0.0.0:9001
2022-03-02 07:58:34.273  - debug: tuya.0 (4366) Redis States: Use Redis connection: 0.0.0.0:9000
2022-03-02 07:58:34.330  - debug: tuya.0 (4366) States create System PubSub Client
2022-03-02 07:58:34.332  - debug: tuya.0 (4366) States create User PubSub Client
2022-03-02 07:58:34.492  - debug: tuya.0 (4366) States connected to redis: 0.0.0.0:9000
2022-03-02 07:58:34.988  - debug: tuya.0 (4366) Plugin sentry Initialize Plugin (enabled=true)
2022-03-02 07:58:35.788  - info: tuya.0 (4366) starting. Version 3.6.15 in /opt/iobroker/node_modules/iobroker.tuya, node: v12.22.9, js-controller: 4.0.15
2022-03-02 07:58:35.837  - info: tuya.0 (4366) Polling interval 1 too short, setting to 30s
2022-03-02 07:58:35.917  - debug: tuya.0 (4366) init 2 known devices
2022-03-02 07:58:35.921  - debug: tuya.0 (4366) bfacd57c23589b3b05crdn: Create device objects if not exist
2022-03-02 07:58:35.924  - debug: tuya.0 (4366) bfacd57c23589b3b05crdn: Objects [{"type":"number","unit":"kW·h","max":99999999,"scale":2,"read":true,"write":false,"name":"total_forward_energy","id":1,"role":"value"},{"type":"string","encoding":"base64","read":true,"write":true,"name":"month_energy","id":3,"role":"text"},{"type":"string","encoding":"base64","read":true,"write":true,"name":"daily_energy","id":4,"role":"text"},{"type":"string","encoding":"base64","read":true,"write":false,"name":"phase_a","id":6,"role":"text"},{"type":"number","read":true,"write":false,"name":"fault","id":9,"role":"value"},{"type":"boolean","read":true,"write":true,"name":"switch","id":16,"role":"switch"},{"type":"string","encoding":"base64","read":true,"write":true,"name":"alarm_set_1","id":17,"role":"text"},{"type":"string","encoding":"base64","read":true,"write":true,"name":"alarm_set_2","id":18,"role":"text"},{"type":"string","read":true,"write":false,"name":"breaker_id","id":19,"role":"text"},{"type":"string","read":true,"write":false,"name":"imei_imsi","id":20,"role":"text"},{"type":"string","encoding":"base64","read":true,"write":true,"name":"Icp","id":101,"role":"text"}]
2022-03-02 07:58:35.926  - debug: tuya.0 (4366) bfacd57c23589b3b05crdn Register onChange for 3
2022-03-02 07:58:35.927  - debug: tuya.0 (4366) bfacd57c23589b3b05crdn Register onChange for 4
2022-03-02 07:58:35.927  - debug: tuya.0 (4366) bfacd57c23589b3b05crdn Register onChange for 16
2022-03-02 07:58:35.928  - debug: tuya.0 (4366) bfacd57c23589b3b05crdn Register onChange for 17
2022-03-02 07:58:35.928  - debug: tuya.0 (4366) bfacd57c23589b3b05crdn Register onChange for 18
2022-03-02 07:58:35.929  - debug: tuya.0 (4366) bfacd57c23589b3b05crdn Register onChange for 101
2022-03-02 07:58:35.931  - debug: tuya.0 (4366) bf99ed882f479e0403zrbn: Create device objects if not exist
2022-03-02 07:58:35.931  - debug: tuya.0 (4366) bf99ed882f479e0403zrbn: Objects [{"type":"string","encoding":"base64","read":true,"write":false,"name":"upward","id":101,"role":"text"},{"type":"string","encoding":"base64","read":true,"write":true,"name":"down","id":102,"role":"text"}]
2022-03-02 07:58:35.932  - debug: tuya.0 (4366) bf99ed882f479e0403zrbn Register onChange for 102
2022-03-02 07:58:35.984  - debug: tuya.0 (4366) connected set to false
2022-03-02 07:58:36.067  - info: tuya.0 (4366) bf99ed882f479e0403zrbn Init with IP=192.168.8.225, Key=60b569b110aa34cb, Version=3.3
2022-03-02 07:58:36.076  - debug: tuya.0 (4366) bf99ed882f479e0403zrbn: Connected to device
2022-03-02 07:58:36.098  - debug: tuya.0 (4366) bf99ed882f479e0403zrbn: Error from device (0): App still open on your mobile phone? json obj data unvalid
2022-03-02 07:58:36.100  - debug: tuya.0 (4366) bf99ed882f479e0403zrbn: Received data: {"1":null,"2":null,"3":null,"101":null,"102":null,"103":null}
2022-03-02 07:58:36.101  - debug: tuya.0 (4366) bf99ed882f479e0403zrbn: Ignore invalid data (Counter: 1)
2022-03-02 07:58:36.106  - debug: tuya.0 (4366) connected set to true
2022-03-02 07:58:36.170  - info: tuya.0 (4366) Existing devices initialized
2022-03-02 07:58:36.178  - info: tuya.0 (4366) Listen for local Tuya devices on port 6666
2022-03-02 07:58:36.179  - info: tuya.0 (4366) Listen for encrypted local Tuya devices on port 6667
2022-03-02 07:58:36.201  - debug: tuya.0 (4366) bf99ed882f479e0403zrbn request data via set-refresh for [101,102]
2022-03-02 07:58:39.343  - warn: hs100.0 (1224) getDevice Socket connection Timeout ip: 192.168.8.110 please reconnect the Device
2022-03-02 07:58:39.629  - debug: tuya.0 (4366) Discovered encrypted device and store for later usage: 192.168.8.225:50244 - 000055aa00000000000000130000009c00000000f4ac6fd3f5e51601430ee97cfe736a90fa993af9eb5d996b75732f55c082b4e97e893b3e90d62b38427ec5c2eab13ba87c7b818700104fda25e7a029da59d03a7256f992ef0bb3c9946f6ca8e2e148532e0dbc9a92c3317286ebf238be5797867fd5182f0dc1949bfe0816f2f9db35807f1d5d330b0495e894e3fb5771e9be667a23e3b2249f5adf48a714f851aaf439c5e84d3f0000aa55
2022-03-02 07:58:41.207  - debug: tuya.0 (4366) bf99ed882f479e0403zrbn: Error from device (0): App still open on your mobile phone? Timeout waiting for status response from device id: bf99ed882f479e0403zrbn
2022-03-02 07:58:41.208  - debug: tuya.0 (4366) bf99ed882f479e0403zrbn response from set-refresh: undefined
2022-03-02 07:58:46.142  - debug: tuya.0 (4366) bf99ed882f479e0403zrbn: Received data: {"6":"CRoAAAAAAAA="}
2022-03-02 07:58:46.186  - warn: tuya.0 (4366) State "tuya.0.bf99ed882f479e0403zrbn.6" has no existing object, this might lead to an error in future versions
2022-03-02 07:58:46.206  - debug: tuya.0 (4366) stateChange tuya.0.bf99ed882f479e0403zrbn.6 {"val":"CRoAAAAAAAA=","ack":true,"ts":1646204326198,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1646204271698}
2022-03-02 07:58:46.284  - debug: tuya.0 (4366) bf99ed882f479e0403zrbn: Received data: {"18":"AQEAPwMBARMEAQCv"}
2022-03-02 07:58:46.288  - warn: tuya.0 (4366) State "tuya.0.bf99ed882f479e0403zrbn.18" has no existing object, this might lead to an error in future versions
2022-03-02 07:58:46.295  - debug: tuya.0 (4366) stateChange tuya.0.bf99ed882f479e0403zrbn.18 {"val":"AQEAPwMBARMEAQCv","ack":true,"ts":1646204326291,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1646069041872}

[oFbEQnpoLKKl6mbY5e13]

@hausbaer
Hast du die App gleichzeit geöffnet?

[Hausbaer]

@ofbeqnpolkkl6mby5e13 App ist geöffnet, aber eher zufällig.

Das ist aber auch nicht praktikabel, wenn ständig die App geöffnet sein muss, um im System was zu ändern.

Heißt für mich eher, mich nach einer Alternative umzusehen.
Hat jemand den HmIP-DRSI4 von Homematic im Einsatz? Den könnt ich mir noch am ehesten vorstellen.....

[oFbEQnpoLKKl6mbY5e13]

@hausbaer sagte in Tuya will nicht:

@ofbeqnpolkkl6mby5e13 App ist geöffnet, aber eher zufällig.

App darf nicht geöffnet sein.

[Hausbaer]

@ofbeqnpolkkl6mby5e13 Auch bei ausgeschaltenem Gerät wird nicht aktualisiert. Letzter Zeitstempel: 01.03.2022, 10:40

[oFbEQnpoLKKl6mbY5e13]

@hausbaer

State mit iobroker schalten und erneut Debug-Log posten.

[Hausbaer]

Hier der Log, zweimal geschalten.
App aus.

2022-03-02 16:20:09.043  - info: host.raspi-iobroker instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-03-02 16:20:11.521  - warn: tuya.0 (589) State "tuya.0.bf99ed882f479e0403zrbn.6" has no existing object, this might lead to an error in future versions
2022-03-02 16:20:11.662  - warn: tuya.0 (589) State "tuya.0.bf99ed882f479e0403zrbn.18" has no existing object, this might lead to an error in future versions
2022-03-02 16:20:20.250  - info: host.raspi-iobroker stopInstance system.adapter.tuya.0 (force=false, process=true)
2022-03-02 16:20:20.519  - info: tuya.0 (589) Got terminate signal TERMINATE_YOURSELF
2022-03-02 16:20:20.519  - info: host.raspi-iobroker stopInstance system.adapter.tuya.0 send kill signal
2022-03-02 16:20:21.854  - warn: hs100.0 (1212) getDevice Socket connection Timeout ip: 192.168.8.110 please reconnect the Device
2022-03-02 16:20:23.523  - info: tuya.0 (589) terminating
2022-03-02 16:20:23.525  - info: tuya.0 (589) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-03-02 16:20:24.323  - info: host.raspi-iobroker instance system.adapter.tuya.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-03-02 16:20:28.252  - info: host.raspi-iobroker instance system.adapter.tuya.0 started with pid 738
2022-03-02 16:20:29.957  - debug: tuya.0 (738) Redis Objects: Use Redis connection: 0.0.0.0:9001
2022-03-02 16:20:30.038  - debug: tuya.0 (738) Objects client ready ... initialize now
2022-03-02 16:20:30.040  - debug: tuya.0 (738) Objects create System PubSub Client
2022-03-02 16:20:30.042  - debug: tuya.0 (738) Objects create User PubSub Client
2022-03-02 16:20:30.220  - debug: tuya.0 (738) Objects client initialize lua scripts
2022-03-02 16:20:30.227  - debug: tuya.0 (738) Objects connected to redis: 0.0.0.0:9001
2022-03-02 16:20:30.301  - debug: tuya.0 (738) Redis States: Use Redis connection: 0.0.0.0:9000
2022-03-02 16:20:30.344  - debug: tuya.0 (738) States create System PubSub Client
2022-03-02 16:20:30.345  - debug: tuya.0 (738) States create User PubSub Client
2022-03-02 16:20:30.457  - debug: tuya.0 (738) States connected to redis: 0.0.0.0:9000
2022-03-02 16:20:30.965  - debug: tuya.0 (738) Plugin sentry Initialize Plugin (enabled=true)
2022-03-02 16:20:31.589  - info: tuya.0 (738) starting. Version 3.6.15 in /opt/iobroker/node_modules/iobroker.tuya, node: v12.22.9, js-controller: 4.0.15
2022-03-02 16:20:31.634  - info: tuya.0 (738) Polling interval 1 too short, setting to 30s
2022-03-02 16:20:31.715  - debug: tuya.0 (738) init 2 known devices
2022-03-02 16:20:31.720  - debug: tuya.0 (738) bfacd57c23589b3b05crdn: Create device objects if not exist
2022-03-02 16:20:31.722  - debug: tuya.0 (738) bfacd57c23589b3b05crdn: Objects [{"type":"number","unit":"kW·h","max":99999999,"scale":2,"read":true,"write":false,"name":"total_forward_energy","id":1,"role":"value"},{"type":"string","encoding":"base64","read":true,"write":true,"name":"month_energy","id":3,"role":"text"},{"type":"string","encoding":"base64","read":true,"write":true,"name":"daily_energy","id":4,"role":"text"},{"type":"string","encoding":"base64","read":true,"write":false,"name":"phase_a","id":6,"role":"text"},{"type":"number","read":true,"write":false,"name":"fault","id":9,"role":"value"},{"type":"boolean","read":true,"write":true,"name":"switch","id":16,"role":"switch"},{"type":"string","encoding":"base64","read":true,"write":true,"name":"alarm_set_1","id":17,"role":"text"},{"type":"string","encoding":"base64","read":true,"write":true,"name":"alarm_set_2","id":18,"role":"text"},{"type":"string","read":true,"write":false,"name":"breaker_id","id":19,"role":"text"},{"type":"string","read":true,"write":false,"name":"imei_imsi","id":20,"role":"text"},{"type":"string","encoding":"base64","read":true,"write":true,"name":"Icp","id":101,"role":"text"}]
2022-03-02 16:20:31.724  - debug: tuya.0 (738) bfacd57c23589b3b05crdn Register onChange for 3
2022-03-02 16:20:31.725  - debug: tuya.0 (738) bfacd57c23589b3b05crdn Register onChange for 4
2022-03-02 16:20:31.726  - debug: tuya.0 (738) bfacd57c23589b3b05crdn Register onChange for 16
2022-03-02 16:20:31.727  - debug: tuya.0 (738) bfacd57c23589b3b05crdn Register onChange for 17
2022-03-02 16:20:31.727  - debug: tuya.0 (738) bfacd57c23589b3b05crdn Register onChange for 18
2022-03-02 16:20:31.728  - debug: tuya.0 (738) bfacd57c23589b3b05crdn Register onChange for 101
2022-03-02 16:20:31.730  - debug: tuya.0 (738) bf99ed882f479e0403zrbn: Create device objects if not exist
2022-03-02 16:20:31.731  - debug: tuya.0 (738) bf99ed882f479e0403zrbn: Objects [{"type":"string","encoding":"base64","read":true,"write":false,"name":"upward","id":101,"role":"text"},{"type":"string","encoding":"base64","read":true,"write":true,"name":"down","id":102,"role":"text"}]
2022-03-02 16:20:31.731  - debug: tuya.0 (738) bf99ed882f479e0403zrbn Register onChange for 102
2022-03-02 16:20:31.784  - debug: tuya.0 (738) connected set to false
2022-03-02 16:20:31.885  - info: tuya.0 (738) bf99ed882f479e0403zrbn Init with IP=192.168.8.225, Key=60b569b110aa34cb, Version=3.3
2022-03-02 16:20:31.895  - debug: tuya.0 (738) bf99ed882f479e0403zrbn: Connected to device
2022-03-02 16:20:31.917  - debug: tuya.0 (738) bf99ed882f479e0403zrbn: Error from device (0): App still open on your mobile phone? json obj data unvalid
2022-03-02 16:20:31.919  - debug: tuya.0 (738) bf99ed882f479e0403zrbn: Received data: {"1":null,"2":null,"3":null,"101":null,"102":null,"103":null}
2022-03-02 16:20:31.920  - debug: tuya.0 (738) bf99ed882f479e0403zrbn: Ignore invalid data (Counter: 1)
2022-03-02 16:20:31.922  - debug: tuya.0 (738) connected set to true
2022-03-02 16:20:31.958  - info: tuya.0 (738) Existing devices initialized
2022-03-02 16:20:31.965  - info: tuya.0 (738) Listen for local Tuya devices on port 6666
2022-03-02 16:20:31.966  - info: tuya.0 (738) Listen for encrypted local Tuya devices on port 6667
2022-03-02 16:20:32.019  - debug: tuya.0 (738) bf99ed882f479e0403zrbn request data via set-refresh for [101,102]
2022-03-02 16:20:35.166  - debug: tuya.0 (738) Discovered encrypted device and store for later usage: 192.168.8.225:50244 - 000055aa00000000000000130000009c00000000f4ac6fd3f5e51601430ee97cfe736a90fa993af9eb5d996b75732f55c082b4e97e893b3e90d62b38427ec5c2eab13ba87c7b818700104fda25e7a029da59d03a7256f992ef0bb3c9946f6ca8e2e148532e0dbc9a92c3317286ebf238be5797867fd5182f0dc1949bfe0816f2f9db35807f1d5d330b0495e894e3fb5771e9be667a23e3b2249f5adf48a714f851aaf439c5e84d3f0000aa55
2022-03-02 16:20:36.813  - warn: hs100.0 (1212) getDevice Socket connection Timeout ip: 192.168.8.110 please reconnect the Device
2022-03-02 16:20:37.023  - debug: tuya.0 (738) bf99ed882f479e0403zrbn: Error from device (0): App still open on your mobile phone? Timeout waiting for status response from device id: bf99ed882f479e0403zrbn
2022-03-02 16:20:37.025  - debug: tuya.0 (738) bf99ed882f479e0403zrbn response from set-refresh: undefined
2022-03-02 16:20:41.919  - debug: tuya.0 (738) stateChange tuya.0.bfacd57c23589b3b05crdn.16 {"val":true,"ack":false,"ts":1646234441914,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1646234441914}
2022-03-02 16:20:41.920  - debug: tuya.0 (738) bfacd57c23589b3b05crdn onChange triggered for 16 and value true
2022-03-02 16:20:46.921  - debug: tuya.0 (738) bf99ed882f479e0403zrbn: Error from device (1): App still open on your mobile phone? Timeout waiting for status response from device id: bf99ed882f479e0403zrbn
2022-03-02 16:20:46.922  - debug: tuya.0 (738) bfacd57c23589b3b05crdn.16: set value true via bf99ed882f479e0403zrbn
2022-03-02 16:20:47.813  - debug: tuya.0 (738) bf99ed882f479e0403zrbn: Received data: {"6":"CPIAAAAAAAA="}
2022-03-02 16:20:47.818  - warn: tuya.0 (738) State "tuya.0.bf99ed882f479e0403zrbn.6" has no existing object, this might lead to an error in future versions
2022-03-02 16:20:47.828  - debug: tuya.0 (738) stateChange tuya.0.bf99ed882f479e0403zrbn.6 {"val":"CPIAAAAAAAA=","ack":true,"ts":1646234447821,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1646234447821}
2022-03-02 16:20:47.964  - debug: tuya.0 (738) bf99ed882f479e0403zrbn: Received data: {"18":"AQEAPwMBARMEAQCv"}
2022-03-02 16:20:47.984  - warn: tuya.0 (738) State "tuya.0.bf99ed882f479e0403zrbn.18" has no existing object, this might lead to an error in future versions
2022-03-02 16:20:47.996  - debug: tuya.0 (738) stateChange tuya.0.bf99ed882f479e0403zrbn.18 {"val":"AQEAPwMBARMEAQCv","ack":true,"ts":1646234447991,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1646069041872}
2022-03-02 16:20:48.923  - debug: tuya.0 (738) bfacd57c23589b3b05crdn request data via set-refresh for [101,102]
2022-03-02 16:20:51.854  - warn: hs100.0 (1212) getDevice Socket connection Timeout ip: 192.168.8.110 please reconnect the Device
2022-03-02 16:20:53.926  - debug: tuya.0 (738) bf99ed882f479e0403zrbn: Error from device (0): App still open on your mobile phone? Timeout waiting for status response from device id: bf99ed882f479e0403zrbn
2022-03-02 16:20:53.927  - debug: tuya.0 (738) bfacd57c23589b3b05crdn response from set-refresh: undefined
2022-03-02 16:21:03.576  - debug: tuya.0 (738) stateChange tuya.0.bfacd57c23589b3b05crdn.16 {"val":false,"ack":false,"ts":1646234463569,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1646234463569}
2022-03-02 16:21:03.579  - debug: tuya.0 (738) bfacd57c23589b3b05crdn onChange triggered for 16 and value false
2022-03-02 16:21:05.973  - debug: tuya.0 (738) bf99ed882f479e0403zrbn: Received data: {"6":"CPIAAAAAAAA="}
2022-03-02 16:21:05.974  - debug: tuya.0 (738) bfacd57c23589b3b05crdn.16: set value false via bf99ed882f479e0403zrbn
2022-03-02 16:21:05.979  - warn: tuya.0 (738) State "tuya.0.bf99ed882f479e0403zrbn.6" has no existing object, this might lead to an error in future versions
2022-03-02 16:21:05.985  - debug: tuya.0 (738) stateChange tuya.0.bf99ed882f479e0403zrbn.6 {"val":"CPIAAAAAAAA=","ack":true,"ts":1646234465980,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1646234447821}
2022-03-02 16:21:06.114  - debug: tuya.0 (738) bf99ed882f479e0403zrbn: Received data: {"18":"AQEAPwMBARMEAQCv"}
2022-03-02 16:21:06.139  - warn: tuya.0 (738) State "tuya.0.bf99ed882f479e0403zrbn.18" has no existing object, this might lead to an error in future versions
2022-03-02 16:21:06.160  - debug: tuya.0 (738) stateChange tuya.0.bf99ed882f479e0403zrbn.18 {"val":"AQEAPwMBARMEAQCv","ack":true,"ts":1646234466157,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1646069041872}
2022-03-02 16:21:06.814  - warn: hs100.0 (1212) getDevice Socket connection Timeout ip: 192.168.8.110 please reconnect the Device
2022-03-02 16:21:07.975  - debug: tuya.0 (738) bfacd57c23589b3b05crdn request data via set-refresh for [101,102]
2022-03-02 16:21:12.976  - debug: tuya.0 (738) bf99ed882f479e0403zrbn: Error from device (0): App still open on your mobile phone? Timeout waiting for status response from device id: bf99ed882f479e0403zrbn
2022-03-02 16:21:12.977  - debug: tuya.0 (738) bfacd57c23589b3b05crdn response from set-refresh: undefined

[oFbEQnpoLKKl6mbY5e13]

@hausbaer

getDevice Socket connection Timeout ip: 192.168.8.110 please reconnect the Device

Ist das die IP von dem Gateway?

Ich weiß aber auch nicht, ob deine Konstellation mit Tuya-Gateway und Zigbee Geräten überhaupt funktioniert.

[Hausbaer]

@ofbeqnpolkkl6mby5e13 sagte in Tuya will nicht:

@hausbaer

getDevice Socket connection Timeout ip: 192.168.8.110 please reconnect the Device

Ist das die IP von dem Gateway?

Nein, das ist eine Funksteckdose, die wegen eines defekten WLan-Repeaters derzeit keine Verbindung hat. Hat nichts mit dem Probem zu tun

Ich weiß aber auch nicht, ob deine Konstellation mit Tuya-Gateway und Zigbee Geräten überhaupt funktioniert.

Hmm, das sind beides tuya Geräte vom gleichen Hersteller. Oder überseh ich da was?
Ich denke, das Gateway wird richtig erkannt. Die richtige IP wird angezeigt, der online Status ebenfalls und die Werte werden regelmäßig aktualisiert.
Den Schalter werde ich heute mal resetten und neu einbinden. Vllt. hab ich da beim Einbinden einfach das falsche Gerät erwischt.

[Hausbaer]

Heute hab ich sowohl das Gateway als auch den Sicherungsschalter neu verbunden - das Ergebnis ist identisch.

Ich frag mich: Ist der Automat mit Tasmota flashbar?