@Robban - I haven’t tried it yet, but does your component support multiple deconz gateways?
No. But it would be easy to add support for it
Great to hear that they work 
I really hope that the deconz guys is able to fix a function to use the siren in them, would be an excellent addition to my homemade alarmsystem.
Which ones are you using? Im thinking of getting Xiaomis smoke detectors, I think someone said that it is rebranded Honeywell detectors
Yeah it’s the rebranded honeywell I’m using, https://goo.gl/cfxwoX
Got 4 of them and I’ve had the pleasure of having a live test of them, my gf started our fireplace without opening a window to make sure the air flow in the room was high and it went off right in time for us to notice and open the door to get the smoke out before it stuck to the furniture 
Also they are really high quality, it feels alot more expensive then the 200sek it costs, and good looking to!
Is there a list of devices that have been confirmed to work with the ConBee? I’m not sure whether to purchase one of these or the ZiGate (I’d like it to work with Xiaomi MiJia devices).
Quick update: marthoc/deconz Docker image updated to 2.05.07.
1 Like
@marthocoo i will try it out some time this week. I have some issues with the mesh network making the lights hard to control
Hi!
First of all thank you for your great work! I’m not sure if reporting my problem with the HA native deconz component is placed here correclty. if not please tell me where to go to.
Setup: I Have hassbian running on a Pi3 with a raspbee connected.
Deconz: 2.04.99
Home Assistant: 0.63.3
I’ve had two Ikea lights connected that worked perfectly with HASS.
Today one of the light entities (light.light1_2) dissapperead in HASS but is still accessible via Deconz WebApp and Rest-API.
I can even still rename it via HASS service “deconz.configure” when i refer to it using { “field”: “/lights/1”, … } but ovilously not via { “entity”: “light.light1”,…}.
I have tried deleting the light from deconz, reseting and readding in the webAPP, renaming via REST-Api but nothing brings it’s entity back in HASS.
Is there way to rediscover this entity or to manually add it?
Thank you very much in advance!
It’s totally fine.
So there are a couple of things you can check.
-
Logs, do you get any errors or can you see any mention of that specific light? You might need to change logger default to debug
-
Check entity_registry.yaml and maybe remove your light from that file.
/R
Quick update: my deCONZ Docker image now supports Conbee (and maybe RaspBee, I haven’t tested yet) on amd64 and armhf: (https://hub.docker.com/r/marthoc/deconz).
It’s multiarch, so it will pull the correct image for your arch when you do pull marthoc/deconz or create/run a container using marthoc/deconz as the image name.
Hass.io addon is currently “in the works” - I need to study how to build addons properly first. One problem is that I don’t use hass.io for either RPi or amd64 so I wouldn’t have a way to test on an ongoing basis. I’m happy to have a collaborator on this though if anyone is interested; my images should work well as an addon base, I would think.
I would definitely like to help! Nevertheless, I do not own that hardware, so testing is going to be hard.
@frenck I was supplied with a Conbee and RaspBee by DE in order to work on docker - I think if you post on their GitHub repo at “manup” he may supply you with the same in order to get a solid addon for Hass.io.
Alternately, I may try taking shot at making an addon and come to you for advice when I can’t figure it out haha
Fine by me. I already offered my help once on GitHub, nevertheless, it was already in the making or something.
That was already some months ago.
Wouldn’t the hassio part be possible to verify without hardware? Making sure the container works with hassio would be enough right? @marthocoo already verified the hardware