Node-RED communication BLOCKED when an update(s) waiting.

The problem

When update waiting, Node-RED communication blocked. I’m telling you the problem occur when updates WAITING not by auto-update. (do not know which update waiting exactly) This is not recent problem but over years. There is none of network and communication issue at all. its Home assistant problem. The reason why now reporting you is that no one care about old core issue that make 24 hours system damage.

An also telling you that, do STOP shitty almost daily update this is home automation operating system, not your toy that update fun. Do professionally open and distribute new update by monthly or quarterly.

Symptom.

• When the ‘Core’ update waiting, Node-RED’s all TCP communication blocked.
• So node red not working. no commend out to Tasmotas and not responding to Alexa.
• After while passes with update waiting, sometime everythings working even though there is update waiting.

What version of Home Assistant Core has the issue?

Every version within 1 year past at least. recently 22.7.x, 22.8.x

What was the last working version of Home Assistant Core?

2022.8.6

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

let me know how to.

Example YAML snippet

No response

Anything in the logs that might be useful for us?

let me know how to.

Additional information

No response

[Mitchell-kw-Lee]

Fir of all, VERY DISAPPOINTED at your responses.

For the record, to the all user of home assistant.

• The problem of this issue from the AWS account of the nabucasa(?) which contain the Alexa skill to link your monthly pay service with each HA pay account. not users. Your organization’s obligation that you simply ignore.
• Totally do not believe your level of understanding of the own organization’s technology that too low.
• This was the good chance to glimpse level of the member of the technical understanding of a core founder of the pay service. No doubt that this is an armature gathering(nabucasa? is that a starwars thing?) have no professionalism.

For the record, to you.

• This issue came from the ‘core’ part by transferring one who in charge or the core. But you can’t/don’t do the same thing to be transferred back. Why you don’t have the authority? Your personal problem?
• No professionals say, ‘not our obligation’ or ‘this is not my issue’ or ‘you customer find other right person yourself’ on a group of paying service who taking MONEY from consumer. As for free service, also no professional do that.

And thank you to remind me that no reason to pay due to this group just doing what they feel fun by taking money from outside. Have no find any higher level of purpose.

FYI, self AWS Skill implementation if way cheaper than your monthly $6.5 pay include issuing 10 years certification. So long.

[mdegat01]

Ok. It seems like at this point this isn’t a supervisor issue. If you have an issue with the cloud service you can create a ticket here. If you have an issue with the way the Alexa integration works you can create an issue or PR for that here. This repo is only about supervisor issues, so it appears to be in the wrong place.

I will note that I just searched core issues and I see zero reports of THROTTLING_EXCEPTION. So I don’t actually believe that anything is systemically wrong with the way it is working otherwise there would be a lot more issues. If you have proof showing otherwise then please lay it out in an issue there. Nothing you’re showing me above suggests that to me currently.

As for the cloud service limits, you’re more then welcome to request an increase. That being said, there is no obligation for Nabu Casa to do so. The limits are set based on the price of the service. If you are blowing through them then you’ll either need to add some throttling by exposing less entities or different entities or switch to the manual Alexa mode as documented in the Integration and pay Amazon based on usage.