Upgraded from 2023.12.4 to 2024.1.2 this morning. Initially, everything looks fine and my normal checks when upgrading to a new HA version checked out. I merrily went on my way thinking that all was good.
A couple of hours later, I made a minor mod to a NodeRed flow, and I got an error when deploying - “No server response” or something of that ilk. Then I get ensuing prompts about server flows having changed and merging, etc. and then into an infinite loop of attempting to deploy those changes, getting the error, and so on.
After a lot of troubleshooting, long story short, syslog on the NodeRed server was showing the following error:-
node red [error] UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "3".
Initially I blamed my OAuth provider (due to the use of the term ‘promise’ in the error) but eliminated that by bypassing authentication and still got the error. It then dawned upon me that a significant change I had made was the HA 2024.1 upgrade, so I restored from backup. Magically, everything came good again under 2023.12.4.
Now, before I go upgrading HA again and breaking it again, has anyone come across this issue?
Environment:
- All nodes running under Proxmox 6.5.11-7-pve
- HA is a Proxmox VM running HAOS (supported configuration)
- Standalone (i.e. not using the HA addon) NodeRed v3.1.3 on a spearate Proxmox LXC running Ubuntu 22.04.3 LTS
- node-red-contrib-home-assistant-websocket version 0.62.2
HA Node Red companion version 3.1.3
Searching for reports of others having a similar issue has come up blank.