hassio-addons/addon-node-red

Entity could not be found in cache #544

hendmele posted onGitHub

Problem/Motivation

NodeRed giving error 'Entity could not be found in cache for entity_id: switch.whatever"'. Error just happens right after deploying. If I wait for around 10 seconds, problem goes away.

It seems to be the same as issue #195 and the same as here, that appears to be solved by a user. https://github.com/Spartan-II-117/node-red-contrib-home-assistant-llat/issues/34

Expected behavior

Flow to work

Actual behavior

Flow stopped

Steps to reproduce

Just put a injection node, some get state node, a debug message, deploy and inject data right after deploy.


:wave: Thanks for opening your first issue here! If you're reporting a :bug: bug, please make sure you include steps to reproduce it. Also, logs, error messages and information about your hardware might be useful.

posted by addons-assistant[bot] about 5 years ago

The addon wraps the existing applications, you would likely be better raising your issue at https://github.com/zachowj/node-red-contrib-home-assistant-websocket

<blockquote><img src="https://avatars2.githubusercontent.com/u/37859597?s=400&v=4" width="48" align="right"><div><img src="https://github.githubassets.com/favicons/favicon.svg" height="14"> GitHub</div><div><strong><a href="https://github.com/zachowj/node-red-contrib-home-assistant-websocket">zachowj/node-red-contrib-home-assistant-websocket</a></strong></div><div>Node-RED integration with Home Assistant Core. Contribute to zachowj/node-red-contrib-home-assistant-websocket development by creating an account on GitHub.</div></blockquote>

posted by sinclairpaul about 5 years ago

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.

posted by addons-assistant[bot] almost 5 years ago

Fund this Issue

$0.00
Funded

Pull requests