ralbright

Thank you for the thought out statement. I have been a bit in both camps for years with my own house. (But now that I am selling it and moving into a fifth wheel I would like to bring part of that automation with me.) Obviously there will be differences, as most of the automation will revolve around 12VDC devices vs 120VAC devices. I will have relatively low latency internet available most places I go (I do have Starlink for the fifth wheel) as well as backup of cellular internet. Just pondering if the eISY is a good platform for this. I have seen a lot of people that use Home Assistant for this type of automation, and I really do not want to give up the great platform that I have with UDI.

With me downsizing into a fifth wheel, I am wanting to take many of my smart home structure into the trailer with me. The eISY looks to be that it could be extremely powerful to control various aspects of an RV. Has anyone thought of doing so?

Michel is usually REALLY quick on tickets. That is my best answer.... sorry I couldn't be of more help.

For anyone else that is having this issue (now or in the future). Michel solved it with a few commands that he gave me to issue via putty. In my case the unit was completely responding to commands on putty, but I could not login to the web interface. Here is how it was fixed: sudo pkg update && sudo pkg upgrade cat /usr/local/etc/udx.d/static/update13.sh | sudo bash This upgraded me to version 13, I was running version 12.

This afternoon I received an email from Generac stating that added an Alexa skill for their Generac generator (which I have installed on my property), and was thinking of looking into the possibility of adding a node to PolyISY for it. Went to log in, type my username/password, click login and nothing happens. Have tried on 3 devices all with the same results. Any ideas as to what is causing this issue.

Looked over the Polisy debug log for today... and I did something because this is what it is now filling with: 6/7/2021, 19:39:34 [polyglot] info: Starting Polyglot.... 6/7/2021, 19:39:34 [polyglot] info: Settings: Polyglot Version 2.2.13 6/7/2021, 19:39:34 [polyglot] info: Settings: Retrieved config from database 6/7/2021, 19:39:34 [polyglot] info: Running in Polisy mode 6/7/2021, 19:39:34 [polyglot] info: Settings: Retrieved config overrides from .env and updated database 6/7/2021, 19:39:34 [polyglot] info: Aedes MQTT Broker Service: Started on port 1883 Same thing every 7-8 seconds..... Is there a way to fix this from SSH

Went to access my Polisy, and forgot all about needing to access via HTTPS port 443, after doing a port scan I remembered it. Well I was screwing around in my system settings..... (yeah I know... but I am a geek so I cannot help it), I thought "why don't I enable communication to the unit on port 80" Well I changed the setting on the system tab from port 443 to port 80, now the unit rebooted and I can only see port 22 and 123 (whereas before I could see ports 22, 123, 443, 9090 and a few others). How do I change the default Polisy port back to port 443 from SSH?

@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)

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

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 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

Good question.... to which my answer is.... I don't know.

The "server" is running Windows 10, which I have in my home, it has VirtualBox running a few VMs, one of which is Debian with the RPi load. Does that help? (It is mainly because I already have it running 24/7 in my home, why put a Pi in place when I already have it. As for the NLS issue, I have the NodeLink running debug now. And then I go and check on my ISY again.... and it is showing the names properly. What a wonderful annoying (apparently not) issue now. logfile_2019-11-25.txt

So I managed to get 0.10.5 loaded on a Debian 9 (RPi) VM. Here is how I did it! Fresh install from 019-04-11-rpd-x86-stretch.iso Set my IP address to a fixed address sudo apt-get update sudo apt-get upgrade sudo apt-get install libicu57 sudo apt-get install libssl1.0.2 wget -qO- https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor > microsoft.asc.gpg sudo mv microsoft.asc.gpg /etc/apt/trusted.gpg.d/ wget -q https://packages.microsoft.com/config/debian/9/prod.list sudo mv prod.list /etc/apt/sources.list.d/microsoft-prod.list sudo chown root:root /etc/apt/trusted.gpg.d/microsoft.asc.gpg sudo chown root:root /etc/apt/sources.list.d/microsoft-prod.list sudo apt-get update sudo apt-get install apt-transport-https sudo apt-get update sudo apt-get install dotnet-sdk-3.0 sudo apt-get install libunwind8 gettext curl wget sudo curl -sSL http://automationshack.com/Files/install.sh | bash I can now run the command: dotnet /home/pi/node/NodeLink.dll However my attempts at following Bumbershoot's systemd startup script fail miserably. The /etc/systemd/system/nodelink.service file looks like this: ### BEGIN INIT INFO # Provides: nodelink.service # Required-Start: $all # Required-Stop: # Default-Start: 2 3 4 5 # Default-Stop: # Short-Description: NodeLink Server ### END INIT INFO [UNIT] Description=NodeLink Server Documentation=http://automationshack.com/nodelink.html Requires=network-online.target After=network-online.target [Service] Type=simple ExecStartPre=/bin/sleep 10 ExecStart=/home/pi/dotnet/dotnet /home/pi/node/NodeLink.dll ExecReload=/bin/sleep 5 | /home/pi/dotnet/dotnet /home/pi/node/NodeLink.dll Restart=always User=pi [Install] WantedBy=multi-user.targetNode Whenever I run status on this service I get this error message: pi@raspberry:~ $ sudo systemctl status nodelink.service ● nodelink.service Loaded: loaded (/etc/systemd/system/nodelink.service; disabled; vendor preset: enabled) Active: activating (start-pre) since Sun 2019-11-24 20:00:38 PST; 4s ago Process: 5599 ExecStart=/home/pi/dotnet/dotnet /home/pi/node/NodeLink.dll (code=exited, status=255) Main PID: 5599 (code=exited, status=255); Control PID: 5604 (sleep) Tasks: 1 (limit: 4915) CGroup: /system.slice/nodelink.service └─control └─5604 /bin/sleep 10 Nov 24 20:00:38 raspberry systemd[1]: nodelink.service: Service hold-off time over, scheduling restart. Nov 24 20:00:38 raspberry systemd[1]: Stopped nodelink.service. Nov 24 20:00:38 raspberry systemd[1]: Starting nodelink.service... Also at times I see this in the status: Nov 24 19:59:56 raspberry systemd[1]: [/etc/systemd/system/nodelink.service:10] Unknown section 'UNIT'. Ignoring. ----- Something I am still experiencing however is naming conventions in ISY. (What caused me to look into all of this upgrade stuff...) All NodeLink nodes follow this naming convention for their various properties: (box 1) - Occupied (box 2) - [NLS-10:ST-GV1-NAME] (box 3) - [NLS-10:ST-GV2-NAME] ....etc....

Also I am not running a true Debian install, I am actually running the RPi Debian on VM. (Not sure if that makes a difference or not.)