-
Notifications
You must be signed in to change notification settings - Fork 13
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
rfxcom node doesn't work with Node-Red v3 #124
Comments
Strangely, reinstalling doesn't work for me. Following is the debug out put:2022-10-19T13:46:37.765Z Install : node-red-contrib-rfxcom 2.11.3 2022-10-19T13:46:37.838Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict [email protected] |
using distro diet-pi with clean node-red installation. Unable to install node-red-contrib-rfxcom. 2022-10-30T10:17:48.853Z Install : node-red-contrib-rfxcom 2.11.3 2022-10-30T10:17:48.235Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict [email protected] |
Same here. Just upgraded to Node-RED 3.0.2 and node-red-contrib-rfxcom stopped working. Gets the following error in the logg: After manually uninstalling node-red-contrib-rfxcom, and then trying to add it again from the UI, I get the same error as previous posts. After hours of trying to manualy installing packages I gave up and reverted to version 2 of Node-Red. |
@Strixx76 That is a NodeJS version problem, nothing to do with the Node-RED version. You need to go to the package directory of |
@doomedsardines, @tenhercules: It looks like I need to update the version of |
As I wrote I did try that, and I tried rebuild only the I will give it some more testing later today or tomorrow to see if I can figure out what is causing this. |
So I started up a brand new container with the official Node-RED image (nodered/node-red:3.0.2). And I am not able to install node-red-contrib-rfxcom 2.11.3. Nothing else is installed in this container. This is the full log:
|
The trouble here is something to do with printf?!
I have no idea where this is coming from. I don't see it when installing. Something to do with Docker maybe? |
I got mine working after rebuilding @serialport: Thanks for the tip @Strixx76 ! |
Well, yes and no I guess. The issue exists on all type of fresh installs on all types container installations. I have tried LXC containers as well now. Different errors but all is about missing dependencies because the need of building the serialport package. It is not working in the Home Assistant Add-on or in Proxmox LXC Container built with tteck helper script or in the official Node-RED docker container The only way I have got it up and running is by building my on container with Alpine Linux as base and install all dependencies for building the serialport package:
Or you have to start with an older Node-RED and node.js version and do updates and upgrades and manually rebuild the serialport package, but even then you need to have all build-essentials and python installed in the container. I know absolutely nothing about how to create Node-RED nodes, but according to the maintainer of the Home Assistant add-on the problem is due to "improperly configured environment". In that Docker container there is already serialport installed. |
Version 2.13.0 now published to npm uses serialport 11.x.x, to retain compatibility with NodeJS v14. If this is available ready-compiled, it should avoid the issue, perhaps? |
Node is not working after upgrade of Node-Red to version 3.
The following error is displayed:
The text was updated successfully, but these errors were encountered: