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

connect ETIMEDOUT error #50

Open
janstepanekcz opened this issue May 3, 2024 · 5 comments
Open

connect ETIMEDOUT error #50

janstepanekcz opened this issue May 3, 2024 · 5 comments

Comments

@janstepanekcz
Copy link

Hello I was using esphome nodes to control water heater settings for almost one year till today. Now I am getting error in title. No entities are available anymore.
etimedout_error

No changes were done before this poped up. Esphome device is up and runnning, available in HomeAssistant, running its web page but not available in nodered.

Till now after issue appeared I restarted node red, restarted esphome device, updated node-red-contrib-esphome to latest version, removed all esphome nodes and uninstalled node-red-contrib-esphome and installed again all without any positive efect.

Do you have any hint what to check?

@twocolors
Copy link
Owner

check ip address of esp?
if you have HA, i recommended use HA for control esphome dev

@janstepanekcz
Copy link
Author

IP adress of my ESP device is unchanged. The reason to use nodered instead of Home assistant is that it is running on Victron Cerbo SGX. I wanted to eliminate another machine (HA) from the chain of devices. Main function is to provide priority relay to prevent overload of my inverter and few other features.

Yesterday it became back up after restarting mqtt broker on Cerbo. But the issue is now back again.

@janstepanekcz
Copy link
Author

I am thining if it is not an issue with too many request to esp device...

@twocolors
Copy link
Owner

you use native api and mqtt ?

@janstepanekcz
Copy link
Author

I was not sure and had to check. No the esp home device is configured to use only api no mqtt.

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