Xiaomi & Aqara Devices - Pairing & Keeping them connected

After adding two more QBKG22LM wired switches I hit a problem; both of the WXKG07LM wireless switches and the SP600 outlet lost connectivity. The recovery mode of the driver would often bring back the wireless switches after three or four presses, which is better than the older version of the wireless switch could manage, but ten minutes later they'd be gone again.

Following the general advice that lamps are terrible repeaters I removed the Trådfri lamps from the mesh and added two more Trådfri repeaters. After about 24 hours things seem to have stabilised again, to the extent that the wireless switch actually worked when my wife pressed it this morning.

@veeceeoh How to avoid having any repeaters, and having a direct connection to the sensor? I don’t have any working repeaters and can’t buy them... should I just unplug every zigbee device in the house? I am fine with avoiding these.

Just a question.
If you do not have any repeaters, why do you need to avoid using them.
Wouldn't your devices connect directly to your hub?
Just a thought.
Thanks.

@bobbles I was asking if it would work directly for 20 feet with a wall.

Anyway, I found a standard Konke sensor for cheaper so I don’t need it now

Hi! I bought an Aqara motion sensor DJT11LM, pair it in hubitat without issue. I put it on my front door, if somebody knocking in the door to give me a notification. The problem I have is that I don't know how to set it in dashboard (I tried motion, acceleration), but is not changing the state. Any ideas? Thanks!

@costin.draghici85 Try this:

  1. enable logging, especially debug logging if possible
  2. wave your hand in front of the motion sensor.
  3. see if you get any logs for that device. If you do, copy and paste them here

Thanks for who ever put these drivers together. I picked up one of the temperature sensors and it's been very reliable for the past week no network drop offs and is pretty much identical to the NYCE motion sensor and thermostat that are within 5 ft of it. I put that there just to test it to see how it would work. The only problem I seem to be having is every hour or so it will report the temperatures 32° and then either simultaneously or within a second or two it goes back to what it should be. Anyone else experience anything like that?

That could be a problem with the driver if it gets data from the device and it thinks it contains temperature information which is 0 and then adds 32 to it.

You could try using a driver that I've written recently for my own use which supports several of these devices:

With that, I do not see the behaviour you are.

Don't have anything kicking aoud for the original button perhaps?
I have had success moving almost all of my 75+ devices over to HE from ST but I have had to use HubConnect (to the ST hub) for the stubborn Fibaro FGK-101 probe and the origial Xaiomi button.
The the buttons show up immediately on pairing but never finish the init no matter what I do like pressing the button repeatedly.

You could try converting this ST driver:

That's what I have been playing with is the old a4refilpad and veeceeoh driver's I used from ST.
So far I have used Minimotes to replace them but that's a but overkill to toggle a light at night :slight_smile:

The fact that it doesn't even finish pairing seems to be the real problem, I guess. When I've had issues with some of these devices before, I've found pairing them to a different hub (like back to the ST hub) and then back again to HE can help. But I imagine you've already done that if you've been going back and forth.

I got them to pair! An old thread clearly stated that it was push the button multiple times until it paired and NOT the reset button.
I ticked the reset button every 4 seconds or so and Voila!, both paired after the discovery.

outstanding.. that did it .. thanks for the driver!

Here's my 2c worth of experience with the C7 and xiaomi sensors. So far they actually work better with the C7 than C4. I use channel 13 and shift my wifi further up the channel bands to minimise interference.

Also essential is if you have repeaters that don't work well with the xiaomis either avoid them or always pair them last (especially for outlets).

Similarly if you have to do a hub restore, make sure any such outlets are disconnected and re-pair them after the restore is completed and the mesh has had a chance to settle.

1 Like

I'm having the exact same issue with this now. Do you say you have to keep pressing the reset button but NOT the actual button? If that's the case, how do you actually do that? Because of the pressure applied I always end up pressing the button first before the reset button can be pressed, if that makes sense.

I'm assuming that's where you were getting stuck as well?

It doesn't matter that this happens. You'll notice the button led flash in a specific way when it actually pairs.

2 Likes

Yeah, I just went ape pressing everything during the pairing and initialisation process and it eventually worked...

Running C7 with 2.2.4.158.

On page /hub/zigbee/getChildAndRouteInfo see actually "nothing":
Parent child parameters
EzspGetParentChildParametersResponse [childCount=1, parentEui64=0000000000000000, parentNodeId=65535]

Child Data
No information for Child 0

Neighbor Table Entry

Route Table Entry
status:Unused

But actually two Zigbee devices in network:
image

Have some same issue ? Can reboot helps ?

Are the devices working?
If they are why worry about what is in the table.

If they are not working, do not delete the device but go into discover devices -> zigbee and then re-pair the devices.
The hub will recognise them as an existing device.

2 Likes