Serial port crash on startup with 11.0.4 on ARM #1312
Comments
|
Try the safe_mode option https://github.com/hassio-addons/addon-node-red/blob/main/node-red/DOCS.md#option-safe_mode Enable the flows one at a time to see the issue. There is nothing in the logs showing which palette has the issue. |
|
I have enabled it and am currently trying to get a trace, but so far I haven't managed to deploy a single node without it crashing instantly. I only deploy a single "debug" node and have my NodeRED set to "only deploy modified nodes" and it crashes, not even anything connected to it. And that is even if the debug node is on its entirely own, blank sheet/tab |
|
@sinclairpaul I figured it out. It is my serial port node (in "Global configuration nodes"). Disabling it makes everything work, enable it and deploy just it and it instantly crashes. In fact, serial seems very broken, trying to list serial ports in Node-RED (11.0.4) just yields |
|
Well as per the release notes So would suggest seeking assistance upstream with it |
|
@sinclairpaul I think I figured out the issue. node-red-node-serialport 1.0.1 depends on serialport 10.x ( node-red/node-red-nodes@184140b#diff-b170e7f896b0acc0bae251b22b9698ba3a0024021bd6df14c972ee82e952392aL6 ) serialprot inside the nodered container for HA is, however, 9.2.8 Is the package installation also upstream or not? |
|
Nope the dependencies should be handled by the build, we would need to look as to why it's not updated. |
|
The more I investigate, the weirder this one gets. |
|
|
|
Found the probable actual cause this time: serialport/node-serialport#2438 |
|
I think it's fair to say it's an upstream challenge, will leave this open for now for tracking. |
|
Agreed. But for sure keep this open so people who find their 11.0.4 crashing. From this it seems like everyone who uses a serial port and is using an ARM-based device will be affected. |
Yes and, Why not to edit the topic? (... due to Serial incompatibilities). I'v got the same problem and roll back to 11.0.3. I'm using Serial to receive ESPNow coms... Thanks @Doridian |
Doridian
changed the title
|
Hi there, Having the same issue tried to upgrade the I'm locking my hassio node-red version to 11.0.3 and node-red-node-serialport 0.15.0 waiting for a better integration between those version. Regards PS : I have no other idea for avoiding the issue. |
|
Hi, Regarding the regurlarly crash of Node-Red addon in case of serial connection. |
|
how to downgrade from 11.0.4 to 11.0.3 ? |
|
Hi, I'd also like to find out how to roll back to 11.0.3 without a backup. |
|
Hi, me also i have the same problem, more i have update to 11.0.4 version Node Red i have an odroid N2 with homeassistant |
|
My Log here :
|
|
@jonvelle Until it is fixed upstream, there is nothing we can do here. Assuming you don't have a snapshot available to restore (which please do in future, the UI prompts you to create one), you may be able to rename your /config/node-red/flows.json, and restart the addon. This will remove all your flows, however you can copy/import them one by one from the original file. |
|
hi, no need to lost all your flows :)
stop nodered
edit flows.json in config/node-red/
go to the right and clic 'clic to see more' , the text is reformatted
now , on the top , you can see like this :
[{"id":"4ad9b255140e2b36","type":"tab","label":"Gestion des
volets","disabled":false,"info":"","env":[]},{"id":"55517bd7c08cc0a1","type":"tab","label":"Linky","disabled":true,"info":"","env":[]},
juste change false to true (after the disabled:) for the flow with the USB
, save and restart nodered .
Le mar. 8 mars 2022 à 01:21, Paul Sinclair ***@***.***> a
écrit :
… @jonvelle <https://github.com/jonvelle> Until it is fixed upstream, there
is nothing we can do here.
Assuming you don't have a snapshot available to restore (which please do
in future, the UI prompts you to create one), you may be able to rename
your /config/node-red/flows.json, and restart the addon. This will remove
all your flows, however you can copy/import them one by one from the
original file.
—
Reply to this email directly, view it on GitHub
<#1312 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHBIBLUXPEIGKBIS4DGIWZTU62MR7ANCNFSM5PSQSLLQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Hi, Have somebody with Serial node tested the 11.1.0? Thanks! |
|
No i don't have updated to 11.1.0 but i have downgraded to 11.0.3 and my system is worked now. |
Yes, same in my side... Waiting for good news. |
I have tested 11.1.0 but the same issue i have downgraded to 11.0.3 after and back normal |
Thanks! This save a lot of time to me. |
|
I confirm too. |
|
Same for me as Ayrton31 description |
|
Any idea about a resolution date, extremely frustration to not be able to monitor my electric consumption since almost 2 weeks due to this Node Red crash when using serial object ? |
For me the solution was to roll back to 11.0.3 and everything is working. I can´t unplug the USB to serial module because there are automations running through... |
Could you help me on that please. |
First of all I'm using HA over a Rpi, so every update was preceded by a back up. Then if I go in trouble the roll back is almost automatic. If you don't have aback up, first export your nodes to JSON to preserve it. Uninstall NodeRED and look for an old version, install and import your nodes... Not impossible to do... Good luck! |
|
Finally figured out how to roll back. You only need to roll back node-red-node-serialport. In Home Assistant, go to the NodeRed add-on. Then go to the configuration for the add-on. Next to npm packages to install, put "node-red-node-serialport@0.15.0". Then save and restart the NR add-on. This will revert node-red-node-serialport to the previous version that was working. |
|
Hi Juan,
Thanks for that trick but...it seems not working...
get:
Échec de l'enregistrement de la configuration du module complémentaire,
Invalid list for option 'npm_packages' in Node-RED (a0d7b954_nodered).
Got {'certfile': 'fullchain.pem', 'credential_secret': '&Petroineos',
'http_node': {'password': '', 'username': ''}, 'http_static':
{'password': '', 'username': ''}, 'init_commands': [], 'keyfile':
'privkey.pem', 'npm_packages': ***@***.***', 'ssl':
False, 'system_packages': [], 'theme': 'default'}
Any advise?
Regards
Patrice
Le 12/03/2022 à 20:57, juanhaywood a écrit :
…
Finally figured out how to roll back. You only need to roll back
node-red-node-serialport.
In Home Assistant, go to the NodeRed add-on. Then go to the
configuration for the add-on. Next to npm packages to install, put
***@***.***".
Then save and restart the NR add-on. This will revert
node-red-node-serialport to the previous version that was working.
—
Reply to this email directly, view it on GitHub
<#1312 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APEDJY4GS4XSWUTNSDP22VLU7TZJ7ANCNFSM5PSQSLLQ>.
You are receiving this because you commented.Message ID:
***@***.***>
|
Try it like this: Alternatively: |
|
Hi Mark,
Tricky but works so far...Further checks to do tomorrow
Many thanks for assistance
Best regards
Patrice
Le 12/03/2022 à 21:50, Mark Dietzer a écrit :
…
Hi Juan, Thanks for that trick but...it seems not working... get:
Échec de l'enregistrement de la configuration du module
complémentaire, Invalid list for option 'npm_packages' in Node-RED
(a0d7b954_nodered). Got {'certfile': 'fullchain.pem',
'credential_secret': '***', 'http_node': {'password': '',
'username': ''}, 'http_static': {'password': '', 'username': ''},
'init_commands': [], 'keyfile': 'privkey.pem', 'npm_packages':
/*@*/./*', 'ssl': False, 'system_packages': [], 'theme':
'default'} Any advise? Regards Patrice Le 12/03/2022 à 20:57,
juanhaywood a écrit :
… <#>
Finally figured out how to roll back. You only need to roll back
node-red-node-serialport. In Home Assistant, go to the NodeRed
add-on. Then go to the configuration for the add-on. Next to npm
packages to install, put /*@*/.*/". Then save and restart the NR
add-on. This will revert node-red-node-serialport to the previous
version that was working. — Reply to this email directly, view it
on GitHub <#1312 (comment)
<#1312 (comment)>>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APEDJY4GS4XSWUTNSDP22VLU7TZJ7ANCNFSM5PSQSLLQ.
You are receiving this because you commented.Message ID: /*@*/.***>
Try it like this:
|npm_packages: - ***@***.*** |
—
Reply to this email directly, view it on GitHub
<#1312 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APEDJY6Q63MVQY6XA3AIIRLU7T7QJANCNFSM5PSQSLLQ>.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Thanks @Doridian, that works perfect! :D Was about to give up and pull out my remaining hair! |
thanks @juanhaywood |
Perfect - have been having a nightmare trying to recover Node-Red the last two weeks, the lack of revealing logs from HA / docker has hampered the troubleshooting - but this has nailed the issue. |
|
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
github-actions
bot
added
the
stale
|
Still an issue |
|
The issue continue |
github-actions
bot
removed
the
stale
|
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
github-actions
bot
added
the
stale
|
If I'm not out of date, this issue is still unresolved. Can, please, someone confirm that is or not resolved? Tx |
|
I am checking.
tor. 19. mai 2022, 11:20 skrev Rsan ***@***.***>:
… If I'm not out of date, this issue is still unresolved.
Can, please, someone confirm that is or not resolved?
Tx
—
Reply to this email directly, view it on GitHub
<#1312 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABBYNEFYUUUDD4NVFW7QSDVKYBVVANCNFSM5PSQSLLQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Hello, just checked on a Raspberry Pi now, running Home Assistant (the problem is related to ARM). When I enable the latest version of "node-red-node-serialport" the addon gets stuck in a start-up loop like this: Never ending loop. When I add this to the configuration: The logs look like this: So this problem is very much the same :) |
Thanks a lot for the update (I'm answering this not to quote your large response). So, the problem is still there, somewhere uphill... |
github-actions
bot
removed
the
stale
|
I have just come across the problem on 2022-05-31 so it is an ongoing problem. As soon as I plug in a usb to serial device into the Raspberry Pi, I lose access to Node Red. The problems described above seem remarkably similar to what I have experienced in the last few days whilst having the latest version 11.1.2 - Most frustrating as HA does not seem to have bi-directional serial port capability built in. Node Red was my hope ! I have temporarily got round the problem by following the advice of Doridian and juanhaywood above and using the older "node-red-node-serialport@0.15.0" npm package. Hopefully a working set up for new users and updaters will include a serial package that doesn't barf node red! |
|
Comfirm this is solved in 12.0.2. :) Thanks @frenck |
|
Good to know! Thanks @corvy 👍 |
Problem/Motivation
In 11.0.4 on ARM devices, serial port nodes crash Node-RED.
Root cause is serialport/node-serialport#2438
Expected behavior
Node-RED starts up and works
Actual behavior
And this repeats over and over, no error messages I can find.
Full log: log.txt
Steps to reproduce
Just on startup, every time.
In case it is related to my config. All my config is in a git project that can be found here: https://github.com/FoxDenHome/nodered
Proposed changes
If this is widespread, unpublish the update or hotfix
The text was updated successfully, but these errors were encountered: