Failing to flash Raspbee 2

Hi @ChrisHae sorry for taking a few days to get back here I’ve been away…

There are no other devices connected (other than ethernet)
Here’s the output of those commands - yes I have stopped deconz / deconz-gui

● deconz.service - deCONZ: ZigBee gateway -- REST API
   Loaded: loaded (/lib/systemd/system/deconz.service; disabled; vendor preset: enabled)
   Active: inactive (dead)
pi@raspberrypi:~ $ systemctl status deconz-gui
● deconz-gui.service - deCONZ: ZigBee gateway -- GUI/REST API
   Loaded: loaded (/lib/systemd/system/deconz-gui.service; disabled; vendor preset: enabled)
   Active: inactive (dead)

Sep 08 12:10:51 raspberrypi systemd[1]: /lib/systemd/system/deconz-gui.service:10: Unknown lvalue 'StartLimitInte
Sep 08 12:10:51 raspberrypi systemd[1]: /lib/systemd/system/deconz-gui.service:10: Unknown lvalue 'StartLimitInte
Sep 08 12:10:51 raspberrypi systemd[1]: /lib/systemd/system/deconz-gui.service:10: Unknown lvalue 'StartLimitInte
Sep 08 12:10:51 raspberrypi systemd[1]: /lib/systemd/system/deconz-gui.service:10: Unknown lvalue 'StartLimitInte
Sep 08 12:11:17 raspberrypi systemd[1]: /lib/systemd/system/deconz-gui.service:10: Unknown lvalue 'StartLimitInte
pi@raspberrypi:~ $
pi@raspberrypi:~ $
pi@raspberrypi:/tmp $ sudo GCFFlasher_internal -l
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
Path             | Vendor | Product | Serial     | Type
-----------------+--------+---------+------------+-------
/dev/ttyAMA0     | 0x0000 | 0x0000  |            | RaspBee

I am using the following charger:

The contents of my config.txt and cmdLine.txt are as follows (Serial settings)

console=tty1 root=PARTUUID=38aa4fc7-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable infrared communication.
#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
#dtoverlay=vc4-fkms-v3d
enable_uart=1
dtoverlay=pi3-miniuart-bt

That looks all ok. Does the RaspBee2 work with the current firmware?

I’ve never been able to detect it through HA (I figured updating firmware may help with that) but perhaps it’s a dud?

Can you please post the output of sudo GCFFlasher_internal -r

And could you try to use GCFFlasher v4 https://github.com/dresden-elektronik/gcfflasher
(you need to build the sourcecode from the github page)

alternatively could you try to flash an older fw version on GCFFlasher v3.17 e.g. deCONZ_RaspBeeII_0x26680700

Running sudo GCFFlasher_internal -r outputs:

pi@raspberrypi:~ $ sudo GCFFlasher_internal -r
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
Reboot device RaspBee (RaspBee)
action: reset device RaspBee
wiringPi 2.52 initialized

Using -x 3

pi@raspberrypi:~ $ sudo GCFFlasher_internal -r -x 3
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
11:59:10:349 ls dev: /dev/ttyAMA0 (0x0000/0x0000) sn:
11:59:10:350 check symlink /dev/ttyAMA0 (/dev/ttyAMA0)
11:59:10:350 dev /dev/ttyAMA0 (/dev/ttyAMA0)
Reboot device RaspBee (RaspBee)
11:59:10:351 query bootloader v1 ID after 0 ms
11:59:11:853 query bootloader v1 ID after 1501 ms
11:59:12:353 query deCONZ firmware version
11:59:14:356 uart reset failed, try RaspBee reset
action: reset device RaspBee
wiringPi 2.52 initialized
11:59:14:560 query bootloader v1 ID after 0 ms
11:59:16:062 query bootloader v3 ID after 1502 ms
11:59:16:062 TX c081027dffc0

Flashing older firmware on 3_17 has the same results as above

pi@raspberrypi:/tmp $ sudo GCFFlasher_internal -t 60 -f /tmp/deCONZ_RaspBeeII_0x26680700.bin.GCF -x 3
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
12:00:54:013 using firmware file: /tmp/deCONZ_RaspBeeII_0x26680700.bin.GCF
12:00:54:086 ls dev: /dev/ttyAMA0 (0x0000/0x0000) sn:
12:00:54:086 check symlink /dev/ttyAMA0 (/dev/ttyAMA0)
12:00:54:086 dev /dev/ttyAMA0 (/dev/ttyAMA0)
Reboot device RaspBee (RaspBee)
12:00:54:087 query bootloader v1 ID after 0 ms
12:00:55:589 query bootloader v1 ID after 1501 ms
12:00:56:090 query deCONZ firmware version
12:00:58:093 uart reset failed, try RaspBee reset
action: reset device RaspBee
wiringPi 2.52 initialized
12:00:58:297 query bootloader v1 ID after 0 ms
12:00:59:798 query bootloader v3 ID after 1502 ms
12:00:59:798 TX c081027dffc0
12:01:00:300 retry, elapsed 6 seconds
12:01:00:405 parse commands: /usr/bin/GCFFlasher_internal.bin -t 60 -f /tmp/deCONZ_RaspBeeII_0x26680700.bin.GCF -x 3

12:01:00:406 using firmware file: /tmp/deCONZ_RaspBeeII_0x26680700.bin.GCF
12:01:00:513 ls dev: /dev/ttyAMA0 (0x0000/0x0000) sn:
12:01:00:514 check symlink /dev/ttyAMA0 (/dev/ttyAMA0)
12:01:00:514 dev /dev/ttyAMA0 (/dev/ttyAMA0)
Reboot device RaspBee (RaspBee)
12:01:00:515 query bootloader v1 ID after 0 ms
12:01:02:017 query bootloader v1 ID after 1501 ms
12:01:02:518 query deCONZ firmware version
12:01:04:520 uart reset failed, try RaspBee reset
action: reset device RaspBee
12:01:04:722 query bootloader v1 ID after 0 ms
12:01:06:224 query bootloader v3 ID after 1502 ms
12:01:06:224 TX c081027dffc0
12:01:06:725 retry, elapsed 12 seconds
12:01:06:828 parse commands: /usr/bin/GCFFlasher_internal.bin -t 60 -f /tmp/deCONZ_RaspBeeII_0x26680700.bin.GCF -x 3

12:01:06:828 using firmware file: /tmp/deCONZ_RaspBeeII_0x26680700.bin.GCF
12:01:06:935 ls dev: /dev/ttyAMA0 (0x0000/0x0000) sn:
12:01:06:935 check symlink /dev/ttyAMA0 (/dev/ttyAMA0)
12:01:06:935 dev /dev/ttyAMA0 (/dev/ttyAMA0)
Reboot device RaspBee (RaspBee)
12:01:06:936 query bootloader v1 ID after 0 ms
12:01:08:437 query bootloader v1 ID after 1501 ms
12:01:08:938 query deCONZ firmware version
12:01:10:941 uart reset failed, try RaspBee reset
action: reset device RaspBee
12:01:11:142 query bootloader v1 ID after 0 ms
12:01:12:644 query bootloader v3 ID after 1502 ms
12:01:12:644 TX c081027dffc0
12:01:13:146 retry, elapsed 19 seconds

Using GCFFLasher v4…
Reset:

pi@raspberrypi:/gcf/gcfflasher $ sudo ./GCFFlasher -r -d RaspBee
command reset timeout
pi@raspberrypi:/gcf/gcfflasher $ sudo ./GCFFlasher -r -d /dev/ttyAMA0
command reset timeout
RaspBee reset done

Attempt to flash:

 sudo ./GCFFlasher -f /tmp/deCONZ_RaspBeeII_0x26680700.bin.GCF -d /dev/ttyAMA0
read file success: /tmp/deCONZ_RaspBeeII_0x26680700.bin.GCF (164387 bytes)
flash firmware
command reset timeout
RaspBee reset done
query bootloader id
query bootloader id
query bootloader failed
retry: 6 seconds left
read file success: /tmp/deCONZ_RaspBeeII_0x26680700.bin.GCF (164387 bytes)
flash firmware
command reset timeout
RaspBee reset done
query bootloader id
query bootloader id
query bootloader failed
retry: 2 seconds left
read file success: /tmp/deCONZ_RaspBeeII_0x26680700.bin.GCF (164387 bytes)
flash firmware
command reset timeout
RaspBee reset done
query bootloader id
query bootloader id
query bootloader failed

If I use RaspBee as the device:

sudo ./GCFFlasher -f /tmp/deCONZ_RaspBeeII_0x26680700.bin.GCF -d RaspBee
read file success: /tmp/deCONZ_RaspBeeII_0x26680700.bin.GCF (164387 bytes)
flash firmware
command reset timeout
retry connect bootloader RaspBee
retry connect bootloader RaspBee
retry connect bootloader RaspBee
retry connect bootloader RaspBee
retry connect bootloader RaspBee
retry connect bootloader RaspBee
retry connect bootloader RaspBee
retry connect bootloader RaspBee
retry connect bootloader RaspBee
retry connect bootloader RaspBee
retry connect bootloader RaspBee
retry connect bootloader RaspBee
retry connect bootloader RaspBee
retry connect bootloader RaspBee
retry connect bootloader RaspBee
retry connect bootloader RaspBee
retry connect bootloader RaspBee
retry connect bootloader RaspBee

Edited:
Using GCFFlasher_internal v4

pi@raspberrypi:/gcf/gcfflasher $ sudo ./GCFFlasher -l
0 devices found

vs 3_17

pi@raspberrypi:/gcf/gcfflasher $ sudo GCFFlasher_internal -l
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
Path             | Vendor | Product | Serial     | Type
-----------------+--------+---------+------------+-------
/dev/ttyAMA0     | 0x0000 | 0x0000  |            | RaspBee

I’m starting to wonder if the issue is my Pi -
The 2nd pin in the GPIO is shorter - although it’s never looked damaged so I don’t know if that was a change for 4B.

Shouldnt be a issue as its power:

I would also say the pin does not look to short to cause problems. I have just tested it with a RaspBee2 sticking it with a gap on the pins and it worked.

When I look at the debug outputs I would say the RaspBee2 is missing its bootloader and so returning it as a faulty device to where you have bought it is the only solution.

Thanks will proceed with that.

Did you figure out how to upgrade the firmware? I have the same issue with my Rasbpee II and Pi4.
I tried to follow the manual upgrade firmware wiki and I also tried it with the prebuild images.
I also have the same problem with the v4 Flasher.

Well, what is your issue? You’re presenting the command to list the DE devices on your system and there is nothing wrong.

No Vendor, Product and Serial?
Flasher fails with retry?
v4 Flasher lists 0 devices

@de_employees

Maybe the “failed” output is not correct. Can you start the service?:
sudo systemctl start deconz-gui
or
sudo systemctl start deconz

And then check the GUI and take a screenshot from deCONZ or check the headless version state:
sudo systemctl status deconz

I upgraded my docker container and therefore installed a newer version of deCONZ. From past experience, I knew, that when my ZigBee devices would not respond anymore, there is a firmware update I am missing. I installed the standalone v4Flasher, but it does not list any devices. I got the prebuild images and the result is posted above. I would love to get some advice on what other things I could try.

I never used the GUI of deCONZ, no idea what I am looking at, but 0x0000 doesn’t look promising.

You have started and connected to the deCONZ GUI that means the FW is installed correctly and the RaspBee is working. There is a bug in GCFFlasher that sometimes it says firmware flashing was not successfull although it was successfull.

On the screenshot you see the coordinator node (the RaspBee) with the network address 0x0000 which is the default for coordinator nodes. So all is fine.
You can check the currently installed firmware bei clicking at “Help” and “abaout deCONZ” in the GUI.
(or with the GCFFlasher command “GCFFLasher_internal -r”) The newest version is the 26720700.

Hi! I also get the “failing” message after flashing. I suspect that I placed the Raspbee II one row offset on the pins the first time I installed it. From the attached picture, is it possible to determine if the Rasbee II is ok or not? The deconz.service seems to start without error.

What I try to do is to install zigbee2mqtt, but I get an errormessage suggesting that the adapter cant be connected. But there are a zillion other things that can go wrong, so I want to confirm that the adapter is ok before proceeding. Is the deconz software necessary at all when running zigbee2mqtt? I also tried to run the Phoscon web app, but I cant log on. There is only a Password box, no Username box, and I always get “wrong password”, or something similar. Can`reset the password either. Tried stop/restart deconz.service before trying to reset password.

deconz status-0

Thought I would try to reset Phoscon password one more time, and this time it actually worked! Can`t say I did anything differently. Powercycled deconz first (sudo systemctl stop deconz, then sudo systemctl start deconz) Have paired a IKEA led driver, switch, and a motion sensor, so the Raspbee works just fine. So far on/off, dim and the switch works, but not the motion sensor. It is recognized, so probably something I do wrong in the app.

Maybe one of these two things happened:

Browser vendors are apparently rolling out new security features. This may cause our Phoscon App Discovery page www.phoscon.de/app (and the beta app) to not work correctly. It should work in Firefox. Our developers are working on a solution. In any case, the variant of calling the Phoscon App via the IP address of the gateway works.

Possibly not current data is displayed in the WebApp. Here it helps to open the Phoscon App again in a private tab. Alternatively, cache and app data can be cleared in the browser.

Thanks for explaining the GUI. It reports back as 26720700. Unfortunately, I still can’t connect any ZigBee device, but this is off-topic. Not sure if threats can get closed here, my issue has been resolved. I kindly suggest reworking the user experience; a failing V3 flasher and a V4 flasher that lists 0 available devices don’t give me the impression that my firmware is up-to-date.