Ecobee: Troubles

[tinkerer]

Hello,

I just purchased and installed an Ecobee4 and decided to try out NodeLink with it.

I am receiving tons of errors (mostly "Request Failed") and none of the changes made on ISY seem to propagate anywhere.  Is it just one way communication from NodeLink to ISY or can the ISY make changes?

I am wondering if there is a listing somewhere of what is and is not functional with NodeLink and Ecobee? 

Ryan

ISY v5.0.14

NodeLink Server v0.9.2

ecobee4 v4.2.0.393

[io_guy]

Everything available in the ISY should work.  Please provide the actual log.

[larryllix]

Hello,
I just purchased and installed an Ecobee4 and decided to try out NodeLink with it.
I am receiving tons of errors (mostly "Request Failed") and none of the changes made on ISY seem to propagate anywhere.  Is it just one way communication from NodeLink to ISY or can the ISY make changes?
I am wondering if there is a listing somewhere of what is and is not functional with NodeLink and Ecobee? 
Ryan
ISY v5.0.14
NodeLink Server v0.9.2
ecobee4 v4.2.0.393

If that Nodelink version is accurate you need to update it.

Sent from my SM-G930W8 using Tapatalk

[tinkerer]

I'm sorry, I just installed NodeLink yesterday.  I missed a digit on the version.  It is v0.9.21.  It should be the latest version as I just downloaded it yesterday.

I would be more than happy to provide logs, but I am a bit new at this.  None of the logs that I can find show anything that seems to indicate a problem to me.

Here is what I've tried:

From the Ecobee Thermostat, I attempt a the following:

1. On the Ecobee Thermostat, I click Setpoint Up.
2. I immediately receive an error dialog box "Request Failed". 
3. I then manually change the heat setpoint up two degrees.
4. The ISY thinks for one second then reverts the dropdown back to the previous temp.
5. I click query.
6. I wait 30 seconds but nothing happens.
7. I click setpoint down.
8. Nothing happens or changes.

Below are the places that I've looked for error logs for the sequence above.

1. I set the Web Display Level in NodeLink to Debug.  Below are the events in Nodelink.

   2018-11-24 10:33:24 - ISY Send: Variable ecobee1_sen1-ST added to queue (Val: 72.5, QS: 1)
   2018-11-24 10:33:25 - ISY Send: Variable ecobee1_sen4-ST added to queue (Val: 75.3, QS: 2)
   2018-11-24 10:33:25 - ISY Send: Variable ecobee1-GV2 added to queue (Val: 1, QS: 3)
   2018-11-24 10:33:25 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_ecobee1_sen1/report/status/ST/72.5/14)
   2018-11-24 10:33:25 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_ecobee1_sen4/report/status/ST/75.3/14)
   2018-11-24 10:33:25 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_ecobee1/report/status/GV2/1/25)
   2018-11-24 10:33:48 - Web Request: /index.htm
   2018-11-24 10:35:17 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><climate enabled="true" locationId="MID_KGRB" rss="http://wx.hamweather.com/?pands=MID_KGRB" lastUpdatedTS="2018/11/24 10:31:43"><Temperature>41 °F</Temperature><Temperature_High>43 °F</Temperature_High><Temperature_Low>37 °F</Temperature_Low><Feels_Like>37 °F</Feels_Like><Temperature_Average>40.4 °F</Temperature_Average><Humidity>93 %</Humidity><Pressure>29.44 inHg</Pressure><Dew_Point>39 °F</Dew_Point><Wind_Speed>6 mph</Wind_Speed><Wind_Direction>SSW</Wind_Direction><Gust_Speed>0 mph</Gust_Speed><Total_Rain_Today>0.26 inches</Total_Rain_Today><Light>63 %</Light><Evapotranspiration>0 inches/day</Evapotranspiration><Irrigation_Requirement>0 inches</Irrigation_Requirement><Water_Deficit_Yesterday>0 inches</Water_Deficit_Yesterday><Elevation>682 </Elevation><Coverage>0</Coverage><Intensity>0</Intensity><Weather_Condition>4</Weather_Condition><Cloud_Condition>5</Cloud_Condition><Average_Temperature_Tomorrow>28 °F</Average_Temperature_Tomorrow><High_Temperature_Tomorrow>34 °F</High_Temperature_Tomorrow><Low_Temperature_Tomorrow>23 °F</Low_Temperature_Tomorrow><Humidity_Tomorrow>76 %</Humidity_Tomorrow><Wind_Speed_Tomorrow>10 mph</Wind_Speed_Tomorrow><Gust_Speed_Tomorrow>22 mph</Gust_Speed_Tomorrow><Rain_Tomorrow>0.01 inches</Rain_Tomorrow><Snow_Tomorrow>0.12 inches</Snow_Tomorrow><Coverage_Tomorrow>3</Coverage_Tomorrow><Intensity_Tomorrow>2</Intensity_Tomorrow><Weather_Condition_Tomorrow>19</Weather_Condition_Tomorrow><Cloud_Condition_Tomorrow>4</Cloud_Condition_Tomorrow><Forecast_Average_Temperature>37 °F</Forecast_Average_Temperature><Forecast_High_Temperature>43 °F</Forecast_High_Temperature><Forecast_Low_Temperature>30 °F</Forecast_Low_Temperature><Forecast_Humidity>89 %</Forecast_Humidity><Forecast_Rain>0.06 inches</Forecast_Rain><Forecast_Snow>0 inches</Forecast_Snow><Forecast_Coverage>3</Forecast_Coverage><Forecast_Intensity>2</Forecast_Intensity><Forecast_Weather_Condition>14</Forecast_Weather_Condition><Forecast_Cloud_Condition>5</Forecast_Cloud_Condition></climate> (climate)
   2018-11-24 10:36:25 - ISY Send: Variable ecobee1_sen2-ST added to queue (Val: 75.2, QS: 1)
   2018-11-24 10:36:25 - ISY Send: Variable ecobee1_sen3-ST added to queue (Val: 72.5, QS: 2)
   2018-11-24 10:36:25 - ISY Send: Variable ecobee1-GV2 added to queue (Val: -1, QS: 3)
   2018-11-24 10:36:25 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_ecobee1_sen2/report/status/ST/75.2/14)
   2018-11-24 10:36:25 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_ecobee1_sen3/report/status/ST/72.5/14)
   2018-11-24 10:36:25 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_ecobee1/report/status/GV2/-1/25)

    

2. For the same event, I went to Tools > Log and exported the log.  The following showed.

   Thermostat / Sun Room	Status	72.5ЉSat 2018/11/24 10:33:48 AM	System	Log	
   Thermostat / Thermostat	Status	75.3ЉSat 2018/11/24 10:33:48 AM	System	Log	
   Thermostat / Ecobee	Custom Control 2	1	Sat 2018/11/24 10:33:48 AM	System	Log

    

3. Under Tools Error Log, I see the following during my attempt.

   Sat 2018/11/24 10:33:16 AM	System	-170001	[HTTP:0-28-5] 10.0.5.0:58261->80	
   Sat 2018/11/24 10:33:16 AM	System	-170001	[HTTP:0-28]: POST[1]-->/services	
   Sat 2018/11/24 10:33:16 AM	System	-170001	<s:Envelope><s:Body><u:GetErrorLog xmlns:u="urn	
   Sat 2018/11/24 10:33:23 AM	System	-170001	[HTTP:0-28-5] 10.0.5.0:58269->80	
   Sat 2018/11/24 10:33:23 AM	System	-170001	[HTTP:0-28]: POST[1]-->/services	
   Sat 2018/11/24 10:33:23 AM	System	-170001	<s:Envelope><s:Body><u:GetDebugLevel xmlns:u="u	
   Sat 2018/11/24 10:33:29 AM	System	-170001	[HTTP:0-28-5] 10.0.5.0:58275->80	
   Sat 2018/11/24 10:33:29 AM	System	-170001	[HTTP:0-28]: POST[1]-->/services	
   Sat 2018/11/24 10:33:29 AM	System	-170001	<s:Envelope><s:Body><u:UDIService xmlns:u="urn:	
   Sat 2018/11/24 10:33:29 AM	System	-170001	[TCP-Conn] -6/-140002, ISY	
   Sat 2018/11/24 10:33:29 AM	System	-170001	[HTTP:0-28-5] 10.0.5.0:58276->80	
   Sat 2018/11/24 10:33:29 AM	System	-170001	[HTTP:0-28]: POST[1]-->/services	
   Sat 2018/11/24 10:33:29 AM	System	-170001	<s:Envelope><s:Body><u:GetLastError xmlns:u="ur	
   Sat 2018/11/24 10:33:29 AM	System	-170001	[HTTP:0-28-5] 10.0.5.0:58277->80	
   Sat 2018/11/24 10:33:29 AM	System	-170001	[HTTP:0-28]: POST[1]-->/services	
   Sat 2018/11/24 10:33:29 AM	System	-170001	<s:Envelope><s:Body><u:ClearLastError xmlns:u="	
   Sat 2018/11/24 10:33:47 AM	System	-170001	[HTTP:0-28-5] 10.0.5.0:58300->80	
   Sat 2018/11/24 10:33:47 AM	System	-170001	[HTTP:0-28]: POST[1]-->/services	
   Sat 2018/11/24 10:33:47 AM	System	-170001	<s:Envelope><s:Body><u:UDIService xmlns:u="urn:	
   Sat 2018/11/24 10:33:47 AM	System	-170001	[TCP-Conn] -6/-140002, ISY	
   Sat 2018/11/24 10:33:48 AM	System	-170001	[HTTP:0-28-5] 10.0.4.12:56860->80	
   Sat 2018/11/24 10:33:48 AM	System	-170001	[HTTP:0-28]: GET-->/rest/ns/1/nodes/n001_ecobee	
   Sat 2018/11/24 10:33:48 AM	System	-170001	[HTTP:0-28-5] 10.0.4.12:56862->80	
   Sat 2018/11/24 10:33:48 AM	System	-170001	[HTTP:0-28]: GET-->/rest/ns/1/nodes/n001_ecobee	
   Sat 2018/11/24 10:33:48 AM	System	-170001	[HTTP:0-28-5] 10.0.4.12:56864->80	
   Sat 2018/11/24 10:33:48 AM	System	-170001	[HTTP:0-28]: GET-->/rest/ns/1/nodes/n001_ecobee	
   Sat 2018/11/24 10:34:19 AM	System	-170001	[HTTP:0-28-5] 10.0.5.0:58352->80	
   Sat 2018/11/24 10:34:19 AM	System	-170001	[HTTP:0-28]: POST[1]-->/services	
   Sat 2018/11/24 10:34:19 AM	System	-170001	<s:Envelope><s:Body><u:GetDebugLevel xmlns:u="u	
   Sat 2018/11/24 10:34:25 AM	System	-170001	[HTTP:0-28-5] 10.0.5.0:58359->80	
   Sat 2018/11/24 10:34:25 AM	System	-170001	[HTTP:0-28]: POST[1]-->/services	
   Sat 2018/11/24 10:34:25 AM	System	-170001	<s:Envelope><s:Body><u:UDIService xmlns:u="urn:	
   Sat 2018/11/24 10:34:25 AM	System	-170001	[TCP-Conn] -6/-140002, ISY	
   Sat 2018/11/24 10:34:25 AM	System	-170001	[HTTP:0-28-5] 10.0.5.0:58361->80	
   Sat 2018/11/24 10:34:26 AM	System	-170001	[HTTP:0-28]: POST[1]-->/services	
   Sat 2018/11/24 10:34:26 AM	System	-170001	<s:Envelope><s:Body><u:GetLastError xmlns:u="ur	
   Sat 2018/11/24 10:34:26 AM	System	-170001	[HTTP:0-28-5] 10.0.5.0:58362->80	
   Sat 2018/11/24 10:34:26 AM	System	-170001	[HTTP:0-28]: POST[1]-->/services	
   Sat 2018/11/24 10:34:26 AM	System	-170001	<s:Envelope><s:Body><u:ClearLastError xmlns:u="	
   Sat 2018/11/24 10:34:34 AM	System	-170001	[HTTP:0-28-5] 10.0.5.0:58371->80	
   Sat 2018/11/24 10:34:34 AM	System	-170001	[HTTP:0-28]: GET-->/rest/nodes/n001_ecobee1/cmd	
   Sat 2018/11/24 10:34:34 AM	System	-170001	[TCP-Conn] -6/-140002, ISY	
   Sat 2018/11/24 10:35:41 AM	System	-170001	[HTTP:0-28-5] 10.0.4.12:56866->80	
   Sat 2018/11/24 10:35:41 AM	System	-170001	[HTTP:0-28]: GET-->/rest/climate	
   Sat 2018/11/24 10:35:52 AM	System	-170001	[HTTP:0-28-5] 10.0.5.0:58466->80	
   Sat 2018/11/24 10:35:52 AM	System	-170001	[HTTP:0-28]: POST[1]-->/services	
   Sat 2018/11/24 10:35:52 AM	System	-170001	<s:Envelope><s:Body><u:UDIService xmlns:u="urn:	
   Sat 2018/11/24 10:35:53 AM	System	-170001	[TCP-Conn] -6/-140002, ISY	
   Sat 2018/11/24 10:36:32 AM	System	-170001	[HTTP:0-28-5] 10.0.5.0:58508->80	
   Sat 2018/11/24 10:36:32 AM	System	-170001	[HTTP:0-28]: POST[1]-->/services	
   Sat 2018/11/24 10:36:32 AM	System	-170001	<s:Envelope><s:Body><u:UDIService xmlns:u="urn:	
   Sat 2018/11/24 10:36:32 AM	System	-170001	[TCP-Conn] -6/-140002, ISY	
   Sat 2018/11/24 10:36:49 AM	System	-170001	[HTTP:0-28-5] 10.0.4.12:56872->80	
   Sat 2018/11/24 10:36:49 AM	System	-170001	[HTTP:0-28]: GET-->/rest/ns/1/nodes/n001_ecobee	
   Sat 2018/11/24 10:36:49 AM	System	-170001	[HTTP:0-28-5] 10.0.4.12:56874->80	
   Sat 2018/11/24 10:36:49 AM	System	-170001	[HTTP:0-28]: GET-->/rest/ns/1/nodes/n001_ecobee	
   Sat 2018/11/24 10:36:50 AM	System	-170001	[HTTP:0-28-5] 10.0.4.12:56876->80	
   Sat 2018/11/24 10:36:50 AM	System	-170001	[HTTP:0-28]: GET-->/rest/ns/1/nodes/n001_ecobee

    

4. Under Tools > Event Viewer, I set to Level 3.  The following showed:

   Sat 11/24/2018 10:36:48 AM : [D2D EVENT   ] Event [n001_ecobee1_sen2] [ST] [752] uom=14 prec=1
   Sat 11/24/2018 10:36:48 AM : [n001_ecobee1_sen2]       ST 752 (uom=14 prec=1)
   Sat 11/24/2018 10:36:48 AM : [D2D EVENT   ] Event [n001_ecobee1_sen3] [ST] [725] uom=14 prec=1
   Sat 11/24/2018 10:36:48 AM : [n001_ecobee1_sen3]       ST 725 (uom=14 prec=1)
   Sat 11/24/2018 10:36:49 AM : [D2D EVENT   ] Event [n001_ecobee1] [GV2] [-1] uom=25 prec=0
   Sat 11/24/2018 10:36:49 AM : [n001_ecobee1]      GV2  -1 (uom=25 prec=0)

    

If there is somewhere else I should check or i should try more actions, please let me know.

Ryan

[io_guy]

ISY logs don't help, just NodeLink.

- Make sure you have the proper IP/Port for NodeLink in your ISY Setup
- Enable the debug log in NodeLink's "System Config" Tab
- Enable the debug log on the NodeLink main page window

Try another command from the ISY.  If you don't see the request in NodeLink's log, then your ISY config is wrong.

[tinkerer]

Somehow the IP address to the NodeLink in under Node Servers on the ISY was incorrect.

I am not sure how that occurred, I am fairly certain that the NodeLink added itself there, I don't recall adding it.

Either way, it seems to be resolved now. 

I have one more dilemma...  The one option that i really needed doesn't seem to be present on the on the ISY.  The option/setting for the fan (Auto or On) is not present.  I see it on the UI of the thermostat itself and in the Ecobee app.  This setting was an option on the ISY for my Insteon thermostat.  Does anyone know if there was a reason this is not present?  If there is some reason, I can probably try cobbling together an API call that does this via a network resource.

Thank you for your help!

Ryan

[io_guy]

There is no "On" for the Ecobee.  Adjust the "Fan On Time" which is the amount of time on every hour.

[rccoleman]

The only way that I know of to control the fan is to set the ‘fan on time’. I set it to zero min/hr when I want it off and 55 or 60 min/hr when I want it on. It may have changed at some point, but there didn’t used to be a way to just turn the fan on and off through an API.

[tinkerer]

Thank you. 

I see the option on the ecobee to either use Auto (which it says follows the time per hour) or On (which is always on). 

Either way, I will just set it to 55 minutes per hour (which appears to be the max.)

Thank you for your help!

Ryan

[larryllix]

Thank you. 

I see the option on the ecobee to either use Auto (which it says follows the time per hour) or On (which is always on). 

Either way, I will just set it to 55 minutes per hour (which appears to be the max.)

Thank you for your help!

Ryan

The times are not accurate either. The fan cycles are variations of 5 minute segments do if you set it at 15 minutes you may get 20 minutes on and 20 minutes off every 40 minutes.

 

I did see a chart somewhere online a while back. I am not sure where now but the ecobee monitoring will show you the history of the cycles you selected.

 

The best part is the fan cycles much more frequently than once per hour that I have found leaves my rooms with dead air at times.

 

The fan on option is not available remotely. However you can set the fan to on for a user defined climate and ISY can select that climate.

 

 

 

[tinkerer]

I wound up setting the fan to 55 minutes per hour.  We shall see how well that works.

I've encountered what appears to be a bug.  I am uncertain if it is an issue with the ecobee sensor node or with the ISY API.  I have a Network Resource setup to store the temperature of the Ecobee Sensors into ISY variables so that I can use them in program conditions.

Example: 

/rest/vars/set/2/9/${sys.node.n001_ecobee1_sen1.ST}

This works fine and the variable is updated with the current temp, as long as the sensor's temperature is not an even number.  (It works when it is 72.7 degrees, but not when it is 69 degrees.)  

I am guessing that this is because there is a difference in the node info precision when it is an even temperature.  See examples below.

Sun Room at 69.0 degrees:

<nodeInfo>
<node flag="0" nodeDefId="EcobeeSensorF" nls="140ES">
<address>n001_ecobee1_sen1</address>
<name>Sun Room</name>
<family instance="1">10</family>
<parent type="3">9955</parent>
<type>1.1.0.0</type>
<enabled>true</enabled>
<deviceClass>0</deviceClass>
<wattage>0</wattage>
<dcPeriod>0</dcPeriod>
<startDelay>0</startDelay>
<endDelay>0</endDelay>
<pnode>n001_ecobee1</pnode>
<ELK_ID>B03</ELK_ID>
</node>
<properties>
<property id="GV1" value="0" formatted="0" uom="25"/>
<property id="ST" value="69" formatted="69°" uom="14"/>
</properties>
</nodeInfo>

Living Room at 72.7 degrees:

<nodeInfo>
<node flag="0" nodeDefId="EcobeeSensorF" nls="140ES">
<address>n001_ecobee1_sen2</address>
<name>Living Room</name>
<family instance="1">10</family>
<parent type="3">9955</parent>
<type>1.1.0.0</type>
<enabled>true</enabled>
<deviceClass>0</deviceClass>
<wattage>0</wattage>
<dcPeriod>0</dcPeriod>
<startDelay>0</startDelay>
<endDelay>0</endDelay>
<pnode>n001_ecobee1</pnode>
<ELK_ID>B04</ELK_ID>
</node>
<properties>
<property id="GV1" value="0" formatted="0" uom="25"/>
<property id="ST" value="727" formatted="72.7°" uom="14" prec="1"/>
</properties>
</nodeInfo>

Note the difference in nodeInfo > properties > property id = "ST".

 

When I try to run the API call:

/rest/vars/set/2/9/${sys.node.n001_ecobee1_sen1.ST}

I receive:

Sun 2018/11/25 03:10:51 PM    System    -140008    Net Module Rule: 14:404

 

When I run the API call:

/rest/vars/set/2/9/${sys.node.n001_ecobee1_sen2.ST}

It succeeds and stores the temp into the variable.

(The sun room also succeeds when the temp isn't even, I am just using the current state as an example.)

 

Is this an issue with the ecobee sensor node or with the ISY API?  Any suggestions would be appreciated. 

Ryan

[rccoleman]

This doesn’t directly address any potential issues with network resources, but since you’re using 5.x, you don’t need to use a network resource to store the value of a node in a variable. When you choose a variable in a program action, you can hit the sideways triangle icon to choose different sources for the value. One of them will give you a pull down list of all node values, including any node server nodes.

[tinkerer]

 

31 minutes ago, rccoleman said:

This doesn’t directly address any potential issues with network resources, but since you’re using 5.x, you don’t need to use a network resource to store the value of a node in a variable. When you choose a variable in a program action, you can hit the sideways triangle icon to choose different sources for the value. One of them will give you a pull down list of all node values, including any node server nodes.

I have never heard or seen that, I see the little arrow; but only variables are listed in the drop down menu.  

How do I go about getting node server nodes to be listed?

(First screenshot below shows only my variables.)

[rccoleman]

You’re modifying a condition (‘if’) and you need to do this in an action (‘then’). Hit ‘action’, select ‘variable’, choose a variable, and hit the triangle there. 

 

[tinkerer]

That is crazy... I just redid all of my variable 'setters'.  That was 100x easier than the network resources. 

This also solved my problem with variables that are even.

Does heartbeat update every time anything changes?  Do you know what 1 and -1 means for heartbeat?

Thanks!!!

Ryan

[rccoleman]

Glad it’s working for you. The heartbeat is just an indication that the values were updated, and it just flips back and forth between 1 and -1. The value doesn’t mean anything on its own. 

[larryllix]

Only a change of value means anything except that -1 or +1 also means it is not zero, as many values power up with. That means it was communicating at least once since power up.

[tinkerer]

It appears that the time of 55 minutes per hour isn't really 55 minutes.  Their own reporting site seems to show that I get about 28 minutes of fan time when it is set to 55 minutes/hour.

When I turn the fan from Auto to On via the portal, I do get a true 60 minutes per hour of run time. I've spent some time investigating how this is accomplished to see if I can automate it.  It appears that the API is used to send a hold to set the fan to indefinite.  It looks like I can accomplish this if I write a script myself and talk to the API, however there is a lot of backend logic required and the ecobee API requires periodically getting new authentication tokens which makes it more complex.

Turn Fan on:

{"selection":{"selectionType":"thermostats","selectionMatch":"999999999999"},"functions":[{"type":"setHold","params":{"coolHoldTemp":920,"heatHoldTemp":450,"holdType":"indefinite","fan":"on","isTemperatureAbsolute":false,"isTemperatureRelative":false}}]}

Turn Fan off:

{"selection":{"selectionType":"thermostats","selectionMatch":"999999999999"},"functions":[{"type":"setHold","params":{"coolHoldTemp":920,"heatHoldTemp":450,"holdType":"indefinite","fan":"auto","isTemperatureAbsolute":false,"isTemperatureRelative":false}}]}

Does anyone know if there is a possibility of getting NodeLink to make these two API calls when triggered by the ISY?

I was looking at the RelayServer in NodeLink, but I am uncertain if that has access to the ecobee information.

I realize this is a stretch, but any suggestions would be appreciated.

[larryllix]

Create a new climate that has all the same temperature setting as the one you want to turn the fan on with. Enter the climate setting on the ecobee and set the fan option to on.

When you want full fan, have ISY set the climate to your custom one just created.

IIRC my fan runs without interruption on any fan setting over about 15 minutes. This is from the ecobee history charts.

 

 

[tinkerer]

Thank you, I don't really want to change the temperature settings though. 

The API calls above include temp settings, but the ecobee ignores them because both isTemperatureAbsolute and isTemperatureRelative are both false.  In the photo, shows that it only has the fan on override.

I will try an see if I can get IFTT to do the ecobee api calls.  It appears there is an ecobee app there.  That should allow me to control it from the ISY.

[larryllix]

Thank you, I don't really want to change the temperature settings though. 
The API calls above include temp settings, but the ecobee ignores them because both isTemperatureAbsolute and isTemperatureRelative are both false.  In the photo, shows that it only has the fan on override.
I will try an see if I can get IFTT to do the ecobee api calls.  It appears there is an ecobee app there.  That should allow me to control it from the ISY.

No temperature changes involved. Read my post again

Sent from my SM-G930W8 using Tapatalk