When using a “notification” to send a message to a mobile phone I now get “rate_limited” error.
The simplest root cause I can think of is that I overloaded a kind of message buffer due to a mistake in another script, that has sent 99 messages to my mobile phone at night. It looks like this message buffer has a max of 99, since that it didn’t send more and I would have expected so now that I know the mistake in the related script.
Now my questions are:
Yes (although the message buffer might be larger than 99 slots but the rate limiting kicks in when that amount of messages is being pushed within a short amount of time).
I don’t think you can.
The question is where the rate limiting occurs. As far as I know, push services for both iOS and Android don’t have rate limiting, so perhaps Athom imposes the rate limiting itself (or Athom uses a third-party service to deliver notifications and that service is rate limiting). It might be worthwhile to ask Athom about it, perhaps they can do some magic and clear the buffer.
Thanks for your answer Robert.
Good news. I think the situation is automatically reset after 24 hrs, I have received pushed messages again. So my problem is solved
I’m having the same problem with motion detectors sending push notifications to my Samsung S20.
I recently purchased a Dio Outdoor Motion Detector Ref. 54744, wireless on batteries. Worked great to start something (i.e. a light) and send push notifications on my phone.
So I purchased 3 more for the other sides of the house and shortly I wouldn’t get the notifications even though the rest (i.e. light) would work and movements would be logged.
Looking in the flows, I noticed the “rate_limited” error.
Restarting Homey solved the issue.
But trying to avoid the overflow in the future, I’m now testing with a delay between the notifications. So, if there’s continuous movement somewhere, I get 1 notification the nothing for XX seconds. Crossing fingers, future will tell
Hi all,
Since more than a day I receive a ‘Rate Limited’ error message on the Home screen of my Homey Android App. I can still go to ‘Devices’, ‘Flow’, ‘More’ but when selecting ‘Home’ I keep getting the ‘Rate Limited’ error message.
Checked the Homey Android app on my tablet but it also gives the same error
Removed all messages on my timeline
The error mesage would suggest that a large amount of messages are being send at a short amount of time. However, both the timeline and SimpleLog doesn’t show any large amount of messages being send.
Okay, this is strange: I just wanted to logoff from my tablet when I noticed that both my tablet and my phone are working again (on my account)!
Maybe beceause I now powered off my Homey for a few minutes, but I did several restarts before without any succes. Anyway, I will keep an eye on it and let it know when the error returns. Fingers crossed it won’t come back
Thanks @Dijker for your help. I appreciate it a lot!
I have send a ticket to Athom and got a response the same day (thank you Athom!). Strangly, the Rate Limited error seems to come from apps requesting the weather forecast. I have several weather-related apps. Most likely, some of these apps are requesting the weather forecast using the same API which is causing the error.
I am disabling or removing weather-related apps one by one to find the root cause. This won’t be easy as the error does not disappear immediately and I have to wait days to see if the error will return or not. So fingers crossed.
Homey is a waste of money. All I get is errors, rate limited on something that worked fine connected directly to Alexa. I wish support would stop making excuses and fix the issue. I’m deleting my account and going back to Amazon. At least with Amazon, I don’t get ‘rate limited’.
So, okay, you took the time and energy to create an account here, only to let us know about your plans with Bezos?
This is just a users forum, so all in all a pretty pointless post imho.
Anyways, have fun with Alexa, say hi to her.
In experimentals there is a flow restart homeyPro. I used that flow to restart. After that i got the same error: rate_limited.
Then i restarted my Internet Browser. ( Chrome ) and it works again.
