That is not what is reported. I have many xiaomi sensors connected to repeaters.
sorry i typed wrong, i think they can connect to bulbs indeed, but smart plugs is more difficult
most of the ones reporting xiaomi are connected to a router, is a bulb, not a plug
FYI for those using a Hue dimmer with Deconz. I’ve just seen that there is a firmware update available for it:
I’ve just grabbed the Hue bridge from the cellar and dusted it off. Will have a go at updating and see what happens.
Successfully updated and now running version 6.1.1.28573 on one of my Hue dimmers.
Hopefully it fixes some of the issues I’ve had with it (sometimes a red LED and a 2nd press needed).
Repaid my dimmer to my hue hub, updated the firmware, and paired it back to deconz.
I can see the buttons pressed when viewing the “deconz_event”.
When viewing the it on the device page I am only seeing one device automation trigger.
That still shows the old firmware version. I deleted it first from Phoscon and re-added it and gave it the same name then rebooted hass.io.
I figured with a firmware update it would need to be re-paired to pull all the correct info through.
Hey All, can anyone tell me how to add Xiaomi smart plugs to deCONZ? I’ve tried pairing as other switch and other light. No luck.
Thank you
Linton
They work as lights. Hold the button until the light flashes blue.
Having said that they don’t seem to act as routers.
Hello all,
what are CLIP sensors? You can enable them on the integration page but i cant see a difference to the situation without them enabled?
Greetings
Got my firmware updated, but still only showing the battery automation. The remote works and HA can see the buttons press when viewing the deconz_event stream. Don’t know why the other button automations don’t show. They show up on my hue tap.
Did you first delete the remote in Phoscon?
My procedure was:
- Reset remote
- Add to Hue bridge
- Update firmware
- Delete remote from Hue
- Delete remote from Phoscon
- Re-pair remote to Phoscon (also reset while pairing)
- Reboot HA
Did all of those in that order. The only other thing I could think of, maybe mine is an older hardware version. I’ve had it for a while. My Hue tap is working fine, so I am guessing it might just be the remote.
Ah. Maybe that’s it. Just noticed yours is listed as RWL020 and mine are RWL021.
I bought mine in April 2016 (still on the original batteries by the way with one at 29% and the other at 6%).
I’m really flummoxed and need to understand a bit about how deConz/Phoscon works “under the hood”. I have an HA setup at home running on a NUC - Hassio on an Ubuntu host, using the official deConz add-on. It uses the original Conbee stick and it works great. I recently set up another HA instance on a Raspberry Pi using Hassio/HassOS, same add-on, to bring to another location. It has a Conbee II stick. When I was setting it up (at home), I shut down my home instance of HA but stupidly did not power down my NUC, so my Conbee was still powered. I could see both gateways in the Phoscon app of my home instance.
Now, the new instance is working and has been moved to its new location, not near my home. However, on my home instance the Phoscon app still shows both gateways. I can only access the home gateway, which makes sense because it’s the only one actually on my network (at 192.168.0.111). What I don’t understand is that in my home Phoscon, I see the IP address of the remote gateway that it has in its new location (192.168.2.120). How does my Phoscon app even know that??? I don’t have a 192.168.2.xxx network at home. I’m using the HA Cloud/Nabu Casa to access the remote instance - unfortunately, since the deConz add-on doesn’t have Ingress support, I can’t see the Phoscon app of the remote instance.
I just don’t understand what is going on…I’d really appreciate if someone could shed some light for me. Ideally I’d like to only see the appropriate gateway from the appropriate instance. Thanks for any help!
Remove cookies. It has a cookie which states you have two conbees in different locations.
I have both if still needed
seems in your screenshot, you have a lot of battery sensors, but none of them is connected to a router plug/bulb, all connected to your conbee itself … is this intended? or is it for you also impossible to pair and end device to a plug/bulb ?
If you’re referring to me, I have no bulbs, just plugs (outlets?), and AFAIK I don’t get to choose how they connect. EVERYTHING connects to the Cobnee 2 because that’s just how it seems to work
yeah, you have the same issue as me then , i also have xiaomis, i want to have them connected to my ikea plug (socket) and not to the conbee …, i now have the conbee on a central location in my house, because i am forced too
already tested osram/ikea, ,and succeeded once though, see screenshot
next week i test a innr plug, seems my colleage has some, and he was able to pair with it…
what brand of sockets do you have?
He didn’t mention he had an issue, you turned his response into one. And looking at the green connections to your xiaomi sensors you do not have an issue as well except you want to manually control your mesh network.