NEST - FIREBASE API - Too many requests exception

Question

Hi I am controlling nest thermostat by Firebase SDK. We have big problem with Too many requests exception. I saw a few threads about that but without solution for that problem. So I would like to ask if someone managed to solve that problem?

Answer 1

From https://developer.nest.com/documentation/data-rate-limits:

To avoid errors, we recommend you limit requests to one call per minute, maximum.

From this, and from other posts on SO, I believe you can make 60 requests in any 60 minute window. But I think this is a Per Access Token limit. Nest say separately that they rate-limit writes to devices and structures - I haven't hit the write limit, but I don't do a lot of writing to the device.

Answer 2

In order to work around this limitation, I did the following:

• When the user issues a command, don't send the command to Firebase immediately; just queue it and execute it after a constant delay, D
• If the user issues another command within delay D, then de-queue the previous command and queue the most recent one.

With this strategy, the number of issues commands is at most one per D seconds.

Here is the code:

-(void) delayedSetValue:(NSArray *)valuesAndURL  {
NSDictionary *values = valuesAndURL[0];
NSString *URL = valuesAndURL[1];

if ([self.subscribedURLs objectForKey:URL]) {
    [[self.fireBi objectForKey:URL]  runTransactionBlock:^FTransactionResult *(FMutableData *currentData) {
        [currentData setValue:values];
        return [FTransactionResult successWithValue:currentData];
    } andCompletionBlock:^(NSError *error, BOOL committed, FDataSnapshot *snapshot) {
        if (error) {
            NSLog(@"Error: %@", error);
        }
    } withLocalEvents:NO];
}
}

/*
 * Sets the values for the given firebase URL.
 */
- (void)setValues:(NSDictionary *)values forURL:(NSString *)URL
{
    [NSObject cancelPreviousPerformRequestsWithTarget:self];
    NSArray *valuesAndURL = @[values, URL];
    [self performSelector:@selector(delayedSetValue:) withObject:valuesAndURL afterDelay:5.0f];
}

Answer 3

I have had a similare issue. but it was only when I authenticated too much. I had to wait for a while to get the change to authenticate again. Now i got a websocket running to get the values and that gives no problems. Setting values is the next step i am going to do. So for that i dont know how much request you can send