Context

You may encounter "gateway busy" errors when trying to unlock multiple TTLock devices, even when you have multiple gateways installed near your locks. This can happen when unlock requests are sent to different locks within a short time period.

Answer

TTLock gateways can only process one command at a time, regardless of how many gateways you have installed. When multiple locks are connected to the same TTLock gateway, sending unlock requests to different locks within a short timeframe will cause the second request to fail with a "gateway busy" error.

The TTLock API automatically determines which gateway handles each command based on signal strength, and there is no way to specify which gateway should process a particular request or bind specific locks to specific gateways.

To reduce gateway busy errors:

1. Space out unlock requests to different locks by at least 30-60 seconds when possible

2. Consider creating separate TTLock accounts for different locks to distribute them across different gateways

This is a limitation of TTLock's API architecture. The system is designed so that gateways process commands sequentially rather than in parallel, even when multiple gateways are available.