I am using both of these devices in a thread network with multiple border routers. No matter what I do, the FP300 refuses to directly connect to the H2 Light Switch (which acts as a router), no matter how far away from other routers and how close the two of them are, leading to weak connections. Is there any way to force this?
Hi there is your H2 switch with neutral or without?because only the switches with neutral cable can be thread border router if is without neutral then is just an matter/thread end device.
It is with neutral. For whatever reason the FP300 just refuses to directly connect to it. It always chooses some other (Thread 1.4) router, no matter how far away it is.
Well from what I see on that photos looks like the FP300 see that hue essential spot is much closer and with better signal and your Aqara switch is further then the hue device.and even if you place the sensor near to the Aqara switch it will connect to it and you place it back were you are using it at some point will reconnect again to that hue device.not so sure why do you want it to connect to the Aqara switch?if it works as it is
The FP300 and The H2 are have direct line of sight of each other and are about 2 meters apart. The Hue Light is in another room behind a brick wall. The connection seems spotty to me because of this. I use the FP300 to turn on the light on the H2 switch, which sometimes takes around 5 seconds when i enter the room. I have experimented with powering down different parts of my thread network before connecting the FP300, but no matter how many (closer) things i disconnect, the FP300 will not connect to the H2 switch and instead always seems to prefer any Thread1.4 Router before using any Thread1.3 router. I could try disconnecting everything but the H2 from the Thread network before adopting the FP300, but it still seems very strange to me that the very obviously best connection is just not chosen.
Well thread is still young so my be there are still things that need to be refined and updated by the platforms in the mean time sure see if you can turn off completely that hue device meaning to disconnect it ether from power of take it off from your matter platform this way you force the FP300 to connect or to try to connect to the H2.also it could be helpfull that after disconnecting the hue device reset the FP300 and also if you can take out his batteries for about 1/2 min then put them back and repair the FP300 and see if this way it would connect to the H2.but I do not thing that the delay is related with the FP300 is thread that sometimes could delay automations because they use same thread network.but give it a try the way I mention so by taking out the hue device the fp300 will force to pair with the H2 if you say is Almost near r to it

