You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to help people who keep posting "issues" when they see ECONNRESET messages in the log.
The Internet is not a 100% reliable data transport mechanism. Between your computer and a server many thousands of miles away, sometimes a connection gets dropped. When this happens on the Google/Nest end, you'll get an ECONNRESET message in the Homebridge log.
If this happens, the plug-in (like any non-junk network software) will simply reconnect. You won't know that anything has happened.
Occasional ECONNRESET messages are useful for debugging if other things are going wrong, but they do not mean anything is wrong. If you get ECONNRESET messages it is not a bug, or an issue, and does not impact the performance of the plug-in in any way. There is no need to report an issue on GitHub if you see ECONNRESET messages.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Would it be possible to add a feature to suppress these error messages? This happens to mine dozens of times a day and it makes reviewing the rest of the logs very difficult.
Trying to help people who keep posting "issues" when they see ECONNRESET messages in the log.
The Internet is not a 100% reliable data transport mechanism. Between your computer and a server many thousands of miles away, sometimes a connection gets dropped. When this happens on the Google/Nest end, you'll get an ECONNRESET message in the Homebridge log.
If this happens, the plug-in (like any non-junk network software) will simply reconnect. You won't know that anything has happened.
Occasional ECONNRESET messages are useful for debugging if other things are going wrong, but they do not mean anything is wrong. If you get ECONNRESET messages it is not a bug, or an issue, and does not impact the performance of the plug-in in any way. There is no need to report an issue on GitHub if you see ECONNRESET messages.
The text was updated successfully, but these errors were encountered: