Does RASPBEE board work with HA?

I thought I saw threads discussing the use of RASPBEE on HA so I ordered one and started building a new hassbian pi3b+ setup.

Now I can’t figure out how to configure it. The zha: configuration requires usb_path: but of course this is not a USB device. So I think perhaps it was a mistake to purchase this board.

I search for raspbee in this community and oddly the first search result is
Is my SD card full on my raspberry pi? :slight_smile:

Is anyone using the RASPBEE?
If not, anyone want to buy a RASPBEE card :slight_smile:

Yes it does - you need to run the deCONZ server software and then use the deconz component (not zha) in HA. Search up deconz in these forums and you’ll find lots of useful threads to read to bring you up to speed. :slight_smile:

1 Like

OK, some misunderstanding here; zha is a generic platform for zigbee devices, but it does not support RaspBee. Instead you need to configure the deconz component, review the component documentation for help on getting started here. In the documentation there is a link to documentation on getting a docker container (by @marthocoo) running deconz. Please read through it carefully. Especially with disabling bluetooth.

Thanks, I appreciate your help. I am still a little confused. I installed the deconz software for the raspbee as per the instructions here. I used the install steps in the documentation. Section 6.1.1

https://www.dresden-elektronik.de/fileadmin/Downloads/Dokumente/Produkte/ZLL/RaspBee-BHB-en.pdf

That part went fine, I think. I just need to get the HA side working now. I understand that I need to install the deCONZ component for that. Documented here

Do I still need to install the docker container if I already installed deCONZ directly on my raspberry? I would think I do not.
If I do not need the docker container since I already installed deCONZ do I still need to disable bluetooth. The instructions say you need to do this in order to get the serial port in docker to work but I suspect I should not need to do this to work directly on the raspberry hardware.

Its your own choice in how to run deconz, running it through docker is just the recommended way.

The bluetooth issue is (to the best of my knowledge) due to limitations in rpi hardware. You can’t have bluetooth and raspbee at the same time, regardless of which way you’re running deconz.

2 Likes

Someone has tried to use Raspbee with the new HassOS image on an rpi3?
I am struggling to let deconz use the Raspbee module as seems that the config.txt is not working anymore.

Same here. After upgrade to hassos…
Just added following lines to config.txt but still can’t find my xiaomi aqara switches in phoscon app
enable_uart=1
dtoverlay=pi3-disable-bt

SOLVED!

Just add following line to config.txt

dtoverlay=pi3-miniuart-bt

1 Like

Great finding!

We have to add it with the usual config lines or we have to replace one of it?

Just add the line to the end of config.txt
dtoverlay=pi3-miniuart-bt

Also I tried to add :

enable_uart=1
dtoverlay=pi3-disable-bt

But it didn’t work, I have removed this two lines and leaved only one mentioned above.

Please reply here https://github.com/marthoc/hassio-addons/issues/17 with the solution so @marthocoo can add it in the docs.

Sure, I will do it.

I have the same issue with xiaomi switches on hassbian install. The deCONZ asks for brand of switch and I don’t know what to choose. Is that your issue also?

smart,
no my issue was that raspbee was not found by hassio add on (https://github.com/marthoc/hassio-addons)
And solved as I described above just with one line in config.txt

I think you should add Xiaomi switches using other sensor then

I got that to work but now the switch shows up only as sensor.squarebutton_battery_level.
Not sure how to make it a switch. Good to see the Raspbee board is working though :slight_smile:

It’s a physical switch but in HASS remote control button presses are only exposed as events. Check the component documentation

Ah, just like mini-mote, Fibaro button etc. I am not used to that but it makes sense since they are momentary buttons so really just quick events. I was reading doc but I was reading xiaomi switch. I think this is a “binary sensor”, is that correct docs to read? If so still confused because they list a binary_sensor.XXX as entity. I have no entity to look for in this case.

Do I need the xiaomi_aqara configured to make the buttons work. If so I can not figure out how to generate the key. I started another thread asking how this is configured since it isn’t really about the raspbee anymore, that is raspbee is working fine.

It is a remote so neither binary or ordinary sensor

@Robban Thanks, sorry I missed that in docs.