blueman2 Posted March 28, 2019 Posted March 28, 2019 (edited) I just realized my version is getting a bit old. V0.9.19. What is the best way to upgrade nodelink? Use the same install script, or can I just replace nodelink.exe? Running on RPi. Edited March 28, 2019 by blueman2 Quote
paulbates Posted March 28, 2019 Posted March 28, 2019 7 minutes ago, blueman2 said: I just realized my version is getting a bit old. V0.9.19. What is the best way to upgrade nodelink? Use the same install script, or can I just replace nodelink.exe? Running on RPi. On the main web page is an option to autoupdate nodelink. Check that and pick a time of day to do it. Then there is nothing to do Paul 1 Quote
io_guy Posted July 3, 2019 Author Posted July 3, 2019 Just a note. I updated the install script to now support all Raspbian versions (such as Jessie, Stretch and Buster). It'll detect which OS version and install packages as required. 7 Quote
rob7419 Posted August 25, 2019 Posted August 25, 2019 Can't get NodeLink to accept the password for the Envisalink 3 card. I've reinstalled twice and every time I hit the set button after inputting the password the browser spins then sets these errors. The first one says the password is incorrect but I can go the the Envisalink card web page with the password I'm using in NodeLink. Any ideas io_guy ? 2019-08-25 18:26:14 - ISY NodeLink Server v0.9.34 started 2019-08-25 18:26:14 - OS: Linux 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux 2019-08-25 18:26:14 - Mono version: 5.18.0.240 (Debian 5.18.0.240+dfsg-3 Sat Apr 20 05:16:08 UTC 2019) 2019-08-25 18:26:15 - Web config server started (http://192.168.1.???:8090) 2019-08-25 18:26:16 - ISY resolved to 192.168.1.??? (5.0.15A) 2019-08-25 18:26:16 - ISY Node Server config detected (profile 1)with the password 2019-08-25 18:26:18 - DSC: EVL User Login - Password Incorrect [dsc1] 2019-08-25 18:27:14 - DSC Error: Data Arrival - Cannot access a disposed object. Object name: 'System.Net.Sockets.Socket'. [dsc1] 2019-08-25 18:27:22 - DSC: No valid parameters setup for connection [dsc1] Quote
io_guy Posted August 26, 2019 Author Posted August 26, 2019 If your password is > 6 characters only enter in the first 6. It's a stupid EVL thing. Quote
snowtech Posted September 3, 2019 Posted September 3, 2019 Oh mannnnnn...? I already had a server running all my notifications and programs on the Rpi i installed the node... Everything stopped working, even the display i had with all the status of my home... ? Quote
lsibarra Posted September 24, 2019 Posted September 24, 2019 Hi io_guy, I am currently have a running Raspbian with your nodelink but due to some my file-systems got corrupted, I need to do re-install Raspbian which is now running the most recent OS (Raspbian buster). I ran your curl command to install Nodelink. However, if all possible I would like to retain my current Nodelink connection in my ISY as I have many programs that are tied to those nodes. I am afraid that once I connect the new Nodelink, it will create new nodes in my ISY. Is there a way to have the new setup recognize the existing nodes? Please advise. Thanks, Larry Quote
io_guy Posted September 25, 2019 Author Posted September 25, 2019 Should be ok. NodeLink auto-names nodes so unless you have multiples of the same device type you should be fine. If you have multiple's you'd want to add them in the same order you did last time. Quote
io_guy Posted October 26, 2019 Author Posted October 26, 2019 Install script is now moved over to .NET Core 3.0 1 Quote
dwengrovitz Posted October 27, 2019 Posted October 27, 2019 I re-ran the install script on my Pi. Is the latest version V0.10.1 or V0.10.0? My system shows the latter, but the release notes only show V0.10.1 with no mention of V0.10.0. In addition, the auto-update doesn't seem to see the proper files and I'm getting a 404 error. Here's the startup (w/o IP addresses) on my system: 2019-10-26 23:47:43 - ISY NodeLink Server v0.10.0 started 2019-10-26 23:47:43 - OS: Linux raspberrypi 4.19.75-v7+ #1270 SMP Tue Sep 24 18:45:11 BST 2019 armv7l GNU/Linux 2019-10-26 23:47:44 - Web config server started (http://192.x.x.x:8090) 2019-10-26 23:47:44 - ISY resolved to 192.x.x.x (5.0.16) 2019-10-26 23:47:44 - ISY Node Server config detected (profile 1) 2019-10-26 23:47:45 - Auto-Update: Error updating file: The remote server returned an error: (404) Not Found. Quote
Maresend Posted October 30, 2019 Posted October 30, 2019 After running the script, I repeatedly get this message through my browser (I tried reinstalling, rebooting the pi, all to no avail): This site can’t be reached 192.168.0.228 refused to connect. Search Google for 192 168 228 8090 ERR_CONNECTION_REFUSEd Quote
Maresend Posted October 30, 2019 Posted October 30, 2019 On 1/22/2019 at 4:52 PM, asbril said: Major progress..... I have access to Nodelink in my browser but it keeps telling me that I have the wrong ISY credentials. I have tried both with username/password for Administrative Console and those for ISY Portal. And each time I have restarted Nodelink to activate changes. I have also restarted the RPi but no luck with credentials. I have also done the ps aux|greb Nodelink that you suggested asbril, do you remember how you finally got access to the server through your browser? I'm still being refused. Quote
asbril Posted October 30, 2019 Posted October 30, 2019 6 hours ago, Maresend said: asbril, do you remember how you finally got access to the server through your browser? I'm still being refused. Sorry..... I don't and right now I don't use Nodelink. Knowing my limited techie competence, I was probably guided by others in this forum and maybe that guidance is listed somewhere. Quote
larryllix Posted October 30, 2019 Posted October 30, 2019 (edited) 6 hours ago, Maresend said: asbril, do you remember how you finally got access to the server through your browser? I'm still being refused. Most people have just left their ISY username as "admin". Are you sure about using an email address for an ISY username? Your RPi reports that WiFi is blocked due to not setting your country parameter. I hope you are connected hard-wired Ethernet and not relying on WiFi for Polyglot. Edited October 30, 2019 by larryllix Quote
Maresend Posted October 30, 2019 Posted October 30, 2019 Getting a segmentation fault when running the script. Still getting connection refused from browser. Considering doing a fresh Pi install to start over as i'm getting nowhere. ### Cleaning/Creating directories ### Installing .NET Core ### Downloading NodeLink ### Modifying startup script ### Starting NodeLink bash: line 48: 1240 Segmentation fault dotnet /home/pi/node/NodeLink.dll ### Install complete. Login to NodeLink at http://192.168.0.228:8090 Quote
Maresend Posted October 30, 2019 Posted October 30, 2019 Man I'm stumped. Brand new Raspbian stretch install, no errors, connection refused! Hmmm...can’t reach this page Try this Make sure you’ve got the right web address: http://192.168.0.29:8090 Search for "http://192.168.0.29:8090" on Bing Refresh the page Details Report this issue Privacy statement Quote
Bumbershoot Posted October 30, 2019 Posted October 30, 2019 18 minutes ago, Maresend said: Man I'm stumped. Brand new Raspbian stretch install, no errors, connection refused! I see three different IP addresses that you've used in your last few posts: 192.168.0.228; 192.168.86.46; 192.168.0.29. If you've got the right IP address, you should be able to SSH (ssh pi@192.168.0.228 for example) into that address and see if NodeLink is indeed running. It should look something like this after you run this command: ps aux | grep Node pi@raspberrypi:~ $ ps aux | grep Node root 598 1.3 6.4 247164 61240 ? Sl Oct29 23:50 dotnet /home/pi/node/NodeLink.dll pi 2929 2.8 6.4 252160 60640 ? Ssl 10:13 0:21 /home/pi/dotnet/dotnet /home/pi/node/NodeLink.dll pi 3163 0.0 0.0 7348 532 pts/0 S+ 10:26 0:00 grep --color=auto Node pi@raspberrypi:~ $ If it's not running, you won't get anything on that IP address:port Quote
Maresend Posted October 30, 2019 Posted October 30, 2019 3 minutes ago, Bumbershoot said: I see three different IP addresses that you've used in your last few posts: 192.168.0.228; 192.168.86.46; 192.168.0.29. If you've got the right IP address, you should be able to SSH (ssh pi@192.168.0.228 for example) into that address and see if NodeLink is indeed running. It should look something like this after you run this command: ps aux | grep Node pi@raspberrypi:~ $ ps aux | grep Node root 598 1.3 6.4 247164 61240 ? Sl Oct29 23:50 dotnet /home/pi/node/NodeLink.dll pi 2929 2.8 6.4 252160 60640 ? Ssl 10:13 0:21 /home/pi/dotnet/dotnet /home/pi/node/NodeLink.dll pi 3163 0.0 0.0 7348 532 pts/0 S+ 10:26 0:00 grep --color=auto Node pi@raspberrypi:~ $ If it's not running, you won't get anything on that IP address:port Bumbershoot, sorry about the IP addresses, its because I gave up on a raspberry pi that I had previously installed, installed a new one from scratch, hence the new ip address at 192.168.0.29. Everything ran smooth as far as I could tell via the scrip, and i'm able to ssh into it no problem. However, I don't believe Nodelink is running, and have no idea where to go next. Running your script gave this: pi@raspberrypi:~ $ ps aux | grep Node pi 1574 0.0 0.4 7332 1892 pts/0 S+ 17:40 0:00 grep --color=auto Node Quote
Maresend Posted October 30, 2019 Posted October 30, 2019 Noticed that when tring to start NodeLink, Its getting the 5242 segementation fault again. ### Updating System - this may take several minutes All packages are up to date. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ### Cleaning/Creating directories ### Installing .NET Core ### Downloading NodeLink ### Modifying startup script ### Starting NodeLink bash: line 48: 5242 Segmentation fault dotnet /home/pi/node/NodeLink.dll ### Install complete. Login to NodeLink at http://192.168.0.29:8090 Any ideas as to what that means? Quote
Bumbershoot Posted October 30, 2019 Posted October 30, 2019 1 hour ago, Maresend said: Bumbershoot, sorry about the IP addresses, its because I gave up on a raspberry pi that I had previously installed, installed a new one from scratch, hence the new ip address at 192.168.0.29. Everything ran smooth as far as I could tell via the scrip, and i'm able to ssh into it no problem. However, I don't believe Nodelink is running, and have no idea where to go next. Running your script gave this: pi@raspberrypi:~ $ ps aux | grep Node pi 1574 0.0 0.4 7332 1892 pts/0 S+ 17:40 0:00 grep --color=auto Node Nope, it's not running. 51 minutes ago, Maresend said: ### Starting NodeLink bash: line 48: 5242 Segmentation fault dotnet /home/pi/node/NodeLink.dll Crash. You might try running NodeLink from the command line, and see if it sends any helpful output to the screen (I think you can just run the command that you see in output above): dotnet /home/pi/node/NodeLink.dll Other than that, I don't know how I can help with a seg fault. Quote
Maresend Posted October 30, 2019 Posted October 30, 2019 (edited) 50 minutes ago, Bumbershoot said: Nope, it's not running. Crash. You might try running NodeLink from the command line, and see if it sends any helpful output to the screen (I think you can just run the command that you see in output above): dotnet /home/pi/node/NodeLink.dll Other than that, I don't know how I can help with a seg fault. Thanks Bumbershoot. I tried running it and it spat this out: pi@raspberrypi:~ $ dotnet /home/pi/node/NodeLink.dll Segmentation fault Is it possible this is because its running on a Pi2? Maybe doesn't have the resources? I couldn't find a definitive answer online. Edited October 30, 2019 by Maresend typo Quote
Bumbershoot Posted October 30, 2019 Posted October 30, 2019 Just now, Maresend said: Thanks Bumbershoot. I tried running it and it spat this out: pi@raspberrypi:~ $ dotnet /home/pi/node/NodeLink.dll Segmentation fault Is it possible this is because its running on a Pi2? Maybe doesn't have to resources? I couldn't find a definitive answer online. No, I'm running it on a Pi2 as well, and it runs like a champ. I think you'll have to wait for the developer to chime in here. Quote
Maresend Posted October 30, 2019 Posted October 30, 2019 Just now, Bumbershoot said: No, I'm running it on a Pi2 as well, and it runs like a champ. I think you'll have to wait for the developer to chime in here. Ok, good to know, Thanks for your time Bumbershoot! Quote
io_guy Posted October 30, 2019 Author Posted October 30, 2019 Can you try: sudo apt install curl apt-transport-https Quote
Maresend Posted October 30, 2019 Posted October 30, 2019 9 minutes ago, io_guy said: Can you try: sudo apt install curl apt-transport-https Hi io_guy, ran this script: pi@raspberrypi:~ $ sudo apt install curl apt-transport-https Reading package lists... Done Building dependency tree Reading state information... Done curl is already the newest version (7.64.0-4). The following NEW packages will be installed: apt-transport-https 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 149 kB of archives. After this operation, 156 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://mirrors.switch.ca/raspbian/raspbian buster/main armhf apt-transport-https all 1.8.2 [149 kB] Fetched 149 kB in 1s (119 kB/s) Selecting previously unselected package apt-transport-https. (Reading database ... 39961 files and directories currently installed.) Preparing to unpack .../apt-transport-https_1.8.2_all.deb ... Unpacking apt-transport-https (1.8.2) ... Setting up apt-transport-https (1.8.2) ... Then I rebooted and looked for the process: pi@raspberrypi:~ $ ps aux | grep Node pi 743 0.0 0.4 7332 1816 pts/0 S+ 20:52 0:00 grep --color=auto Node should I be re-running the original install script? 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.