Posted February 28, 20178 yr Just installed nodelink and appreciate the effort and sharing. Firmware 5.0.8 On my nodlink console, at boot it tells me I need to update nodesetup.zip on isy. However, I don't know where to get the updated zip file. The only link to this file I have found is in the instruction sheet found here http://automationshack.com/Files/NodeLink_Setup.pdf which is the one I used. Also, what can I do with these nodes now? They show up in my main console and the status of the nodes shows up on the summary page when I click the folder on the left tree. But individually clicking on a node brings up a blank page on the right window. Should I be getting something on that screen? Like the status of the inputs/outputs and an on/off for the outputs? Also, the nodes don't show up as devices in programming. Should I see them there? I created a test scene and dropped one of the outputs into that scene. It only gave me an option to be a responder. I was able to turn the output on/off by turning the scene on/off. But, when I click on the scene, the scene details in the right window is empty. Perhaps all of this is fixed by having the correct zip file? Thanks, EDIT: I tried deleting the whole thing and starting over. Same result, except, now when I click on the individual node in the main tree, on the right window I get on/off/query/etc buttons at the bottom of the page. And in the middle section I get "beep duration" and "backlihgt" options. The status spot in the upper left is blank. Summary page of all nodes in the folder still shows the status of each node like before. Regarding programs, still nothing there. EDIT2: Restarted admin console. Now clicking on individual devices in the left tree brings up different menu. On/off buttons gone, status now says "off" in upper left (even if on). "backlight" is only option in the middle of page. It looks like a kpl menu with button grouping options at the bottom. The summary page when I click on the folder in the left tree didn't change. Edited February 28, 20178 yr by apostolakisl
February 28, 20178 yr See the nodelink mgt page on your installation on port 8090 by default, Devices page: The link to the current zip is there. Hope this helps. -Xathros Edited February 28, 20178 yr by Xathros
February 28, 20178 yr Author See the nodelink mgt page on your installation on port 8090 by default, Devices page: Screen Shot 2017-02-28 at 4.07.11 PM.jpg The link to the current zip is there. Hope this helps. -Xathros Thanks. That is the same link as on the pdf instructions and is the one I installed. So i don't know what is up with that. Here is my log 2017-02-28 15:15:54 - ISY NodeLink Server v0.6.8 started 2017-02-28 15:15:54 - ISY resolved to 192.168.1.9 2017-02-28 15:15:54 - Web config server started (http://192.168.1.71:8090) 2017-02-28 15:15:54 - ISY Node Server config detected (profile 2) 2017-02-28 15:15:55 - Warning: nodesetup.zip file needs updating in ISY 2017-02-28 15:15:55 - Auto-Update: Checking for program update... 2017-02-28 15:15:55 - Auto-Update: No web update available 2017-02-28 15:15:55 - Relay Server: Started on port 2405 Edited February 28, 20178 yr by apostolakisl
February 28, 20178 yr Thanks. That is the same link as on the pdf instructions and is the one I installed. So i don't know what is up with that. Sorry, should have read your whole post before I replied. Click the Install Node button on the page for the node server you configured then RESTART (Power cycle) the ISY - Twice if necessary. The blank nodes is the ISY not fully loading the nodes from my experience. Restart fixes that after initial install. There is another condition that I see with the admin console where it will not display statuses for anything Non-Insteon and can affect these nodes as well. When this happens, the Icons in the AC for ZWave devices will appear as the basic lightbulb icon rather than the appropriate icon for the device/node. Restart the AC until you see the correct icons and status is displayed. Based on your description, I believe just restarting the ISY will resolve the problem for you. -Xathros Edited February 28, 20178 yr by Xathros
February 28, 20178 yr Author Sorry, should have read your whole post before I replied. Click the Install Node button on the page for the node server you configured then RESTART (Power cycle) the ISY - Twice if necessary. -Xathros I did a remote reboot and now it is like it was originally. When I click on any individual node in the tree on the left, the right window is just blank. No buttons or status or anything. The summary page still reports status.
February 28, 20178 yr I did a remote reboot and now it is like it was originally. When I click on any individual node in the tree on the left, the right window is just blank. No buttons or status or anything. The summary page still reports status. For Nodelink nodes or Insteon as well? -Xath
February 28, 20178 yr Author For Nodelink nodes or Insteon as well? -Xath Just nodelink. No problems with anything else. I'm not sure all the functions I am supposed to be getting here. Are you using the CAI webcontrol board with nodelink or are you doing something else?
February 28, 20178 yr Just nodelink. No problems with anything else. I'm not sure all the functions I am supposed to be getting here. Are you using the CAI webcontrol board with nodelink or are you doing something else? On my production ISY running 5.04 I have Nodelink 0.6.8 with CAI, ISY Data and Milight node servers active. On my testbed running 5.0.8 I have nodelink 0.6.8 with Milight and ISYData node servers active. For me, the install nodesetup.zip, click install nodes buttons, restart ISY was the magic that got it working. I would recommend doing the above in order again. You are close and you are not the first to be in this place. Anything useful in the nodelink log output? -Xath Edited February 28, 20178 yr by Xathros
February 28, 20178 yr Author On my production ISY running 5.04 I have Nodelink 0.6.8 with CAI, ISY Data and Milight node servers active. On my testbed running 5.0.8 I have nodelink 0.6.8 with Milight and ISYData node servers active. For me, the install nodesetup.zip, click install nodes buttons, restart ISY was the magic that got it working. I would recommend doing the above in order again. You are close and you are not the first to be in this place. Anything useful in the nodelink log output? -Xath What CAI functions should I be seeing? 1) Status of nodes as program trigger? 2) Direct execution of output changes in programs (as opposed to within a scene) 3) Controllers of scenes? Thanks.
February 28, 20178 yr What CAI functions should I be seeing? 1) Status of nodes as program trigger? 2) Direct execution of output changes in programs (as opposed to within a scene) 3) Controllers of scenes? Thanks. Yes, Don't Understand the Question and (EDIT: Yes, I can control the WC8 outputs from the AC and programs via nodelink) maybe but I haven't tested as scene controller. -Xath Edited February 28, 20178 yr by Xathros
February 28, 20178 yr Author Yes, Don't Understand the Question and (EDIT: Yes, I can control the WC8 outputs from the AC and programs via nodelink) maybe but I haven't tested as scene controller. Screen Shot 2017-02-28 at 4.44.27 PM.jpg -Xath mine looks nothing like yours. The whole structure of the device and sub-nodes is all wrong. Definitely something wrong here.
February 28, 20178 yr mine looks nothing like yours. The whole structure of the device and sub-nodes is all wrong. Definitely something wrong here. That looks to me like nodesetup.zip needs to be installed again then reboot the ISY. I assume you have checked the node server / configure menu and double checked the host name/address for the nodelink machine? I called my nodelink profile "isylink". Here is my configuration for example: -Xath Edited February 28, 20178 yr by Xathros
February 28, 20178 yr Author That looks to me like nodesetup.zip needs to be installed again then reboot the ISY. I assume you have checked the node server / configure menu and double checked the host name/address for the nodelink machine? I called my nodelink profile "isylink". Here is my configuration for example: Screen Shot 2017-02-28 at 5.01.32 PM.jpg -Xath I did the same setup.
February 28, 20178 yr Author Just deleted it all off of ISY. Power cycled, downloaded everything, installed everything, power cycled Result No change.
February 28, 20178 yr Author Still have that error about nodesetup needing to be updated also. My suspicion is that something with 5.0.8 is incompatible.
February 28, 20178 yr Well, I'm running on 5.0.8 with it just fine but I did migrate from 5.0.4 with it already installed. -Xathros
February 28, 20178 yr Author Well, I'm running on 5.0.8 with it just fine but I did migrate from 5.0.4 with it already installed. -Xathros ???? Maybe you are using a different nodesetup file?
February 28, 20178 yr ???? Maybe you are using a different nodesetup file? Possibly but I have updated it each time io_guy indicated that we needed to. Are you running nodelink 0.6.8? I will see if I still have the most recent zip in my downloads and share it with you if I do. EDIT: Looks like the last update was prior to my last cleanup. I'll check at the office tomorrow to see if I might have a copy there. -Xathros Edited March 1, 20178 yr by Xathros
March 1, 20178 yr Author Possibly but I have updated it each time io_guy indicated that we needed to. Are you running nodelink 0.6.8? I will see if I still have the most recent zip in my downloads and share it with you if I do. EDIT: Looks like the last update was prior to my last cleanup. I'll check at the office tomorrow to see if I might have a copy there. -Xathros 0.6.8 yes.
March 1, 20178 yr mine looks nothing like yours. The whole structure of the device and sub-nodes is all wrong. Definitely something wrong here. This looks suspiciously like the problem with node servers that I'm having, and it appears that the problem is in the ISY, not Nodelink. See this Polyglot thread for more info.
March 1, 20178 yr Author This looks suspiciously like the problem with node servers that I'm having, and it appears that the problem is in the ISY, not Nodelink. See this Polyglot thread for more info. Your post 78 and its screen shot look a lot like mine. It sounds like a factory reset and rebuild the entire system to fix? The fact that nodelink recognizes that there is a problem . .. it says "Warning: nodesetup.zip file needs updating in ISY" must mean something useful. I deleted everything from all the nodeserver spots and started over using slot 1. But still same thing. Before I used slot 2. Edited March 1, 20178 yr by apostolakisl
March 1, 20178 yr Your post 78 and its screen shot look a lot like mine. It sounds like a factory reset and rebuild the entire system to fix? The fact that nodelink recognizes that there is a problem . .. it says "Warning: nodesetup.zip file needs updating in ISY" must mean something useful. I deleted everything from all the nodeserver spots and started over using slot 1. But still same thing. Before I used slot 2. Yes, your screenshot is what tipped me off. I can add node servers in every slot but slot 1 (though they still won't work - I can't add anything to slot 1). I even get data from Nodelink in the logs (see screenshot), just nothing usable in the Admin Console (or any other UI, for that matter). A factory reset/rebuild would be the way to resolve this, as a restore won't work. I would have done this long ago if I hadn't undertaken a major remodel between 5.0.4 and 5.0.8, where I added a slew of new devices, programs, scenes, etc. When the 5.x.x series is out of Alpha and into Beta, I'll file a support ticket to see if UDI can fix it (if not otherwise fixed by then). If they can't fix my system, then I'll quit being lazy and just rebuild it, but I'm really dragging my feet on that.
March 1, 20178 yr Agreed, looks like an ISY issue. Your node list looks fine. Not seeing anything under each node points to the zip file not being loaded by the ISY correctly. On startup NodeLink compares the ISY's internal node config to the nodesetup.zip. Obviously yours don't match. Edited March 1, 20178 yr by io_guy
March 1, 20178 yr Author Agreed, looks like an ISY issue. Your node list looks fine. Not seeing anything under each node points to the zip file not being loaded by the ISY correctly. On startup NodeLink compares the ISY's internal node config to the nodesetup.zip. Obviously yours don't match. OK. Not sure what to do about this. Asked for help from UD but refused secondary to alpha firmware not supported.
March 2, 20178 yr OK. Not sure what to do about this. Asked for help from UD but refused secondary to alpha firmware not supported. I haven't tried to file a support ticket for alpha firmware, as I figured that would be the response. FWIW, in the release announcement for 5.0.7, UDI included this line, which makes me think/hope they have an active ticket open on this: Cannot recreate reported problems: 0000314 – Node server disappears after restart My impression is that node servers are an important piece of UDI's development strategy, but since we're still in alpha and that only a small percentage of folks are reporting this problem, it's lingering on the bug list. I'm betting that UDI will fix this eventually, which is why I haven't rebuilt my system to solve it myself. So far, it's just an inconvenience to me, not a calamity, so I'm patient.
Archived
This topic is now archived and is closed to further replies.