Homeassistant doesn't detect conbee II

Hi,
I have problems to integrate my Conbee II in the Homeassistant. The following scenario: I have two HASSIO in the network, at the master is already a Conbee integrated and runs great.
The second HASSIO is newly set up and will be linked to the master as a slave at another location via VPN.
At this slave Homeassistant I now want to integrate a Conbee as well. Add-On installed, Conbee connected, in the interface the Conbee is accessible, firmware is up to date. But if I want to integrate the DeCONZ interation in the Homeassistant, I don’t get an API key. The IP of the Conbee is also not suggested to me. Only the Conbee from the first Homeassistant is recognized here. Also phoscon discover finds only the first Conbee.

Strange is the recurring entry in the logs:
15:41:25:409 invalid mac address 0x040D84FFFE2B92B5

what is this all about?

I hope someone here can give me a good tip. Thanks a lot!

Did you load a backup on the slave conbee from the master ?

no, it is a new conbee integration. no backup, nothing.
but the conbee is second hand and was used in another system before. could this be a problem?

I recommend resetting it. That’s where the message is from

but how can I reset the conbee? I already tried via the phoscon frontend, but doesn’t help

Can you share some Logs?

In #deconz you can find out how and what log levels.

Does this help?

[17:37:08] INFO: GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
Path             | Vendor | Product | Serial     | Type
-----------------+--------+---------+------------+-------
/dev/ttyACM0     | 0x1CF1 | 0x0030  | DE2407422  | ConBee II 
/dev/ttyAMA0     | 0x0000 | 0x0000  |            | RaspBee 
cont-init: info: /etc/cont-init.d/firmware.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
cont-init: info: running /etc/cont-init.d/novnc.sh
cont-init: info: /etc/cont-init.d/novnc.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun deconz (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
services-up: info: copying legacy longrun otau-deconz (no readiness notification)
services-up: info: copying legacy longrun otau-ikea (no readiness notification)
services-up: info: copying legacy longrun otau-ledvance (no readiness notification)
services-up: info: copying legacy longrun websockify (no readiness notification)
s6-rc: info: service legacy-services successfully started
[17:37:09] INFO: Running the IKEA OTA updater...
[17:37:09] INFO: Running the OSRAM LEdvance OTA updater...
[17:37:09] INFO: Running the deCONZ OTA updater...
[17:37:09] INFO: Websockify waiting for VNC to start
[17:37:09] INFO: Starting VNC server (local/yes)...
[17:37:09] INFO: Starting websockify...
WebSocket server settings:
  - Listen on 127.0.0.1:5901
  - Flash security policy server
  - Web server. Web root: /usr/share/novnc
  - No SSL/TLS support (no cert file)
  - proxying from 127.0.0.1:5901 to 127.0.0.1:5900
[17:37:12] INFO: deCONZ waiting for VNC to start
[17:37:13] INFO: Starting the deCONZ gateway...
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
[17:37:14] INFO: Starting Nginx...
2023/02/23 17:37:14 [notice] 121#121: using the "epoll" event method
2023/02/23 17:37:14 [notice] 121#121: nginx/1.14.2
2023/02/23 17:37:14 [notice] 121#121: OS: Linux 5.15.84-v8
2023/02/23 17:37:14 [notice] 121#121: getrlimit(RLIMIT_NOFILE): 1048576:1048576
2023/02/23 17:37:14 [notice] 121#121: start worker processes
2023/02/23 17:37:14 [notice] 121#121: start worker process 1178
17:37:14:371 HTTP Server listen on address 0.0.0.0, port: 40850, root: /usr/share/deCONZ/webapp/
17:37:14:388 /data/.local/share/dresden-elektronik/deCONZ/config.ini exists and is writeable
17:37:14:388 /data/.local/share/dresden-elektronik/deCONZ/zll.db exists and is writeable
17:37:14:448 COM: use stable device path /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2407422-if00
17:37:14:495 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2407422-if00 / serialno: DE2407422, ConBee II
17:37:14:497 ZCLDB init file /data/.local/share/dresden-elektronik/deCONZ/zcldb.txt
17:37:14:621 DDF enabled for Gold status
17:37:15:199 parent process s6-supervise
17:37:15:199 gw run mode: normal
17:37:15:199 GW sd-card image version file does not exist: /data/.local/share/dresden-elektronik/deCONZ/gw-version
17:37:15:200 sd-card cid: 035344534433324785ffffffff016600
17:37:15:201 DB sqlite version 3.27.2
17:37:15:201 DB PRAGMA page_count: 46
17:37:15:202 DB PRAGMA page_size: 4096
17:37:15:202 DB PRAGMA freelist_count: 0
17:37:15:202 DB file size 188416 bytes, free pages 0
17:37:15:202 DB PRAGMA user_version: 9
17:37:15:202 DB cleanup
17:37:15:202 DB create temporary views
17:37:15:207 [INFO] - Timezone read is 'Etc/UTC'
17:37:15:207 [INFO] - Environment variable TZ found: Europe/Berlin...
17:37:15:208 Started websocket server on 0.0.0.0, port: 8081
17:37:15:211 [INFO] - Found file containing button maps. Parsing data...
17:37:15:221 [INFO] - Button maps loaded.
17:37:15:222 found node plugin: libde_rest_plugin.so - REST API Plugin
17:37:15:223 found node plugin: libde_signal_plugin.so - Signal Monitor Plugin
17:37:18:786 OTAU: create 1189-0082-020E6550.zigbee
17:37:18:808 OTAU: create 1189-0082-020E6550.zigbee
17:37:18:830 OTAU: create 1189-0083-020E6550.zigbee
17:37:18:852 OTAU: create 1189-0083-020E6550.zigbee
17:37:19:780 OTAU: create 1189-00B9-02226550.zigbee
17:37:19:804 OTAU: create 1189-00B9-02226550.zigbee
17:37:19:826 OTAU: create 1189-00BA-02226550.zigbee
17:37:19:850 OTAU: create 1189-00BA-02226550.zigbee
17:37:20:159 found node plugin: libstd_otau_plugin.so - STD OTAU Plugin
parse error: Invalid numeric literal at line 1, column 34
17:37:20:429 dlg action: Read binding table
17:37:20:494 New websocket 127.0.0.1:39288 (state: 3) 
17:37:20:774 Announced to internet https://phoscon.de/discover
17:37:20:775 discovery server date: Thu, 23 Feb 2023 16:37:20 GMT
17:37:20:775 	 local time seems to be ok
17:37:21:250 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2407422-if00 / serialno: DE2407422, ConBee II
17:37:22:912 Device firmware version 0x26780700 ConBee II
17:37:22:942 unlocked max nodes: 512
17:37:22:943 Device protocol version: 0x010E
17:37:23:184 Current channel 11
17:37:23:245 CTRL got nwk update id 1
17:37:23:267 CTRL ANT_CTRL 0x03
17:37:23:289 CTRL ZDP_RESPONSE handler 0x0001
17:37:23:408 DEV Tick.Init: booted after 8000 seconds
17:37:23:490 ZDP get active endpoints for 0x0000
17:37:23:646 DEV no DDF for 0x040D84FFFE2B92B5, modelId: ConBee II
17:37:23:647 DEV create on-the-fly DDF for 0x040D84FFFE2B92B5
17:37:25:409 invalid mac address 0x040D84FFFE2B92B5
17:37:30:409 GW update firmware found: /usr/share/deCONZ/firmware/deCONZ_ConBeeII_0x26720700.bin.GCF
17:37:30:409 GW firmware version is up to date: 0x26780700
17:37:35:408 invalid mac address 0x040D84FFFE2B92B5
17:37:45:408 invalid mac address 0x040D84FFFE2B92B5

this mac adress seems to be the virtual default sensor in deconz:

{
    "1": {
        "config": {
            "configured": true,
            "on": true,
            "sunriseoffset": 30,
            "sunsetoffset": -30
        },
        "etag": "1d3034291e8c637446d7adc53bb14b47",
        "manufacturername": "Philips",
        "modelid": "PHDL00",
        "name": "Daylight",
        "state": {
            "dark": false,
            "daylight": false,
            "lastupdated": "2023-02-23T16:37:15.208",
            "status": 200,
            "sunrise": "2023-02-23T06:08:59",
            "sunset": "2023-02-23T16:34:37"
        },
        "swversion": "1.0",
        "type": "Daylight",
        "uniqueid": "04:0d:84:ff:fe:2b:92:b5-01"
    }
}

how can I delete this one?

Please use the correct log levels als requested and pastebin.

because of an appointment I cannot go on to get the logs right now. hope to finish this tomorrow.
thanks a lot for the great support so far.
if there is any chance to hard reset the conbee, a hint would be great.
thanks a lot

I made it. hope that’s fine:
https://paste.debian.net/1271864

17:50:30:285 dlg action: Read binding table
17:50:30:598 Announced to internet https://phoscon.de/discover
17:50:30:599 discovery server date: Thu, 23 Feb 2023 16:50:30 GMT
17:50:30:600 	 local time seems to be ok
17:50:31:116 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2407422-if00 / serialno: DE2407422, ConBee II
17:50:32:622 Device firmware version 0x26780700 ConBee II
17:50:32:648 unlocked max nodes: 512
17:50:32:649 Device protocol version: 0x010E
17:50:32:892 Current channel 11
17:50:32:953 CTRL got nwk update id 1
17:50:32:975 CTRL ANT_CTRL 0x03
17:50:32:997 CTRL ZDP_RESPONSE handler 0x0001
17:50:33:196 ZDP get active endpoints for 0x0000
17:50:33:348 DEV no DDF for 0x040D84FFFE2B92B5, modelId: ConBee II
17:50:33:348 DEV create on-the-fly DDF for 0x040D84FFFE2B92B5
17:50:33:408 DEV Tick.Init: booted after 8000 seconds
17:50:35:408 invalid mac address 0x040D84FFFE2B92B5
17:50:40:409 GW update firmware found: /usr/share/deCONZ/firmware/deCONZ_ConBeeII_0x26720700.bin.GCF
17:50:40:410 GW firmware version is up to date: 0x26780700
17:50:45:408 invalid mac address 0x040D84FFFE2B92B5
17:50:55:408 invalid mac address 0x040D84FFFE2B92B5
17:51:05:408 invalid mac address 0x040D84FFFE2B92B5
17:51:15:409 invalid mac address 0x040D84FFFE2B92B5
17:51:25:408 invalid mac address 0x040D84FFFE2B92B5
17:51:35:408 invalid mac address 0x040D84FFFE2B92B5
17:51:45:410 invalid mac address 0x040D84FFFE2B92B5
17:51:55:408 invalid mac address 0x040D84FFFE2B92B5
17:52:05:410 invalid mac address 0x040D84FFFE2B92B5
17:52:15:409 invalid mac address 0x040D84FFFE2B92B5
17:52:25:408 invalid mac address 0x040D84FFFE2B92B5
17:52:35:409 invalid mac address 0x040D84FFFE2B92B5
17:52:45:408 invalid mac address 0x040D84FFFE2B92B5
17:52:55:409 invalid mac address 0x040D84FFFE2B92B5
17:53:05:409 invalid mac address 0x040D84FFFE2B92B5
17:53:15:408 invalid mac address 0x040D84FFFE2B92B5
17:53:25:408 invalid mac address 0x040D84FFFE2B92B5
17:53:35:408 invalid mac address 0x040D84FFFE2B92B5
17:53:45:408 invalid mac address 0x040D84FFFE2B92B5
17:53:50:408 Idle timer triggered
17:53:55:408 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:53:55:409 invalid mac address 0x040D84FFFE2B92B5
17:53:59:300 APS-DATA.request id: 21, addrmode: 0x03, addr: 0x040d84fffe2b92b5, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:53:59:348 APS-DATA.confirm id: 21, status: 0x00 SUCCESS
17:53:59:349 APS-DATA.confirm request id: 21 -> confirmed, timeout 9673894
17:53:59:350 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 69, rssi: 27
17:53:59:351 APS-DATA.indication request id: 21 -> finished
17:53:59:351 APS-DATA.request id: 21 erase from queue
17:54:01:700 APS-DATA.request id: 33, addrmode: 0x03, addr: 0x040d84fffe2b92b5, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:54:01:702 	asdu (length: 2): bc00
17:54:01:735 APS-DATA.confirm id: 33, status: 0x00 SUCCESS
17:54:01:736 APS-DATA.confirm request id: 33 -> confirmed, timeout 9676295
17:54:01:738 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 69, rssi: 27
17:54:01:738 	asdu: bc00000000
17:54:01:739 APS-DATA.indication request id: 33 -> finished
17:54:01:739 APS-DATA.request id: 33 erase from queue
17:54:04:101 APS-DATA.request id: 45, addrmode: 0x03, addr: 0x040d84fffe2b92b5, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:54:04:102 	asdu (length: 2): c700
17:54:04:119 APS-DATA.confirm id: 45, status: 0x00 SUCCESS
17:54:04:119 APS-DATA.confirm request id: 45 -> confirmed, timeout 9678695
17:54:04:128 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 69, rssi: 27
17:54:04:129 	asdu: c700000000
17:54:04:129 APS-DATA.indication request id: 45 -> finished
17:54:04:129 APS-DATA.request id: 45 erase from queue
17:54:05:408 Daylight now: sunsetEnd, status: 200, daylight: 0, dark: 1
17:54:05:409 invalid mac address 0x040D84FFFE2B92B5
17:54:06:500 APS-DATA.request id: 57, addrmode: 0x03, addr: 0x040d84fffe2b92b5, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:54:06:501 	asdu (length: 2): d200
17:54:06:531 APS-DATA.confirm id: 57, status: 0x00 SUCCESS
17:54:06:532 APS-DATA.confirm request id: 57 -> confirmed, timeout 9681094
17:54:06:536 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 69, rssi: 27
17:54:06:537 	asdu: d200000000
17:54:06:537 APS-DATA.indication request id: 57 -> finished
17:54:06:538 APS-DATA.request id: 57 erase from queue
17:54:08:901 APS-DATA.request id: 69, addrmode: 0x03, addr: 0x040d84fffe2b92b5, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:54:08:902 	asdu (length: 2): dd00
17:54:08:932 APS-DATA.confirm id: 69, status: 0x00 SUCCESS
17:54:08:933 APS-DATA.confirm request id: 69 -> confirmed, timeout 9683495
17:54:08:937 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 69, rssi: 27
17:54:08:938 	asdu: dd00000000
17:54:08:939 APS-DATA.indication request id: 69 -> finished
17:54:08:939 APS-DATA.request id: 69 erase from queue
17:54:11:300 APS-DATA.request id: 81, addrmode: 0x03, addr: 0x040d84fffe2b92b5, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
17:54:11:301 	asdu (length: 2): e800
17:54:11:328 APS-DATA.confirm id: 81, status: 0x00 SUCCESS
17:54:11:328 APS-DATA.confirm request id: 81 -> confirmed, timeout 9685894
17:54:11:333 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 69, rssi: 27
17:54:11:334 	asdu: e800000000
17:54:11:334 APS-DATA.indication request id: 81 -> finished
17:54:11:335 APS-DATA.request id: 81 erase from queue