Hallo zusammen,
sorry erst mal, das ich solange kein Update gegeben hab. Letzte Woche Gamescom und div. anderer Stress hat mich etwas zurückgeworfen ;-).

Leider hat sich grundsätzlich nicht viel geändert. Zahlreiche Geräte wollen einfach nicht mehr antworten. einiges Geht Grundsätzlich. Nachdem ich bspw. mein Stimmungslicht (irgendwie versehentlich) in den Koppelmodus versetzt hab und im Zigbee Adapter angelernt hab hat es auch wieder in meinen Szenen funktioniert.

es kommen auch immer wieder Meldungen wie:

DeviceAvailability:Stopping to ping 0x540f57fffe3f5d26 TS011F after 4 ping attempts
(das ist die Einspeisesteckdose von meinem Balkonkraftwerk)

Was bspw. immer noch nicht geht ist die Erfassung meiner Schaltsteckdose von der Solaranlage. Seitdem bekomm ich auch keine Messwerte mehr über die erzeugte Energie. Mittlerweile hab ich mich ja fast damit abgefunden, das ich die Geräte teilweise neu anlernen muss. Aber ich trau mich auch nicht ganz gerade diese neu zu koppeln, da ich bedenken hab, das die akt. gespeicherte Werte dann auch gelöscht werden und der kWh-Zähler wieder bei 0 steht... Habt ihr hier Erfahrungen?

@dp20eic sagte in Zigbee Problem nach Migration:

Aber wie gesagt, wichtig ist, dass da wohl ein Kabel zwischen RasPI und Zigbee-Stick ist, damit der Stick die besten Voraussetzungen hat, um korrekt zu arbeiten.
ich habe bereits nach dem ersten Hinweis von dir bereits ein USB-Verlängerungskabel dazwischen gehängt. Seit dem leider aber eigentlich keine Änderung im Verhalten.

@dp20eic sagte in Zigbee Problem nach Migration:

P.S.: Du solltest vielleicht auch nicht /dev/ttyACMx nutzen, sondern lieber /dev/serial/by-id/dein_usb-stick das ist eindeutig, auch wenn du den mal an einen anderen Port hängst.
Ich arbeite bereits von Anfang an mit dem String

/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE26xxxxx-if00

@dp20eic sagte in Zigbee Problem nach Migration:

Du kannst dir ausführliche Informationen anschauen, mit

# sudo lsusb -v
oder
# usb-device

bei usb-devices kommt für con ConBee folgendes raus:

T:  Bus=01 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#=  3 Spd=12  MxCh= 0
D:  Ver= 2.01 Cls=02(commc) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=1cf1 ProdID=0030 Rev=01.00
S:  Manufacturer=dresden elektronik ingenieurtechnik GmbH
S:  Product=ConBee II
S:  SerialNumber=DE26xxxxx
C:  #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=cdc_acm
E:  Ad=83(I) Atr=03(Int.) MxPS=  64 Ivl=16ms
I:  If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms

Und bei "lsusb -v" folgendes

Bus 001 Device 003: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II]
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.01
  bDeviceClass            2 Communications
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x1cf1 Dresden Elektronik
  idProduct          0x0030 ZigBee gateway [ConBee II]
  bcdDevice            1.00
  iManufacturer           1 dresden elektronik ingenieurtechnik GmbH
  iProduct                2 ConBee II
  iSerial                 3 DE26xxxxx
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0043
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         2 Communications
      bInterfaceSubClass      2 Abstract (modem)
      bInterfaceProtocol      1 AT-commands (v.25ter)
      iInterface              0 
      CDC Header:
        bcdCDC               1.10
      CDC ACM:
        bmCapabilities       0x02
          line coding and serial state
      CDC Union:
        bMasterInterface        0
        bSlaveInterface         1 
      CDC Call Management:
        bmCapabilities       0x03
          call management
          use DataInterface
        bDataInterface          1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval              16
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Binary Object Store Descriptor:
  bLength                 5
  bDescriptorType        15
  wTotalLength       0x000c
  bNumDeviceCaps          1
  USB 2.0 Extension Device Capability:
    bLength                 7
    bDescriptorType        16
    bDevCapabilityType      2
    bmAttributes   0x00000002
      HIRD Link Power Management (LPM) Supported
Device Status:     0x0000
  (Bus Powered)

Gruß Christian

@dp20eic
spannende Sache auf jedenfall. ich bin nicht sicher wie die Ports nummeriert werden, aber es sieht so aus als würde der stick nicht am Port 3 hängen

$ ls -R /dev/bus/usb
/dev/bus/usb:
001  002
/dev/bus/usb/001:
001  002  003
/dev/bus/usb/002:
001

$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II]
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

@thomas-braun sagte in Zigbee Problem nach Migration:

Gib dem System etwas SWAP.

ich hab den Swap mal von 2GB auf 4GB erweitert. ich bin jetzt nicht so der ober Linux Spezi, aber es sieht so aus als würde der swap nicht verwendet:

$ free -m
               total        used        free      shared  buff/cache   available
Mem:            3790        1014        2277           3         497        2613
Swap:           4095           0        4095

das war der Zustand kurz nach dem Reboot. vorher (habs leider nicht kopiert) waren es eben 2047 und auch 0 used Swap. Der free-Mem stand glaub ich irgendwo im 3-Stelligen bereich...
ab wann wird Swap verwendet? ich hab das Tool dphys-swapfile installiert um die Änderungen am Swap umzusetzen.

Gruß Chris

servus Thomas,

heute hab ich die Kühlköper installiert und das original Netzteil in Betrieb genommen. Zudem auch noch die letzten Ubuntu Updates installiert.

aktuell verählt sich Zigbee aber quasi genau wie vorher:

christian@iobroker:~$ iob logs zigbee | grep -v info
2023-08-15 21:59:26.737  - error: zigbee.0 (1140) DeviceConfigure:Failed to DeviceConfigure.configure 0x2c1165fffe99b52f TS004F (Error: Read 0x2c1165fffe99b52f/1 genBasic([4,0,1,5,7,65534], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received (2))
2023-08-15 21:59:37.777  - warn: zigbee.0 (1140) DeviceAvailability:Failed to ping 0x842e14fffe5a22f6 TS011F
2023-08-15 21:59:38.777  - warn: zigbee.0 (1140) DeviceAvailability:Failed to ping 0xa4c138cdb62a8b5d TS011F
2023-08-15 21:59:38.778  - warn: zigbee.0 (1140) DeviceAvailability:Failed to ping 0x540f57fffe3f5d26 TS011F
2023-08-15 21:59:39.777  - warn: zigbee.0 (1140) DeviceAvailability:Failed to ping 0xe0798dfffe886e8e A10
2023-08-15 21:59:39.778  - warn: zigbee.0 (1140) DeviceAvailability:Failed to ping 0x842e14fffeefe9d2 TS011F
2023-08-15 21:59:40.777  - warn: zigbee.0 (1140) DeviceAvailability:Failed to ping 0xa4c138912df72585 TS011F
2023-08-15 22:00:05.576  - error: zigbee.0 (1140) No entity for 0x9035eafffe233190
2023-08-15 22:00:05.918  - error: zigbee.0 (1140) No entity for 0x9035eafffe233190
2023-08-15 22:00:11.627  - error: zigbee.0 (1140) No entity for 0x9035eafffe233190
2023-08-15 22:00:11.695  - error: zigbee.0 (1140) No entity for 0x9035eafffe233190
2023-08-15 22:01:38.546  - warn: zigbee.0 (1140) Device '0x847127fffe75db97' announced itself
2023-08-15 22:01:53.284  - error: zigbee.0 (1140) No entity for 0x9035eafffe233190
2023-08-15 22:01:55.943  - error: zigbee.0 (1140) No entity for 0x9035eafffe233190
2023-08-15 22:01:57.092  - error: zigbee.0 (1140) No entity for 0x9035eafffe233190
2023-08-15 22:01:58.885  - error: zigbee.0 (1140) No entity for 0x9035eafffe233190
2023-08-15 22:02:06.989  - error: zigbee.0 (1140) No entity for 0x9035eafffe233190
2023-08-15 22:03:43.457  - error: zigbee.0 (1140) No entity for 0x9035eafffe233190
2023-08-15 22:03:48.291  - error: zigbee.0 (1140) No entity for 0x9035eafffe233190

======================= SUMMARY =======================
		     v.2023-04-16


Operatingsystem: 	Ubuntu 22.04.3 LTS
Kernel: 		5.15.0-1035-raspi
Installation: 		Native
Timezone: 		Europe/Berlin (CEST, +0200)
User-ID: 		1000
X-Server: 		false
Boot Target: 		graphical.target

Pending OS-Updates: 	0
Pending iob updates: 	0

Nodejs-Installation: 	/usr/bin/nodejs 	v18.17.1
			/usr/bin/node 		v18.17.1
			/usr/bin/npm 		9.6.7
			/usr/bin/npx 		9.6.7

Recommended versions are nodejs 18.x.y and npm 9.x.y
Your nodejs installation is correct

MEMORY: 
               total        used        free      shared  buff/cache   available
Mem:            3.8G        1.1G        1.9G        3.0M        837M        2.5G
Swap:             0B          0B          0B
Total:          3.8G        1.1G        1.9G

Active iob-Instances: 	13
Active repo(s): stable

ioBroker Core: 		js-controller 		4.0.24
			admin 			6.3.5

ioBroker Status: 	iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Status admin and web instance:
+ system.adapter.admin.0                  : admin                 : iobroker                                 -  enabled, compact disabled, port: 443, bind: 192.168.178.251 (SSL), run as: admin
+ system.adapter.web.0                    : web                   : iobroker                                 -  enabled, compact disabled, port: 8082, bind: 192.168.178.251 (SSL), run as: admin

Objects: 		4797
States: 		3738

Size of iob-Database:

14M	/opt/iobroker/iobroker-data/objects.jsonl
5.8M	/opt/iobroker/iobroker-data/states.jsonl



=================== END OF SUMMARY ====================

was soll mir der Eintrag " No entity for 0x9035eafffe233190 " sagen? das ist bspw. ein Stimmungslicht von Livrano (Lidl)

noch Ideen was ich tun kann?

Gruß Chris

@thomas-braun

@thomas-braun sagte in Zigbee Problem nach Migration:

@derroch sagte in Zigbee Problem nach Migration:

Raspberry only: throttled=0x50005

Dem Raspberry geht's nicht gut. Zu warm oder zu wenig Saft.

Okay, dann besorg ich mir doch mal das original Netzteil. aktuell hab ich ein 2.5A-Netzteil dran. ich hab irgendwann mal eine Log-Meldung im Raspi gesehen die sich über zuwenig Power beschwert hat. Evtl ist dass des Rätsels lösung.

Besten dank für die schnellen Antworten. Mega gut
Gute nacht schon mal.
Gruß Chris

@thomas-braun

======================= SUMMARY =======================
		     v.2023-04-16


Operatingsystem: 	Ubuntu 22.04.3 LTS
Kernel: 		5.15.0-1034-raspi
Installation: 		Native
Timezone: 		Europe/Berlin (CEST, +0200)
User-ID: 		1000
X-Server: 		false
Boot Target: 		graphical.target

Pending OS-Updates: 	3
Pending iob updates: 	0

Nodejs-Installation: 	/usr/bin/nodejs 	v18.17.1
			/usr/bin/node 		v18.17.1
			/usr/bin/npm 		9.6.7
			/usr/bin/npx 		9.6.7

Recommended versions are nodejs 18.x.y and npm 9.x.y
Your nodejs installation is correct

MEMORY: 
               total        used        free      shared  buff/cache   available
Mem:            3.8G        1.2G        1.4G        3.0M        1.1G        2.4G
Swap:             0B          0B          0B
Total:          3.8G        1.2G        1.4G

Active iob-Instances: 	14
Active repo(s): stable

ioBroker Core: 		js-controller 		4.0.24
			admin 			6.3.5

ioBroker Status: 	iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Status admin and web instance:
+ system.adapter.admin.0                  : admin                 : iobroker                                 -  enabled, compact disabled, port: 443, bind: 192.168.178.251 (SSL), run as: admin
+ system.adapter.web.0                    : web                   : iobroker                                 -  enabled, compact disabled, port: 8082, bind: 192.168.178.251 (SSL), run as: admin

Objects: 		4843
States: 		3764

Size of iob-Database:

12M	/opt/iobroker/iobroker-data/objects.jsonl
1000K	/opt/iobroker/iobroker-data/states.jsonl



=================== END OF SUMMARY ====================

christian@iobroker:~$ iob logs zigbee | grep -v info
2023-08-14 00:08:45.034  - error: zigbee.0 (9225) DeviceConfigure:Failed to DeviceConfigure.configure 0x2c1165fffe99b52f TS004F (Error: Read 0x2c1165fffe99b52f/1 genBasic([4,0,1,5,7,65534], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received (2))
2023-08-14 00:08:56.861  - warn: zigbee.0 (9225) DeviceAvailability:Failed to ping 0x842e14fffeefe9d2 TS011F
2023-08-14 00:08:56.864  - warn: zigbee.0 (9225) DeviceAvailability:Failed to ping 0x842e14fffe5a22f6 TS011F
2023-08-14 00:08:56.866  - warn: zigbee.0 (9225) DeviceAvailability:Failed to ping 0x540f57fffe3f5d26 TS011F
2023-08-14 00:08:57.859  - warn: zigbee.0 (9225) DeviceAvailability:Failed to ping 0xe0798dfffe886e8e A10
2023-08-14 00:08:58.861  - warn: zigbee.0 (9225) DeviceAvailability:Failed to ping 0xa4c138cdb62a8b5d TS011F
2023-08-14 00:08:58.863  - warn: zigbee.0 (9225) DeviceAvailability:Failed to ping 0xa4c138912df72585 TS011F

Hallo zusammen,

ich habe heute meine iobroker installation auf einen Raspberry Pi 4 migriert. ist meines Wissens nach alles auf dem aktuellsten Stand. Node.js v18.17.1, NPM 9.6.7, Admin 6.3.5, Zigbee 1.8.23...
Zuvor lief alles auf einem Master/Slave installation. Master war eine Ubuntu VM auf meiner QNAP die alles außer Zigbee beherbergte. Auf einem OrangePi lief Armbian mit der iobroker Slave installation. das Ganze lief knapp ein 3/4 Jahr weitgehend stabil.

Weil die QNAP weichen muss habe ich das auf einen neuen Raspi migriert. Das war zwar auch etwas hakelig, letztlich läuft aber alles dank BackItUp. Konnte auch Zigbee wieder auf die Hauptinstanz zurück verschieben, den nicht mehr vorhandenen Slave entfernen.

Zigbee läuft grundlegend würde ich sagen. Hardware ist ein USB-Stick von Dresden ConBee2. Es lassen sich auch einige Geräte wieder schalten, viele aber leider nicht. Insg. sind knapp 44 Geräte angemeldet. Davon sind leider nur 13 erreichbar, der rest ist "available" false. Es gibt ja immer wieder mal Geräte die nicht verfügbar sind (weil nur mit Knopfzellen betrieben wie Fenstersensoren) aber nach dem Upgrade ist es schon viel.

Ein Beispiel ist auch ein Stimmungslicht (mit Netzteil) welches im Log immer nur meldet: No entity for 0x9035eafffe233190 (das ist die ID des Geräts).

so siehts im Log aus (gefiltert auf zigbee; ohne info):

iob logs zigbee | grep -v info
2023-08-13 22:36:45.179  - error: zigbee.0 (3305) DeviceConfigure:Failed to DeviceConfigure.configure 0x2c1165fffe99b52f TS004F (Error: Bind 0x2c1165fffe99b52f/1 genPowerCfg from '0x00212effff095f03/1' failed (waiting for response TIMEOUT)
2023-08-13 22:37:47.097  - warn: zigbee.0 (3305) DeviceAvailability:Failed to ping 0x842e14fffe5a22f6 TS011F
2023-08-13 22:37:48.097  - warn: zigbee.0 (3305) DeviceAvailability:Failed to ping 0x540f57fffe3f5d26 TS011F
2023-08-13 22:37:49.097  - warn: zigbee.0 (3305) DeviceAvailability:Failed to ping 0x842e14fffeefe9d2 TS011F
2023-08-13 22:37:50.098  - warn: zigbee.0 (3305) DeviceAvailability:Failed to ping 0xe0798dfffe886e8e A10
2023-08-13 22:37:50.107  - warn: zigbee.0 (3305) DeviceAvailability:Failed to ping 0xa4c138cdb62a8b5d TS011F
2023-08-13 22:37:50.109  - warn: zigbee.0 (3305) DeviceAvailability:Failed to ping 0xa4c138912df72585 TS011F
2023-08-13 22:40:50.200  - error: zigbee.0 (4359) DeviceConfigure:Failed to DeviceConfigure.configure 0x2c1165fffe99b52f TS004F (Error: Read 0x2c1165fffe99b52f/1 genBasic([4,0,1,5,7,65534], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received (2))
2023-08-13 22:41:03.046  - warn: zigbee.0 (4359) DeviceAvailability:Failed to ping 0x842e14fffeefe9d2 TS011F
2023-08-13 22:41:03.048  - warn: zigbee.0 (4359) DeviceAvailability:Failed to ping 0x5c0272fffe8c7426 TS011F
2023-08-13 22:41:03.050  - warn: zigbee.0 (4359) DeviceAvailability:Failed to ping 0x842e14fffe5a22f6 TS011F
2023-08-13 22:41:03.051  - warn: zigbee.0 (4359) DeviceAvailability:Failed to ping 0x540f57fffe3f5d26 TS011F
2023-08-13 22:41:04.045  - warn: zigbee.0 (4359) DeviceAvailability:Failed to ping 0xe0798dfffe886e8e A10
2023-08-13 22:41:05.045  - warn: zigbee.0 (4359) DeviceAvailability:Failed to ping 0xe0798dfffec6c464 A10
2023-08-13 22:41:05.047  - warn: zigbee.0 (4359) DeviceAvailability:Failed to ping 0xa4c138cdb62a8b5d TS011F
2023-08-13 22:41:05.049  - warn: zigbee.0 (4359) DeviceAvailability:Failed to ping 0xa4c138912df72585 TS011F
2023-08-13 22:41:56.428  - error: zigbee.0 (4359) No entity for 0x9035eafffe233190
2023-08-13 22:41:56.448  - error: zigbee.0 (4359) No entity for 0x9035eafffe233190
2023-08-13 22:42:34.626  - error: zigbee.0 (4359) No entity for 0x9035eafffe233190
2023-08-13 22:42:34.771  - error: zigbee.0 (4359) No entity for 0x9035eafffe233190
2023-08-13 22:42:45.472  - error: zigbee.0 (4359) Send command to 0x5c0272fffe8c7426 failed with no error code (no response received (22)
2023-08-13 22:42:45.483  - error: zigbee.0 (4359) Send command to 0xe0798dfffec6c464 failed with no error code (no response received (24)
2023-08-13 22:42:45.497  - error: zigbee.0 (4359) Send command to 0xe0798dfffec6c464 failed with no error code (no response received (23)
2023-08-13 22:42:47.740  - error: zigbee.0 (4359) No entity for 0x9035eafffe233190
2023-08-13 22:42:47.847  - error: zigbee.0 (4359) No entity for 0x9035eafffe233190
2023-08-13 22:42:53.252  - error: zigbee.0 (4359) No entity for 0x9035eafffe233190
2023-08-13 22:42:53.270  - error: zigbee.0 (4359) No entity for 0x9035eafffe233190
2023-08-13 22:42:58.473  - error: zigbee.0 (4359) Send command to 0x5c0272fffe8c7426 failed with no error code (no response received (25)
2023-08-13 22:42:58.481  - error: zigbee.0 (4359) Send command to 0xe0798dfffec6c464 failed with no error code (no response received (27)
2023-08-13 22:42:58.493  - error: zigbee.0 (4359) Send command to 0xe0798dfffec6c464 failed with no error code (no response received (26)
2023-08-13 22:43:03.473  - error: zigbee.0 (4359) Send command to 0x5c0272fffe8c7426 failed with no error code (no response received (29)
2023-08-13 22:43:03.481  - error: zigbee.0 (4359) Send command to 0xe0798dfffec6c464 failed with no error code (no response received (31)
2023-08-13 22:43:03.487  - error: zigbee.0 (4359) Send command to 0xe0798dfffec6c464 failed with no error code (no response received (30)
2023-08-13 22:51:20.295  - error: zigbee.0 (4359) No entity for 0x0c4314fffe20e936
2023-08-13 22:51:24.645  - error: zigbee.0 (4359) No entity for 0x0c4314fffe20e936
2023-08-13 22:51:30.677  - error: zigbee.0 (4359) No entity for 0x0c4314fffe20e936
2023-08-13 22:55:07.913  - error: zigbee.0 (4359) Send command to 0x842e14fffeefe9d2 failed with no error code (no response received (64)
2023-08-13 23:05:06.686  - error: zigbee.0 (5628) DeviceConfigure:Failed to DeviceConfigure.configure 0x2c1165fffe99b52f TS004F (Error: Read 0x2c1165fffe99b52f/1 genBasic([4,0,1,5,7,65534], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received (2))
2023-08-13 23:05:17.173  - warn: zigbee.0 (5628) DeviceAvailability:Failed to ping 0x5c0272fffe8c7426 TS011F
2023-08-13 23:05:18.173  - warn: zigbee.0 (5628) DeviceAvailability:Failed to ping 0x842e14fffe5a22f6 TS011F
2023-08-13 23:05:18.175  - warn: zigbee.0 (5628) DeviceAvailability:Failed to ping 0x540f57fffe3f5d26 TS011F
2023-08-13 23:05:19.173  - warn: zigbee.0 (5628) DeviceAvailability:Failed to ping 0xe0798dfffe886e8e A10
2023-08-13 23:05:19.174  - warn: zigbee.0 (5628) DeviceAvailability:Failed to ping 0xe0798dfffec6c464 A10
2023-08-13 23:05:19.176  - warn: zigbee.0 (5628) DeviceAvailability:Failed to ping 0x842e14fffeefe9d2 TS011F
2023-08-13 23:05:20.173  - warn: zigbee.0 (5628) DeviceAvailability:Failed to ping 0xa4c138cdb62a8b5d TS011F
2023-08-13 23:05:20.175  - warn: zigbee.0 (5628) DeviceAvailability:Failed to ping 0xa4c138912df72585 TS011F
2023-08-13 23:21:53.498  - error: zigbee.0 (5628) Send command to 0x540f57fffe3f5d26 failed with no error code (no response received (54)
2023-08-13 23:21:59.502  - error: zigbee.0 (5628) Send command to 0x540f57fffe3f5d26 failed with no error code (no response received (55)
2023-08-13 23:22:42.431  - error: zigbee.0 (5628) No entity for 0x04cd15fffe9628f3
2023-08-13 23:22:50.012  - error: zigbee.0 (5628) No entity for 0x04cd15fffe9628f3
2023-08-13 23:25:37.784  - error: zigbee.0 (5628) No entity for 0x9035eafffe233190
2023-08-13 23:25:41.933  - error: zigbee.0 (5628) No entity for 0x9035eafffe233190
2023-08-13 23:25:53.916  - error: zigbee.0 (5628) No entity for 0x9035eafffe233190
2023-08-13 23:25:58.526  - error: zigbee.0 (5628) No entity for 0x9035eafffe233190
2023-08-13 23:32:38.688  - warn: zigbee.0 (5628) DeviceAvailability:Failed to ping 0x5c0272fffe8c7426 TS011F
2023-08-13 23:32:40.688  - warn: zigbee.0 (5628) DeviceAvailability:Failed to ping 0xe0798dfffec6c464 A10
christian@iobroker:~$ iob logs zigbee | grep -v info
2023-08-13 22:37:47.097  - warn: zigbee.0 (3305) DeviceAvailability:Failed to ping 0x842e14fffe5a22f6 TS011F
2023-08-13 22:37:48.097  - warn: zigbee.0 (3305) DeviceAvailability:Failed to ping 0x540f57fffe3f5d26 TS011F
2023-08-13 22:37:49.097  - warn: zigbee.0 (3305) DeviceAvailability:Failed to ping 0x842e14fffeefe9d2 TS011F
2023-08-13 22:37:50.098  - warn: zigbee.0 (3305) DeviceAvailability:Failed to ping 0xe0798dfffe886e8e A10
2023-08-13 22:37:50.107  - warn: zigbee.0 (3305) DeviceAvailability:Failed to ping 0xa4c138cdb62a8b5d TS011F
2023-08-13 22:37:50.109  - warn: zigbee.0 (3305) DeviceAvailability:Failed to ping 0xa4c138912df72585 TS011F
2023-08-13 22:40:50.200  - error: zigbee.0 (4359) DeviceConfigure:Failed to DeviceConfigure.configure 0x2c1165fffe99b52f TS004F (Error: Read 0x2c1165fffe99b52f/1 genBasic([4,0,1,5,7,65534], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received (2))
2023-08-13 22:41:03.046  - warn: zigbee.0 (4359) DeviceAvailability:Failed to ping 0x842e14fffeefe9d2 TS011F
2023-08-13 22:41:03.048  - warn: zigbee.0 (4359) DeviceAvailability:Failed to ping 0x5c0272fffe8c7426 TS011F
2023-08-13 22:41:03.050  - warn: zigbee.0 (4359) DeviceAvailability:Failed to ping 0x842e14fffe5a22f6 TS011F
2023-08-13 22:41:03.051  - warn: zigbee.0 (4359) DeviceAvailability:Failed to ping 0x540f57fffe3f5d26 TS011F
2023-08-13 22:41:04.045  - warn: zigbee.0 (4359) DeviceAvailability:Failed to ping 0xe0798dfffe886e8e A10
2023-08-13 22:41:05.045  - warn: zigbee.0 (4359) DeviceAvailability:Failed to ping 0xe0798dfffec6c464 A10
2023-08-13 22:41:05.047  - warn: zigbee.0 (4359) DeviceAvailability:Failed to ping 0xa4c138cdb62a8b5d TS011F
2023-08-13 22:41:05.049  - warn: zigbee.0 (4359) DeviceAvailability:Failed to ping 0xa4c138912df72585 TS011F
2023-08-13 22:41:56.428  - error: zigbee.0 (4359) No entity for 0x9035eafffe233190
2023-08-13 22:41:56.448  - error: zigbee.0 (4359) No entity for 0x9035eafffe233190
2023-08-13 22:42:34.626  - error: zigbee.0 (4359) No entity for 0x9035eafffe233190
2023-08-13 22:42:34.771  - error: zigbee.0 (4359) No entity for 0x9035eafffe233190
2023-08-13 22:42:45.472  - error: zigbee.0 (4359) Send command to 0x5c0272fffe8c7426 failed with no error code (no response received (22)
2023-08-13 22:42:45.483  - error: zigbee.0 (4359) Send command to 0xe0798dfffec6c464 failed with no error code (no response received (24)
2023-08-13 22:42:45.497  - error: zigbee.0 (4359) Send command to 0xe0798dfffec6c464 failed with no error code (no response received (23)
2023-08-13 22:42:47.740  - error: zigbee.0 (4359) No entity for 0x9035eafffe233190
2023-08-13 22:42:47.847  - error: zigbee.0 (4359) No entity for 0x9035eafffe233190
2023-08-13 22:42:53.252  - error: zigbee.0 (4359) No entity for 0x9035eafffe233190
2023-08-13 22:42:53.270  - error: zigbee.0 (4359) No entity for 0x9035eafffe233190
2023-08-13 22:42:58.473  - error: zigbee.0 (4359) Send command to 0x5c0272fffe8c7426 failed with no error code (no response received (25)
2023-08-13 22:42:58.481  - error: zigbee.0 (4359) Send command to 0xe0798dfffec6c464 failed with no error code (no response received (27)
2023-08-13 22:42:58.493  - error: zigbee.0 (4359) Send command to 0xe0798dfffec6c464 failed with no error code (no response received (26)
2023-08-13 22:43:03.473  - error: zigbee.0 (4359) Send command to 0x5c0272fffe8c7426 failed with no error code (no response received (29)
2023-08-13 22:43:03.481  - error: zigbee.0 (4359) Send command to 0xe0798dfffec6c464 failed with no error code (no response received (31)
2023-08-13 22:43:03.487  - error: zigbee.0 (4359) Send command to 0xe0798dfffec6c464 failed with no error code (no response received (30)
2023-08-13 22:51:20.295  - error: zigbee.0 (4359) No entity for 0x0c4314fffe20e936
2023-08-13 22:51:24.645  - error: zigbee.0 (4359) No entity for 0x0c4314fffe20e936
2023-08-13 22:51:30.677  - error: zigbee.0 (4359) No entity for 0x0c4314fffe20e936
2023-08-13 22:55:07.913  - error: zigbee.0 (4359) Send command to 0x842e14fffeefe9d2 failed with no error code (no response received (64)
2023-08-13 23:05:06.686  - error: zigbee.0 (5628) DeviceConfigure:Failed to DeviceConfigure.configure 0x2c1165fffe99b52f TS004F (Error: Read 0x2c1165fffe99b52f/1 genBasic([4,0,1,5,7,65534], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received (2))
2023-08-13 23:05:17.173  - warn: zigbee.0 (5628) DeviceAvailability:Failed to ping 0x5c0272fffe8c7426 TS011F
2023-08-13 23:05:18.173  - warn: zigbee.0 (5628) DeviceAvailability:Failed to ping 0x842e14fffe5a22f6 TS011F
2023-08-13 23:05:18.175  - warn: zigbee.0 (5628) DeviceAvailability:Failed to ping 0x540f57fffe3f5d26 TS011F
2023-08-13 23:05:19.173  - warn: zigbee.0 (5628) DeviceAvailability:Failed to ping 0xe0798dfffe886e8e A10
2023-08-13 23:05:19.174  - warn: zigbee.0 (5628) DeviceAvailability:Failed to ping 0xe0798dfffec6c464 A10
2023-08-13 23:05:19.176  - warn: zigbee.0 (5628) DeviceAvailability:Failed to ping 0x842e14fffeefe9d2 TS011F
2023-08-13 23:05:20.173  - warn: zigbee.0 (5628) DeviceAvailability:Failed to ping 0xa4c138cdb62a8b5d TS011F
2023-08-13 23:05:20.175  - warn: zigbee.0 (5628) DeviceAvailability:Failed to ping 0xa4c138912df72585 TS011F
2023-08-13 23:21:53.498  - error: zigbee.0 (5628) Send command to 0x540f57fffe3f5d26 failed with no error code (no response received (54)
2023-08-13 23:21:59.502  - error: zigbee.0 (5628) Send command to 0x540f57fffe3f5d26 failed with no error code (no response received (55)
2023-08-13 23:22:42.431  - error: zigbee.0 (5628) No entity for 0x04cd15fffe9628f3
2023-08-13 23:22:50.012  - error: zigbee.0 (5628) No entity for 0x04cd15fffe9628f3
2023-08-13 23:25:37.784  - error: zigbee.0 (5628) No entity for 0x9035eafffe233190
2023-08-13 23:25:41.933  - error: zigbee.0 (5628) No entity for 0x9035eafffe233190
2023-08-13 23:25:53.916  - error: zigbee.0 (5628) No entity for 0x9035eafffe233190
2023-08-13 23:25:58.526  - error: zigbee.0 (5628) No entity for 0x9035eafffe233190
2023-08-13 23:32:38.688  - warn: zigbee.0 (5628) DeviceAvailability:Failed to ping 0x5c0272fffe8c7426 TS011F
2023-08-13 23:32:40.688  - warn: zigbee.0 (5628) DeviceAvailability:Failed to ping 0xe0798dfffec6c464 A10
2023-08-13 23:45:27.778  - error: zigbee.0 (5628) No entity for 0x9035eafffe233190
2023-08-13 23:46:52.108  - warn: zigbee.0 (5628) DeviceAvailability:Stopping to ping 0x842e14fffe5a22f6 TS011F after 4 ping attempts
2023-08-13 23:46:52.109  - warn: zigbee.0 (5628) DeviceAvailability:Stopping to ping 0x540f57fffe3f5d26 TS011F after 4 ping attempts
2023-08-13 23:46:53.107  - warn: zigbee.0 (5628) DeviceAvailability:Stopping to ping 0xe0798dfffe886e8e A10 after 4 ping attempts
2023-08-13 23:46:53.108  - warn: zigbee.0 (5628) DeviceAvailability:Stopping to ping 0x842e14fffeefe9d2 TS011F after 4 ping attempts
2023-08-13 23:46:54.107  - warn: zigbee.0 (5628) DeviceAvailability:Stopping to ping 0xa4c138cdb62a8b5d TS011F after 4 ping attempts
2023-08-13 23:46:54.109  - warn: zigbee.0 (5628) DeviceAvailability:Stopping to ping 0xa4c138912df72585 TS011F after 4 ping attempts
2023-08-13 23:50:17.442  - error: zigbee.0 (5628) No entity for 0x9035eafffe233190
2023-08-13 23:50:18.429  - error: zigbee.0 (5628) No entity for 0x9035eafffe233190
2023-08-13 23:50:23.968  - error: zigbee.0 (5628) No entity for 0x9035eafffe233190
2023-08-13 23:50:25.487  - error: zigbee.0 (5628) No entity for 0x9035eafffe233190
2023-08-13 23:50:26.601  - error: zigbee.0 (5628) No entity for 0x9035eafffe233190
2023-08-13 23:50:27.204  - error: zigbee.0 (5628) No entity for 0x9035eafffe233190
2023-08-13 23:50:27.747  - error: zigbee.0 (5628) No entity for 0x9035eafffe233190

Hat jemand einen tipp wie ich die Geräte wieder zum kommunizieren bewege? idealer Weiße ohne all die Geräte neu koppeln zu müssen.
Besten dank euch schon mal.
Gruß Chris

Was ich jetzt grad im Moment noch komisch finde sind meine Temperatur-Sensoren (SNZB-02 - SONOFF Temperature and humidity sensor). Hab ich aktuell 4 funktionierende im Einsatz. Bei bei zwei Sensoren wird die Humidity nicht übertragen/angezeigt (im Objekt-Browser kann man ja auch im Mouseover sehen wann der Wert zuletzt aktualisiert wurde).

Die Batterie-Werte der Sensoren wurde bisher auch noch nicht wieder aktualisiert (bei keinem) - Letztes Update am 06.01.2023 - kurz vor dem Kartenausfall.

Nachtrag: nach rund 30-45 min kommen auch die anderen Humi-Werte. Die Batterie-Werte wurden aber noch nicht auf Stand gebracht. Ich geh mal davon aus, dass das Verhalten normal ist

@arteck

Besten dank, das hat super geklappt. iobroker gestoppt, shepherd.db an die angegebene Position kopiert und wieder gestartet. läuft. Geräte lassen sich wieder schalten. oh wunder ;-).
Ich bin irgendwie davon ausgegangen, da die Adapter alle durch den Master gesteuert/übertragen werden, dass das auch für die Datenbank vom Master übertragen wird.

Aber zum Glück gibts Backups und zum Glück hab ichs auch funktionsfähig eingerichtet ;-).

Allerdings hab ich im Log noch ganz viele "spannende" Meldungen die ich euch nicht vorenthalten möchte:

2023-01-09 19:15:27.318  - info: zigbee.0 (4151) cleaned everything up...
2023-01-09 19:15:27.334  - info: zigbee.0 (4151) Zigbee: disabling joining new devices.
2023-01-09 19:15:27.994  - info: zigbee.0 (4151) Got terminate signal TERMINATE_YOURSELF
2023-01-09 19:15:28.065  - info: zigbee.0 (4151) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-01-09 19:18:08.458  - info: zigbee.0 (5024) starting. Version 1.8.10 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.0, js-controller: 4.0.24
2023-01-09 19:18:08.905  - info: zigbee.0 (5024) delete old Backup files. keep only last 10
2023-01-09 19:18:08.914  - info: zigbee.0 (5024) Starting Zigbee  npm ...
2023-01-09 19:18:11.901  - info: zigbee.0 (5024) Installed Version: iobroker.zigbee@1.8.10
2023-01-09 19:18:12.060  - info: zigbee.0 (5024) Coordinator firmware version: {"type":"ConBee2/RaspBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":114,"maintrel":0,"revision":"0x26720700"}}
2023-01-09 19:18:12.182  - info: zigbee.0 (5024) Unable to disable LED, unsupported function.
2023-01-09 19:18:12.265  - info: zigbee.0 (5024)   --> transmitPower : normal
2023-01-09 19:18:12.884  - info: zigbee.0 (5024) Unable to set transmit power, unsupported function.
2023-01-09 19:18:12.946  - info: zigbee.0 (5024) Currently 37 devices are joined:
2023-01-09 19:18:13.469  - info: zigbee.0 (5024) Configuring 0x2c1165fffe99b52f TS004F
2023-01-09 19:18:13.483  - info: zigbee.0 (5024) 0x2c1165fffe99b52f (addr 2710): HG08164 - Lidl Silvercrest smart button (EndDevice)
2023-01-09 19:18:13.529  - info: zigbee.0 (5024) 0x5c0272fffe8c7426 (addr 58801): HG06337 - Lidl Silvercrest smart plug (EU, CH, FR, BS, DK) (Router)
.
. (gekürzt)
.
2023-01-09 19:18:13.829  - info: zigbee.0 (5024) Zigbee started
2023-01-09 19:18:14.278  - warn: zigbee.0 (5024) download icon from https://www.zigbee2mqtt.io/images/devices/HG08164.jpg saved into /opt/iobroker/node_modules/iobroker.zigbee/admin/img/HG08164.png
.
. (gekürzt)
.
2023-01-09 19:18:19.438  - warn: zigbee.0 (5024) Object 5c0272fffe8c7426.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.440  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.443  - warn: zigbee.0 (5024) Object 842e14fffe5a22f6.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.445  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.452  - warn: zigbee.0 (5024) Object 00124b0026b6f49d.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.454  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.460  - warn: zigbee.0 (5024) Object 842e14fffeefe9d2.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.463  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.466  - warn: zigbee.0 (5024) Object e0798dfffe886e8e.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.468  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.472  - warn: zigbee.0 (5024) Object e0798dfffec6c464.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.474  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.480  - warn: zigbee.0 (5024) Object 04cd15fffe9628f3.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.482  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.486  - warn: zigbee.0 (5024) Object b4e3f9fffec516f6.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.488  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.491  - warn: zigbee.0 (5024) Object b4e3f9fffecb1d1b.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.493  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.590  - warn: zigbee.0 (5024) Object zigbee.0.5c0272fffe8c7426.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.592  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.648  - warn: zigbee.0 (5024) Object zigbee.0.842e14fffe5a22f6.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.655  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.658  - warn: zigbee.0 (5024) Object zigbee.0.00124b0026b6f49d.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.659  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.661  - warn: zigbee.0 (5024) Object zigbee.0.842e14fffeefe9d2.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.662  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.663  - warn: zigbee.0 (5024) Object zigbee.0.e0798dfffe886e8e.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.665  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:19.667  - warn: zigbee.0 (5024) Object zigbee.0.e0798dfffec6c464.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-01-09 19:18:19.668  - warn: zigbee.0 (5024) This object will not be created in future versions. Please report this to the developer.
2023-01-09 19:18:54.242  - info: zigbee.0 (5024) List of port: [{"path":"/dev/ttyS1"},{"path":"/dev/ttyS2"},{"path":"/dev/ttyS3"},{"path":"/dev/ttyS4"},{"path":"/dev/ttyS5"},{"path":"/dev/ttyS6"},{"path":"/dev/ttyS7"},{"path":"/dev/ttyACM0","manufacturer":"dresden elektronik ingenieurtechnik GmbH","serialNumber":"DE2661519","pnpId":"usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2661519-if00","vendorId":"1cf1","productId":"0030"},{"path":"/dev/ttyS0"}]
2023-01-09 19:19:14.163  - error: zigbee.0 (5024) DeviceConfigure:Failed to DeviceConfigure.configure 0x2c1165fffe99b52f TS004F (Error: Bind 0x2c1165fffe99b52f/1 genPowerCfg from '0x00212effff095f03/1' failed (waiting for response TIMEOUT)
2023-01-09 19:20:00.235  - error: zigbee.0 (5024) Send command to 0xe0798dfffec6c464 failed with no error code (no response received)
2023-01-09 19:20:01.238  - error: zigbee.0 (5024) Send command to 0xe0798dfffec6c464 failed with no error code (no response received)
2023-01-09 19:20:03.575  - error: zigbee.0 (5024) Send command to 0xe0798dfffec6c464 failed with no error code (no response received)
2023-01-09 19:20:04.898  - error: zigbee.0 (5024) Send command to 0xe0798dfffec6c464 failed with no error code (no response received)
2023-01-09 19:20:07.252  - error: zigbee.0 (5024) Send command to 0xe0798dfffec6c464 failed with no error code (no response received)
2023-01-09 19:20:08.753  - error: zigbee.0 (5024) Send command to 0xe0798dfffec6c464 failed with no error code (no response received)
2023-01-09 19:20:18.256  - warn: zigbee.0 (5024) DeviceAvailability:Failed to ping 0x540f57fffe3f5d26 TS011F
2023-01-09 19:20:20.256  - warn: zigbee.0 (5024) DeviceAvailability:Failed to ping 0xe0798dfffe886e8e A10
2023-01-09 19:20:20.259  - warn: zigbee.0 (5024) DeviceAvailability:Failed to ping 0xe0798dfffec6c464 A10
2023-01-09 19:20:20.262  - warn: zigbee.0 (5024) DeviceAvailability:Failed to ping 0xa4c138cdb62a8b5d TS011F
2023-01-09 19:20:20.264  - warn: zigbee.0 (5024) DeviceAvailability:Failed to ping 0xa4c138912df72585 TS011F
2023-01-09 19:20:30.896  - error: zigbee.0 (5024) Send command to 0x847127fffe75db97 failed with no error code (undefined)
2023-01-09 19:20:30.978  - error: zigbee.0 (5024) Send command to 0x847127fffe75db97 failed with no error code (undefined)
2023-01-09 19:20:31.378  - error: zigbee.0 (5024) Send command to 0x847127fffe75db97 failed with no error code (undefined)
2023-01-09 19:20:31.450  - error: zigbee.0 (5024) Send command to 0x847127fffe75db97 failed with no error code (undefined)
2023-01-09 19:21:31.585  - error: zigbee.0 (5024) Send command to 0xe0798dfffec6c464 failed with no error code (no response received)

Spannend fand ich die Meldung This object will not be created in future versions. Please report this to the developer.

Vielen Dank nochmal für eure Unterstützung

@asgothian sagte in Probleme mit Zigbee auf Slave:

@derroch hast du die Datei shepherd.db im Verzeichnis /opt/iobroker/iobroker-data/zigbee_0 auf dem Slave von der defekten Karte auf die neue übertragen ?

Guten Morgen,

Ne, ist bisher nicht passiert. sollte ich das mal tun? Ist auf Grund der defekten Karte evtl schwierig.
Ach, ich hab ein Backup mit backitup eingerichtet und hier scheint in der Backup-Datei die besagte shepherd.db vorhanden zu sein.

@asgothian sagte in Probleme mit Zigbee auf Slave:

@derroch Zeig mal bitte was als adapter auf dem Master angezeigt wird.

meinst du das hier?

user@iobroker:/opt/iobroker$ npm ls
iobroker.inst@3.0.0 /opt/iobroker
├── iobroker.admin@6.3.5
├── iobroker.alexa2@3.23.2
├── iobroker.backitup@2.5.9
├── iobroker.daswetter@3.1.4
├── iobroker.discovery@3.1.0
├── iobroker.dwd@2.8.3
├── iobroker.firetv@1.0.0
├── iobroker.heatingcontrol@2.9.3
├── iobroker.ical@1.13.2
├── iobroker.influxdb@3.2.0
├── iobroker.info@1.9.19
├── iobroker.iot@1.11.9
├── iobroker.jarvis@3.1.2
├── iobroker.javascript@6.1.4
├── iobroker.js-controller@4.0.24
├── iobroker.net-tools@0.2.0
├── iobroker.opi@0.1.1
├── iobroker.rpi2@1.3.2
├── iobroker.smartcontrol@1.2.1
├── iobroker.trashschedule@2.0.3
├── iobroker.vis-icontwo@0.90.0
├── iobroker.vis-timeandweather@1.2.2
├── iobroker.vis@1.4.15
├── iobroker.web@4.3.0
├── iobroker.whatsapp-cmb@0.2.3
└── iobroker.zigbee@1.8.10

Auch: wie genau hast du das Update der Zigbee-Instanz durchgeführt ?

Ich wollte das Update eigentlich übers Admin-Interface durchführen. Das hab ich 2 mal versucht. Jedesmal war es immer noch Version 1.7.5... dann hab ichs über die CLI auf dem Slave durchgeführt mit "iobroker update/upgrade".

Gruß Christian