Unable to find devices with RaspBee II

Phoscon App General Support
#1

Hello all,
I’m trying to change from a conbee2 to a RaspBee2
I’ve removed the usb stic and installed the new device.
My system is rasbian OS update to today. I run deconz as a docker container with the following command:

docker run -d \
 --name=deconz \
 --net=host \
 --restart=always \
 -v /etc/localtime:/etc/localtime:ro \
 -v /home/pi/Deconz/opt:/opt/deconz \
 -v ~/.local/share/dresden-elektronik/deCONZ:/root/.local/share/dresden-elektronik/deCONZ \
 --device /dev/ttyAMA0:/dev/ttyAMA0 \
 -e DECONZ_WEB_PORT=1380 \
 -e DECONZ_WS_PORT=8443 \
 -e DECONZ_VNC_MODE=1 \
 -e DECONZ_VNC_PORT=5907 \
 -e DECONZ_VNC_PASSWORD=changeme \
 marthoc/deconz

The fact is that I cannot find any zigbee device anymore.
If I enterin the phoscon app, no lights or anything else is found.
The strange thing is that if go in the gateway page
Vendor is unknow
there is no product data
the version is the 2.13.01 / 6/10/2021
and it says that the firmware is not connected.

May I give any other infos to help me to solve the clue?

#2

Check if you don’t have disconnection, if yes, update the firwmare.

Have you make a backup of the previous network and re upload it on the new one ?

#3

It seems I do

 $ docker logs deconz
[manymany]
15:13:32:482 failed to reconnect to network try=1
15:13:33:334 dev /dev/ttyAMA0

As far I see I have the latest firmware, or there is a newer one?

 $ sudo GCFFlasher_internal -r
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
Reboot device RaspBee (RaspBee)
deCONZ firmware version 26720700
Bootloader version 0x00030003, app crc: 0x01BB96DC

Yes I’ve done it (the one done with the conbeeII) but at the end the loaded file does not gives any result :frowning:

Any other idea?

#4

Only one, or you have them in loop mode ?

Information about firmware version changelog.en

But you can use the same you already have, just upload it again (the issue can come from a bad installed one)

#5

the option --device should by like: --device /dev/ttyAMA0

Also I think its better that you add -e DECONZ_DEVICE=/dev/ttyAMA0

#6

Many many many :frowning:

If you mean at this link I’m up to date

I’ve modified as you suggested in the following code:

docker run -d \
--name=deconz_test  \
--net=host  \
--restart=always  \
-v /etc/localtime:/etc/localtime:ro  \
-v /home/pi/Deconz/opt:/opt/deconz  \
-v ~/.local/share/dresden-elektronik/deCONZ:/root/.local/share/dresden-elektronik/deCONZ \
--device /dev/ttyAMA0:/dev/ttyAMA0  \
-e DECONZ_WEB_PORT=1380  \
-e DECONZ_WS_PORT=8443  \
-e DECONZ_VNC_MODE=1  \
-e DECONZ_VNC_PORT=5907  \
-e DECONZ_VNC_PASSWORD=changeme  \
-e DECONZ_DEVICE=/dev/ttyAMA0 \
marthoc/deconz

The only change I’ve noticed that adding the DECONZ_DEVICE at least the vendor is now correct.

any other try?

#7

You should als change ‘–device /dev/ttyAMA0:/dev/ttyAMA0’ into ‘–device /dev/ttyAMA0’

Could you also share your log?

#8

Here you can find all the log file

and I modified the start with the following command:

docker run -d \
 --name=deconz \
 --net=host \
 --restart=always \
 -v /etc/localtime:/etc/localtime:ro \
 -v /home/pi/Deconz/opt:/opt/deconz \
 -v ~/.local/share/dresden-elektronik/deCONZ:/root/.local/share/dresden-elektronik/deCONZ \
 --device /dev/ttyAMA0 \
 -e DECONZ_WEB_PORT=1380 \
 -e DECONZ_WS_PORT=8443 \
 -e DECONZ_VNC_MODE=1 \
 -e DECONZ_VNC_PORT=5907 \
 -e DECONZ_VNC_PASSWORD=changeme \
 -e DECONZ_DEVICE=/dev/ttyAMA0 \
 marthoc/deconz

But the result is always the same :frowning:

#9

Have you done sudo apt install wiringpi ?

can you bash into the container and do ls -all /dev/ttyAMA0?

#10

yes

 $ sudo apt install wiringpi
Reading package lists... Done
Building dependency tree
Reading state information... Done
wiringpi is already the newest version (2.52).
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.

done

$ docker exec -it deconz /bin/sh
#
# ls -all /dev/ttyAMA0
crw-rw---- 1 root dialout 204, 64 Nov 17 23:20 /dev/ttyAMA0
#
#11

Is sudo usermod -a -G dialout $USER also done on you docker host?

#12

don’t know if it is really needed, since inside the istance deconz runs as root

$ docker exec -it deconz /bin/sh
# ps -ef | grep -i deco
root        73     1  1 09:16 ?        00:03:18 /usr/bin/deCONZ --auto-connect=1 --dbg-info=1 --dbg-aps=0 --dbg-zcl=0 --dbg-zdp=0 --dbg-otau=0 --dbg-error=0 --http-port=1380 --ws-port=8443 --dev=/dev/ttyAMA0
root       612   604  0 12:05 pts/1    00:00:00 grep -i deco

Or you mean the user wich I lounch the docker istance, then it is already part of the dialout group

 $ id
uid=1000(docker_user) gid=1000(docker_user) groups=1000(docker_user),4(adm),20(dialout),24(cdrom),27(sudo),29(audio),44(video),46(plugdev),60(games),100(users),105(input),109(netdev),112(bluetooth),995(docker),997(gpio),998(i2c),999(spi)
#13

Did you try it without docker? Just native?

#14

Not untill now, but now I did, and I’m getting totaly crazy.

I’ve stopped the docker istance

$ docker stop deconz
deconz
$ docker ps
CONTAINER ID   IMAGE                                          COMMAND                  CREATED         STATUS       PORTS                                                                                  NAMES
$ ps -ef |grep -i decon
docker_user        1530 19234  0 14:55 pts/0    00:00:00 grep --color=auto -i decon

OK nothing is running!
Now I’ve followed the instructions written on this site RaspBee II Installation

after that I’ve started the service

$ sudo systemctl start deconz

Now I’ve ponted my browser to the IP of the server and here start ne strange things.
I’ve got the first surprise.

immagine

why two istances? ok maybe a problem of the cache. I try to empty totaly the cache of the browser, but no changes ?!?!

OK, let’s continue anyway.
I select one of the two , and star the setup as it was brand new installation.
I enter the name of the device and the new password, and I get in to the flow to find new devices (wich I skip for the moment).

I go in the main settings → gateway and… SURPRISE!!!
it seems to work!! even better then the docker version since it sees also the wifi part!!!
immagine

Now I’ve tried to load a previus backup.
Everything seems to go ok; all my devices are listed… BUT… no, I cannot pilot them trought the web interface :frowning: :’-(
I mean that I can change the values in the GUI but it has no effect on the lights.

Something more I can try?

#15

But you have the GUI too ?

Do you have some logs or error mesage ?

#16

Sorry, no gui, it is a headless system.
I don’t know this time where to retrive the logs… could you help me pls

#17

On headless OS, need to use command line https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/deCONZ-debug-flags

1 Like
#18

First of all thank you @Smanar for pointing me to the right link :pray:

here are what I had as result of the following command:

# /usr/bin/deCONZ -platform minimal --dbg-info=2 --dbg-error=2 > debug.txt

On the console I had the following messages:

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
libpng warning: iCCP: known incorrect sRGB profile
"No carrier"
This plugin does not support propagateSizeHints()
This plugin does not support propagateSizeHints()
This plugin does not support propagateSizeHints()
"No carrier"

The “No carrier” messages was repited endless.

the debug file you can find it here

hope it helps

#19

From this log, it seem you don’t have sensors ? (only the integrated one)
We can see too a poor router trying to connect, but nothing more.

Wich one channel have you choose ?

I m realy skeptical when you said you can see all your devices with this kind of logs, it 's not normal.

#20

I can assure you that I have 12 bubl lights, 5 sensors and 3 buttons… but none of them is detected :frowning: all of them, with the usb stick everything was working perfectly… I think I will return to this solution :sob:

the channel indicated with the command line command is channel 20 and network id is 0c37 now I will try to switch to 11 to see if it changes something…

I ment I was able to see all my devices with the usbstick, but not now with the raspbeeII