March 8, 20178 yr Author Curiously, ISY has now seemingly at least partially fixed things . . . spontaneously. I didn't do anything and now it is showing the correct symbols next to each CAI node (like a thermometer next to the temp) and if you click on the node, it shows appropriate stuff, like an on/off button for an output. However, it still not putting all the nodes under the main node of the CAI itself. I also can not add to scenes as a controller, only responder. Perhaps that is normal? But I would think that the on/off status of an output should be usable as a controller.
March 8, 20178 yr Curiously, ISY has now seemingly at least partially fixed things . . . spontaneously. I didn't do anything and now it is showing the correct symbols next to each CAI node (like a thermometer next to the temp) and if you click on the node, it shows appropriate stuff, like an on/off button for an output. However, it still not putting all the nodes under the main node of the CAI itself. I also can not add to scenes as a controller, only responder. Perhaps that is normal? But I would think that the on/off status of an output should be usable as a controller. Right click on the primary Nodelink node and select Group devices
March 8, 20178 yr Author Right click on the primary Nodelink node and select Group devices Ahhh, so obvious yet I missed it. Thanks. I am now able to use CAI nodes in programs. I have no idea why this seems to have fixed itself. I did nothing except shut down the node server and then a couple days later I noticed the nodes on ISY admin panel changed. Is it correct that CAI nodes can not be added to scenes as controllers? It would be nice to have an input control a scene.
March 8, 20178 yr Ahhh, so obvious yet I missed it. Thanks. I am now able to use CAI nodes in programs. I have no idea why this seems to have fixed itself. I did nothing except shut down the node server and then a couple days later I noticed the nodes on ISY admin panel changed. Is it correct that CAI nodes can not be added to scenes as controllers? It would be nice to have an input control a scene. Glad I could help. I'm not sure about scene support. I haven't got anything tied to my CAI digital inputs to test with. It was said that mixed protocol scenes was part of the new 5.x framework and I believe they are actively working on that aspect now. All of that said, its easy enough to test: See if the console will allow you to add a CAI input to a scene as a controller. If so, add a responder, configure and test. -Xathros
March 8, 20178 yr Author Glad I could help. I'm not sure about scene support. I haven't got anything tied to my CAI digital inputs to test with. It was said that mixed protocol scenes was part of the new 5.x framework and I believe they are actively working on that aspect now. All of that said, its easy enough to test: See if the console will allow you to add a CAI input to a scene as a controller. If so, add a responder, configure and test. -Xathros Yeah, that is what I did. It only gives responder as an option. Not sure if this is proper behavior, or if my suspect implementation of the node server is still partially broken. I was hoping that someone who knows for sure what the node server is capable of can tell me for certain that the lack of "controller" option is to be expected.
March 8, 20178 yr Yeah, that is what I did. It only gives responder as an option. Not sure if this is proper behavior, or if my suspect implementation of the node server is still partially broken. I was hoping that someone who knows for sure what the node server is capable of can tell me for certain that the lack of "controller" option is to be expected. I think you should post a question in the 5.0.8 thread for Chris and Michel, Don't think they are monitoring this thread. -Xathros Edited March 8, 20178 yr by Xathros
March 8, 20178 yr Author In Summary 1) Nodelink I think is working as it supposed to. It has the correct icons and appropriate buttons (on/off for outputs, but not inputs, etc) 2) It still says I need to update .zip file at boot even thought it seems like it is proper. 3) None of the nodes can be added as scene controllers, only responders. This may be normal. 4) The nodes show up both as "if's" and "then's" in ISY programs as expected. Assuming point 3 is normal, then all is as it should be, except error message telling me I need to update zip file.
March 8, 20178 yr In Summary 1) Nodelink I think is working as it supposed to. It has the correct icons and appropriate buttons (on/off for outputs, but not inputs, etc) 2) It still says I need to update .zip file at boot even thought it seems like it is proper. 3) None of the nodes can be added as scene controllers, only responders. This may be normal. 4) The nodes show up both as "if's" and "then's" in ISY programs as expected. Assuming point 3 is normal, then all is as it should be, except error message telling me I need to update zip file. Where exactly are you seeing this error message? In the ISY console or Nodelink's console output? -Xathros
March 8, 20178 yr Author Where exactly are you seeing this error message? In the ISY console or Nodelink's console output? -Xathros Its at boot on the nodelink server. I copied it to the forum on one of my earlier posts. (post 3) Edited March 8, 20178 yr by apostolakisl
March 8, 20178 yr Its at boot on the nodelink server. I copied it to the forum on one of my earlier posts. (post 3) I just restarted mine and am seeing the same warning. Never noticed it before but its probably been there all along. -Xathros
March 8, 20178 yr Author OK, this is just WTF I logged into my ISY, and the cai node is now all screwed up like it was before. The icons are all back to lightbuls and none of the devices show appropriate controls.
March 9, 20178 yr Author I just restarted mine and am seeing the same warning. Never noticed it before but its probably been there all along. -Xathros Please see post 294 in http://forum.universal-devices.com/topic/20686-release-508-alpha-is-now-available/page-15 I added the blank line at the end of the NLS file and now it all works, no errors. The node server has been running for hours now with not a single error. Edited March 9, 20178 yr by apostolakisl
March 10, 20178 yr Author Update. 24 hours into the addition of the blank line at the end of the NLS file and not a single glitch. It would seem to have been the solution.
March 10, 20178 yr I can also confirm that by adding an extra line (CRLF) to the end of the NLS file got rid of the error message in the Nodelink log about an out of date file. For good measure, I also added an extra line to one of the other two files as well. I think it was the nodedef file. Having said that, I haven't noticed any other issues with Nodelink. It seemed to work fine, I just always saw the out of date nodesetup.zip file warning in the log. Now, that warning is gone. FWIW, I'm still on v0.6.8. Awesome program, by the way! EDIT: Now I see that the icons for the Ecobee thermostat and remote sensors now look like a red thermometer. I think they had been light bulbs before. I honestly hadn't really cared much about the icons but it is nice to have them be correct. Edited March 10, 20178 yr by Toddimus
Archived
This topic is now archived and is closed to further replies.