NodeLink v0.8.0 / ecobee3 - climate type

[io_guy]

Thanks Larry,

I'm away for the next week but I'll dig into this as soon as I get back.

[larryllix]

Thanks Larry,

I'm away for the next week but I'll dig into this as soon as I get back.

Hopefully there is some vacation break in there for you and yours.

[io_guy]

0.8.4 is out.  Hopefully it fixes the state and climate type issues (I found bugs in both).

[larryllix]

0.8.4 is out.  Hopefully it fixes the state and climate type issues (I found bugs in both).

Thanks!

 

Unfortunately it doesn't fix a few some and broke others.

 

Climate Type still  only shows Home, Sleep, and Away and not the custom defined climate types. This hasn't changed AFAICT.

 

Schedule permanantly shows "Schedule" in NodeLink or "Running" in Admin Console  device page and never changes. V8.0 showed these correctly.

 

HVAC State shows "AuxHeat" instead of "Heat" in NodeLink and Admin Console. V8.0 showed these correctly. Since I only use "Idle" this is working OK for now in ISY.

 

 

 

The v8.4 install ISY update feature is very cool, along with the remote ISY reboot. Real step savers!

[io_guy]

AuxHeat is expected, that's what your ecobee is reporting.

 

For the schedule/running (same thing), this would only change when you set the stat to hold. Grab me a hold log if you can.

 

The climate type seems to take a long time to change. In the logs you sent me they only changed once.

[larryllix]

AuxHeat is expected, that's what your ecobee is reporting.

 

For the schedule/running (same thing), this would only change when you set the stat to hold. Grab me a hold log if you can.

 

The climate type seems to take a long time to change. In the logs you sent me they only changed once.

Yeah. Great stat but this API is crazy. They change the terminology and do weird things. LOL

 

I reset my preferences (schedules and location) on the ecobee3 stat and I think it crashed NodeLink's Ethernet driver. All devices reported errors. I should have captured the errors but I am about to try it again to prove it was related or not.

 

EDIT:Nope. Second stat (ecobee4) reset without any problems in NodeLink. 

[larryllix]

AuxHeat is expected, that's what your ecobee is reporting.

 

For the schedule/running (same thing), this would only change when you set the stat to hold. Grab me a hold log if you can.

 

The climate type seems to take a long time to change. In the logs you sent me they only changed once.

Hold until 11 PM logs!

Regular poll grab and a NodeLink reboot initialiasation.

 

Hold until 11 PM.txt

 

Hold until 11 with reboot.txt

[io_guy]

Nothing in your first log, NodeLink can't do what it doesn't see.

 

Holds are based off "events". There are none in your first log.

[larryllix]

Nothing in your first log, NodeLink can't do what it doesn't see.

 

Holds are based off "events". There are none in your first log.

OK. I think I grabbed one this time. I thought they would be a continuous ststus. Sorry.

 

hold.txt

[io_guy]

All i can guess is it's something in the code because you have two stats.

 

I need a bigger log that includes the ISY debug info too (checkbox on the NodeLink log page) to see what is and isn't being sent.

[larryllix]

All i can guess is it's something in the code because you have two stats.

 

I need a bigger log that includes the ISY debug info too (checkbox on the NodeLink log page) to see what is and isn't being sent.

Strangely enough I seem to be getting updates on heat state etc. now in a resonable time (3-4 minutes), from the few state changes  I forced this morning???

 

The cimate type is back to just Home or Sleep (without Nodelink reboot). Smart2 schedule was active since 3 AM and at 8:30 AM still indcated "sleep". Rebooting Nodelink seems to get all the climate types through to ISY but not regular polling.

 

The heat state = AuxHeat is too bad but I can just detect the negative "Idle" anyway.

 

I'll be away for the weekend until I can stare at it and create more simulation captures.

 

Thanks!!!

[io_guy]

Why can't you just use the auxHeat variable?

State updates every 3 minutes from the stat. Almost everything else is min 15 minutes.

[larryllix]

Why can't you just use the auxHeat variable?

State updates every 3 minutes from the stat. Almost everything else is min 15 minutes.

I am using the same variable but with the not 'idle' status detection.

 

Away now but IIRC I am detecting HVAC running period and assuming whether heat or cool by season.

 

Later if ecobee ever corrects the report it should still work

 

Sent from my SGH-I257M using Tapatalk

[larryllix]

All i can guess is it's something in the code because you have two stats.

 

I need a bigger log that includes the ISY debug info too (checkbox on the NodeLink log page) to see what is and isn't being sent.

Trying to get the logs for you. I turned on the Log for the ecobee4 stat, all was happening.

I turned on the log to file and log for ISY and NodeLink wiped my config.xml file.

 

NodeLink forgot ISY IP address so I  reset it but devices all gone. Checked log file in dir, and only an ISY connect few lines inside. config.xml only contains ISY setup lines. 

 

Rebuilding NodeLink from fresh now.

[larryllix]

I started with the ecobee4 stat from install logging. Then I added an ecobee3, a Venstar, and finally the MiLight bridge node you did. You should see all that in the log file.

 

The file is getting huge so I zipped it but captured about 30 minutes worth.

 

Each time I clicked on the NodeLink "Main" tab it appeared to hang again but NodeLink seemed intact so I think NodeLink was just so busy sorting out the log file for view, my browser threw errors (500).

 

Please note that maybe once per day the new ecobee4 throws an error linethat looks like some new parameter not handled by ecobee4. I will try to capture one of those but there is no pattern I can detect yet.

 

When I'm in Hold until 11 PM mode it reflects the Hold, and the Climate Type shows "N/A". Seems fair as the schedule is not in effect at that point in time.

 

Thanks again!!

 

 

 

logfile_2017-12-04.zip

[io_guy]

Larry,

What am I looking for in this log?

[larryllix]

Larry,

What am I looking for in this log?

LOL. See post 35.

 

 

 

Sent from my SGH-I257M using Tapatalk

[io_guy]

So a quick look at the log shows Gathering Room on temp hold and Rec Room not.

 

And here is where NodeLink adds it to the queue:

2017-12-04 21:24:55 - ISY: Variable ecobee1-CLISMD added to queue (Val: 1, QS: 20)

 

And here is where it successfully writes to the ISY:

2017-12-04 21:24:57 - ISY: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_ecobee1/report/status/CLIMD/1/67)

[larryllix]

Loaded NdeLink v8.8 and ISY v5.0.11B and after some update fights (missed the update option in NdeLink..) it all looks really good.

 

 

The climate type shows smart3 to smart9 available in ISY programs.

However, smart1 and smart2 are MIA. I find NodeLink scraping smart1 correctly but ISY showing this as smart3. Looks like a list misallignment only.

 

 

Nice job io_guy!

[io_guy]

I thought you told me smart started at 3?

 

Thought 0-2 were occupied by home/away/sleep.

[io_guy]

No method exists in the ISY API for me to use adaptive labels.  I'd have to adjust the nodedefs based on thermostat feedback, which is out of the question.

[larryllix]

OK. Looks like v0.9.0 cleaned all this up very nicely!

 

Climate types look awesome and are controllable with any errors for the night.

The setpoint Temporary control and reporting from/to  ISY works like a charm now...Awesome!

The setpoint Hold control and reporting from/to ISY worked a few fixes ago! Awesome!

 

You hard work is really appreciated here. 

 

 

I only have the one small problem that popped up again. This appear to be just a webpage GUI problem, that only happens when I select the ecobee2 webpage. It throws an HTTP 500 error.

It does not seem to affect any data passing through and clears itself in less than an hour, with the webpage being available again. It did not error last night after v9.0 installation.  NodeLink just seems to forget the webpage should exist.

 

 

Every error line was created by me clicking on the ecobee2 webpage. The error does not appear without human intervention. Again, I checked ISY and the heartbeat and data appear to be changing.

 

2018-01-10 21:15:25 - ISY NodeLink Server v0.9.0 started

2018-01-10 21:15:25 - Mono version: 5.2.0.215 (tarball Mon Aug 14 16:25:12 UTC 2017)

2018-01-10 21:15:26 - ISY resolved to 192.168.0.161

2018-01-10 21:15:26 - Web config server started (http://192.168.0.175:8090)

2018-01-10 21:15:27 - ISY Node Server config detected (profile 1)

2018-01-11 08:12:57 - Error Processing Request: /ecobee2.htm (Index was outside the bounds of the array.)

2018-01-11 08:13:09 - Error Processing Request: /ecobee2.htm (Index was outside the bounds of the array.)

2018-01-11 08:13:24 - Error Processing Request: /ecobee2.htm (Index was outside the bounds of the array.)

2018-01-11 08:13:51 - Error Processing Request: /ecobee2.htm (Index was outside the bounds of the array.)

2018-01-11 08:18:21 - Error Processing Request: /ecobee2.htm (Index was outside the bounds of the array.)

2018-01-11 08:19:23 - Error Processing Request: /ecobee2.htm (Index was outside the bounds of the array.)

2018-01-11 08:23:00 - Error Processing Request: /ecobee2.htm (Index was outside the bounds of the array.)

2018-01-11 08:23:39 - Error Processing Request: /ecobee2.htm (Index was outside the bounds of the array.)

2018-01-11 08:23:48 - Error Processing Request: /ecobee2.htm (Index was outside the bounds of the array.)

2018-01-11 08:24:44 - Error Processing Request: /ecobee2.htm (Index was outside the bounds of the array.)

2018-01-11 08:26:19 - Error Processing Request: /ecobee2.htm (Index was outside the bounds of the array.)

2018-01-11 08:29:24 - Error Processing Request: /ecobee2.htm (Index was outside the bounds of the array.)

2018-01-11 08:37:17 - Error Processing Request: /ecobee2.htm (Index was outside the bounds of the array.)

2018-01-11 08:52:10 - Error Processing Request: /ecobee2.htm (Index was outside the bounds of the array.)

[io_guy]

Larry, does it happen every time you select it?

[larryllix]

Larry, does it happen every time you select it?

No! I worked fine for the first few views after v0.9.0 installation, last night, five seconds after you announced it.

 

This morning, as shown, the webpage error'd  500 every time over about 30 minutes or so, tested?

 

I went out for the day and tonight it works fine again with half a dozen reloads of the page.

 

I have never detected any data loss or weirdness in the ISY nodes. Heartbeat always worked checked by  my heartbeat monitoring notification programs.

 

 

I ran a bunch of this through some testing and all end to end functions work great now. hmmmmm..... I always used ecobee1 though.

This appears to be just a GUI error maybe between ecobee2 data update gaps. It seems to indicate some process goes to sleep and NodeLink  takes it off an internal device list. Always shows in the device list page when viewed, though..

[larryllix]

OK. The ecobee2 webpage is throwing error 500  again, this morning.

 

The common element from yesterday may be the climate type is "Home" again, from 7:00 AM to 5:00 PM each day.

 

 

UPDATE: The webpage access has returned while the same climate type "Home" is present on ecobee2. 10:30 AM