# Latency on Homey Bridge too high for decent use of (Zigbee) motion sensors? **URL:** \ **Category:** Questions & Help\ **Tags:** zigbee, homey-bridge\ **Created:** [March 31, 2023, 11:51am UTC](https://community.homey.app/t/latency-on-homey-bridge-too-high-for-decent-use-of-zigbee-motion-sensors/78700 "2023-03-31T11:51:08Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Pierre\_Van\_de\_Briel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pierre_van_de_briel/32/48231_2.png) [@Pierre\_Van\_de\_Briel](https://community.homey.app/u/Pierre_Van_de_Briel)\ **Post date:** [March 31, 2023, 11:51am UTC](https://community.homey.app/t/latency-on-homey-bridge-too-high-for-decent-use-of-zigbee-motion-sensors/78700/1 "2023-03-31T11:51:08Z")
I’ve been using the Homey Bridge since its Beta introduction, and was hoping that when it moved to ‘Production’, latency would fall to acceptable levels. The reliability increased a LOT, but latency stayed the same, of even got worse over time. I’m located in Belgium and connect to the Stuttgart DC, and when one of my Zigbee sensors see motion, it can take up to 5+ seconds for the Zigbee lamp(s) to switch on (although sometimes it’s less than 1 second so it IS possible). There can even be a time laps of several seconds between two lamps in the same zone. When you’re waiting in the dark, that’s a long time :-). Do any of you experience the same? Is the latency (as I expect) MUCH less on the Pro? ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [March 31, 2023, 12:00pm UTC](https://community.homey.app/t/latency-on-homey-bridge-too-high-for-decent-use-of-zigbee-motion-sensors/78700/2 "2023-03-31T12:00:31Z")
Are those motion sensors connected to a Hue hub by any chance? ---
**Author:** ![Pierre\_Van\_de\_Briel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pierre_van_de_briel/32/48231_2.png) [@Pierre\_Van\_de\_Briel](https://community.homey.app/u/Pierre_Van_de_Briel)\ **Post date:** [March 31, 2023, 12:41pm UTC](https://community.homey.app/t/latency-on-homey-bridge-too-high-for-decent-use-of-zigbee-motion-sensors/78700/3 "2023-03-31T12:41:45Z")
No, they’re connected either via an Innr plug or an Innr lamp (1 intermediate device only). In theory they could connect directly to the Bridge, but they prefer to take another route and I don’t think the Athom Bridge/cloud solution can force a certain connection path. I did manage to connect them directly (had to physically shield off the Innr routers with metal plates: even very close to the Bridge the Aqara sensors still preferred the Innr routers). But even then, I didn’t notice a significant differene in response time. And a few hours later, they’d left the Bridge for an Innr router again. I’m afraid that it’s the cloud solution that gives unpredictable latency, which is why I’m asking if others have the same experience. ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [March 31, 2023, 12:48pm UTC](https://community.homey.app/t/latency-on-homey-bridge-too-high-for-decent-use-of-zigbee-motion-sensors/78700/4 "2023-03-31T12:48:02Z")
It sounds like the server your “Homey” is running on is overloaded. You can test your network latency here: [https://support.homey.app/hc/en-us/articles/7494444235292](https://support.homey.app/hc/en-us/articles/7494444235292) but my guess is that this show an acceptable figure, because it will _only_ measure network latency and not how fast the server that serves your Homey will process requests. Homey Pro, being a local solution, will very likely be much faster. ---
**Author:** ![Pierre\_Van\_de\_Briel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pierre_van_de_briel/32/48231_2.png) [@Pierre\_Van\_de\_Briel](https://community.homey.app/u/Pierre_Van_de_Briel)\ **Post date:** [March 31, 2023, 1:17pm UTC](https://community.homey.app/t/latency-on-homey-bridge-too-high-for-decent-use-of-zigbee-motion-sensors/78700/5 "2023-03-31T13:17:06Z")
You’re right, I shoudn’t have used the term ‘latency’ which typically refers to the network only, which is not so bad (around 37ms, measured on different occasions in the past). I meant ‘total response time’, which is - in best cases - just below 1s and often way higher. But if it’s the DC server, I’m not sure that I’ll find a ‘Service Level Description’ to rely on 🙂 In that case, the bridge/cloud solution is perfect for temperature/humidity… sensors or flows based on time events (e.g. switch on lights at sunset, …) , but not ideal for motion sensors that require a very quick response. ---
**Author:** ![Vnet](https://avatars.discourse-cdn.com/v4/letter/v/d78d45/32.png) [@Vnet](https://community.homey.app/u/Vnet)\ **Post date:** [March 31, 2023, 6:03pm UTC](https://community.homey.app/t/latency-on-homey-bridge-too-high-for-decent-use-of-zigbee-motion-sensors/78700/6 "2023-03-31T18:03:10Z")
It depends how the docker platform is configured in aws. If they use docker swarm with enough nodes (and powerful vm’s) or paas. Only then you can tell. My latency to main account hosted on aws frankfurt is 23ms, to my other account in london is 27ms. Everything reacts very quick