unhandled error: HTTP response (429 Rate exceeded.) about node-red-contrib-smartnora

[andrei-tatar]

That's a weird one. I'll check the logs. This is definitely NORA.
Do you know the time it happened (with time zone)?
Did it go away after some time?

[andrei-tatar]

ok, checking the logs revealed a weird issue. It seems that everyone disconnected from firebase at around the same time (probably some Google maintenance thing) and everyone connected back at the exact same time, flooding the backend with sync requests.

It seems to have recovered pretty quick after that.

I definitely need to spread out the 1st sync call after the connect. I wasn't aware this might happen.

[andrei-tatar]

Found a bug: after a failure, the retry doesn't really work and just shows the same error message over, and over.
This is also related to #17

[FireWizard52]

Hello Andrei,

You already found the cause, but to answer the questions:

When I created this issue, the issue was present, so it was approx 19:00 h CET (Timezone Amsterdam).
I think it last about half an hour?
I had it on one machine, but didn't see it on my production machine.
On my test device, I disabled the flow in order to get rid of all the debug messages. So I'm not sure when it returned.
It is okay at the moment.

Regards

[andrei-tatar]

@FireWizard52 I published v1.0.5 that addresses this issue:
https://github.com/andrei-tatar/node-red-contrib-smartnora/releases/tag/v1.0.5

Summary:

• firebase disconnected lots of users at the same time and they all connected again at the same time (few seconds later)
• some sync calls failed (the 429 status code) because of the load (some hundreds of requests in a few milliseconds)
• the retry didn't really work prior to this fix

I will close this bug for now.