Just now, simplextech said:

Can I ask... what is " Debian with the RPi load" ???  Raspbian is just debian for arm with some additional edu packages and hardware specific packages for rPi.

I use the Raspian x86 image to install the image onto a VM. The ISO is titled (from the download): 019-04-11-rpd-x86-stretch.iso

1 minute ago, ralbright said:

I use the Raspian x86 image to install the image onto a VM. The ISO is titled (from the download): 019-04-11-rpd-x86-stretch.iso

Gotcha...

I always forget there's the Raspian desktop image.  The "debian with rPi load" threw me off

 

 

On 11/22/2019 at 3:33 PM, Bumbershoot said:

Sorry, I'm traveling so I can't look at the script on my RPi, but I notice right away that you're calling 'nodelink.exe' instead of 'nodelink.dll'. You might edit 'nodelink.service' to see if that matters.  I really haven't touched Windows machines much in over a decade, so my expertise with Windows executables is low.

Been about a month, I got really busy (joys of being a professional Santa Claus), I went to go look at my Insteon network and remembered that I still had not figured out the startup script for it. @Bumbershoot is it possible to get a copy of your startup script with the dotnet changes?

2 hours ago, ralbright said:

Been about a month, I got really busy (joys of being a professional Santa Claus), I went to go look at my Insteon network and remembered that I still had not figured out the startup script for it. @Bumbershoot is it possible to get a copy of your startup script with the dotnet changes?

I just made a file in /etc/systemd/system/ called 'nodelink.service'.  Below are the contents:

[UNIT]
Description=NodeLink Server
Documentation=http://automationshack.com/nodelink.html
Requires=network-online.target
After=network-online.target

[Service]
Type=simple
ExecStart=/home/pi/dotnet/dotnet /home/pi/node/NodeLink.dll
Restart=always
User=pi

[Install]
WantedBy=multi-user.target

 

1 hour ago, Bumbershoot said:

I just made a file in /etc/systemd/system/ called 'nodelink.service'.  Below are the contents:

[UNIT]
Description=NodeLink Server
Documentation=http://automationshack.com/nodelink.html
Requires=network-online.target
After=network-online.target

[Service]
Type=simple
ExecStart=/home/pi/dotnet/dotnet /home/pi/node/NodeLink.dll
Restart=always
User=pi

[Install]
WantedBy=multi-user.target

 

Hmmm.... That is what I did and this is what I get:

pi@raspberry:~ $ sudo systemctl status nodelink.service
● nodelink.service - NodeLink Server
   Loaded: loaded (/etc/systemd/system/nodelink.service; disabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2019-12-29 18:03:32 PST; 979ms ago
     Docs: http://automationshack.com/nodelink.html
  Process: 21313 ExecStart=/home/pi/dotnet/dotnet /home/pi/node/NodeLink.dll (code=exited, status=255)
 Main PID: 21313 (code=exited, status=255)

Dec 29 18:03:32 raspberry systemd[1]: nodelink.service: Main process exited, code=exited, status=255/n/a
Dec 29 18:03:32 raspberry systemd[1]: nodelink.service: Unit entered failed state.
Dec 29 18:03:32 raspberry systemd[1]: nodelink.service: Failed with result 'exit-code'.
Dec 29 18:03:32 raspberry systemd[1]: nodelink.service: Service hold-off time over, scheduling restart.
Dec 29 18:03:32 raspberry systemd[1]: Stopped NodeLink Server.
Dec 29 18:03:32 raspberry systemd[1]: nodelink.service: Start request repeated too quickly.
Dec 29 18:03:32 raspberry systemd[1]: Failed to start NodeLink Server.
Dec 29 18:03:32 raspberry systemd[1]: nodelink.service: Unit entered failed state.
Dec 29 18:03:32 raspberry systemd[1]: nodelink.service: Failed with result 'exit-code'.

But it will run just fine if I just run from the command line: dotnet /home/pi/node/NodeLink.dll

@Bumb

FIGURED IT OUT!!

Changed the line

ExecStart=/home/pi/dotnet/dotnet /home/pi/node/NodeLink.dll

To this:

ExecStart=/usr/bin/dotnet /home/pi/node/NodeLink.dll

Now I get this:

pi@raspberry:/etc/systemd/system $ sudo systemctl status nodelink.service
● nodelink.service
   Loaded: loaded (/etc/systemd/system/nodelink.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2019-12-29 18:43:35 PST; 6s ago
 Main PID: 21918 (dotnet)
    Tasks: 17 (limit: 4915)
   CGroup: /system.slice/nodelink.service
           └─21918 /usr/bin/dotnet /home/pi/node/NodeLink.dll

Dec 29 18:43:35 raspberry systemd[1]: Started nodelink.service.
Dec 29 18:43:36 raspberry dotnet[21918]: 2019-12-29 18:43:36 - ISY NodeLink Server v0.10.5 started
Dec 29 18:43:36 raspberry dotnet[21918]: 2019-12-29 18:43:36 - OS: Linux raspberry 4.9.0-11-amd64 #1 SMP Debian 4.9.189-3+deb9u2 (2019-11-11) x86_64 GNU/Lin
Dec 29 18:43:36 raspberry dotnet[21918]: 2019-12-29 18:43:36 - Web config server started (http://192.168.3.24:8090)
Dec 29 18:43:36 raspberry dotnet[21918]: 2019-12-29 18:43:36 - ISY resolved to 192.168.2.4 (5.0.15A)
Dec 29 18:43:36 raspberry dotnet[21918]: 2019-12-29 18:43:36 - ISY Node Server config detected (profile 1)

 

Edited December 30, 20195 yr by ralbright

I have been running 0.9.30 under mono, and just tried to use the script to update to the new version.  However, when I go to the web page, it is still showing that I am running 0.9.30.  The install script said it installed the 0.10.5 version, but did  give a warning that the 8090 port was in use.  Any ideas what I did wrong?

I am running on an Rpi3 under Stretch.  

EDIT: I was able to solve by editing the nodelink.service file in /etc/systemd/system to change the execution line to

ExecStart=/home/pi/dotnet/dotnet /home/pi/node/NodeLink.dll

and then removing the similar line in rc.local to avoid having 2 instances running.  

Edited August 3, 20205 yr by blueman2

Yep, the install script assumes you used the old install script, meaning you're running NodeLink from rc.local.  You did a custom systemd startup so the old .exe would keep running.  

Trying to install for the first time on a RPI 3 B+. The only other thing I've ever installed is polyglot.

sorka@raspberrypi:~ $ sudo curl -sSL http://automationshack.com/Files/install.sh | bash

### Updating System - this may take several minutes
All packages are up to date.
The following packages were automatically installed and are no longer required:
  coinor-libipopt1v5 libmumps-seq-4.10.0 libraw15 lxkeymap python-cairo python-gobject python-gobject-2 python-gtk2 python-xklavier realpath
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

### Cleaning/Creating directories
mkdir: cannot create directory ‘/home/pi/dotnet’: Permission denied
bash: line 25: cd: /home/pi/dotnet: No such file or directory

### Installing .NET Core 3.1.7

### Downloading NodeLink
/home/pi/node/NodeLink.dll: Permission denied
/home/pi/node/NodeLink.runtimeconfig.json: Permission denied

### Modifying startup script

### Starting NodeLink
bash: line 45: dotnet: command not found

### Install complete. Login to NodeLink at http://192.168.1.98:8090
 

No if I do a "sudo mkdir /home/pi/dotnet" it creates the directory but after running the script and getting this error, that directory is done.

Just did a shotgun permission add "sudo chmod ugo+rw /home/pi" and "sudo chmod ugo+rw /home/pi/node" and it succeed without error.

I have NodeLink running in a docker container on my Synology. It want to move it to my RPI. I'm using both DSC and CAI. Do I need to turn NodeLink off first on the synology? Will it mess things up if I try to configure it on the RPI first? Do I need to delete the nodes on the ISY from the old copy running first? Will I nee to edit all my programs that use the DSC and CAI nodes?

Get it running on the Pi and then just copy over the config.xml file.  No need to change anything on the ISY with the exception of the new IP address for the Node Server.   

7 hours ago, io_guy said:

Get it running on the Pi and then just copy over the config.xml file.  No need to change anything on the ISY with the exception of the new IP address for the Node Server.   

 

Thanks. That worked seamlessly!

 

I moved it off my NAS because I'm scheduling it to turn on for only an hour a day so my Blue Iris can do it's long term storage backups. It takes 50 watts just sitting there doing almost nothing 365. Just did solar and 3 powerwalls and cutting out unnecessary usage.

Edited October 24, 20204 yr by sorka

I was curious why you moved off the Synology.  Makes sense.

Just an FYI,

Next version of NodeLink will be a "breaking" change.  I'll be moving to .NET 5 (which comes out in 3 weeks) and I've modified all the NodeDef files to allow for dynamic changing of units.  It will be similar to the move to .NET Core 3 where it didn't auto upgrade.

I'll stick with .NET 5 for a long time so this should be the last of the painful updates.

I'll also be adding a couple new devices:
- Weatherbit
- Hayward Omnilogic pool controller
- MyQ