All,
I just both a pi 3 Model A+
This has a bluetooth in and they used for the bluetooht device the serial port which is used also for raspbee.
I cost me a while to find this out and to help others I put here a solution might be you update the source and check it a bluetooht device is in the board.
Regards
Franz
here is the solution
https://openenergymonitor.github.io/forum-archive/node/12311.html
I do still not get it up to work.
always get:
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
18:06:28:953 using firmware file: deCONZ_RaspBeeII_0x26780700.bin.GCF
18:06:29:061 ls dev: /dev/ttyAMA0 (0x0000/0x0000) sn:
18:06:29:061 check symlink /dev/ttyAMA0 (/dev/ttyAMA0)
18:06:29:061 dev /dev/ttyAMA0 (/dev/ttyAMA0)
Reboot device RaspBee (RaspBee)
18:06:29:064 query bootloader v1 ID after 0 ms
18:06:30:566 query bootloader v1 ID after 1502 ms
18:06:31:067 query deCONZ firmware version
18:06:33:070 uart reset failed, try RaspBee reset
action: reset device RaspBee
wiringPi 2.52 initialized
18:06:33:274 query bootloader v1 ID after 0 ms
18:06:33:765 RX 8 bytes ASCII after 491 ms
18:06:33:765 RX 030085a1628fe0f9 after 491 ms
18:06:34:766 query bootloader v1 ID after 1492 ms
18:06:36:268 query bootloader v3 ID after 2994 ms
18:06:36:268 TX c081027dffc0
Hello, you want to use the internal bleutooth, or disable it ?
Have you tried too with
enable_uart=1
What is the result for
GCFFlasher_internal -l and lsusb
I disabled the bluetooth in config.txt enable_uart=1
dtoverlay=pi3-disable-bt
I compiled the new GCFFlasher v4.0.4-beta and used it the result is:
$ ./GCFFlasher -l
0 devices found
$lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I tried:
~/gcfflasher $ ./GCFFlasher -r -c -d /dev/ttyS0 -f …/deCONZ_RaspBeeII_0x26780700.bin.GCF
read file success: …/deCONZ_RaspBeeII_0x26780700.bin.GCF (163244 bytes)
flash firmware
RaspBee reset done
query bootloader id V3
query bootloader id V3
query bootloader failed
retry: 6 seconds left
read file success: …/deCONZ_RaspBeeII_0x26780700.bin.GCF (163244 bytes)
flash firmware
RaspBee reset done
query bootloader id V3
query bootloader id V3
query bootloader failed
retry: 2 seconds left
read file success: …/deCONZ_RaspBeeII_0x26780700.bin.GCF (163244 bytes)
flash firmware
RaspBee reset done
query bootloader id V3
query bootloader id V3
query bootloader failed
the debugg window in deCONZ said
1:20:00:797 wait reconnect 2 seconds
11:20:00:898 COM: /dev/ttyAMA0 : (0x0000/0x0000)
11:20:00:900 dev /dev/ttyAMA0 (/dev/ttyAMA0)
11:20:00:901 GW firmware update select /dev/ttyAMA0 device
11:20:00:908 GW update firmware not found:
11:20:01:795 wait reconnect 1 seconds
11:20:01:889 COM: /dev/ttyAMA0 : (0x0000/0x0000)
11:20:01:891 dev /dev/ttyAMA0 (/dev/ttyAMA0)
11:20:01:892 failed open com status: (-3), path: /dev/ttyAMA0
11:20:02:795 wait reconnect 5 seconds
11:20:02:886 COM: /dev/ttyAMA0 : (0x0000/0x0000)
11:20:02:887 dev /dev/ttyAMA0 (/dev/ttyAMA0)
11:20:03:795 wait reconnect 4 seconds
11:20:04:795 wait reconnect 3 seconds
11:20:05:795 Daylight now: goldenHour1, status: 160, daylight: 1, dark: 0
11:20:05:797 failed to reconnect to network try=2
11:20:05:798 wait reconnect 2 seconds
11:20:06:796 wait reconnect 1 seconds
11:20:06:893 COM: /dev/ttyAMA0 : (0x0000/0x0000)
11:20:06:895 dev /dev/ttyAMA0 (/dev/ttyAMA0)
11:20:06:896 failed open com status: (-3), path: /dev/ttyAMA0
11:20:07:795 wait reconnect 5 seconds
11:20:07:886 COM: /dev/ttyAMA0 : (0x0000/0x0000)
11:20:07:888 dev /dev/ttyAMA0 (/dev/ttyAMA0)
11:20:08:795 wait reconnect 4 seconds
I have another modul on another rasbery and I change the rasbee model and the model is fine.
The clock as well ??
strange
You mean you have a second Raspbee, and this one is working on the same raspberry ? because for the moment the module is not visible at all.
Correct I have two modules and two raspberry a zero one working now for years and I had a pi4 also with a rasbee and openhab, The pi4 died and needed a new one and I bought the pi3.
I swaped the rasbee 2 just to see if the module is broken as well but it works.
Simply I cannot manage to reach the module on the new pi3
the old flascher says:
openhabian@hab-adler:~ $ sudo GCFFlasher_internal -r -x 3
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
14:12:24:513 ls dev: /dev/ttyAMA0 (0x0000/0x0000) sn:
14:12:24:513 check symlink /dev/ttyAMA0 (/dev/ttyAMA0)
14:12:24:514 dev /dev/ttyAMA0 (/dev/ttyAMA0)
Reboot device RaspBee (RaspBee)
14:12:24:518 query bootloader v1 ID after 0 ms
14:12:26:020 query bootloader v1 ID after 1502 ms
14:12:26:521 query deCONZ firmware version
14:12:28:524 uart reset failed, try RaspBee reset
action: reset device RaspBee
wiringPi 2.52 initialized
14:12:28:742 query bootloader v1 ID after 0 ms
14:12:29:233 RX 8 bytes ASCII after 491 ms
14:12:29:233 RX 030085a1628fe000 after 491 ms
14:12:30:234 query bootloader v1 ID after 1493 ms
14:12:31:737 query bootloader v3 ID after 2995 ms
14:12:31:737 TX c081027dffc0
Is deconz running? If it is, close it as you can’t have deconz running while flashing.
Reason 3 in your logs means stick can’t be accessed.
Ha so you have tried the raspbee on another pi, not another raspbee on the same pi ?
IDK what is your hardware, but can you tried with a pre-installed SD card to make test ? (if you have one in spare ?)
https://phoscon.de/en/raspbee/sdcard
I think the image is tested too on Pi 3.
When I flashed the deCON and all other was of including
sudo systemctl stop ModemManager
I have a spare sd card and a second pi3 good idea I will try tomorrow,
I used the image without desttop and started it the result is exact the same. when I start deCONZ from command line it does not connect.
And when I start phoscon app from browser I can log in etc. but when I go to gateway it says no connected
looks to me something with the serial port, but here I am lost.
This evening I have to go to Berlin back friday next week
thx
Now I left it for a while running the image from phoscon and the gateway was found 2.19.01 / 19/09/2022 Firmware 26780700 then I tried to reset the gateway and the message was failed.
if I starte deCONZ from command line and look into the help INFO_L2 I et:
4:40:25:571 DB save zll database items 0x00000080
14:40:25:573 DB sql exec REPLACE INTO sensors (sid, name, type, modelid, manufacturername, uniqueid, swversion, state, config, fingerprint, deletedState, mode, lastseen, lastannounced) VALUES (‘1’, ‘Daylight’, ‘Daylight’, ‘PHDL00’, ‘Philips’, ‘00:21:2e:ff:ff:06:e6:f5-01’, ‘1.0’, ‘{“dark”:false,“daylight”:true,“lastupdated”:“2023-08-06T13:39:25.607”,“status”:170,“sunrise”:“2023-08-06T04:04:09”,“sunset”:“2023-08-06T19:15:02”}’, ‘{“configured”:true,“lat”:“51.526200”,“long”:“6.907800”,“on”:true,“sunriseoffset”:30,“sunsetoffset”:-30}’, ‘’, ‘normal’, ‘1’, ‘’, ‘’)
14:40:25:589 DB saved in 18 ms
14:40:25:592 Daylight now: solarNoon, status: 170, daylight: 1, dark: 0
14:40:26:671 [Master] kill cmd 0x08 (TIMEOUT)
14:40:26:971 [Master] kill cmd 0x08 (TIMEOUT)
14:40:30:571 GW update firmware not found:
14:40:35:571 Daylight now: solarNoon, status: 170, daylight: 1, dark: 0
finally I made some progress but still strange.
I added a force_turbo=1
due to the fact that the rasbee comes when I wait long I found out that this pi board has low bautrate on the serial port and with force_turbo=1
the speed went up.
Now I the modul is running but still not sure if this is a proper solution.
after a sudo systemctl stop deconz
and deCONZ on command line everything worked out.
Ha yes I making a search on google with “force_turbo=1 deconz” and you are not the only one that use this.
But seriously I have no idea what it’s needed …