Problem/Motivation

After upgrade to 9.1.0 errors show in the log and Node Red no longer loads Home Assistant states. See error log below.

Expected behavior

Node Red logs show no errors and nodes that access HA data function correctly

Actual behavior

Debug errors are shown in Node Red stating entity cannot be found in cache

Steps to reproduce

Running correctly with Node Red 9.0.1 add-on, upgrade to 9.1.0, errors are shown and HA access fails Host reboot is required after snapshot restore to return to correct functioning

Proposed changes

n/a

System Health

version	core-2021.5.5
installation_type	Home Assistant Supervised
dev	false
hassio	true
docker	true
virtualenv	false
python_version	3.8.9
os_name	Linux
os_version	5.10.17-v7l+
arch	armv7l
timezone	Europe/London

Home Assistant Community Store

GitHub API	ok
Github API Calls Remaining	4944
Installed Version	1.12.3
Stage	running
Available Repositories	885
Installed Repositories	8

Home Assistant Supervisor

host_os	Raspbian GNU/Linux 10 (buster)
update_channel	stable
supervisor_version	supervisor-2021.04.3
docker_version	20.10.6
disk_total	29.0 GB
disk_used	11.8 GB
healthy	true
supported	failed to load: Unsupported
supervisor_api	ok
version_api	ok
installed_addons	File editor (5.3.1), SSH & Web Terminal (8.2.1), Node-RED (9.0.1), Dropbox Sync (1.3.0), Portainer (1.5.0), Nginx Proxy Manager (0.11.0), MariaDB (2.3.0)

Lovelace

dashboards	1
resources	4
views	2
mode	storage

Error log

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Add-on: Node-RED
 Flow-based programming for the Internet of Things
-----------------------------------------------------------
 Add-on version: 9.1.0
 You are running the latest version of this add-on.
 System: Raspbian GNU/Linux 10 (buster)  (armv7 / raspberrypi3)
 Home Assistant Core: 2021.5.5
 Home Assistant Supervisor: 2021.04.3
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to WARNING
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] customizations.sh: executing... 
npm WARN deprecated xmldom@0.1.31: Deprecated due to CVE-2021-21366 resolved in 0.5.0
> ejs@2.7.4 postinstall /opt/node_modules/ejs
> node ./postinstall.js
Thank you for installing EJS: built with the Jake JavaScript build tool (https://jakejs.com/)
+ node-red-contrib-ical-events@0.23.0
+ node-red-contrib-gc-trigger@0.0.1
+ node-red-contrib-combine@1.8.1
+ node-red-contrib-advanced-ping@1.2.0
+ luxon@1.27.0
+ rrule@2.6.4
added 21 packages from 41 contributors, updated 1 package and audited 1216 packages in 29.977s
96 packages are looking for funding
  run `npm fund` for details
found 6 vulnerabilities (2 low, 3 moderate, 1 high)
  run `npm audit fix` to fix them, or `npm audit` for details
[cont-init.d] customizations.sh: exited 0.
[cont-init.d] nginx.sh: executing... 
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] node-red.sh: executing... 
patching file nodes/ui_base.html
Hunk #1 succeeded at 1160 (offset 629 lines).
up to date in 0.79s
found 0 vulnerabilities
[cont-init.d] node-red.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
> addon-node-red@ start /opt
> node $NODE_OPTIONS node_modules/node-red/red.js "--settings" "/etc/node-red/config.js"
20 May 13:16:12 - [warn] Projects disabled : editorTheme.projects.enabled=false
(node:525) UnhandledPromiseRejectionWarning: #<Object>
(Use `node --trace-warnings ...` to show where the warning was created)
(node:525) UnhandledPromiseRejectionWarning: Unhandled promise rejection. 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(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 55)
(node:525) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
20 May 13:16:23 - [error] [api-current-state:On ?] Entity could not be found in cache for entity_id: input_boolean.booking