Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Entity could not be found in cache for entity_id: #112

Open
RestOp opened this issue Jul 22, 2020 · 2 comments
Open

Entity could not be found in cache for entity_id: #112

RestOp opened this issue Jul 22, 2020 · 2 comments

Comments

@RestOp
Copy link

RestOp commented Jul 22, 2020

Hello,

After full deploying or restart of NR or full system i get this error - Entity could not be found in cache for entity_id.
Here is the screenshot.
image

I understand that the node starts to work before NR connected to HA server.
But it it the greatest BUG i have ever seen! In this case NR and HA become unusable.

Simple example from screenshot: on the restart of system (because of turning off electricity or other reason) i need to listen to light sensor and set correct time of day and then use this time of day in all my other flows. I do not get it or get incorrect one and all other flows uses this incorrect value. What does it mean i think you understand... My HA becomes unsusable.

Last NR 7.0
HA 0.112.4 in Docker
But it does not matter, i see this error already more the half a year on different versions.

@walthowd
Copy link

This project is abandoned. You should switch over to the maintained web socket version:

https://zachowj.github.io/node-red-contrib-home-assistant-websocket/guide/

@RestOp
Copy link
Author

RestOp commented Jul 22, 2020

Thanks a lot, i made it.
Now it connects to HA not in 5 sec, but in 0.5
But the problem stays the same.
Please reopen issue.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants