Ed Sybesma Posted April 9, 2022 Posted April 9, 2022 The Program Summary tab Shows the most recent run time and status result for programs. Is there any way to keep or obtain a log which shows the history of previous runs, similar to the Log of device events available under the Tools menu?
tmorse305 Posted April 9, 2022 Posted April 9, 2022 I use NodeLink for logging. It can keep track of devices, programs and variables. It's very useful for tracking down intermittent problems. 1
Ed Sybesma Posted April 10, 2022 Author Posted April 10, 2022 18 hours ago, tmorse305 said: I use NodeLink for logging. It can keep track of devices, programs and variables. It's very useful for tracking down intermittent problems. Thank you for that input. Follow-up questions: I am using windows. I have previously loaded nodes for ISY through polyglot cloud. That now is unavailable. I am not otherwise familiar with running this type of file/program. What do you run/load NodeLink with: Polisy? Docker? Or? The instructions for NodeLink say: Download and run the latest version of NodeLink from:http://automationshack.com/Files/NodeLink.dllhttp://automationshack.com/Files/NodeLink.runtimeconfig.json Neither .dll files nor .json files run directly from Windows. I am obviously missing some basic background here, but my search of the Internet has not given me any answers. Thank you much for any help you can provide.
MrBill Posted April 10, 2022 Posted April 10, 2022 1 hour ago, Ed Sybesma said: Thank you for that input. Follow-up questions: I am using windows. I have previously loaded nodes for ISY through polyglot cloud. That now is unavailable. I am not otherwise familiar with running this type of file/program. What do you run/load NodeLink with: Polisy? Docker? Or? The instructions for NodeLink say: Download and run the latest version of NodeLink from:http://automationshack.com/Files/NodeLink.dllhttp://automationshack.com/Files/NodeLink.runtimeconfig.json Neither .dll files nor .json files run directly from Windows. I am obviously missing some basic background here, but my search of the Internet has not given me any answers. Thank you much for any help you can provide. Unless you have a dedicated windows machine running 24/7 for some other reason, the best bet is likely running it on a raspberry pi... more info here: http://automationshack.com/wp/nodelink/
Ed Sybesma Posted April 10, 2022 Author Posted April 10, 2022 3 minutes ago, MrBill said: Unless you have a dedicated windows machine running 24/7 for some other reason, the best bet is likely running it on a raspberry pi... more info here: http://automationshack.com/wp/nodelink/ Thanks. I do have a dedicated Windows machine running 24/7. What do I need to do to run NodeLink on Windows?
MrBill Posted April 10, 2022 Posted April 10, 2022 3 minutes ago, Ed Sybesma said: Thanks. I do have a dedicated Windows machine running 24/7. What do I need to do to run NodeLink on Windows? Couldn't tell you how to run via windows, but let's tag @io_guy
io_guy Posted April 10, 2022 Posted April 10, 2022 Install the Windows .NET 5 or 6 runtime. You can then run "dotnet NodeLink.dll". 1
Ed Sybesma Posted April 10, 2022 Author Posted April 10, 2022 (edited) 1 hour ago, io_guy said: Install the Windows .NET 5 or 6 runtime. You can then run "dotnet NodeLink.dll". Thank you so much. That is a great start. When I run either "dotnet NodeLink.dll" or "dotnet NodeLink.dll NodeLink.runtimeconfig.json" (within a folder where all the files are located), I get the following result ( with some numbers intentionally concealed with x's here): 2022-04-10 16:13:35 - ISY NodeLink Server v0.11.3 started 2022-04-10 16:13:35 - OS: Microsoft Windows NT 10.0.19044.0 2022-04-10 16:13:35 - Installed .NET Runtime Version: 5.0.15 [5] 2022-04-10 16:13:35 - Web config server started (http://192.xxx.xx.x:8xxx) 2022-04-10 16:13:35 - No password specified for the ISY 2022-04-10 16:13:36 - ISY resolved to 192.xxx.xx.xx (5.0.16C) The Windows Powershell Administrator window then freezes and nothing else obvious happens. So it looks like I have gotten to the first step properly, but something else is missing. Any further ideas? Edited April 10, 2022 by Ed Sybesma
io_guy Posted April 10, 2022 Posted April 10, 2022 That's it. Go to the webconfig with your browser. 1
Ed Sybesma Posted April 11, 2022 Author Posted April 11, 2022 18 hours ago, io_guy said: That's it. Go to the webconfig with your browser. Thanks again for your help. Unfortunately, the last tip doesn't seem to be helping. I have 16 web.config files on my drive. Some of them are human readable and some not. None of them are new enough to have anything to do with running the NodeLink. Of the ones that are readable, none have anything to do with NodeLink or ISY. What am I missing?
Solution tmorse305 Posted April 11, 2022 Solution Posted April 11, 2022 (edited) 18 hours ago, Ed Sybesma said: 2022-04-10 16:13:35 - Web config server started (http://192.xxx.xx.x:8xxx) Open a browser and go to the web config server page for NodeLink. There you will add the ISY credentials. The port is 8090, and the ip is the ip for the computer running NodeLink. Edited April 11, 2022 by tmorse305 1
Ed Sybesma Posted April 11, 2022 Author Posted April 11, 2022 5 minutes ago, tmorse305 said: Open a browser and go to the web config server page for NodeLink. There you will add the ISY credentials. The port is 8090, and the ip is the ip for the computer running NodeLink. Those numbers did in fact properly appear in the first place. I just concealed them with x's just in case (contrary to my expectation) they could have been used by anyone to hack my system.
tmorse305 Posted April 11, 2022 Posted April 11, 2022 (edited) 4 minutes ago, Ed Sybesma said: Those numbers did in fact properly appear in the first place. Yes, you said that, I included the port number in case you no longer had access to the non-redacted version. 8090 is the std port for NodeLink, common knowledge. Can you access the browser interface? Edited April 11, 2022 by tmorse305
Ed Sybesma Posted April 11, 2022 Author Posted April 11, 2022 9 minutes ago, tmorse305 said: Yes, you said that, I included the port number in case you no longer had access to the non-redacted version. 8090 is the std port for NodeLink, common knowledge. Can you access the browser interface? Yes. That solves the issue. I did not previously understand quite what was going on. I now see that the fourth line of the original input was directing me to the web config server. Thank you very much.
tmorse305 Posted April 11, 2022 Posted April 11, 2022 Glad you got it working. It's a great addition to your ISY environment.
tmorse305 Posted April 11, 2022 Posted April 11, 2022 I should be tagged with an "assist" not the solution. That goes to @io_guy for developing the app for all of us!!
Ed Sybesma Posted April 12, 2022 Author Posted April 12, 2022 1 hour ago, tmorse305 said: I should be tagged with an "assist" not the solution. That goes to @io_guy for developing the app for all of us!! Interesting. I would not have known that from the thread on this topic. Thank you for making it known and @io_guy for "making it".
Recommended Posts