Xathros Posted May 24, 2016 Posted May 24, 2016 Hello io_guy, Just upgraded to NL 0.5.0 and while its working nicely with the ISY, I've lost the ability to manage the CAI webcontrol device as the web console returns a 404 for cai.htm (I named the CAI Webcontrol device cai). It worked initially for configuration but after a restart now I get a 404. I deleted and recreated the CAI device and was able to configure it again up until I restarted Nodelink. Thoughts? Thanks. -Xathros
io_guy Posted May 24, 2016 Posted May 24, 2016 Can't reproduce it here, my guess is it's a decoding error when trying to parse the CAI data. Anything showing up in the log? Can you send me the return from your webcontrol webpage (/api/status.xml)? I don't have a CAI anymore - mine broke.
Xathros Posted May 24, 2016 Author Posted May 24, 2016 The log looks to be normal activity. All of the inputs, temps, heartbeat and outputs are working all the way through to the ISY just fine. Just can't go back and change user/pass, IP address or logging option for the WC8 once I have configured and restarted NL. Not a major problem as it's easy enough to delete and recreate if I need to change one of those. Here is the output: Xathros_CAI_status_xml.txt -Xathros
larryllix Posted May 24, 2016 Posted May 24, 2016 The log looks to be normal activity. All of the inputs, temps, heartbeat and outputs are working all the way through to the ISY just fine. Just can't go back and change user/pass, IP address or logging option for the WC8 once I have configured and restarted NL. Not a major problem as it's easy enough to delete and recreate if I need to change one of those. Here is the output: Xathros_CAI_status_xml.txt -Xathros What does NodeLink do for the WC8? I already have all the data being stuffed into ISY via REST. What am I missing?
Xathros Posted May 24, 2016 Author Posted May 24, 2016 What does NodeLink do for the WC8? I already have all the data being stuffed into ISY via REST. What am I missing? Nothing that you can't do that way but makes the WC8 I/O native ISY nodes: Temp2High - [ID 00A3][Parent 009A] If '0_NodeServers / Nodelink Nodes / WebControl8 / Climate' Temperature 2 > '$i.TEMP.2.HI Index' Then $i.TEMP.2.HI = '0_NodeServers / Nodelink Nodes / WebControl8 / Climate' Temperature 2 $i.TEMP.2.HI Init To $i.TEMP.2.HI Else - No Actions - (To add one, press 'Action') -Xathros
larryllix Posted May 24, 2016 Posted May 24, 2016 Thanks for those photos and words. The screenshots ay it all. Interesting! How does NodeLink hook into the WC8? There must be some setup I have never paid attention to, so far.
io_guy Posted May 24, 2016 Posted May 24, 2016 Xathros, Couldn't reproduce by forcing in your xml file. I'll put additional error handling (on webpage creation) in the next version so hopefully that will help figure this out. Larry, No special setup, it uses the CAI API. It's also useful for older firmware CAIs that don't have REST calls, or if someone doesn't want to add code to the CAI to keep it a little more stable.
Xathros Posted May 25, 2016 Author Posted May 25, 2016 Xathros, Couldn't reproduce by forcing in your xml file. I'll put additional error handling (on webpage creation) in the next version so hopefully that will help figure this out. Larry, No special setup, it uses the CAI API. It's also useful for older firmware CAIs that don't have REST calls, or if someone doesn't want to add code to the CAI to keep it a little more stable. Thanks. I'll follow up again after the next version drops. So far, other than that, it's working like a champ! -Xathros Sent from my iPhone using Tapatalk
io_guy Posted May 29, 2016 Posted May 29, 2016 Just pushed version 0.5.1, if you have NodeLink set to auto-update a click of the restart button will get it. Tim was having the same 404 error on Webcontrol, appears to work now. Hopefully this fixes yours.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.