deConz and conBee help - cannot see any gateways from web app -

1

Hi,
I’m having some problem setting up ConBee USB stick with deConz.
I use a Rapsberry with Raspbian and manual installation of Home Assistant.

dmesg looks to found the stick when i plug it:

[276600.510417] usb 1-1.2: new full-speed USB device number 7 using dwc_otg [276600.667958] usb 1-1.2: New USB device found, idVendor=0403, idProduct=6015 [276600.667974] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [276600.667983] usb 1-1.2: Product: FT230X Basic UART [276600.667991] usb 1-1.2: Manufacturer: FTDI [276600.667999] usb 1-1.2: SerialNumber: DM01BKAU [276600.676085] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected [276600.676278] usb 1-1.2: Detected FT-X [276600.677234] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0

Then i run the marthoc/deconz container regularly with docker-compose.yml:

version: "2"
services:
  deconz:
    image: marthoc/deconz
    container_name: deconz
    network_mode: host
    restart: always
    volumes:
      - /opt/deconz:/root/.local/share/dresden-elektronik/deCONZ
    devices:
      - /dev/ttyUSB0
    environment:
      - DECONZ_WEB_PORT=80
      - DECONZ_WS_PORT=443
      - DEBUG_INFO=1
      - DEBUG_APS=0
      - DEBUG_ZCL=0
      - DEBUG_ZDP=0
      - DEBUG_OTAU=0

This is the docker log:

[marthoc/deconz] Starting deCONZ...

[marthoc/deconz] Current deCONZ version: 2.05.44

[marthoc/deconz] Web UI port: 80

[marthoc/deconz] Websockets port: 443

libpng warning: iCCP: known incorrect sRGB profile

This plugin does not support propagateSizeHints()

This plugin does not support propagateSizeHints()

This plugin does not support propagateSizeHints()

Then browsing to my raspberry IP port 80 I can see the app but it tells there is any gateways.

What am I missing?

2

Hmm, it looks ok. Are you sure it is on /dev/usb0 on host-os?

3

dmesg tells that.
I don’t know how to test it in another way.
Of course the stick works fine in a Windows OS.

4

You can increase logging for container and see what is printed inside

5

I cannot find anything wrong but…
In the log it is reported /dev/ttyAMA0 and not /dev/ttyUSB0.
It could be matter?

[marthoc/deconz] Starting deCONZ...

[marthoc/deconz] Current deCONZ version: 2.05.44

[marthoc/deconz] Web UI port: 80

[marthoc/deconz] Websockets port: 443

libpng warning: iCCP: known incorrect sRGB profile

This plugin does not support propagateSizeHints()

This plugin does not support propagateSizeHints()

This plugin does not support propagateSizeHints()

09:23:14:944 HTTP Server listen on address 0.0.0.0, port: 80, root: /usr/share/deCONZ/webapp/

09:23:14:958 CTRL. 3.16.209:23:15:042 dev /dev/ttyAMA0

09:23:15:042 ZCLDB init file /root/.local/share/dresden-elektronik/deCONZ/zcldb.txt

09:23:15:202 parent process /bin/sh

09:23:15:203 gw run mode: normal

09:23:15:203 sd-card cid: 035344534333324780ffffffff012aa7

09:23:15:204 DB sqlite version 3.16.2

09:23:15:206 DB PRAGMA page_count: 30

09:23:15:206 DB PRAGMA page_size: 4096

09:23:15:206 DB PRAGMA freelist_count: 0

09:23:15:206 DB file size 122880 bytes, free pages 0

09:23:15:206 DB PRAGMA user_version: 6

09:23:15:206 DB cleanup

09:23:15:206 DB create temporary views

09:23:15:212 don't close database yet, keep open for 900 seconds

09:23:15:213 started websocket server at port 443

09:23:15:218 discovery updated announce interval to 10 minutes

09:23:15:220 found node plugin: libde_rest_plugin.so - REST API Plugin

09:23:15:224 found node plugin: libde_signal_plugin.so - Signal Monitor Plugin

09:23:15:239 found node plugin: libstd_otau_plugin.so - STD OTAU Plugin

09:23:15:273 dev /dev/ttyAMA0

09:23:15:318 discard sensor state push for 1: state/dark (already pushed)

09:23:15:320 discard sensor state push for 1: state/status (already pushed)

09:23:15:321 discard sensor state push for 1: state/lastupdated (already pushed)

09:23:16:137 dev /dev/ttyAMA0

09:23:16:182 dev /dev/ttyAMA0

09:23:16:240 Device firmware version 0x261F0500

09:23:16:260 unlocked max nodes: 200

09:23:16:549 Device protocol version: 0x0106

09:23:16:569 new node - ext: 0x00212effff02a416, nwk: 0x0000

09:23:16:679 APS-DATA.request id: 3, addrmode: 0x02, addr: 0x0000, profile: 0x0000, cluster: 0x0002, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00

09:23:16:679 ZDP send request id: 0x03 to 0x00212effff02a416

09:23:16:757 Current channel 15

09:23:16:821 CTRL ANT_CTRL 0x02

09:23:16:933 Device protocol version: 0x0106

09:23:17:126 Current channel 15

09:23:17:189 CTRL ANT_CTRL 0x02

09:23:17:430 APS-DATA.confirm id: 3, status: 0x00 SUCCESS

09:23:17:430 APS-DATA.confirm request id: 3 -> confirmed, timeout 13277104

09:23:17:463 APS-DATA.indication srcAddr: 0x00212effff02a416, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0002, lqi: 0, rssi: 0

09:23:17:463 ZDP status = 0x00 -> SUCCESS

09:23:17:494 APS-DATA.indication srcAddr: 0x00212effff02a416, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8002, lqi: 0, rssi: 0

09:23:17:494 APS-DATA.indication request id: 3 -> finished

09:23:17:494 APS-DATA.request id: 3 erase from queue

09:23:17:494 ZDP status = 0x00 -> SUCCESS

09:23:17:496 don't close database yet, keep open for 900 seconds

09:23:17:558 ZDP active ep request to 0x00212effff02a416

09:23:17:559 APS-DATA.request id: 7, addrmode: 0x02, addr: 0x0000, profile: 0x0000, cluster: 0x0005, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00

09:23:17:559 ZDP send request id: 0x07 to 0x00212effff02a416

09:23:17:622 APS-DATA.confirm id: 7, status: 0x00 SUCCESS

09:23:17:622 APS-DATA.confirm request id: 7 -> confirmed, timeout 15371688

09:23:17:654 APS-DATA.indication srcAddr: 0x00212effff02a416, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0005, lqi: 0, rssi: 0

09:23:17:654 ZDP status = 0x00 -> SUCCESS

09:23:17:687 APS-DATA.indication srcAddr: 0x00212effff02a416, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8005, lqi: 0, rssi: 0

09:23:17:687 APS-DATA.indication request id: 7 -> finished

09:23:17:687 APS-DATA.request id: 7 erase from queue

09:23:17:687 ZDP status = 0x00 -> SUCCESS

09:23:17:687 ZDP active ep response for 0x00212effff02a416

09:23:17:687 ep: 0x01

09:23:17:687 ep: 0x50

09:23:17:879 APS-DATA.request id: 10, addrmode: 0x02, addr: 0x0000, profile: 0x0000, cluster: 0x0004, ep: 0x00 -> 0x00 queue: 0 len: 4 tx.options 0x00

09:23:17:879 ZDP send request id: 0x05 to 0x00212effff02a416

09:23:17:943 APS-DATA.confirm id: 10, status: 0x00 SUCCESS

09:23:17:943 APS-DATA.confirm request id: 10 -> confirmed, timeout 15448448

09:23:17:974 APS-DATA.indication srcAddr: 0x00212effff02a416, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0004, lqi: 0, rssi: 0

09:23:17:974 ZDP status = 0x00 -> SUCCESS

09:23:18:007 APS-DATA.indication srcAddr: 0x00212effff02a416, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8004, lqi: 0, rssi: 0

09:23:18:007 APS-DATA.indication request id: 10 -> finished

09:23:18:007 APS-DATA.request id: 10 erase from queue

09:23:18:007 ZDP status = 0x00 -> SUCCESS

09:23:18:011 don't close database yet, keep open for 900 seconds

09:23:18:039 APS-DATA.request id: 13, addrmode: 0x02, addr: 0x0000, profile: 0x0000, cluster: 0x0004, ep: 0x00 -> 0x00 queue: 0 len: 4 tx.options 0x00

09:23:18:039 ZDP send request id: 0x05 to 0x00212effff02a416

09:23:18:102 APS-DATA.confirm id: 13, status: 0x00 SUCCESS

09:23:18:102 APS-DATA.confirm request id: 13 -> confirmed, timeout 15371768

09:23:18:134 APS-DATA.indication srcAddr: 0x00212effff02a416, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0004, lqi: 0, rssi: 0

09:23:18:134 ZDP status = 0x00 -> SUCCESS

09:23:18:167 APS-DATA.indication srcAddr: 0x00212effff02a416, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8004, lqi: 0, rssi: 0

09:23:18:167 APS-DATA.indication request id: 13 -> finished

09:23:18:167 APS-DATA.request id: 13 erase from queue

09:23:18:167 ZDP status = 0x00 -> SUCCESS

09:23:18:170 don't close database yet, keep open for 900 seconds

09:23:18:279 ZDP discovery done in 271 ms09:23:18:519 Mgmt_Lqi_req zdpSeq: 5 to 0x00212EFFFF02A416 start index 0

09:23:18:519 APS-DATA.request id: 16, addrmode: 0x03, addr: 0x00212effff02a416, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00

09:23:18:582 APS-DATA.confirm id: 16, status: 0x00 SUCCESS

09:23:18:583 APS-DATA.confirm request id: 16 -> confirmed, timeout 15457056

09:23:18:615 APS-DATA.indication srcAddr: 0x00212effff02a416, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0031, lqi: 0, rssi: 0

09:23:18:615 ZDP status = 0x00 -> SUCCESS

09:23:18:647 APS-DATA.indication srcAddr: 0x00212effff02a416, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 0, rssi: 0

09:23:18:647 APS-DATA.indication request id: 16 -> finished

09:23:18:647 APS-DATA.request id: 16 erase from queue

09:23:18:647 ZDP status = 0x00 -> SUCCESS

09:23:18:647 ZDP Mgmt_Lqi_rsp zdpSeq: 5 from 0x00212EFFFF02A416 total: 0, startIndex: 0, listCount: 0

09:23:20:557 dev /dev/ttyAMA0

09:23:20:558 GW update firmware found: /usr/share/deCONZ/firmware/deCONZ_Rpi_0x262d0500.bin.GCF

09:23:20:558 GW firmware version: 0x261f0500

09:23:20:558 GW firmware version shall be updated to: 0x262d0500

09:23:20:919 Mgmt_Lqi_req zdpSeq: 6 to 0x00212EFFFF02A416 start index 0

09:23:20:919 APS-DATA.request id: 19, addrmode: 0x03, addr: 0x00212effff02a416, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00

09:23:20:985 APS-DATA.confirm id: 19, status: 0x00 SUCCESS

09:23:20:985 APS-DATA.confirm request id: 19 -> confirmed, timeout 15568776

09:23:21:008 Announced to internet

09:23:21:009 discovery server date: Sat, 10 Nov 2018 09:23:20 GMT

09:23:21:009 local time seems to be ok

09:23:21:009 discovery found version 2.04.35 for update channel stable

09:23:21:016 APS-DATA.indication srcAddr: 0x00212effff02a416, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0031, lqi: 0, rssi: 0

09:23:21:017 ZDP status = 0x00 -> SUCCESS

09:23:21:048 APS-DATA.indication srcAddr: 0x00212effff02a416, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 0, rssi: 0

09:23:21:048 APS-DATA.indication request id: 19 -> finished

09:23:21:048 APS-DATA.request id: 19 erase from queue

09:23:21:048 ZDP status = 0x00 -> SUCCESS

09:23:21:048 ZDP Mgmt_Lqi_rsp zdpSeq: 6 from 0x00212EFFFF02A416 total: 0, startIndex: 0, listCount: 0

09:23:23:319 Mgmt_Lqi_req zdpSeq: 7 to 0x00212EFFFF02A416 start index 0

09:23:23:319 APS-DATA.request id: 22, addrmode: 0x03, addr: 0x00212effff02a416, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00

09:23:23:386 APS-DATA.confirm id: 22, status: 0x00 SUCCESS

09:23:23:386 APS-DATA.confirm request id: 22 -> confirmed, timeout 15461680

I found in this DOC this section:

### Configuring Raspbian for RaspBee

By default, Raspbian enables Bluetooth and configures a login shell over serial (tty); you must disable BT, disable the tty, and enable the serial port hardware to allow RaspBee to work properly under Docker.

On a fresh install of Raspbian:

1. `echo 'dtoverlay=pi3-disable-bt' | sudo tee -a /boot/config.txt`
2. `sudo raspi-config`
3. Select  `Interfacing Options`
4. Select  `Serial`
5. “Would you like a login shell to be accessible over serial?” Select  `No`
6. “Would you like the serial port hardware to be enabled?” Select  `Yes`
7. Exit raspi-config and reboot

but it is written for RaspBee and not for ConBee…

6

It is because that is when using the rpi GPIO.

You get a channel and everything so deconz is connected to your conbee.

7

Sorry I didn’t catch if I have to disable BT from my raspberry…

8

Anyway… I tried to star from scratch installing deConz package and I got same issue.
I suspect I miss something in the “serial stuff” configuration.
@Robban do you remember if there are some steps required to well configure the app?

9

Describe what issue you have more exactly; you can’t see any gateway from the webgui?

If that is the case I recommend you to seek support with the developers of deCONZ. They have a GitHub where you get good support on your issues.

One thing you can try is to add an extension cord between computer and conbee. This can sometimes help if users have issues with adding zigbee devices to deconz, but why not try it for your situation as well.

10

If I go to http://my_raspberry_ip I am forwarded to http://my_raspberry_ip/pwa/login.html but here after a message “Please wait until the search for gateways has finished.” I cannot find anything.
Moreover in Home assistant I have discover: enabled in configuration.yaml but if I go Configuration->Integration->deCONZ Zigbee gateway I got a message that says : No deCONZ bridges discovered

Just to be sure to point to correct USB device I also bound the ConBee stick with a specific tty name like:

pi@moon:~/script $ sudo udevadm info --query=property --name=/dev/ttyUSB1 | grep SERIAL

ID_SERIAL=FTDI_FT230X_Basic_UART_DM01BKAU

ID_SERIAL_SHORT=DM01BKAU

then I create a file /etc/udev/rules.d/99-usbserial.rules

pi@moon:~/script $ cat /etc/udev/rules.d/99-usbserial.rules

ACTION=="add",ENV{ID_BUS}=="usb",ENV{ID_SERIAL_SHORT}=="DM01BKAU",SYMLINK+="ttyConBee"

So now the stick is bound to /dev/ttyConBee which is a symlink to the right /dev/ttyUSBx
Then I changed the docker-compose file amending the right device

pi@moon:~/script $ cat docker-compose.yml 
version: "2"
services:
  deconz:
    image: marthoc/deconz
    container_name: deconz
    network_mode: host
    restart: always
    volumes:
      - /opt/deconz:/root/.local/share/dresden-elektronik/deCONZ
    devices:
      - /dev/ttyConBee
    environment:
      - DECONZ_WEB_PORT=80
      - DECONZ_WS_PORT=443
      - DEBUG_INFO=1
      - DEBUG_APS=0
      - DEBUG_ZCL=0
      - DEBUG_ZDP=0
      - DEBUG_OTAU=0
11

The discovery seems to be broken. It doesn’t work for me either. There is a PR (unfortunately coming with 0.83) that will allow manual input through the frontend. You can configure the component manually through configuration.yaml though;

deconz:
  host: x
  port: y

You would also need to map it internally to usb0, like this;

devices:
  - /dev/ttyConBee:/dev/ttyUSB0

note that certain things might require you to restart the system to work properly

12

Ok I inserted first part in configuration.yaml and now HA tells me there is a new device discovered to be configured. Unfortunately I cannot press the “Unlock gateway” button since I don’t see the device.

The second part you mentioned (the device mapping) where should I put it? Is that a HA config o a deConz container config o what else?

Thank You again

13

Inside your docker-compose.yaml

14

Ops I found the issue you were referring https://github.com/marthoc/docker-deconz/issues/29

1 Like
15

@Robban
Ok, I started all from scratch again.
Just to avoid any error due to routine I used this time a RaspBee instead of ConBee USB stick.
I used latest version of marthoc/docker-deconz and HA container images too.
At the end of the process I went to http://my_raspbian_IP/login.htm and I found a device named Phoscon-GW.
Then I clicked on the button “open network” and went to HA->Configuration->Integration selecting deCONZ Zigbee gateway and I went through the procedure.
At the end appeared as configured a deCONZ zigbee gateway: de-CONZ-<some figures> with a sun icon.
If i click on this HA opens a new page with two groups: Phoscon-GW and Daylight (which looks to be something by Philips).
Could you confirm that this is what I should obtain if RaspBee and deCONZ are well configured?

What is the stuff showed by Philips?

Now how can I add new ZigBee devices such as Xiaomi water leakage sensor or something else in HA? Is there any docs explain that?

Thank You again for your support

16

Do you see a channel specified in your settings in deconz?

17

@Robban
Mmmm not sure about you question.
Are you referring to this ?

33
33967×597 27.8 KB

18

Press the show advanced settings button and you should see the channel. If it is 0 the hardware hasn’t been properly found.

19

I did some tests…
When I use ConBee I can see that it was seen on specific channel different from 0.
When I use RaspBee I can only see zero. So it looks that ConBee is well recognised and RaspBee is not.
Ok i’m am quite happy for the ConBee success :sweat_smile:
Now I would like to understand why the RaspBee is not working correctly and I wouls work in parallel in two streams.

RaspBee
Of course I did the extra setting:

### Configuring Raspbian for RaspBee

By default, Raspbian enables Bluetooth and configures a login shell over serial (tty); you must disable BT, disable the tty, and enable the serial port hardware to allow RaspBee to work properly under Docker.

On a fresh install of Raspbian:

1. `echo 'dtoverlay=pi3-disable-bt' | sudo tee -a /boot/config.txt`
2. `sudo raspi-config`
3. Select  `Interfacing Options`
4. Select  `Serial`
5. “Would you like a login shell to be accessible over serial?” Select  `No`
6. “Would you like the serial port hardware to be enabled?” Select  `Yes`
7. Exit raspi-config and reboot

Is there any way to check if the module is recognized by OS?

ConBee
Now how can I go forward with my settings including the Xiaomi water sensor?

Thanks

20

Did you also put in an extra new line? If I remember correct that was important when editing the file.

How do you mean settings? If it all works it is time to pair it

I don’t use a Raspbee so can’t say for sure. Google is your friend here :slight_smile: