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

Invalid warning message that custom integration needs to be installed #15

Closed
declanshanaghy opened this issue Mar 3, 2020 · 10 comments
Closed

Comments

@declanshanaghy
Copy link

declanshanaghy commented Mar 3, 2020

Version of the custom_component:

v0.4.1

Describe the bug

I have some binary_sensors in my flows that generate the following warning message upon every deploy.

Node-RED custom integration needs to be installed in Home Assistant for this node to function correctly.

They all work fine, but this warning clutters the debug window.

See screenshot
Within the screenshot 2 sensor nodes are visible. The warning is printed by one of them but not the other. There is also a warning from another sensor node that is off screen.

@declanshanaghy
Copy link
Author

For some reason this warning has now stopped appearing for the sensors shown in that screenshot. However, it is now appearing for a new sensor I just added. It also appears to be preventing that sensor from setting it's state correctly.

@steveneon
Copy link

i have this issue as well same as above.

@markozekic
Copy link

Me too :-).

@zachowj
Copy link
Owner

zachowj commented Mar 26, 2020

@declanshanaghy @steveneon @markozekic What do you have your deploy method set to?

image

If the server config node has to reestablish connection every time you deploy this can cause the issue. Full will always restart the connection and Modified Flows will sometime restart the connection.

@declanshanaghy
Copy link
Author

I had it set to Full. The issue isn't happening at the moment.
I changed to Modified Nodes and will keep an eye out for it.

Thx

@cjramseyer
Copy link

cjramseyer commented Mar 30, 2020

I have this (v0.4.1) installed on two different instances of HA.
One instance is showing the same error, though it has already been added through integrations.
The other instance does not show this message. Both instances of HA have been restarted

@Jpsy
Copy link

Jpsy commented May 5, 2020

I had dozens of these msgs on every deploy. Setting the deploy method to "Modified Nodes" solved the problem at hand. But shouldn't this warning be issued only if no connection could be established.

@zachowj
Copy link
Owner

zachowj commented May 6, 2020

@Jpsy When you do a Full Deploy it also reinitializes the configuration node which is the node that controls the connection to HA. When the HA nodes all reinitialize, the connection to HA could be in several different states. If it hasn't connected and read the HA config to check if the custom component has been installed you will get the error.

@Jpsy
Copy link

Jpsy commented May 10, 2020

Thanks @zachowj, so this is basically a kind of race condition. Is there something I can do to change my config node so that the HA connection is reliably started first?

@gitolicious
Copy link

For me the message was shown when I added the HA component but ignored the last step:

In the HA UI go to "Configuration" -> "Integrations" click "+" and search for "Node-RED"

Just in case someone else stumbles upon the same...

@zachowj zachowj closed this as completed Jun 17, 2020
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

7 participants