How I can use the ZHA integration? I’m asking because the deCONZ is not recognising my Lidl plugs or at least I’m not sure how to do it
you cant use them both at the same time with the same conbee II
stick
Perfect, so, is it mandatory to use deCONZ? or can I remove the container and use the ZHA?
DeConz works flawlessly with Lidl smart units. What did you try to connect to it?
I’m trying to add the Lidl smart plugs. I set the discovering mode on it and do the discovery in the web (under lights) but nothing happens. I have also tried with sensors and the other one
I usually do it just opposite. First allow the inclusion in the web and then include the devices.
Maybe you want to try the reverse method, as Sergi already mentioned:
Bring the Conbee near to the plugged Lidl plug.
Open Phoscon.
Choose „Add switch“. (or lights if switch doesn‘t work)
Pull the link button for a few seconds.
I’ve seen quite some posts by @ebaauw about the support of the IKEA Styrbar button/switch. Can’t find any conclusive comments about whether it actuallys is supported yet. I’ve got one at home, but can’t get it to pair via deconz → Switch → IKEA → Tradfri Remote Control.
Using the method to reset the device by pressing the button 4 times in 5 seconds, and pair it by holding the button for 10s, but nothing pops up.
If anyone knows more about the Styrbar, please let me know! 
It took me some time as well to find out, but you need to login via Phoscon Beta App:
phoscon.de/pwabeta/login.html#host/IP:40850
Thanks for your quick reply! Trying to login to Phoscon Beta gives me “Login failed” even though I’m using the same password I’m using for the stable Phoscon environment. Trying to reset the password gives me “Failed to reset password Make sure the gateway was powercycled recently.” while I just power cycled the device. Tried different browsers, private windows etc. Gonna have to look further into this first.
Thanks for your reply.
The IP address that shows in my screenshot is different than the one I see in HomeAssistant > deConz > Phoscon app, yes. When I use the one I see there (starting with 192) in the address bar like this: hoscon.de/pwabeta/login.html#host/192.xxx.x.xxx:40850 it still shows me the one starting with 172, even after pressing the letter “P” to search for gateways.
How would I get the unit connected to the beta environment? I can login perfectly fine via the normal environment.
1 Like
Handy link. Then I see the IP which is shown in my first screenshot as internal IP. The port is 40850.
On a side note: when I go to http://phoscon.de/app, the same 172 IP address is showing there. Though when I run the deCONZ integration from HomeAssistant and use The Phoscon App over there, the gateway shows the 192 IP address.
I cannot judge how up-to-date the DeConz addon is kept. In my installation it never worked properly (plus the same IP problem), but that may also been due to my ancient PC that I use as a host.
Since then I always update to the latest successful beta version of the deconz-rest-plugin.
Thanks for your reply.
I just managed to fix it by simply filling in the port number here:
The 172 gateway address changed to 192 by itself after that .
This topic has helped me a lot with finding the solution: Connect to Rest API problem · Issue #2716 · dresden-elektronik/deconz-rest-plugin · GitHub
I even managed to add Styrbar to Switches Beta in Phoscon! Can’t get it to connect to my bulbs yet though, because it doesn’t show up in the ‘Link Switch’ menu within Phoscon.
@erik7 how did you manage to connect it to the right bulbs?
1 Like
-facepalm-
I‘m thinking too complicated… congrats!
1 Like
After updating from 6.8.0 to 6.9.0 i can’t access the Deconz web interface, i get this error:
Looking Deconz log this is what happen if i try to enter the web interface:
172.30.32.2 - - [13/Jun/2021:09:59:31 +0200] “GET /pwa/index.html HTTP/1.1” 413 0 “http://192.168.1.53:8123/api/hassio_ingress/TzAKeMF7NpgdagxrYzKdD7Th3X-xn4IizFL04jNytGQ/ingress.html” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.77 Safari/537.36”
Rolling back to 6.8.0 the problem disappears and i can enter the web interface and this is what happen if i try to enter the web interface:
172.30.32.2 - - [13/Jun/2021:10:18:40 +0200] “GET api/hassio_ingress/TzAKeMF7NpgdagxrYzKdD7Th3X-xn4IizFL04jNytGQ/api/config?_=1623572320282 HTTP/1.1” 403 140 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.77 Safari/537.36”
Any ideas?
Hi, just for everyone who is interested.
Since 6.9.0 I activated source routing. Before, I had alway bulbs which were unresponsible or lost their contact to deConz. With this new option it is history.
Since four month absolutely rock solid. No lost bulbs or switches anymore.
This is a real success story imo.
2 Likes
Sounds good! I checked in deconz and I can see that I can enable this feature. Is it suited to particular types of networks? I have about 30+ powered devices (Ikea and Hue bulbs, some smart switches) but about 60+ battery devices (xiaomi open / close sensors, motion sensors, climate sensors, smoke detectors etc).
My network has been really stable except for one or two stubborn battery-powered devices that fail to return after power outages, and occasionally a xiaomi sensor on a door failing to “close”, so I’d be concerned that I might actually make things worse…