I have a presence sensor FP300 which was connected to my main Hub M3, working just fine, but with weak signal because they’re far apart. So I got a Hub M200 to place in the upper floor and have better Zigbee coverage, and connected the sensor to it (signal now shows as “strong”).
The sensor reports now very badly, most of the times taking many minutes to show presence/absence or big changes in luminosity. Obviously this makes this sensor unusable, because the point of it is to turn on/off lights based on presence and luminosity.
I’ve tried tweaking everything possible, I had reset it, re-paired, changed protocol back and forth to Thread, etc, etc, you name it. Nothing helps. It still reports instantly to the M3, but not to the M200, which is literally 1 metre away from the sensor.
Any ideas or similar experiences?
Thanks!
Hi there, it looks like you’re experiencing a support-related issue. We’ve automatically created a support ticket for you and will reach out via the forum email within the next two business days.
If other members have any suggestions or insights on this topic, feel free to share!
Hi.you could just add an smart plug from Aqara to make the bridge between the sensor and M3 hub less expensive and will still be using the M3 hub.now with M2 did you made an factory reset to the FP300 or you just reset it to pair it with the M200?after the reset unplug the M200 for 1min from the power then plug it back and pair the FP300 on his final destinación place meaning were you want to use it.see if that works.
Thanks for the prompt reply! Unfortunately a plug is not viable for me because I don’t have an electrical outlet on the staircase separating the FP300 and the M3, so there’s no “in-between”.
And, yes, I performed a factory reset, actually on both the FP300 and on the new hub M200… nothing of that helped…
Well the only thing I can think right now is to take out the batteries from the FP300 to clear his cache because you have pairing it as zigbee and then thread and my be there are some conflicts right now that make the sensor to not recognize well the automation you made.sow take the batteries out for an min or two and try it again.also you should contact Aqara support if you still have the same issue as my be the M200 could be the problem also see if the M3 is the cluster and shows the M200 like this check on M3 this
Here you need to see your M200 as an secondary hub
Thanks again,
Yes, the M3 is the leader and the M200 is one of the secondary devices.
I’d say the issue is on the M200, because it’s just fine on the M3. I can of course try removing the batteries of the FP300 but factory resetting it would have cleared the cache as well…
I didn’t ask what power supply do you have on M3 and M200?my be is the power supply that is not giving it to much power and that is why is make the zigbee connection slower or broken.you need to add on M200 an adapter from 10v or more to be sure it gets the amount of power it needs
10v? Hmmm I doubt that. The manual says 5v 2A…
Sure but an 10v or more is better as the M200 only takes what it needs it won’t take 10v but will be more stable.my M3 is power by an apple charger 20w and it works perfectly but make sure to be an quality one not an cheap adaptor.if you have an apple charger and an type C cable try it and see as it should improve the stability and the FP300 should work better
Thanks. Yes it is already on an apple 5v/9v. Unfortunately that’s not the origin of the problem
OK well did you try taking out the batteries and let it without a few min?as if doesn’t work ether I recommend contact Aqara support and tell them your issue as they can investigate better why is not working well with M200
By the way also take out the M3 from the power for 1min as well to clear his cache as well as my be the M3 also have saved the connection with the M3 on his memory and could send false signal to the FP300.to try you do not loose nothing.but you couldn’t move a bit closer the M3 to the FP300 ether?
Well I could but it’s not any cache in the FP300 since it works perfect on the M3 and has been factory reset many times
I cannot move the FP300 closer to the MP3. If I could I would have avoided buying an M200.
At this point I’m considering returning the M200 for a refund.
Well that is an option but I was referring to move the M3 a bit closer if you can not the sensor but I forget to mention that if you same some light on the stairs you could check a bulb as that could also work as bridge between M3 and sensor.
Thanks. No that’s not possible. The m3 is in the cabinet next to the modem and router. There’s no other place. And I use lights embedded on the ceiling that already have a particular setup.
My option is to have a functioning M200, that’s what I’m trying to solve in this topic that I created, and I simply want the M200 to do what’s supposed to do.
For an extra piece of information: it takes 3, 4 or 5 presses of the FP300 button to get the message from the hub “connection stable”. It’s like the hub has to be awaken.
Well then there is nothing else to try out.did you pair it back to M3 hub?also didn’t asked if you check if there is no update for M200 or FP300?
Of course there’s no update…
Well… maybe some other user with a similar experience to mine or someone from Aqara could help?
My be you got an faulty M200 I suggest you to get an replacement see if with another new one will work or will be the same.