In future we may try to be a bit smarter about which lock is connected to which gateway and throttle per gateway, but since the TTLock API makes it clear that locks can move between gateways and that fetching this data is in itself a request to the gateway I don't think that will be particularly easy to get right.
In future we may try to be a bit smarter about which lock is connected to which gateway and throttle per gateway, but since the TTLock API makes it clear that locks can move between gateways and that fetching this data is in itself a request to the gateway I don't think that will be particularly easy to get right.
Hopefully fixes #34