# Conbee2 | Firmware: not connected 2.14.01, buster **URL:** \ **Category:** Setup Support\ **Created:** [March 14, 2022, 9:44pm UTC](https://forum.phoscon.de/t/conbee2-firmware-not-connected-2-14-01-buster/1734 "2022-03-14T21:44:52Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![nixoso](https://forum.phoscon.de/user_avatar/forum.phoscon.de/nixoso/32/1584_2.png) [@nixoso](https://forum.phoscon.de/u/nixoso)\ **Post date:** [March 14, 2022, 9:44pm UTC](https://forum.phoscon.de/t/conbee2-firmware-not-connected-2-14-01-buster/1734/1 "2022-03-14T21:44:52Z")
I rebooted the Rasp 4 today and since then the Conbee2 can no longer be found in the Phoscon app. ![2022-03-14 22_36_48-Phoscon App](https://forum.phoscon.de/uploads/default/original/2X/6/64cac663b20e58b9113f539b2d2c5fec12e451bc.png) I have already changed the USB ports but that makes no difference. The stick also seems to be detected: ```auto openhabian@openhab:~ $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1cf1:0030 Dresden Elektronik Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ``` I just plugged the stick into Windows 10 and it runs there. Under Windows I have then also successfully flashed directly to version deCONZ\_ConBeeII\_0x26720700.bin.GCF. But still no stick is detected under Linux and I can’t see any problem in the logs either: ```auto -- Reboot -- Mar 14 22:21:48 openhab systemd[1]: Started deCONZ: ZigBee gateway -- REST API. -- Subject: A start job for unit deconz.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit deconz.service has finished successfully. -- -- The job identifier is 109. Mar 14 22:21:49 openhab deCONZ[358]: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-openhabian' Mar 14 22:21:50 openhab deCONZ[358]: libpng warning: iCCP: known incorrect sRGB profile Mar 14 22:21:50 openhab deCONZ[358]: libpng warning: iCCP: known incorrect sRGB profile Mar 14 22:21:51 openhab deCONZ[358]: This plugin does not support propagateSizeHints() Mar 14 22:21:51 openhab deCONZ[358]: This plugin does not support propagateSizeHints() ``` What else can I do? ---
**Author:** ![Mimiix](https://forum.phoscon.de/user_avatar/forum.phoscon.de/mimiix/32/10_2.png) [@Mimiix](https://forum.phoscon.de/u/Mimiix)\ **Post date:** [March 14, 2022, 9:55pm UTC](https://forum.phoscon.de/t/conbee2-firmware-not-connected-2-14-01-buster/1734/2 "2022-03-14T21:55:02Z")
Can you share some logs? In #deconz you can find out how. ---
**Author:** ![nixoso](https://forum.phoscon.de/user_avatar/forum.phoscon.de/nixoso/32/1584_2.png) [@nixoso](https://forum.phoscon.de/u/nixoso)\ **Post date:** [March 14, 2022, 10:08pm UTC](https://forum.phoscon.de/t/conbee2-firmware-not-connected-2-14-01-buster/1734/3 "2022-03-14T22:08:58Z")
Logs under: [debian Pastezone](https://paste.debian.net/1234197) ---
**Author:** ![Mimiix](https://forum.phoscon.de/user_avatar/forum.phoscon.de/mimiix/32/10_2.png) [@Mimiix](https://forum.phoscon.de/u/Mimiix)\ **Post date:** [March 15, 2022, 9:24am UTC](https://forum.phoscon.de/t/conbee2-firmware-not-connected-2-14-01-buster/1734/4 "2022-03-15T09:24:33Z")
22:56:20:866 device disconnected reason: 1, device index: 0 That indicates that the stick is either removed from the PI or that it reboots. We often see this when theres not enough power. What Power supply do you use? ---
**Author:** ![nixoso](https://forum.phoscon.de/user_avatar/forum.phoscon.de/nixoso/32/1584_2.png) [@nixoso](https://forum.phoscon.de/u/nixoso)\ **Post date:** [March 15, 2022, 8:05pm UTC](https://forum.phoscon.de/t/conbee2-firmware-not-connected-2-14-01-buster/1734/5 "2022-03-15T20:05:36Z")
I have been using the following power supply for a year: [Miuzei 5 V 3A USB-C](https://www.amazon.de/Miuzei-Geh%C3%A4use-L%C3%BCfterk%C3%BChlung-Aluminiumk%C3%BChlk%C3%B6rper-USB-C-Netzteil-AUS-Schalter/dp/B08L5ZVJXS/ref=pd_sbs_3/262-7071396-3306207?pd_rd_w=pWi82&pf_rd_p=82d99ec5-b8da-4272-89b1-cfb4cde1f172&pf_rd_r=FB660NAMF8X0GD9PHQXQ&pd_rd_r=1350f969-8372-454d-b10d-f06b130c8b79&pd_rd_wg=1zR3Y&pd_rd_i=B08L5ZVJXS&psc=1) ---
**Author:** ![ich](https://forum.phoscon.de/user_avatar/forum.phoscon.de/ich/32/19_2.png) [@ich](https://forum.phoscon.de/u/ich)\ **Post date:** [March 16, 2022, 10:44am UTC](https://forum.phoscon.de/t/conbee2-firmware-not-connected-2-14-01-buster/1734/7 "2022-03-16T10:44:36Z")
When using a Raspberry Pi, the [original power supply](https://www.raspberrypi.com/products/type-c-power-supply/?variant=raspberry-pi-psu-eu-b) is required to guarantee a stable gateway. Only this power supply delivers 5.1V and 2.5A (Raspberry Pi 3B+) respectively 3A (Raspberry Pi 4B). And it definitely has good quality. [https://www.raspberrypi.org/documentation/computers/raspberry-pi.html#power-supply](https://www.raspberrypi.org/documentation/computers/raspberry-pi.html#power-supply) ---
**Author:** ![nixoso](https://forum.phoscon.de/user_avatar/forum.phoscon.de/nixoso/32/1584_2.png) [@nixoso](https://forum.phoscon.de/u/nixoso)\ **Post date:** [March 16, 2022, 7:20pm UTC](https://forum.phoscon.de/t/conbee2-firmware-not-connected-2-14-01-buster/1734/8 "2022-03-16T19:20:52Z")
I just ordered the official power supply and will give feedback if this solves the problem. ---
**Author:** ![nixoso](https://forum.phoscon.de/user_avatar/forum.phoscon.de/nixoso/32/1584_2.png) [@nixoso](https://forum.phoscon.de/u/nixoso)\ **Post date:** [March 17, 2022, 7:27pm UTC](https://forum.phoscon.de/t/conbee2-firmware-not-connected-2-14-01-buster/1734/9 "2022-03-17T19:27:14Z")
Unfortunately, the orginal power supply did not bring success ☹ . The stick is found on the Raspberry: ```auto openhabian@openhab:~ $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1cf1:0030 Dresden Elektronik Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ``` ```auto openhabian@openhab:~ $ dmesg [313.787442] usb 1-1.3: new full-speed USB device number 3 using xhci_hcd [313.926485] usb 1-1.3: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00 [313.926508] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [313.926526] usb 1-1.3: Product: ConBee II [313.926543] usb 1-1.3: Manufacturer: dresden elektronik ingenieurtechnik GmbH [313.926560] usb 1-1.3: SerialNumber: DE2470694 [317.530053] usb 1-1.3: USB disconnect, device number 3 [317.827502] usb 1-1.3: new full-speed USB device number 4 using xhci_hcd [317.966580] usb 1-1.3: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00 [317.966602] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [317.966621] usb 1-1.3: Product: ConBee II [317.966638] usb 1-1.3: Manufacturer: dresden elektronik ingenieurtechnik GmbH [317.966655] usb 1-1.3: SerialNumber: DE2470694 ``` ---
**Author:** ![ich](https://forum.phoscon.de/user_avatar/forum.phoscon.de/ich/32/19_2.png) [@ich](https://forum.phoscon.de/u/ich)\ **Post date:** [March 18, 2022, 6:57am UTC](https://forum.phoscon.de/t/conbee2-firmware-not-connected-2-14-01-buster/1734/10 "2022-03-18T06:57:16Z")
I would do a manually [firmware rewrite](https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Update-deCONZ-manually) with a Raspberry Pi and a separate SD card. Just write our [Image with Desktop](https://www.phoscon.de/en/conbee2/sdcard) to the SD card for a temporary test system. With this system it can be checked whether in the Phoscon App under Menu \> Gateway \> General \> Firmware a version in the format 26xx0700 is available - and not “Firmware not connected”. If yes, a device can also be tried to be connected and controlled as a test. ---
**Author:** ![nixoso](https://forum.phoscon.de/user_avatar/forum.phoscon.de/nixoso/32/1584_2.png) [@nixoso](https://forum.phoscon.de/u/nixoso)\ **Post date:** [March 19, 2022, 1:27pm UTC](https://forum.phoscon.de/t/conbee2-firmware-not-connected-2-14-01-buster/1734/11 "2022-03-19T13:27:00Z")
After a reinstallation of the raspberry pi (what was due anyway 😉 ) - access to the stick was possible again 🥳 .