That’s not how it works.
And athom just closed my ticket saying that it has been resolved. Not.
Well, in the mean time i made my hue system primary, all zigbee to homey wall switches replaced with hue switches. Homey is only for automations by sending scene requests, but for manual operation, hue is primary controlling the lights. Family is happy now. For now i use hue timers but i have to see where to put the light automations. I guess thst homey cloud will be exit. Will be My 2019 pro or ha. Both are for the moment testing thingy’s
Samma för mig. Funkar fortfarande inte.
Still not working.
Fantastic that his has not been corrected yet
Same issue, Please inform when resolved its bloking all my light System. Thanks
We’ve followed up with Signify about this issue. They mentioned increasing the rate limits, but we now suspect that their systems may have preemptively blocklisted certain IPs to manage traffic.
We’ll keep you updated!
Same here
Hue cloud is build on google cloud. On the diagram, homey is connecting to hue cloud api. (Which might be the google api gateway) I assume that the rate limiting is happening there as the api gateway can be configured with quota’s linked to the client (=homey) Can imagine that the change process has a certain leadtime. And then the changes may be replicated over the different geographic zones
It’s not solved yet. Where can I report the problem? If everyone reports it, it should be raised as a higher priority.
And @doekse can be right in blacklisting of Homey IP’s can be the issue now. Many cloud vendors implement protection against brute force, and one of the ways is to blacklist.
If this is the case, then we can only hope that Homey and Signify can agree on whitelisting instead.
I expect everyone at Signify is enjoying their weekend! I’ll update the thread on Monday if it isn’t fixed by then.
I guess I should’ve just got an Apple TV as a HomeKit hub instead. Cancelling the subscription for now. Might use it for five 433 MHz devices, but that’s all.
Seems not, late Sunday and Rate Limited are still hitting back ![]()
I have the same issue since about a week. I discovered that very early about 3 o clock in the morning, the system suddenly works in the toilet. The question is how long it will take Homey to repair the app??
Sooo all my light sources has been reimported now, still half of them are “inaccessible”. Will wait and see if that change - so were some of the way. ![]()
Do you need to reinstall the app and all lights for it to work again ?
I’ve just sent another email to my contact at Signify to gain a clearer understanding of the issue. In the meantime, some users have reported that disconnecting their Hue Bridge from power, reconnecting it, and then restarting the HUE app on Homey resolved the issue for them.
Keep you all posted!
How do you restart the Homey app on Homey?
More → Apps → Phillips Hue App → Cog icon in the top right → Restart App
I don’t think so, I removed and reinstalled the app during the early days to check if it fixed something.
