Daily crash of addon #1451
Comments
|
To narrow down the process.on('unhandledRejection', (reason, p) => {
console.log('Unhandled Rejection: ', p, 'reason:', reason);
});Secondly, you can connect directly to Node-RED and not through the Home Assistant proxy. https://zachowj.github.io/node-red-contrib-home-assistant-websocket/guide/#configuration |
|
Thank you for getting back to me... QQ though re: your request... how do I make this change to node-red given its running as a container as an add-on? Wont any change be lost as soon as I restart the process?
…-John
On Jul 27, 2024, at 9:04 PM, Jason ***@***.***> wrote:
To narrow down the UnhandledPromiseRejection can you add the following code to your settings.js file to help capture a better description of the error? This can removed once the error happens.
process.on('unhandledRejection', (reason, p) => {
console.log('Unhandled Rejection: ', p, 'reason:', reason);
});
Secondly, you can connect directly to Node-RED and not through the Home Assistant proxy. https://zachowj.github.io/node-red-contrib-home-assistant-websocket/guide/#configuration
—
Reply to this email directly, view it on GitHub <#1451 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAOG6QDOXKONK6TE35RVDLZOQ7QVAVCNFSM6AAAAABLSEZHAGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJUGMYDAMRYGU>.
You are receiving this because you authored the thread.
|
|
Actually I think I found it in ~/addon_configs/a0d7b954_nodered here is the file after editing, I assume this is at the right scope within this module ? process.on('unhandledRejection', (reason, p) => {
console.log('Unhandled Rejection: ', p, 'reason:', reason);
});
module.exports = {
mqttReconnectTime: 15000,
serialReconnectTime: 15000,
functionGlobalContext: {
// os:require('os'),
// jfive:require("johnny-five"),
// j5board:require("johnny-five").Board({repl:false})
},
paletteCategories: [
"home_assistant",
"subflows",
"common",
"function",
"network",
"sequence",
"parser",
"storage",
],
logging: {
console: {
metrics: false,
audit: false,
},
},
editorTheme: {
projects: {
enabled: false,
},
},
}; |
correct |
|
Have you narrowed it down? I am experiencing the same connection lost error everyday at the same time. |
|
I managed to fix it, not sure if the core problem is the same for everyone. I used to access Home Assistant only through my public domain and public IP address. That IP address was internally routed back to my server without leaving the local network. Still, the IP changed every night. It seems that node-red doesn't get notifiied or doesn't act upon losing connection with Home Assistant that way. Only once an automation later on actiively tries to reach Home Assistant (for me my wake-up automation), does node-red get an error communicating with Home Assistant. On the next request, node-red will connect to the correct IP again. I solved it by setting up a local PKI with self-signed root certificate and connecting node-red to Home Assistant via a local domain and IP address instead. Hope this helps. |
This comment was marked as off-topic.
This comment was marked as off-topic.
Describe the bug
About once a day the add-on crashes and the watchdog doesn't seem to trigger a restart, seems to have started w/ Home Assistant: 2024.07.00
To Reproduce
Start it, wait and watch for crash
Expected behavior
Crashes to not happen daily
Screenshots
No response
Example Flow
No response
Environment Information
Node-Red Addon - : 18.0.4
HassOS: 2024-07-03
Supervisor: 2024.07.00
Additional context
Supervisor logs
Forked from hassio-addons/addon-node-red#1917
The text was updated successfully, but these errors were encountered: