-
Notifications
You must be signed in to change notification settings - Fork 113
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
Cannot compile on Raspberry Pi Zero #204
Comments
BTW, You're trying to install You can use openZWave through |
Hello Elias, Thank you very much for the help. I followed these steps: This is the output:
For some reason, it cannot find Manager.h. I don't know if this is a temporary filed created in the "Make" process but I cannot find it in that area either. I have tried to use the "Manage palette" option in the node-red ui. When I install, I get this output from the console window I started node-red with.
Any ideas or alternative methods getting the node-red nodes set up, please let me know. I appreciate the help. |
This means you're missing OpenZWave development files from your system
|
I have very little Linux experience so if you offer a solution please be very specific and detailed.
I have successfully made it to step #2. I did not have any luck installing the "(New!) Download and install the precompiled Raspbian/ARMv6 packages for Raspberry 1:" so I have chosen the Hercules' path of blight.
The following commands executed successfully:
The command "MinOZW /dev/ttyACM0" returns:
I am unclear as to the meaning of "project directory" so I entered the following command:
cd ~/.node-red
The prompt now looks like:
pi@taboo:~/.node-red $
The contents of the directory is as follows:
Upon entering the command:
npm install openzwave-shared
The following output is generated:
Here are the contents of 2017-11-28T19_53_37_320Z-debug.log:
2017-11-28T19_53_37_320Z-debug.log
Any help or direction would be greatly appreciated as I am about 3 weeks on and off of trying to figure out on my own. Kind Regards -bill
The text was updated successfully, but these errors were encountered: