io_guy Posted October 29, 2018 Posted October 29, 2018 NodeLink installation on a Raspberry Pi is now a lot simpler. On a running Pi you type: sudo curl -sSL http://automationshack.com/Files/install.sh | bash That's it. It updates the Pi, installs .NET Core 3.0, downloads NodeLink and sets up the startup script. 7 1 Quote
BamBamF16 Posted October 29, 2018 Posted October 29, 2018 Can nodelink and polyglot run on the same rpi? Quote
larryllix Posted October 29, 2018 Posted October 29, 2018 19 minutes ago, bambamf16 said: Can nodelink and polyglot run on the same rpi? I am. 1 Quote
Bumbershoot Posted October 29, 2018 Posted October 29, 2018 17 minutes ago, larryllix said: I am. Me too, along with the WeatherFlow node server, which invokes another instance of Mono. No problems Quote
paulbates Posted October 29, 2018 Posted October 29, 2018 There's no reason it shouldn't. Python (polyglot) and Mono (Nodelink) are separate processes that can run at the same time. There is more than enough horsepower in Pis as well. I'm running nodelink with 4 devices on a Pi Model 2B... its taking a nap - typically 1% of CPU. I have an older pi that is a model B+ and I've tested my Nodelink setup on it too. It runs fine. Paul Quote
RRoyceus Posted November 3, 2018 Posted November 3, 2018 (edited) My NodeLink recently quit working. I tried this hoping it would correct it. It got 95% installed within an hour then stopped. I left it running over night and this morning I rebooted the Pi. After restarting I got errors and a message to run "sudo dpkg --configure -a" I ran that command line. Now when trying to run NodeLink, I get the attached errors. Edited November 3, 2018 by RRoyceus Quote
io_guy Posted November 3, 2018 Author Posted November 3, 2018 Rerun the install script now. I added an option to the mono run command to fix a bug in mono 5.16.0.179. (mono -O=-aot NodeLink.exe) 1 Quote
MrTinker Posted November 6, 2018 Posted November 6, 2018 I had to completely remove mono 5.16.0.179 to get by the precompilation errors (it would consume all available RAM/swap). This was one of the suggested options in the error thread to which you linked. I then used your script to install again. Thank you! Quote
beninsteon Posted November 8, 2018 Posted November 8, 2018 Hi @io_guy, Thanks for this! How long should it take to run this install script? I've been stuck here for about an hour.. Ben Quote
beninsteon Posted November 8, 2018 Posted November 8, 2018 I let it run all night and my Pi crashed. Had to unplug and plug it back in to get things running again. Any suggestions as to why that may have happened? Quote
io_guy Posted November 8, 2018 Author Posted November 8, 2018 Nope, the part running was just a standard apt-get install. Maybe it ran out of memory. I see you're running X and VNC. Quote
beninsteon Posted November 10, 2018 Posted November 10, 2018 You're right. After I disabled X and VNC, it installed correctly. Thanks! Quote
RRoyceus Posted November 11, 2018 Posted November 11, 2018 I was out of town a week and reran the script when I go back. I still have errors when starting NodelInk Quote
io_guy Posted November 11, 2018 Author Posted November 11, 2018 You're manually starting mono without the proper arguements to resolve the 5.16.0.179 bug. Look at the rc.local. Quote
RRoyceus Posted November 11, 2018 Posted November 11, 2018 I looked at re.local. It appears to be correct. I ran 'mono -O=-aot NodeLink.exe' from the node directory. NodeLink freezes. Quote
io_guy Posted November 11, 2018 Author Posted November 11, 2018 Reboot the Pi, you have two instances running (hence the "Already in use"). Quote
RRoyceus Posted November 12, 2018 Posted November 12, 2018 I finally got this working by erasing all files in the node directory and re-running the script. After restarting, I had to go into config and set up the ISY, then had to add back my devices. 1 Quote
io_guy Posted November 12, 2018 Author Posted November 12, 2018 Restarting was the fix. Deleting the dir wouldn't make a difference unless your previous config had NodeLink on some strange port that was used by another resource. In that case you would edit the config.xml to change the port. Quote
lsibarra Posted November 23, 2018 Posted November 23, 2018 Hi io_guy Thanks for this new script to install and load the nodelink. I noticed that NodeLink Server v0.9.21 no longer have the option to install the geofence/location device. Is this node device no longer supported in this version? Thanks. Quote
io_guy Posted December 28, 2018 Author Posted December 28, 2018 Looks like mono 5.18 is now released for the Pi. I've removed the aot option from the install script as we should be back to normal now. 1 Quote
bipto Posted December 28, 2018 Posted December 28, 2018 Will the aot option cause any issues when used with mono 5.18? As usual my timing sucks and I think my Christmas eve Pi rebuild may have put me in that situation. Seems fine - any harm leaving it? Quote
io_guy Posted December 28, 2018 Author Posted December 28, 2018 Leaving it is fine. That options just runs a little slower than without, although you'd likely never notice it in an application like NodeLink. Quote
dwengrovitz Posted December 29, 2018 Posted December 29, 2018 On 10/29/2018 at 7:56 AM, io_guy said: NodeLink installation on a Raspberry Pi is now a lot simpler. On a running Pi you type: sudo curl -sSL http://automationshack.com/Files/install.sh | bash Got a new toy over the holidays (a Raspberry Pi), so I thought I'd try installing Nodelink on it. I have some other apps I need to run that require Raspbian 8. Does the install script for Nodelink care which version of Raspbian I'm running? Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.