ConBee ZigBee Stick and HA, will this work together?

Hi, This is my first post.

I’ve been testing HA for some time and I’v wanted to get me some Philips Hue light bulbs, but I dont want the bridge.
The I found this ZigBee USB stick

This stick has the following specs,

  • Central control element for intelligent wireless light control
  • Comfortable Light Control per WebApp of Philips Hue, OSRAM Lightify, CREE, GE and dresden elektronik FLS
  • 2.4 GHz ZigBee USB Gateway
  • Compatibility: ZigBee Home Automation, ZigBee Light Link, ZigBee 3.0
  • Host OS: Windows 7 / 8 / 8.1 / 10, Ubuntu Linux, Raspbian

This makes me belive that it will work together. But I’m not sure, so I was wondering if any one else has tested this and can confirm that it works?

And if this works it will mean that we dont have to use Philips Hue Bridge?

Or maby this can be used?

  • Paul

Hi. Thats a really good question as I also wanna swap to this stick. I just bought it and waiting the delivery. I saw that this might work with hue component. but I wanna ask again if theres a way to integrate this stick as a independent component.The RestApi is well documented and I would highly appreciate an answer from a dev as i am not a coder or programmer. A feedback also from users with experiences would be highly appreciated :slight_smile:

Yes. This works. It supported by HUE component.
Check this thread: RaspBee ZigBee

great … so i just need to change the host to lacalhost as soon as I added the stick physically :slight_smile: great news. And all devices are well reachable all the time ?

Ok, I did it… I have ordered a RaspBee. It seems to me a cheap all-in-one solution.

As far as I have seen the solution seems to be pretty solid. The rest-api appears to be well documented. Besides that, the supplied software deConz can be directly connected (swedish guide) to home assistant using the hue config.

As I’ve seen on the homebridge github page of ebaauw a lot of devices are supported already. Even more are added daily. His bridge connects the zigbee devices trough a emulated homekit bridge. So his list of sensors are known to be working with the current release.
It support for the following sensors:

  • Hue motion sensor (1,2),
  • IKEA Trådfri motion sensor (2),
  • Xiaomi Aqara weather sensor (2),
  • Xiaomi Aqara door/window sensor (2),
  • Xiaomi Aqara motion sensor (2),
  • Xiaomi Mi temperature/humidity sensor (2),
  • Xiaomi Mi door/window sensor (2),
  • Built-in Daylight sensor (1),
  • CLIP sensors: Presence, LightLevel, Temperature, Humidity, Pressure (2), OpenClose,
  • Writeable CLIP sensors: GenericFlag, GenericStatus;

It support for the following switches:

  • Hue dimmer switch (1,2),
  • Hue tap (1,2),
  • IKEA Trådfri remote (2),
  • Xiaomi Aqara smart wireless switch (2),
  • Xiaomi Mi wireless switch (2),
  • Xiaomi Mi smart cube (2),
  • Hue bridge link button (1);

It support for the following lights:

  • Philips Hue lights (1,2),
  • ZigBee Light Link (ZLL) lights from other manufacturers (1,2).
  • ZigBee Home Automation (ZHA) lights (2),
  • ZigBee 3.0 lights (2);

I’ve never programmed a single line in Python so I realy have no clue where to begin, but I’m pretty sure that with some help of the HA community it will work!

It would be nice to know if some other members already bought this ConBee / RasBee, I know @DariBer has one (do you like it?).

Good news, the Tradfri is supported already!

It actually does. They even got the new smartcube working already!

Do you have any Xiaomi sensors or switches? what happens if you just connect HA using the Swedish guide (use google translate)
@donnib did you received it yet? did some testing already?
@abmantis … did you made up your mind yet?
@touliloup … while the kickstart campain cannot be backed anymore I’ve ordered this module :slight_smile:


Nice summary! No, I’ve not yet ordered one, but I’ll very probably will soon.
By the way, do you have an headless raspberry pi? I have the lite version of Raspbian, without stuff, and I think Deconz needs that to work. But it seems to already work correctly without a GUI, but still needs libs:

Yes I have a RasBee in one RPi3 and I have connected some IKEA Trådfri and som Philips Hue and my Hass see the RasBee as a Hue Bridge.

I haven’t connected any remotes and my Firmware is old, so I haven’t upgraded it to latest where you can use IKEA remote.

It’s time for a small update!

Yesterday I have received my Raspbee.
The Xiami motion sensors are supported out of the box.

The Xiaomi swich (round one’s) are working as well, for now it only reports the states on / off (double click long click etc.) needs to be added.

The Xiaomi smoke detector is able to connect and recognized, I’ve created an issue on github and the developer is working on support for the smoke detector.

The Xiaomi smart plug (zigbee) as able to connect and recognized. Working out of the box, however I have created an issue regarding the power consumption / mains voltage reporting. The developer responds within 5 minutes and is working on adding those fields to the API as well.

So far so good :sunny: it realy looks promising.

I’ve contacted the supplier regarding my questions about the difference between the Conbee(usb) en the Raspbee (rpi shield). They both support zigbee pro, so all devices are supported. The chip is the same the usb version just uses a ftdi connection while the RPI shield uses the RPI RX TX pins.

The RPI image is just burn and boot :slight_smile: there is no need to connect it to a tv or usb keyboard. Out of the box they have installed a VNC server, you can connect using a free vnc server or ssh. Deconz start on boot and they have installed a watchdog to keep things running.

So all relevant hardware is supported, no need to buy a hue bridge, xiaomi gateway or ikea bridge, this gateway does it all. As the developer told me;all Zigbee devices that use the Zigbee standard can be supported. The next big question is, how to integrate this into HA.

At the moment there are multiple ways to get it connected. It would need a component witch is able to do two things:

  • Poll the REST-API and add / update devices to HA
  • Bind to the websocket interface allowing instant actions on motion / switch events.

I’ve issued two feature reqests, one to deconz: adding mqtt support. Another on HA, websocket client sensor support. Both might come in handy.

Deconz replied he will investigate the MQTT request. But first they will focus on bugs and a new web interface.

HA user @donnib has created his own custom component. He uses both the rest-api and websockets. I have asked him if he is willing to share his work with us. As I have read somewhere he wants to clean up his code before publishing it.

Any questions? please let me know!


Update two;
I have migrated all my Xiaomi motion sensors to the Raspbee. Works great, even the range is better.
I’ve noticed there is even a solder pad for an external antenna, so who knows what the range will be when mouting an extra antenna.

What I did to get it all working with HA is this.
I have decided to create a Deconz to MQTT gateway using Node-Red.
Node-Red listens to events on the websocket and publishes those messages to the MQTT broker.

I’ve created the sensors in HA like this:

  - platform: mqtt
    state_topic: "/Deconz/motion/6"
    name: "Motion Kitchen"
    device_class: motion


- platform: mqtt
  command_topic: "/Deconz/switch/1"
  state_topic: "/Deconz/switch/1"
  name: "Switch 1"

Node-red publishes the states using retain = true, so no polling is needed. The gateway automatically checks the last MQTT state when booting.

Motion sensors, temperature sensors and switches are all compatible and working like this.

I will share the node-red flow when someone is interested.


Could you please share the link to RPI image. I found only guide how to install Rest API on their GitHub.

The image can be found here.

However after imaging your SD card you should upgrade to the latest (beta) version using the information found here.


The result so far. This is my flow:

A little explanation might be handy:

  • On the left the websocket binding. Here you should fill in the IP of the Deconz RPI.
  • Then the conversion to a JSON object.
  • Then multiple switches, based on the existence of various keys we can identify what kind of sensor is submitting the event.
  • The function element generates the MQTT topic and converts the value to preferred HA state, for example, motion sensors should be ON while motion and OFF while no motion. This was a little bit weird. At first I used the HA rest-api to set the sensor. Because this meant I had to create all sensors in HA and Node-red I switched to MQTT. However, the HA rest api accepts “on” and “off” while the MQTT sensor wants “ON” and “OFF” in order to work :wink:
  • At last publishing the message to the broker.

One thing I should add, is filtering on the input to process only events with changed states. The events with new device added or sensor x is reachable should be ignored.

I’m posting this because one might find it handy. Switches and Motion sensors are working and have been tested. Light sensors and open close sensors will arrive soon :slight_smile:

(The debugging elements can be removed. I kept them because they provide some nice info.)


Thanks @rtenklooster,

I undust an old raspberry pi, imaged the SD, did some tests (philips dimming switch with osram lightify plug).

Works great, now I’ll start moving forward:

  • testing aqara switch
  • connecting it to hass

Thanks! Much appreciated.

Could you explain a bit more how to link raspbee-gw with hass?

It’s still a bit cryptic for me :smiley:

Do you use HASS.IO or normal HA?

Normal HA right now, but planning to move to HASS.IO in the near future.

I have MQTT enabled & working though.

In that case it should be fairly simple to get started.

  1. Install node-red
  2. import this flow:
  3. Edit IP Addresses of MQTT broker and websocket client
  4. Add the corresponding sensors / switches in your HA conf.

Like this for a motion sensor with ID 2 in deconz:


  • platform: mqtt
    state_topic: “/Deconz/motion/2”
    name: “Pir woonkamer”
    device_class: motion


I’ll try that.

Right now I just tried to compile as described in the doc but it failed on my Raspberry 1 B:

Makefile.Release:712: recipe for target 'release/rest_groups.o' failed
make[1]: *** [release/rest_groups.o] Error 4
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory '/home/pi/deconz-rest-plugin'
Makefile:34: recipe for target 'release' failed
make: *** [release] Error 2

Could it be because of my raspberry 1 instead of 3?

@rtenklooster sorry I don’t want to hijack the thread about this. I logged an issue on the github, we’ll see what the answer is. On the page it’s stated that RPi1 is supported.

I don’t know. What I know is the RPI 1 isn’t supported.
rpi 2