bipto Posted January 1, 2018 Posted January 1, 2018 Prior to the upgrade I had nodes for Indoor and Outdoor temp; after the NodeLink and NodeDef files upgrade I noticed that I had a new "Space Temp" node with a value corresponding to the indoor temp, and that the original Indoor and Outdoor nodes no longer had values. There are no errors in the NodeLink log, and all other values on the thermostat node appear to be correct and updating properly. The only other oddity I notice is that on the NodeLink Web Interface thermostat node page I see three sensors listed - "Space Temp" which shows the indoor temp value, "Outdoor" which displays a seemingly correct outdoor temp value, and "Sensor 00" which displays no value at all... Not sure whether this may be a bug or I screwed up somehow, but any help / suggestions would be much appreciated!
larryllix Posted January 1, 2018 Posted January 1, 2018 Prior to the upgrade I had nodes for Indoor and Outdoor temp; after the NodeLink and NodeDef files upgrade I noticed that I had a new "Space Temp" node with a value corresponding to the indoor temp, and that the original Indoor and Outdoor nodes no longer had values. There are no errors in the NodeLink log, and all other values on the thermostat node appear to be correct and updating properly. The only other oddity I notice is that on the NodeLink Web Interface thermostat node page I see three sensors listed - "Space Temp" which shows the indoor temp value, "Outdoor" which displays a seemingly correct outdoor temp value, and "Sensor 00" which displays no value at all... Sensors.JPG Not sure whether this may be a bug or I screwed up somehow, but any help / suggestions would be much appreciated! Some things I missed. Make sure you clicked on the update ISY module in NodeLink. A new module is needed, I rebooted my ISY after the update. This always seems to clean things up. I upgraded ISY to v5.0.11b as well as NodeLink and had to re-install my devices.
io_guy Posted January 2, 2018 Posted January 2, 2018 bipto, I've made a number of changes to the sensor nodes in Venstar lately in order to support the wireless sensors. Can you shoot me over a piece of verbose log that shows what NodeLink gets from the Venstar? It appears your nodedef needs updating (the log will tell you this). I'd like to see your log to get info on Sensor 00.
bipto Posted January 2, 2018 Author Posted January 2, 2018 Thanks for the quick replies! @ io_guy - Log PM'd. I assume what you were requesting was verbose tstat log rather than ISY log - if not please let me know and I'll get you what you need. @ larryllix - thanks for the tips - I think my efforts so far have them covered with the exception of the ISY version - I am still on 5.0.10E - hopefully that does not make a difference. Thank again! --Bill
io_guy Posted January 2, 2018 Posted January 2, 2018 This should now be cleaned up on 0.8.9. Check your log after startup, it'll tell you if any Venstar nodes in the ISY are stale (not used anymore) and safe to delete.
bipto Posted January 2, 2018 Author Posted January 2, 2018 I updated and PM'd the resulting log. Note that although there is an "Outdoor" sensor with valid value included in the log, I still do not see a corresponding node from which I can use that value... Please advise. Thanks! --Bill
bipto Posted January 2, 2018 Author Posted January 2, 2018 That's awesome io_guy - thank you so much for figuring this out!
bipto Posted January 3, 2018 Author Posted January 3, 2018 So I installed 0.8.10 and updated to the latest NodeDef files, but unfortunately I don't think we're out of the woods quite yet. Two "Space Nodes" are now added (I had deleted all existing temp nodes prior to this upgrade) - one that maps to n001_tstat_s00, the other to n001_tstat_s01. Both display the same indoor temp value. There is still no node for outdoor temp. The NodeLink Web Interface thermostat node page now shows only one "Space Temp" sensor displaying the appropriate indoor temp - the "Outdoor" and "Sensor 00" entries are now gone. I'll collect a verbose log and PM it to you shortly. Thanks! --Bill
larryllix Posted January 3, 2018 Posted January 3, 2018 Here is my log file for this. (jumped from another thread.) https://forum.universal-devices.com/topic/23246-remote-temp/page-2?do=findComment&comment=230030 Nodelink creates a node with the s01 node name and then tries to write to a node with a s00 node name. Clicking the Install Nodes into ISY fixes this but then you have two nodes, one defunct. logfile_2018-01-02.txt
io_guy Posted January 3, 2018 Posted January 3, 2018 0.8.11 should fix this. I made a change in the last version to only grab the stat info once which reduces the continuously polled http calls from 4 to 3. Unfortunately it didn't save the API version so it would revert to "old firmware API" after the first polling which had Space Temp as s01. Now I save off the API value and also moved the "old firmware API" to s00 just in case.
larryllix Posted January 3, 2018 Posted January 3, 2018 0.8.11 should fix this. I made a change in the last version to only grab the stat info once which reduces the continuously polled http calls from 4 to 3. Unfortunately it didn't save the API version so it would revert to "old firmware API" after the first polling which had Space Temp as s01. Now I save off the API value and also moved the "old firmware API" to s00 just in case. Lookin' real good so far! Awesome. The climate types look good too. I will be able to simplify some of my HVAC programs with this. I have few small error that pops up occasionally. I will try to capture a verbose log of it tomorrow, if I can make it happen again. 2018-01-03 00:35:06 - ISY Error: Object reference not set to an instance of an object. () Another error I was getting a few times appears to be some new parameter that ecobee4 has created. I can't seem to figure a pattern on it, but only every few days. Could be just a comm data error too. Thanks so much!
larryllix Posted January 3, 2018 Posted January 3, 2018 I can create an error from my ecobee4 (node = ecobee1) by selecting the Home and Hold mode on the ecobee webpage or from ISY. This error is reported in NodeLink logs using the wrong node tag name (node reported = ecobee2). Here is the log containing the errosr I created before (without verbose) and after a NodeLink reboot (with verbose). <useless attachment removed>
io_guy Posted January 3, 2018 Posted January 3, 2018 Larry, Gonna need Ecobee verbose turned on for this one, not Venstar. Also, what's the error - I don't see it?
larryllix Posted January 3, 2018 Posted January 3, 2018 Larry, Gonna need Ecobee verbose turned on for this one, not Venstar. Also, what's the error - I don't see it? grrrrrrr... this file got truncated a lot. Nothing left to see in it. I'll have another look at the original paired down to about 450K. EDIT: It seems this damn Chromium browser won't load the whole thing??? More checking
larryllix Posted January 3, 2018 Posted January 3, 2018 OK. My aologies for that screw up. Here is another log grab, Started just before I enabled "Home and Hold:, although I cannot find the error in the log for that event. I do find the event for "resuming Schedule" I think, and marked it with "**********" toward the end of the file. @ 2018-01-03 14:24:51 My ecobee4 is node named [ecobee1] = "GathRm", and my ecobee3 is node named [ecobee2] = "RecRm". [ecobee1] was the stat I created the event on, but reported as [ecobee2] in the error (just a typo?). It ssems like tthe new ecobee4 [ecobee1] = "GathRm" has a new parameter that is causing come confusion to where it goes???? logfile_2018-01-03.txt
larryllix Posted January 3, 2018 Posted January 3, 2018 And you're hiding the log where? See intended attachment post #16. Wow! Too many different computers going for each style of task. LOL
io_guy Posted January 3, 2018 Posted January 3, 2018 Because of Ecobee's "wonderful" cloud API, NodeLink polls the cloud once and then the Master (first Ecobee installed) redistributes the data to the other stats. The ecobee2 error you're seeing is it not liking the forwarded data. It's odd because I compared the restart data to the 2nd data set and there's really nothing changed pertaining to ecobee2 or why it would crap out. Currently no idea, I really need to step through the crash to recreate. Does this happen anytime you change a program/hold on the E4? Also, can you enable verbose data on ecobee2 as well and send the new one so I can compare what ecobee1 sends vs. what ecobee2 receives?
larryllix Posted January 3, 2018 Posted January 3, 2018 Because of Ecobee's "wonderful" cloud API, NodeLink polls the cloud once and then the Master (first Ecobee installed) redistributes the data to the other stats. The ecobee2 error you're seeing is it not liking the forwarded data. It's odd because I compared the restart data to the 2nd data set and there's really nothing changed pertaining to ecobee2 or why it would crap out. Currently no idea, I really need to step through the crash to recreate. Does this happen anytime you change a program/hold on the E4? Also, can you enable verbose data on ecobee2 as well and send the new one so I can compare what ecobee1 sends vs. what ecobee2 receives? Sure. I get an error every time NodeLink reboots and when I turn on the Hold. I first noticed this when I tested the ISY/ NodeLink setpoint change. It forces a Hold. IIRC this error started when I installed the ecobee4 so I think it has some new parameter or format that isn't liked. I'll work on that log tonight later to see if I can slice it into a smaller file. You want ISY verbose also?
io_guy Posted January 3, 2018 Posted January 3, 2018 You can turn off ISY verbose. Odd with the E4, they share the same API code.
bipto Posted January 4, 2018 Author Posted January 4, 2018 Still no joy for me I'm afraid. With the upgrade to 0.8.11 I now no longer see duplicate "Space Temp" nodes - just one that shows the appropriate indoor temp value, but there is still no Outdoor Temp node in the admin console, and no outdoor temp sensor displayed on the NodeLink Web Interface thermostat node page. I have verified that the outdoor sensor value comes through in the Venstar verbose log, but it seems to go no farther... Thanks again io_guy, --Bill
larryllix Posted January 4, 2018 Posted January 4, 2018 You can turn off ISY verbose. Odd with the E4, they share the same API code. I turned on the "Home and Hold" before verbose, during verbose, and no verbose again. I couldn't find the error in the log until I turned it off gain but two showed up in the log, anyway.. logfile_2018-01-03.txt Bipto . Sorry about hijacking this thread on you. I hope this results in some Venstar results for you, also. . io_guy has worked hard and some Venstar improvements have been noted so far.
bipto Posted January 4, 2018 Author Posted January 4, 2018 Bipto . Sorry about hijacking this thread on you. I hope this results in some Venstar results for you, also. . io_guy has worked hard and some Venstar improvements have been noted so far. No worries Larry, I'm glad you did. Our issues sounded similar and I enjoy the lessons learned through troubleshooting... --Bill
io_guy Posted January 4, 2018 Posted January 4, 2018 Still no joy for me I'm afraid. With the upgrade to 0.8.11 I now no longer see duplicate "Space Temp" nodes - just one that shows the appropriate indoor temp value, but there is still no Outdoor Temp node in the admin console, and no outdoor temp sensor displayed on the NodeLink Web Interface thermostat node page. I have verified that the outdoor sensor value comes through in the Venstar verbose log, but it seems to go no farther... Thanks again io_guy, --Bill Sorry about that, was focused on fixing the Space Temp and forgot all about Outdoor. Should be fixed in the next version, just waiting to see if I can figure out Larry's ecobee issue before releasing.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.