Installed OK

NodeLink now reports all schedule segments properly as "climate types" to ISY.

ISY now offers all "climate types' as available on programming pulldown menus.

 

I cannot get "climate types" selections to affect anything in ecobee3. All schedule segmentsstatus  reporting is good and accurate but the control does  not function here. I tried with schedule running and schedule Hold.  I have no way to control Home/Away mode now.

The schedule change does not show up on the ecobee3 app either.

 

Schedule mode On/Off works and reports fine. Hold On/Off works and reports fine.

 

Thanks!

 

 

Yep, my bad. I'll get it in the next version.

Yep, my bad. I'll get it in the next version.

Thanks!!! Glad it was found.

Hi @io_guy ! Any plans on making a home-assistant node server?

 

 

Sent from my iPhone using Tapatalk

Hi @io_guy ! Any plans on making a home-assistant node server?

Not quite sure what you mean? HA already has Insteon (ISY) support and native device support for hundreds of devices.

Not quite sure what you mean? HA already has Insteon support and native device support for hundreds of devices.

I mean, it would be nice to see HA devices in the ISY!

Not gonna happen by me. That's just another layer to go wrong, and i hate python.

 

The V5 node layer would be a nightmare to dynamically support whatever a user has in their HA setup.

Yes, if there are specific devices supported by HA that don't have a node server from io_guy or. one of the Polyglot devs, then request one. But for the most part io_guy is more willing to support devices he doesn't actually use [emoji3] But you never know...

 

Sent from my Pixel XL using Tapatalk

Yep, my bad. I'll get it in the next version.

Tried 8.1. It seems NodeLink gets the climate type right now, but ISY only shows two climate Types. "Home" and all other statuses show "Away".. In NodeLink all but "Home" show "N/A". I guess this displays in admin console as "Away"

 

The controls seems to work from ISY programs to the actual stat, but I thought the statuses were working before and now broken. LOL

 

From a test ISY program I managed to set the stat to "Night" schedule OK (as well as other schedule segments) but it becomes permanent and the internal schedue can never change it.

Edited October 19, 20178 yr by larryllix

I need some logs, it's working on my setup.

 

Also, in the program did you choose permanent or transition for the duration?

Nevermind, I see the issues with the extra climates. This is going to be painful to fix.

Thx for the Input, it would be a non issue for me once ISY z-wave is fixed...here’s hoping!

 

 

Sent from my iPhone using Tapatalk

I am not sure this is going to work. I set the stat to Night schedule "comfort setting"  and it showed on the stat and ecobee app OK, with a hold.

 

In the morning after three time schedule "comfort setting" changes it still showed the same Night "schedule comfort setting", so the changes in "comfort settings" did not release the Hold anyway.

 

Perhaps  you know something about the command structure that can do otherwise, separating the Hold and Schedule segment commands?

 

The schedule "comfort settings" should show on the ISY properly anyway, if it is even possible. This sounds like there may be some quirks here that may not allow this.

 

For now, I just force a temperature on the stat and since it is in the "hold until next schedule activity" it drops out and forgets the forced temperature at that time. It would be nice for ISY not to have to deal with any absolute temperatures and just switch "comfort settings"

 

Thanks again.

Basic Home/Away setting is working for me again with 0.8.2.  Thanks!

Where can I find NodeLink? A seach only reveals topics that refer to NodeLink.

http://forum.universal-devices.com/index.php?/topic/17228-NodeLink:-Latest-Version-v0.8.2

 

Sent from my Pixel XL using Tapatalk

Jimbo, thanks. But I'm staying with ISY v4+ for now. I wasn't aware v5+ was required.

Basic Home/Away setting is working for me again with 0.8.2. Thanks!

For the benefit of others, if you were setting home/away in programs with earlier versions of NodeLink, check your programs. The new climate type changes may have made the Ecobee-related lines incomplete and nonfunctional. Easy to fix, but it may go unnoticed.

NodeLink only shows the last Climate Type at the time of last reboot. Hours after a schedule change it still displays the reboot schedule segment. 

 

When I set the climate type to anything the stats schedule locks permanently to it still and never returns to the schedule. The settng command fully works from ISY programs and thn NodeLink shows what ws set but not when the change is done from the scheduler or manually.

When I set the climate type to anything the stats schedule locks permanently to it still and never returns to the schedule. The settng command fully works from ISY programs and thn NodeLink shows what ws set but not when the change is done from the scheduler or manually.

I have absolutely no clue what you're talking about. What's a scheduler? What locks permanently?

I have absolutely no clue what you're talking about. What's a scheduler? What locks permanently?

Sorry. These stats use their own language for sure.

 

I guess you have used a different nomenclature "climate type" for the field name. The ecobee3 app only shows the schedule segments as

"Comfort Settings" and I am not sure what the API codes come down labelled as from the schedule table.

 

You posted this may be impossible! The climate types display a strange behaviour. The "Home" and "Sleep" climate types seem to update more quickly but the others, climate types "smart3",  "smart4" etc.. seem to not update for hours, or never, for some reason. My stat changes over to "sleep" at 11:00 PM, to "smart3" at 3:00 AM, and "smart4" at 6:00 AM. At t 9:00AM every  morning, ISY and NodeLink / ecobee page it is still showing "sleep" as the climate type.

So that field is working mostly, but somehow selective in updating. I am not sure it ever updates to "smart3" or "smart4" even though on a NodeLink reboot it always updates immediately on reboot.

 

 

Unfortunately, in the v0.8.x updates a new problem has cropped up. The "Heat/Cool" state now shows "Idle" and never changes. This was functioning until v0.8.0 or v0.8.1. I am not sure when it quit working, as I haven't been watching my HVAC reported runtimes as closely, with the weather changeover from A/C to Heating and back so often needed in this Ontario season.

 

Thanks again. I hope some of this is more comprehensive.

Can you grab some logs of these when you get a chance?

Can you grab some logs of these when you get a chance?

See if these help. They should throw a lot of data back at you!

 

It would seem a complete (as per NodeLink reboot) poll would be needed every 15 minutes after the finest resolution (15 minutes)  possible schedule change  to pick up any climate (schedule) change. Possibly 18, 33, 48, &  03 minutes after each hour to allow for clock syncro errors. ecobee3 stat only has selectable 15 minute block resolution for schedule change clicks.

 

Would it help if you gave me a PIN and I installed that permission into my access?

I thought you had an ecobee3 but it may not be set up for these extra schedule "comfort settings" = climate types.

 

Heat Idle, schedule smart4.txt

 

Heat On, schedule smart4.txt

 

Heat On, regular poll.txt

You posted this may be impossible! The climate types display a strange behaviour. The "Home" and "Sleep" climate types seem to update more quickly but the others, climate types "smart3",  "smart4" etc.. seem to not update for hours, or never, for some reason. My stat changes over to "sleep" at 11:00 PM, to "smart3" at 3:00 AM, and "smart4" at 6:00 AM. At t 9:00AM every  morning, ISY and NodeLink / ecobee page it is still showing "sleep" as the climate type.

So that field is working mostly, but somehow selective in updating. I am not sure it ever updates to "smart3" or "smart4" even though on a NodeLink reboot it always updates immediately on reboot.

This appears to be an API flaw. Polling is not based on 15min, it's based on when the thermostat revision changes. A program change is supposed to trigger this:

https://www.ecobee.com/home/developer/api/documentation/v1/operations/get-thermostat-summary.shtml

 

Give me a decent length of log file (not startup) spanning a climate change so I can see if the thermostat revision is actually changing.

 

Unfortunately, in the v0.8.x updates a new problem has cropped up. The "Heat/Cool" state now shows "Idle" and never changes. This was functioning until v0.8.0 or v0.8.1. I am not sure when it quit working, as I haven't been watching my HVAC reported runtimes as closely, with the weather changeover from A/C to Heating and back so often needed in this Ontario season.

What does NodeLink show for HVAC State? It's the status update that is used for state, such as:

"statusList": ["311079071638:auxHeat1,fan,humidifier"]

This indicates AuxHeat1 is on. Let me know if NodeLink shows this.

This appears to be an API flaw. Polling is not based on 15min, it's based on when the thermostat revision changes. A program change is supposed to trigger this:

https://www.ecobee.com/home/developer/api/documentation/v1/operations/get-thermostat-summary.shtml

 

Give me a decent length of log file (not startup) spanning a climate change so I can see if the thermostat revision is actually changing.

 

What does NodeLink show for HVAC State? It's the status update that is used for state, such as:

"statusList": ["311079071638:auxHeat1,fan,humidifier"]

This indicates AuxHeat1 is on. Let me know if NodeLink shows this.

I do not have any auxHeat AFAIK. These info packets from the API are very confusing. The HVAC stat was working fine in v0.7.x, before we started fooling with the  climate types. My HVAC run time reports are broken now. 

 

I got two captures with climate type changes at 3, 6 and 10 AM in these two files. I hope this helps. It seems as if NodeLink would have to keep a complete duplicate shedule table to know what climate type it should be in.   I don't really understand where it is coming from though.

 

Climate changes at 3 and 6 AM.txt

 

Climate change at 10 AM.txt

 

Thanks so much io_guy!