Navigation

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

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    S
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 22
    • Best 0
    • Groups 1

    Snert

    @Snert

    Starter

    0
    Reputation
    3
    Profile views
    22
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    Snert Follow
    Starter

    Latest posts made by Snert

    • RE: Neu bei ioBroker und Vis (ein MAX! Projekt).

      @opossum said in Neu bei ioBroker und Vis (ein MAX! Projekt).:

      Ich baue die Widgets einzeln, in der Hauptansicht kommt dann das Basic View in Widget zum Einsatz. Hat den Vorteil, dass ich bei Änderungen in einer Ansicht nur die eine View pflegen muss. Diese Thermostatview ist also 9 mal auf der Grundansicht eingebaut.

      Kannst du mir das evtl. genauer erläutern?
      Ich habe mir jetzt eine neue View "Thermostat_Vorlage" erstellt und in dieser habe ich jetzt 1x alles so aufgebaut (inkl. der Datenpunkte für ein Thermostat) wie es gerne hätte.
      Auf meiner View "Thermostat_Übersicht" kann ich 1x ohne Probleme die "Thermostat_Vorlage" über das Widget "View in Widget" einfügen. Sobal ich ein weiteres Widget mit dem Vorlagenview hinzufüge, verschwindet das andere.
      Ebenso die Frage: Wie kann ich innerhalb der "View in Widget" die Datenpunkte anpassen, ohne damit auch die Vorlage zu ändern?

      Vielen Dank

      posted in Visualisierung
      S
      Snert
    • RE: Sonoff zbbridge pro mit Tastmota und ZigBee-Adapter

      @ralla66 Jetzt langsam verstehe ich es nicht mehr.
      Ich hatte zuletzt folgendes gemacht:

      • Auto-configuration auf "Sonoff ZBPro TCP" gestellt (Restart danach)
        Info am Rande, das Template steht auf:
      {"NAME":"TCP ZBBridge Pro","GPIO":[0,0,576,0,480,0,0,0,0,1,1,5792,0,0,0,5472,0,320,5793,5504,0,640,608,32,0,0,0,0,0,1,0,0,0,0,0,0],"FLAG":0,"BASE":1}
      
      • Tasmota wer per web installer (mit FTDI) auf development -> Tasmota32 Sonoff-ZigbeeBridgePro -> All, in der Version 13.2.0.1 geflashed worden.

      • Danach bin ich der Anleitung zum flashen der coordinater Firmware von hier https://notenoughtech.com/home-automation/tasmota-on-sonoff-zb-bridge-pro/#flash gefolgt. Dies wird auch von https://zigbee.blakadder.com/Sonoff_ZBBridge-P.html empfohlen. Allerdings habe ich nicht die SonoffZBPro_coord_20220219.hex Firmware, sondern die SonoffZBPro_coord_20230507.hex hochgeladen und verwendet.

      • Der Flashvorgang wurde auch in der Console mit ok bestätigt, jedoch habe ich zu diesem Zeitpunkt nie folgende Meldungen bekommen:

      22:01:25.294 RSL: RESULT = {"ZbState":{"Status":3,"Message":"Configured, starting coordinator"}}
      22:01:31.293 RSL: RESULT = {"ZbState":{"Status":40,"NewState":9,"Message":"Started as coordinator"}}
      22:01:31.944 RSL: RESULT = {"ZbState":{"Status":0,"Message":"Started"}}
      
      • Der ZigBee-Adapter ist wie folgt konfiguriert:
        0a764cee-9ee9-4c50-a1bb-58813cd80e3d-grafik.png

      Dann musste ich mich eben um mein Kind kümmern und war weg vom PC. Ebenfalls musste ich den Bosch Smart Home Controller II kurzzeitig vom Strom nehmen. (Nur als Info, kp ob das was zu bedeuten hat?!)
      Als ich eben an den PC zurück bin, lief der Adapter und ich kann die ZigBee Geräte anlernen.
      WTF, ich verstehe die Welt nicht mehr.

      Falls noch weitere Infos benötigt werden, um evtl. meine Dummheit oder einen Fehler zu belegen, gerne Bescheid geben.

      EDIT:
      Ich habe eben mal kurz die Erweiterte Pan ID umstellen wollen, danach lief der Adapter nicht mehr. Mit 16x D ging er direkt wieder auf Grün.

      posted in ioBroker Allgemein
      S
      Snert
    • RE: Sonoff zbbridge pro mit Tastmota und ZigBee-Adapter

      @ralla66 Wenn ich den Auto-configuration auf Sonoff ZBPro stelle, erhalte ich nach einem Neustart auch die Meldungen.

      00:00:00.003 HDW: ESP32-D0WD-V3 v3.0 
      00:00:00.207 UFS: FlashFS mounted with 408 kB free
      00:00:00.239 CFG: Loaded from File, Count 39
      00:00:00.241 FRC: Some settings have been reset (2)
      00:00:00.246 I2C: Bus1 using GPIO26(SCL) and GPIO25(SDA)
      00:00:00.392 BRY: Berry initialized, RAM used=3932 bytes
      00:00:00.457 TFS: File '.drvset003' not found
      00:00:00.465 Project tasmota - Tasmota Version 13.2.0.1(zbbrdgpro)-2_0_14(2023-10-27T15:39:53)
      00:00:01.183 WIF: Connecting to AP1 FRITZ!Box 7590 2.4 Channel 1 BSSId 2C:3A:FD:FB:F0:6E in mode 11n as tasmota-6063A4-0932...
      00:00:03.005 WIF: Connected
      00:00:03.262 HTP: Web server active on tasmota-6063A4-0932 with IP address 192.168.178.86
      08:37:35.244 RSL: INFO1 = {"Info1":{"Module":"Sonoff Zigbee Pro","Version":"13.2.0.1(zbbrdgpro)","FallbackTopic":"cmnd/DVES_6063A4_fb/","GroupTopic":"cmnd/tasmotas/"}}
      08:37:35.259 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-6063A4-0932","IPAddress":"192.168.178.86","IP6Global":"","IP6Local":"fe80::4222:d8ff:fe60:63a4"}}
      08:37:35.273 RSL: INFO3 = {"Info3":{"RestartReason":"Software reset CPU","BootCount":19}}
      08:37:35.296 RUL: SYSTEM#BOOT performs "TCPStart 8888"
      08:37:35.299 RSL: RESULT = {"Command":"Error"}
      08:37:37.753 QPC: Reset
      08:37:39.749 RSL: STATE = {"Time":"2023-10-28T08:37:39","Uptime":"0T00:00:09","UptimeSec":9,"Heap":165,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":20,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-28,"LinkCount":1,"Downtime":"0T00:00:04"}}
      08:37:46.745 ZIG: rebooting ZNP device
      08:37:49.397 RSL: RESULT = {"ZbState":{"Status":1,"Message":"CCxxxx ZNP booted","RestartReason":"Power-up","MajorRel":2,"MinorRel":7}}
      08:37:49.597 RSL: RESULT = {"ZbState":{"Status":50,"MajorRel":2,"MinorRel":7,"MaintRel":1,"Revision":20230507}}
      08:37:49.747 RSL: RESULT = {"ZbState":{"Status":2,"Message":"Resetting configuration"}}
      08:37:51.997 RSL: RESULT = {"ZbState":{"Status":3,"Message":"Configured, starting coordinator"}}
      08:37:56.197 RSL: RESULT = {"ZbState":{"Status":40,"NewState":9,"Message":"Started as coordinator"}}
      08:37:56.297 RSL: RESULT = {"ZbState":{"Status":51,"IEEEAddr":"0x00124B00257B0374","ShortAddr":"0x0000","DeviceType":7,"DeviceState":9,"NumAssocDevices":0}}
      08:37:56.797 RSL: RESULT = {"ZbState":{"Status":0,"Message":"Started"}}
      08:37:56.800 ZIG: Zigbee started
      08:37:56.808 ZIG: No Zigbee device information
      08:37:56.811 ZIG: No Zigbee device data
      08:37:56.813 ZIG: ZbLoad '<internal_plugin>' loaded successfully
      

      Mit dier Einstellung bekomme ich aber keine Verbindung vom ioBroker zur Bridge aufgebaut.
      Mit der Auto-configuration Sonoff ZBPro TCP bekomme ich keinerlei Meldungen bezüglich dem Chip, dafür kann die Verbindung wieder hergestellt werden. Zumindest steht das Connect drin.

      00:00:00.003 HDW: ESP32-D0WD-V3 v3.0 
      00:00:00.200 UFS: FlashFS mounted with 408 kB free
      00:00:00.232 CFG: Loaded from File, Count 41
      00:00:00.233 FRC: Some settings have been reset (2)
      00:00:00.239 I2C: Bus1 using GPIO26(SCL) and GPIO25(SDA)
      00:00:00.381 BRY: Berry initialized, RAM used=3936 bytes
      00:00:00.450 TFS: File '.drvset003' not found
      00:00:00.459 Project tasmota - Tasmota Version 13.2.0.1(zbbrdgpro)-2_0_14(2023-10-27T15:39:53)
      00:00:01.195 WIF: Connecting to AP1 FRITZ!Box 7590 2.4 Channel 1 BSSId 2C:3A:FD:FB:F0:6E in mode 11n as tasmota-6063A4-0932...
      00:00:03.020 WIF: Connected
      00:00:03.276 HTP: Web server active on tasmota-6063A4-0932 with IP address 192.168.178.86
      08:43:49.260 RSL: INFO1 = {"Info1":{"Module":"TCP ZBBridge Pro","Version":"13.2.0.1(zbbrdgpro)","FallbackTopic":"cmnd/DVES_6063A4_fb/","GroupTopic":"cmnd/tasmotas/"}}
      08:43:49.275 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-6063A4-0932","IPAddress":"192.168.178.86","IP6Global":"","IP6Local":"fe80::4222:d8ff:fe60:63a4"}}
      08:43:49.289 RSL: INFO3 = {"Info3":{"RestartReason":"Software reset CPU","BootCount":20}}
      08:43:49.312 RUL: SYSTEM#BOOT performs "TCPStart 8888"
      08:43:49.314 TCP: Starting TCP server on port 8888
      08:43:49.318 RSL: RESULT = {"TCPStart":"Done"}
      08:43:51.779 QPC: Reset
      08:43:53.794 RSL: STATE = {"Time":"2023-10-28T08:43:53","Uptime":"0T00:00:09","UptimeSec":9,"Heap":165,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-31,"LinkCount":1,"Downtime":"0T00:00:04"}}
      08:44:18.576 TCP: Got connection from 192.168.178.36
      

      Jetzt die Frage: Sollte ich in der Tasmota console Zigbee infos angezeigt bekommen, wenn die Bridge auf TCP eingestellt ist?
      Mir scheint ja fast, dass etwas mit den GPIO Einstellungen nicht passt. So als ob entweder eine c2652 Verbindung XOR eine TCP Verbindung aufgebaut werden kann.

      Hier auch nochmal der Log vom ioBroker, mit der TCP Einstellung auf der Bridge:

      2023-10-28 09:51:42.548 - info: zigbee.0 (14273) starting. Version 1.8.24 (non-npm: ioBroker/ioBroker.zigbee) in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.20.2, js-controller: 5.0.12
      2023-10-28 09:51:42.597 - info: zigbee.0 (14273) delete old Backup files. keep only last 10
      2023-10-28 09:51:42.598 - info: zigbee.0 (14273) Starting Zigbee npm ...
      2023-10-28 09:51:42.733 - info: zigbee.0 (14273) Installed Version: ioBroker/ioBroker.zigbee
      2023-10-28 09:53:01.043 - info: admin.0 (6349) ==> Connected system.user.admin from ::ffff:192.168.178.89
      2023-10-28 09:53:01.165 - error: zigbee.0 (14273) getGroups: caught error: TypeError: Cannot read properties of undefined (reading 'getGroups')
      2023-10-28 09:53:01.403 - info: zigbee.0 (14273) List of port: [{"path":"/dev/ttyS10"},{"path":"/dev/ttyS11"},{"path":"/dev/ttyS12"},{"path":"/dev/ttyS13"},{"path":"/dev/ttyS14"},{"path":"/dev/ttyS15"},{"path":"/dev/ttyS16"},{"path":"/dev/ttyS17"},{"path":"/dev/ttyS18"},{"path":"/dev/ttyS19"},{"path":"/dev/ttyS2"},{"path":"/dev/ttyS20"},{"path":"/dev/ttyS21"},{"path":"/dev/ttyS22"},{"path":"/dev/ttyS23"},{"path":"/dev/ttyS24"},{"path":"/dev/ttyS25"},{"path":"/dev/ttyS26"},{"path":"/dev/ttyS27"},{"path":"/dev/ttyS28"},{"path":"/dev/ttyS29"},{"path":"/dev/ttyS3"},{"path":"/dev/ttyS30"},{"path":"/dev/ttyS31"},{"path":"/dev/ttyS4"},{"path":"/dev/ttyS5"},{"path":"/dev/ttyS6"},{"path":"/dev/ttyS7"},{"path":"/dev/ttyS8"},{"path":"/dev/ttyS9"},{"path":"/dev/ttyS0"},{"path":"/dev/ttyS1"}]
      2023-10-28 09:53:07.422 - info: admin.0 (6349) <== Disconnect system.user.admin from ::ffff:192.168.178.89
      2023-10-28 09:53:09.031 - info: host.smarthome-VM stopInstance system.adapter.zigbee.0 (force=false, process=true)
      2023-10-28 09:53:09.142 - info: zigbee.0 (14273) Got terminate signal TERMINATE_YOURSELF
      2023-10-28 09:53:09.147 - info: host.smarthome-VM stopInstance system.adapter.zigbee.0 send kill signal
      2023-10-28 09:53:09.143 - info: zigbee.0 (14273) cleaned everything up...
      2023-10-28 09:53:09.145 - info: zigbee.0 (14273) Zigbee: disabling joining new devices.
      2023-10-28 09:53:09.645 - info: zigbee.0 (14273) terminating
      2023-10-28 09:53:09.647 - info: zigbee.0 (14273) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      2023-10-28 09:53:10.154 - info: host.smarthome-VM stopInstance system.adapter.zigbee.0 killing pid 14273
      2023-10-28 09:53:10.272 - info: host.smarthome-VM instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
      2023-10-28 09:53:12.223 - info: host.smarthome-VM instance system.adapter.zigbee.0 started with pid 14291
      2023-10-28 09:53:14.780 - info: zigbee.0 (14291) starting. Version 1.8.24 (non-npm: ioBroker/ioBroker.zigbee) in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.20.2, js-controller: 5.0.12
      2023-10-28 09:53:14.830 - info: zigbee.0 (14291) delete old Backup files. keep only last 10
      2023-10-28 09:53:14.831 - info: zigbee.0 (14291) Starting Zigbee npm ...
      2023-10-28 09:53:14.928 - info: zigbee.0 (14291) Installed Version: ioBroker/ioBroker.zigbee
      2023-10-28 09:54:09.764 - info: host.smarthome-VM instance system.adapter.solarmanpv.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
      2023-10-28 09:54:18.878 - info: admin.0 (6349) ==> Connected system.user.admin from ::ffff:192.168.178.89
      2023-10-28 09:54:19.145 - error: zigbee.0 (14291) getGroups: caught error: TypeError: Cannot read properties of undefined (reading 'getGroups')
      2023-10-28 09:54:19.329 - info: zigbee.0 (14291) List of port: [{"path":"/dev/ttyS10"},{"path":"/dev/ttyS11"},{"path":"/dev/ttyS12"},{"path":"/dev/ttyS13"},{"path":"/dev/ttyS14"},{"path":"/dev/ttyS15"},{"path":"/dev/ttyS16"},{"path":"/dev/ttyS17"},{"path":"/dev/ttyS18"},{"path":"/dev/ttyS19"},{"path":"/dev/ttyS2"},{"path":"/dev/ttyS20"},{"path":"/dev/ttyS21"},{"path":"/dev/ttyS22"},{"path":"/dev/ttyS23"},{"path":"/dev/ttyS24"},{"path":"/dev/ttyS25"},{"path":"/dev/ttyS26"},{"path":"/dev/ttyS27"},{"path":"/dev/ttyS28"},{"path":"/dev/ttyS29"},{"path":"/dev/ttyS3"},{"path":"/dev/ttyS30"},{"path":"/dev/ttyS31"},{"path":"/dev/ttyS4"},{"path":"/dev/ttyS5"},{"path":"/dev/ttyS6"},{"path":"/dev/ttyS7"},{"path":"/dev/ttyS8"},{"path":"/dev/ttyS9"},{"path":"/dev/ttyS0"},{"path":"/dev/ttyS1"}]
      2023-10-28 09:54:54.365 - info: zigbee.0 (14291) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20230507}}
      2023-10-28 09:54:54.432 - info: zigbee.0 (14291) Unable to disable LED, unsupported function.
      2023-10-28 09:54:54.498 - info: zigbee.0 (14291) --> transmitPower : normal
      2023-10-28 09:54:54.849 - info: zigbee.0 (14291) Currently no devices.
      2023-10-28 09:54:54.849 - info: zigbee.0 (14291) Zigbee started
      2023-10-28 09:54:54.853 - error: zigbee.0 (14291) Unable to apply ExtPanID changes: Error: SRSP - SYS - osalNvRead after 0,2ms
      2023-10-28 09:54:54.890 - info: host.smarthome-VM stopInstance system.adapter.zigbee.0 (force=false, process=true)
      2023-10-28 09:54:54.972 - info: zigbee.0 (14291) Got terminate signal TERMINATE_YOURSELF
      2023-10-28 09:54:54.980 - info: host.smarthome-VM stopInstance system.adapter.zigbee.0 send kill signal
      2023-10-28 09:54:54.972 - info: zigbee.0 (14291) cleaned everything up...
      2023-10-28 09:54:54.973 - info: zigbee.0 (14291) Zigbee: disabling joining new devices.
      2023-10-28 09:54:54.999 - info: zigbee.0 (14291) debug devices set to []
      2023-10-28 09:54:55.474 - info: zigbee.0 (14291) terminating
      2023-10-28 09:54:55.475 - info: zigbee.0 (14291) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      2023-10-28 09:54:55.981 - info: host.smarthome-VM stopInstance system.adapter.zigbee.0 killing pid 14291
      2023-10-28 09:54:56.008 - info: host.smarthome-VM instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
      2023-10-28 09:54:58.063 - info: host.smarthome-VM instance system.adapter.zigbee.0 started with pid 14322
      2023-10-28 09:55:00.927 - info: zigbee.0 (14322) starting. Version 1.8.24 (non-npm: ioBroker/ioBroker.zigbee) in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.20.2, js-controller: 5.0.12
      2023-10-28 09:55:01.017 - info: zigbee.0 (14322) delete old Backup files. keep only last 10
      2023-10-28 09:55:01.019 - info: zigbee.0 (14322) Starting Zigbee npm ...
      2023-10-28 09:55:01.209 - info: zigbee.0 (14322) Installed Version: ioBroker/ioBroker.zigbee
      2023-10-28 09:55:20.906 - error: zigbee.0 (14322) Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)"
      2023-10-28 09:55:20.907 - error: zigbee.0 (14322) Failed to start Zigbee
      2023-10-28 09:55:20.907 - error: zigbee.0 (14322) Error herdsman start
      2023-10-28 09:55:30.911 - info: zigbee.0 (14322) Try to reconnect.
      2023-10-28 09:55:30.912 - info: zigbee.0 (14322) Starting Zigbee npm ...
      2023-10-28 09:55:30.924 - info: zigbee.0 (14322) Installed Version: ioBroker/ioBroker.zigbee
      2023-10-28 09:55:48.615 - info: admin.0 (6349) <== Disconnect system.user.admin from ::ffff:192.168.178.89
      2023-10-28 09:55:49.971 - error: zigbee.0 (14322) Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)"
      2023-10-28 09:55:49.973 - error: zigbee.0 (14322) Failed to start Zigbee
      2023-10-28 09:55:49.974 - error: zigbee.0 (14322) Error herdsman start
      2023-10-28 09:55:59.976 - info: zigbee.0 (14322) Try to reconnect.
      2023-10-28 09:55:59.977 - info: zigbee.0 (14322) Starting Zigbee npm ...
      2023-10-28 09:55:59.992 - info: zigbee.0 (14322) Installed Version: ioBroker/ioBroker.zigbee
      2023-10-28 09:56:19.054 - error: zigbee.0 (14322) Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)"
      2023-10-28 09:56:19.056 - error: zigbee.0 (14322) Failed to start Zigbee
      2023-10-28 09:56:19.056 - error: zigbee.0 (14322) Error herdsman start
      2023-10-28 09:56:29.061 - info: zigbee.0 (14322) Try to reconnect.
      2023-10-28 09:56:29.063 - info: zigbee.0 (14322) Starting Zigbee npm ...
      2023-10-28 09:56:29.073 - info: zigbee.0 (14322) Installed Version: ioBroker/ioBroker.zigbee
      2023-10-28 09:56:48.128 - error: zigbee.0 (14322) Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)"
      2023-10-28 09:56:48.131 - error: zigbee.0 (14322) Failed to start Zigbee
      2023-10-28 09:56:48.131 - error: zigbee.0 (14322) Error herdsman start
      2023-10-28 09:56:58.134 - info: zigbee.0 (14322) Try to reconnect.
      2023-10-28 09:56:58.134 - info: zigbee.0 (14322) Starting Zigbee npm ...
      2023-10-28 09:56:58.142 - info: zigbee.0 (14322) Installed Version: ioBroker/ioBroker.zigbee
      
      posted in ioBroker Allgemein
      S
      Snert
    • RE: Sonoff zbbridge pro mit Tastmota und ZigBee-Adapter

      @ralla66 Ja, beide Meldungen sind gekommen.
      Ich habe auch schon vor lauter Verzweiflung mit den "Typen" im ioBroker Adapter gespielt.
      Ebenso auch per Webinstaller den Develop Status verwendet und auch das aktuellste hex file "SonoffZBPro_coord_20230507.hex" genutzt.
      Alles lief immer ohne Probleme durch. Einzig die oben erwähnte Meldung erhalte ich nicht.
      Jetzt kann ich noch mit den Templates spielen, aber ob das was ändert?

      posted in ioBroker Allgemein
      S
      Snert
    • RE: Sonoff zbbridge pro mit Tastmota und ZigBee-Adapter

      @ralla66 Ich habe jetzt alles nochmal von Grund auf neu gemacht.
      Alles beim alten 😞

      Was mir aufgefallen ist, ich erhalte beim flashen vom cc2652 NICHT diese Meldung:

      22:01:25.294 RSL: RESULT = {"ZbState":{"Status":3,"Message":"Configured, starting coordinator"}}
      22:01:31.293 RSL: RESULT = {"ZbState":{"Status":40,"NewState":9,"Message":"Started as coordinator"}}
      22:01:31.944 RSL: RESULT = {"ZbState":{"Status":0,"Message":"Started"}}
      

      Wie in der Anleitung von notenoughtech beschrieben.
      Kann ich irgendwie prüfen welche Version auf dem Chip ist, oder was sein Status ist?
      Das flashen ansonsten wurde jeweils mit ok quitiert.

      posted in ioBroker Allgemein
      S
      Snert
    • RE: Sonoff zbbridge pro mit Tastmota und ZigBee-Adapter

      @ralla66

      8506e8bf-6630-4bb3-8e7e-5a815e96bd8e-grafik.png

      Die eine LED blinkt blau bei WLAN und die andere blinkt grün bei Zigbee Verbindung.

      posted in ioBroker Allgemein
      S
      Snert
    • RE: Sonoff zbbridge pro mit Tastmota und ZigBee-Adapter

      @ralla66 Ja, alles so durchgeführt.
      Baudrate sollte so auch passen.

      RESULT = {"TCPBaudrate":115200}
      

      Könnt ihr mir sagen was in der Tasmota Console bei korrekter Verbindung angezeigt wird?

      Wenn das Kind heute Abend im Bett ist, werde ich alles nochmal in Ruhe neu anfangen. Gibts ne Möglichkeit alles auf 0 zu setzen (auch den CC2652) oder geschieht das automatisch mit dem neuen flashen von Tasmota?

      Edit:

      00:00:00.002 HDW: ESP32-D0WD-V3 v3.0 
      00:00:00.067 UFS: FlashFS mounted with 908 kB free
      00:00:00.081 CFG: Loaded from File, Count 59
      00:00:00.091 QPC: Count 1
      00:00:00.097 I2C: Bus1 using GPIO26(SCL) and GPIO25(SDA)
      00:00:00.162 BRY: Berry initialized, RAM used=3902 bytes
      00:00:00.174 TFS: File '.drvset003' not found
      00:00:00.183 Project tasmota - Tasmota Version 13.2.0(zbbrdgpro)-2_0_14(2023-10-19T09:04:58)
      00:00:00.667 WIF: Connecting to AP1 FRITZ!Box 7590 2.4 Channel 1 BSSId 2C:3A:FD:FB:F0:6E in mode 11n as tasmota-6063A4-0932...
      00:00:02.398 WIF: Connected
      00:00:02.656 HTP: Web server active on tasmota-6063A4-0932 with IP address 192.168.178.86
      10:03:13.662 RSL: INFO1 = {"Info1":{"Module":"Sonoff Zigbee Pro","Version":"13.2.0(zbbrdgpro)","FallbackTopic":"cmnd/DVES_6063A4_fb/","GroupTopic":"cmnd/tasmotas/"}}
      10:03:13.677 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-6063A4-0932","IPAddress":"192.168.178.86","IP6Global":"","IP6Local":"fe80::4222:d8ff:fe60:63a4"}}
      10:03:13.691 RSL: INFO3 = {"Info3":{"RestartReason":"Software reset CPU","BootCount":31}}
      10:03:13.716 RUL: SYSTEM#BOOT performs "TCPStart 8888"
      10:03:13.718 TCP: Starting TCP server on port 8888
      10:03:13.722 RSL: RESULT = {"TCPStart":"Done"}
      10:03:16.964 QPC: Reset
      10:03:17.891 RSL: STATE = {"Time":"2023-10-27T10:03:17","Uptime":"0T00:00:08","UptimeSec":8,"Heap":164,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-37,"LinkCount":1,"Downtime":"0T00:00:03"}}00:00:02.398 WIF: Connected
      00:00:02.656 HTP: Web server active on tasmota-6063A4-0932 with IP address 192.168.178.86
      10:03:13.662 RSL: INFO1 = {"Info1":{"Module":"Sonoff Zigbee Pro","Version":"13.2.0(zbbrdgpro)","FallbackTopic":"cmnd/DVES_6063A4_fb/","GroupTopic":"cmnd/tasmotas/"}}
      10:03:13.677 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-6063A4-0932","IPAddress":"192.168.178.86","IP6Global":"","IP6Local":"fe80::4222:d8ff:fe60:63a4"}}
      10:03:13.691 RSL: INFO3 = {"Info3":{"RestartReason":"Software reset CPU","BootCount":31}}
      10:03:13.716 RUL: SYSTEM#BOOT performs "TCPStart 8888"
      10:03:13.718 TCP: Starting TCP server on port 8888
      10:03:13.722 RSL: RESULT = {"TCPStart":"Done"}
      10:03:16.964 QPC: Reset
      10:03:17.891 RSL: STATE = {"Time":"2023-10-27T10:03:17","Uptime":"0T00:00:08","UptimeSec":8,"Heap":164,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-37,"LinkCount":1,"Downtime":"0T00:00:03"}}
      10:03:28.123 TCP: Got connection from 192.168.178.36
      10:04:12.032 TCP: Got connection from 192.168.178.36
      10:08:17.901 RSL: STATE = {"Time":"2023-10-27T10:08:17","Uptime":"0T00:05:08","UptimeSec":308,"Heap":160,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-38,"LinkCount":1,"Downtime":"0T00:00:03"}}
      10:13:08.930 APP: Serial logging disabled
      10:13:17.936 RSL: STATE = {"Time":"2023-10-27T10:13:17","Uptime":"0T00:10:08","UptimeSec":608,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-36,"LinkCount":1,"Downtime":"0T00:00:03"}}
      10:18:17.912 RSL: STATE = {"Time":"2023-10-27T10:18:17","Uptime":"0T00:15:08","UptimeSec":908,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-35,"LinkCount":1,"Downtime":"0T00:00:03"}}
      10:23:17.896 RSL: STATE = {"Time":"2023-10-27T10:23:17","Uptime":"0T00:20:08","UptimeSec":1208,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-36,"LinkCount":1,"Downtime":"0T00:00:03"}}
      10:28:17.912 RSL: STATE = {"Time":"2023-10-27T10:28:17","Uptime":"0T00:25:08","UptimeSec":1508,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-36,"LinkCount":1,"Downtime":"0T00:00:03"}}
      10:33:17.889 RSL: STATE = {"Time":"2023-10-27T10:33:17","Uptime":"0T00:30:08","UptimeSec":1808,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-36,"LinkCount":1,"Downtime":"0T00:00:03"}}
      10:38:17.927 RSL: STATE = {"Time":"2023-10-27T10:38:17","Uptime":"0T00:35:08","UptimeSec":2108,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-34,"LinkCount":1,"Downtime":"0T00:00:03"}}
      10:43:17.922 RSL: STATE = {"Time":"2023-10-27T10:43:17","Uptime":"0T00:40:08","UptimeSec":2408,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-37,"LinkCount":1,"Downtime":"0T00:00:03"}}
      10:48:17.893 RSL: STATE = {"Time":"2023-10-27T10:48:17","Uptime":"0T00:45:08","UptimeSec":2708,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-36,"LinkCount":1,"Downtime":"0T00:00:03"}}
      10:53:17.889 RSL: STATE = {"Time":"2023-10-27T10:53:17","Uptime":"0T00:50:08","UptimeSec":3008,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-37,"LinkCount":1,"Downtime":"0T00:00:03"}}
      10:58:17.916 RSL: STATE = {"Time":"2023-10-27T10:58:17","Uptime":"0T00:55:08","UptimeSec":3308,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-37,"LinkCount":1,"Downtime":"0T00:00:03"}}
      11:03:17.910 RSL: STATE = {"Time":"2023-10-27T11:03:17","Uptime":"0T01:00:08","UptimeSec":3608,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-35,"LinkCount":1,"Downtime":"0T00:00:03"}}
      11:08:17.903 RSL: STATE = {"Time":"2023-10-27T11:08:17","Uptime":"0T01:05:08","UptimeSec":3908,"Heap":163,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-36,"LinkCount":1,"Downtime":"0T00:00:03"}}
      11:11:45.034 CMD: TCPBaudRate
      11:11:45.039 RSL: RESULT = {"TCPBaudrate":115200}
      11:13:17.921 RSL: STATE = {"Time":"2023-10-27T11:13:17","Uptime":"0T01:10:08","UptimeSec":4208,"Heap":160,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-35,"LinkCount":1,"Downtime":"0T00:00:03"}}
      11:18:17.925 RSL: STATE = {"Time":"2023-10-27T11:18:17","Uptime":"0T01:15:08","UptimeSec":4508,"Heap":160,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":43},"Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 2.4","BSSId":"2C:3A:FD:FB:F0:6E","Channel":1,"Mode":"11n","RSSI":100,"Signal":-36,"LinkCount":1,"Downtime":"0T00:00:03"}}
      11:21:46.024 CMD: TCPBaudRate
      11:21:46.029 RSL: RESULT = {"TCPBaudrate":115200}
      
      posted in ioBroker Allgemein
      S
      Snert
    • RE: Sonoff zbbridge pro mit Tastmota und ZigBee-Adapter

      @arteck Da noch einiges mehr auf dem Server an VMs läuft, hatte ich mich dafür entschieden den ioBroker hier zu installieren.

      Bezüglich udev, ist das nicht nur erforderlich wenn ich einen USB Stick verwenden würde?

      @Ralla66 ich habe jetzt auch per OTA geupdated, ohne weitere Verbesserungen.

      posted in ioBroker Allgemein
      S
      Snert
    • RE: Sonoff zbbridge pro mit Tastmota und ZigBee-Adapter

      @ralla66 In einer Windows Server HyperV VM mit Ubuntu. Die VM hat 16GB Ram und die Host CPU ist ein Intel Core i5-4590 CPU @ 3.30GHz.

      posted in ioBroker Allgemein
      S
      Snert
    • RE: Sonoff zbbridge pro mit Tastmota und ZigBee-Adapter

      @arteck Habe die Version 1.8.24 über GIT geladen. Ergebnis ist erstmal das selbe, aber vll. hilft es trozdem weiter.

      2023-10-26 22:17:19.749 - info: host.smarthome-VM instance system.adapter.zigbee.0 started with pid 874855
      2023-10-26 22:17:20.240 - info: admin.0 (649296) ==> Connected system.user.admin from ::ffff:192.168.178.89
      2023-10-26 22:17:22.388 - info: zigbee.0 (874855) starting. Version 1.8.24 (non-npm: ioBroker/ioBroker.zigbee) in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.0, js-controller: 4.0.24
      2023-10-26 22:17:22.477 - error: zigbee.0 (874855) Serial port not selected! Go to settings page.
      2023-10-26 22:17:22.595 - info: zigbee.0 (874855) delete old Backup files. keep only last 10
      2023-10-26 22:17:22.596 - info: zigbee.0 (874855) Starting Zigbee npm ...
      2023-10-26 22:17:23.319 - error: zigbee.0 (874855) Starting zigbee-herdsman problem : "No path provided and failed to auto detect path"
      2023-10-26 22:17:23.320 - error: zigbee.0 (874855) Failed to start Zigbee
      2023-10-26 22:17:23.320 - error: zigbee.0 (874855) Error herdsman start
      2023-10-26 22:17:23.344 - info: zigbee.0 (874855) Installed Version: ioBroker/ioBroker.zigbee
      2023-10-26 22:17:33.322 - info: zigbee.0 (874855) Try to reconnect. 1 attempts left
      2023-10-26 22:17:33.324 - info: zigbee.0 (874855) Starting Zigbee npm ...
      2023-10-26 22:17:33.368 - info: zigbee.0 (874855) Installed Version: ioBroker/ioBroker.zigbee
      2023-10-26 22:17:33.733 - error: zigbee.0 (874855) Starting zigbee-herdsman problem : "No path provided and failed to auto detect path"
      2023-10-26 22:17:33.734 - error: zigbee.0 (874855) Failed to start Zigbee
      2023-10-26 22:17:33.735 - error: zigbee.0 (874855) Error herdsman start
      2023-10-26 22:18:19.826 - info: host.smarthome-VM stopInstance system.adapter.zigbee.0 (force=false, process=true)
      2023-10-26 22:18:19.893 - info: zigbee.0 (874855) Got terminate signal TERMINATE_YOURSELF
      2023-10-26 22:18:19.904 - info: host.smarthome-VM stopInstance system.adapter.zigbee.0 send kill signal
      2023-10-26 22:18:19.894 - info: zigbee.0 (874855) cleaned everything up...
      2023-10-26 22:18:19.897 - info: zigbee.0 (874855) Zigbee: disabling joining new devices.
      2023-10-26 22:18:19.925 - warn: zigbee.0 (874855) Failed to stop zigbee during startup
      2023-10-26 22:18:19.932 - info: zigbee.0 (874855) terminating
      2023-10-26 22:18:19.933 - info: zigbee.0 (874855) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      2023-10-26 22:18:20.094 - info: admin.0 (649296) <== Disconnect system.user.admin from ::ffff:192.168.178.89
      2023-10-26 22:18:20.540 - info: host.smarthome-VM instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
      2023-10-26 22:18:22.995 - info: host.smarthome-VM instance system.adapter.zigbee.0 started with pid 874887
      2023-10-26 22:18:26.421 - info: zigbee.0 (874887) starting. Version 1.8.24 (non-npm: ioBroker/ioBroker.zigbee) in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.0, js-controller: 4.0.24
      2023-10-26 22:18:26.504 - info: zigbee.0 (874887) delete old Backup files. keep only last 10
      2023-10-26 22:18:26.506 - info: zigbee.0 (874887) Starting Zigbee npm ...
      2023-10-26 22:18:26.914 - info: zigbee.0 (874887) Installed Version: ioBroker/ioBroker.zigbee
      2023-10-26 22:18:36.915 - error: zigbee.0 (874887) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      2023-10-26 22:18:36.916 - error: zigbee.0 (874887) unhandled promise rejection: Reset error: Error: {"sequence":-1} after 10000ms
      2023-10-26 22:18:37.058 - error: zigbee.0 (874887) Error: Reset error: Error: {"sequence":-1} after 10000ms
      at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23
      at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
      2023-10-26 22:18:37.059 - error: zigbee.0 (874887) Reset error: Error: {"sequence":-1} after 10000ms
      2023-10-26 22:18:37.164 - info: zigbee.0 (874887) cleaned everything up...
      2023-10-26 22:18:37.172 - info: zigbee.0 (874887) Zigbee: disabling joining new devices.
      2023-10-26 22:18:37.443 - warn: zigbee.0 (874887) Failed to stop zigbee during startup
      2023-10-26 22:18:37.444 - info: zigbee.0 (874887) terminating
      2023-10-26 22:18:37.445 - warn: zigbee.0 (874887) Terminated (UNCAUGHT_EXCEPTION): Without reason
      2023-10-26 22:18:38.095 - error: host.smarthome-VM Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
      2023-10-26 22:18:38.095 - error: host.smarthome-VM Caught by controller[0]: Error: Reset error: Error: {"sequence":-1} after 10000ms
      2023-10-26 22:18:38.096 - error: host.smarthome-VM Caught by controller[0]: at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23
      2023-10-26 22:18:38.096 - error: host.smarthome-VM Caught by controller[0]: at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
      2023-10-26 22:18:38.096 - error: host.smarthome-VM instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
      2023-10-26 22:18:38.096 - info: host.smarthome-VM Restart adapter system.adapter.zigbee.0 because enabled
      2023-10-26 22:19:08.160 - info: host.smarthome-VM instance system.adapter.zigbee.0 started with pid 874904
      2023-10-26 22:19:11.250 - info: zigbee.0 (874904) starting. Version 1.8.24 (non-npm: ioBroker/ioBroker.zigbee) in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.0, js-controller: 4.0.24
      2023-10-26 22:19:11.312 - info: zigbee.0 (874904) delete old Backup files. keep only last 10
      2023-10-26 22:19:11.313 - info: zigbee.0 (874904) Starting Zigbee npm ...
      2023-10-26 22:19:11.675 - info: zigbee.0 (874904) Installed Version: ioBroker/ioBroker.zigbee
      2023-10-26 22:19:21.672 - error: zigbee.0 (874904) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      2023-10-26 22:19:21.674 - error: zigbee.0 (874904) unhandled promise rejection: Reset error: Error: {"sequence":-1} after 10000ms
      2023-10-26 22:19:21.746 - error: zigbee.0 (874904) Error: Reset error: Error: {"sequence":-1} after 10000ms
      at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23
      at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
      2023-10-26 22:19:21.747 - error: zigbee.0 (874904) Reset error: Error: {"sequence":-1} after 10000ms
      2023-10-26 22:19:21.772 - info: zigbee.0 (874904) cleaned everything up...
      2023-10-26 22:19:21.775 - info: zigbee.0 (874904) Zigbee: disabling joining new devices.
      2023-10-26 22:19:21.980 - warn: zigbee.0 (874904) Failed to stop zigbee during startup
      2023-10-26 22:19:21.981 - info: zigbee.0 (874904) terminating
      2023-10-26 22:19:21.982 - warn: zigbee.0 (874904) Terminated (UNCAUGHT_EXCEPTION): Without reason
      2023-10-26 22:19:22.603 - error: host.smarthome-VM Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
      2023-10-26 22:19:22.603 - error: host.smarthome-VM Caught by controller[1]: Error: Reset error: Error: {"sequence":-1} after 10000ms
      2023-10-26 22:19:22.603 - error: host.smarthome-VM Caught by controller[1]: at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23
      2023-10-26 22:19:22.603 - error: host.smarthome-VM Caught by controller[1]: at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
      2023-10-26 22:19:22.604 - error: host.smarthome-VM instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
      2023-10-26 22:19:22.604 - info: host.smarthome-VM Restart adapter system.adapter.zigbee.0 because enabled
      2023-10-26 22:19:52.688 - info: host.smarthome-VM instance system.adapter.zigbee.0 started with pid 874919
      2023-10-26 22:19:55.225 - info: zigbee.0 (874919) starting. Version 1.8.24 (non-npm: ioBroker/ioBroker.zigbee) in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.0, js-controller: 4.0.24
      2023-10-26 22:19:55.282 - info: zigbee.0 (874919) delete old Backup files. keep only last 10
      2023-10-26 22:19:55.283 - info: zigbee.0 (874919) Starting Zigbee npm ...
      2023-10-26 22:19:55.596 - info: zigbee.0 (874919) Installed Version: ioBroker/ioBroker.zigbee
      2023-10-26 22:20:00.074 - info: host.smarthome-VM instance system.adapter.netatmo-crawler.0 started with pid 874934
      2023-10-26 22:20:05.596 - error: zigbee.0 (874919) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      2023-10-26 22:20:05.655 - info: host.smarthome-VM instance system.adapter.netatmo-crawler.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
      2023-10-26 22:20:05.598 - error: zigbee.0 (874919) unhandled promise rejection: Reset error: Error: {"sequence":-1} after 10000ms
      2023-10-26 22:20:05.736 - error: zigbee.0 (874919) Error: Reset error: Error: {"sequence":-1} after 10000ms
      at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23
      at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
      2023-10-26 22:20:05.736 - error: zigbee.0 (874919) Reset error: Error: {"sequence":-1} after 10000ms
      2023-10-26 22:20:05.795 - info: zigbee.0 (874919) cleaned everything up...
      2023-10-26 22:20:05.809 - info: zigbee.0 (874919) Zigbee: disabling joining new devices.
      2023-10-26 22:20:05.939 - warn: zigbee.0 (874919) Failed to stop zigbee during startup
      2023-10-26 22:20:05.940 - info: zigbee.0 (874919) terminating
      2023-10-26 22:20:05.941 - warn: zigbee.0 (874919) Terminated (UNCAUGHT_EXCEPTION): Without reason
      2023-10-26 22:20:06.603 - error: host.smarthome-VM Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
      2023-10-26 22:20:06.604 - error: host.smarthome-VM Caught by controller[0]: Error: Reset error: Error: {"sequence":-1} after 10000ms
      2023-10-26 22:20:06.604 - error: host.smarthome-VM Caught by controller[0]: at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23
      2023-10-26 22:20:06.604 - error: host.smarthome-VM Caught by controller[0]: at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
      2023-10-26 22:20:06.604 - error: host.smarthome-VM instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
      2023-10-26 22:20:06.605 - info: host.smarthome-VM Restart adapter system.adapter.zigbee.0 because enabled
      2023-10-26 22:20:06.605 - warn: host.smarthome-VM Do not restart adapter system.adapter.zigbee.0 because restart loop detected
      

      @Ralla66 auch mit angepastem Template und der Rule, selbes Ergebnis. Morgen kann ich gerne nochmal mich an die andere Anleitung halten.

      posted in ioBroker Allgemein
      S
      Snert
    Community
    Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
    The ioBroker Community 2014-2023
    logo