larryllix Posted September 29, 2017 Posted September 29, 2017 Hi io_guy. Two items I would appreciate if you could look into. NodeLink 7.3 / ISY v5.0.10 - In ISY admin console setpoints are only comparabe to F temperaure range...ie. 32 - 90 degrees, in the admin console pulldown menus. I use C and a usable temperature for logic comparisons is not available in the preset range menu. -In ISY admin console the ecobee schedule setting is only settable as Home, Away, or Sleep. Is it possible to add more settings, in order to access other time sections, either scraped from inside the ecobee3 stat by name (eg: Evening, Morning, Wee hours etc..) or by the number of the user defined time sections in the ecobee3 (eg Home, Sleep, 3, 4, 5)? Currently only the three settings are allowed in ISY menus and user defined time sections are not available for remote setting. Thank you for an amazing product making a huge difference to ISY users.
io_guy Posted September 30, 2017 Posted September 30, 2017 Screenshot the range, can't figure where you're talking about. I'm in C and it's fine for me. Can't create new dropdown items based on the ecobee receive since ISY node defs are not dynamic. 1-7,8,9 whatever won't work because the API is fed a string (named) reference. I'd have to keep a list of your set of functions within NodeLink, allow 1-10 in ISY (numerical), and look up the values myself. Could do it but I'll need your log data since I don't have any custom settings.
larryllix Posted September 30, 2017 Author Posted September 30, 2017 Here is the setpoint F/C range restriction. I have no problems selecting inside a realistic C range with other ecobee/NodeLink settings. The problem is only with the setpoint comparison logic statement (right side) that restricts from 32 to 90 degrees. Here are the time segment selections consisting of only Home, Away, and Sleep The ecobee offers up to six time segments (I think). I only use four, plus "away". They are numbered inthe screenshot as 3 (Wee Hours) and 4 (Morning). Text labels are user assigned. Thanks for looking at this. Update: I just looked at my NodeLink ecobee3 web page. The field is labelled "Schedule Type" and is currently reporting as "sleep". I will see what it reports in the morning when Schedule Type should be showing 4 (morning) on the same NodeLink status page.
io_guy Posted September 30, 2017 Posted September 30, 2017 If you can grab a verbose log of it it'd be good too.
larryllix Posted September 30, 2017 Author Posted September 30, 2017 I acught the ecobee in both time segment 3 and 4 but the NodeLink webpage just shows "sleep". This may be after you filter for resonability though. I assume "sleep" is cded as "2" and 3,4 would be assumed to just be too high. I don't see a Shedule ype field in this data grab. Mabe I captured the wrong chunk? 2017-09-30 00:40:39 - ISY NodeLink Server v0.7.3 started 2017-09-30 00:40:39 - Mono version: 5.2.0.215 (tarball Mon Aug 14 16:25:12 UTC 2017) 2017-09-30 00:40:39 - ISY resolved to 192.168.0.161 2017-09-30 00:40:40 - Web config server started (http://192.168.0.175:8090) 2017-09-30 00:40:40 - ISY Node Server config detected (profile 1) 2017-09-30 09:20:51 - Ecobee Data: { "thermostatCount": 1, "revisionList": [ "311079071638:Gathering Room:true:170930033026:170621103120:170930131837:170930130000" ], "statusList": [ "311079071638:auxHeat1,fan" ], "status": { "code": 0, "message": "" <snipped for forum space brevity> ] } ] } ], "status": { "code": 0, "message": "" } } [ecobee1]
io_guy Posted September 30, 2017 Posted September 30, 2017 Yep, wrong part. Schedule isn't grabbed very often. Restart is the easiest.
larryllix Posted October 2, 2017 Author Posted October 2, 2017 OK, Got a NodeLink reboot data grab during the "Morning" period "smart4". It seems NodeLink knows about the custom schedule periods but ISY doesn't. The ecobee status page shows Shedule Type "N/A". Saving that field nets 0 value in a variable. Returning the stat to Schedule type "Home", status pages shows "Home" and saving to a variable nets "1", as expected. 2017-10-02 07:54:50 - ISY NodeLink Server v0.7.3 started 2017-10-02 07:54:50 - Mono version: 5.2.0.215 (tarball Mon Aug 14 16:25:12 UTC 2017) 2017-10-02 07:54:50 - ISY resolved to 192.168.0.161 2017-10-02 07:54:50 - Web config server started (http://192.168.0.175:8090) 2017-10-02 07:54:51 - ISY Node Server config detected (profile 1) 2017-10-02 07:54:55 - Ecobee: New tokens received from ecobee.com [ecobee1] 2017-10-02 07:54:56 - Ecobee Data: { "thermostatCount": 1, "revisionList": [ "311079071638:Gathering Room:true:171002032420:170621103120:171002115431:171002114500" ], "statusList": [ "311079071638:auxHeat1,fan" ], "status": { "code": 0, "message": "" } } [ecobee1] 2017-10-02 07:54:57 - Ecobee Data: { "page": { "page": 1, "totalPages": 1, "pageSize": 1, "total": 1 }, "thermostatList": [ { "identifier": "311079071638", "name": "Gathering Room", "thermostatRev": "171002032420", "isRegistered": true, "modelNumber": "athenaSmart", "brand": "ecobee", "features": "HomeKit", "lastModified": "2017-10-02 03:24:20", "thermostatTime": "2017-10-02 07:54:57", "utcTime": "2017-10-02 11:54:57", "alerts": [], "settings": { "hvacMode": "heat", "lastServiceDate": "2014-01-04", "serviceRemindMe": false, "monthsBetweenService": 6, "remindMeDate": "2014-01-04", "vent": "off", "ventilatorMinOnTime": 20, "serviceRemindTechnician": false, "eiLocation": "", "coldTempAlert": 644, "coldTempAlertEnabled": true, "hotTempAlert": 824, "hotTempAlertEnabled": true, "coolStages": 1, "heatStages": 1, "maxSetBack": 100, "maxSetForward": 80, "quickSaveSetBack": 40, "quickSaveSetForward": 40, "hasHeatPump": false, "hasForcedAir": true, "hasBoiler": false, "hasHumidifier": true, "hasErv": false, "hasHrv": false, "condensationAvoid": false, "useCelsius": true, "useTimeFormat12": true, "locale": "en", "humidity": "38", "humidifierMode": "manual", "backlightOnIntensity": 10, "backlightSleepIntensity": 8, "backlightOffTime": 30, "soundTickVolume": 0, "soundAlertVolume": 0, "compressorProtectionMinTime": 240, "compressorProtectionMinTemp": 550, "stage1HeatingDifferentialTemp": 10, "stage1CoolingDifferentialTemp": 5, "stage1HeatingDissipationTime": 30, "stage1CoolingDissipationTime": 30, "heatPumpReversalOnCool": true, "fanControlRequired": false, "fanMinOnTime": 10, "heatCoolMinDelta": 20, "tempCorrection": 0, "holdAction": "nextPeriod", "heatPumpGroundWater": false, "hasElectric": false, "hasDehumidifier": false, "dehumidifierMode": "on", "dehumidifierLevel": 48, "dehumidifyWithAC": false, "dehumidifyOvercoolOffset": 0, "autoHeatCoolFeatureEnabled": false, "wifiOfflineAlert": false, "heatMinTemp": 450, "heatMaxTemp": 1200, "coolMinTemp": -100, "coolMaxTemp": 1200, "heatRangeHigh": 770, "heatRangeLow": 626, "coolRangeHigh": 824, "coolRangeLow": 680, "userAccessCode": "", "userAccessSetting": 22, "auxRuntimeAlert": 10800, "auxOutdoorTempAlert": 500, "auxMaxOutdoorTemp": 700, "auxRuntimeAlertNotify": false, "auxOutdoorTempAlertNotify": false, "auxRuntimeAlertNotifyTechnician": false, "auxOutdoorTempAlertNotifyTechnician": false, "disablePreHeating": true, "disablePreCooling": false, "installerCodeRequired": false, "drAccept": "always", "isRentalProperty": false, "useZoneController": false, "randomStartDelayCool": 0, "randomStartDelayHeat": 0, "humidityHighAlert": 55, "humidityLowAlert": 25, "disableHeatPumpAlerts": false, "disableAlertsOnIdt": false, "humidityAlertNotify": true, "humidityAlertNotifyTechnician": false, "tempAlertNotify": true, "tempAlertNotifyTechnician": false, "monthlyElectricityBillLimit": 0, "enableElectricityBillAlert": false, "enableProjectedElectricityBillAlert": false, "electricityBillingDayOfMonth": 1, "electricityBillCycleMonths": 1, "electricityBillStartMonth": 1, "ventilatorMinOnTimeHome": 5, "ventilatorMinOnTimeAway": 0, "backlightOffDuringSleep": true, "autoAway": false, "smartCirculation": false, "followMeComfort": false, "ventilatorType": "none", "isVentilatorTimerOn": false, "ventilatorOffDateTime": "", "hasUVFilter": true, "coolingLockout": false, "ventilatorFreeCooling": true, "dehumidifyWhenHeating": false, "ventilatorDehumidify": false, "groupRef": "", "groupName": "", "groupSetting": 0 }, "runtime": { "runtimeRev": "171002115431", "connected": true, "firstConnected": "2017-06-21 01:20:23", "connectDateTime": "2017-09-30 03:10:19", "disconnectDateTime": "2017-09-29 23:22:23", "lastModified": "2017-10-02 11:54:31", "lastStatusModified": "2017-10-02 11:54:31", "runtimeDate": "2017-10-02", "runtimeInterval": 141, "actualTemperature": 707, "actualHumidity": 45, "desiredHeat": 716, "desiredCool": 734, "desiredHumidity": 38, "desiredDehumidity": 48, "desiredFanMode": "on", "desiredHeatRange": [ 626, 770 ], "desiredCoolRange": [ 680, 824 ] }, "extendedRuntime": { "lastReadingTimestamp": "2017-10-02 11:45:00", "runtimeDate": "2017-10-02", "runtimeInterval": 141, "actualTemperature": [ 705, 706, 707 ], "actualHumidity": [ 44, 44, 44 ], "desiredHeat": [ 716, 716, 716 ], "desiredCool": [ 734, 734, 734 ], "desiredHumidity": [ 38, 38, 38 ], "desiredDehumidity": [ 0, 0, 0 ], "dmOffset": [ 0, 0, 0 ], "hvacMode": [ "heatStage1On", "heatStage1On", "heatStage1On" ], "heatPump1": [ 0, 0, 0 ], "heatPump2": [ 0, 0, 0 ], "auxHeat1": [ 300, 300, 300 ], "auxHeat2": [ 0, 0, 0 ], "auxHeat3": [ 0, 0, 0 ], "cool1": [ 0, 0, 0 ], "cool2": [ 0, 0, 0 ], "fan": [ 300, 300, 300 ], "humidifier": [ 0, 0, 0 ], "dehumidifier": [ 0, 0, 0 ], "economizer": [ 0, 0, 0 ], "ventilator": [ 0, 0, 0 ], "currentElectricityBill": 0, "projectedElectricityBill": 0 }, "weather": { "timestamp": "2017-10-02 11:34:10", "weatherStation": "CW:800585", "forecasts": [ { "weatherSymbol": 1, "dateTime": "2017-10-02 07:27:08", "condition": "Quite cool.", "temperature": 525, "pressure": 1028, "relativeHumidity": 91, "dewpoint": 435, "visibility": -5002, "windSpeed": 3000, "windGust": -5002, "windDirection": "SE", "windBearing": 150, "pop": 75, "tempHigh": 690, "tempLow": 462, "sky": -5002 }, { "weatherSymbol": 2, "dateTime": "2017-10-03 07:27:08", "condition": "Morning clouds. Mild.", "temperature": 635, "pressure": 1027, "relativeHumidity": 54, "dewpoint": 544, "visibility": -5002, "windSpeed": 8000, "windGust": -5002, "windDirection": "S", "windBearing": 198, "pop": 62, "tempHigh": 739, "tempLow": 532, "sky": 32 }, { "weatherSymbol": 5, "dateTime": "2017-10-04 07:27:08", "condition": "Numerous showers. Morning clouds. Mild.", "temperature": 649, "pressure": 1015, "relativeHumidity": 86, "dewpoint": 636, "visibility": -5002, "windSpeed": 13000, "windGust": -5002, "windDirection": "SW", "windBearing": 230, "pop": 26, "tempHigh": 708, "tempLow": 590, "sky": 32 }, { "weatherSymbol": 1, "dateTime": "2017-10-05 07:27:08", "condition": "Mostly sunny. Mild.", "temperature": 595, "pressure": 1016, "relativeHumidity": 70, "dewpoint": 521, "visibility": -5002, "windSpeed": 13000, "windGust": -5002, "windDirection": "W", "windBearing": 258, "pop": 37, "tempHigh": 640, "tempLow": 550, "sky": 3 }, { "weatherSymbol": 1, "dateTime": "2017-10-06 07:27:08", "condition": "Mostly sunny. Cool.", "temperature": 548, "pressure": 1016, "relativeHumidity": 64, "dewpoint": 455, "visibility": -5002, "windSpeed": 5000, "windGust": -5002, "windDirection": "SW", "windBearing": 246, "pop": 16, "tempHigh": 593, "tempLow": 503, "sky": 3 }, { "weatherSymbol": 2, "dateTime": "2017-10-02 06:00:00", "condition": "High level clouds. Cool.", "temperature": 462, "pressure": -5002, "relativeHumidity": 95, "dewpoint": 447, "visibility": 12000, "windSpeed": 7000, "windGust": -5002, "windDirection": "SE", "windBearing": 147, "pop": 0, "tempHigh": -5002, "tempLow": -5002, "sky": 12 }, { "weatherSymbol": 2, "dateTime": "2017-10-02 12:00:00", "condition": "High level clouds. Mild.", "temperature": 690, "pressure": -5002, "relativeHumidity": 49, "dewpoint": 492, "visibility": 16000, "windSpeed": 6000, "windGust": -5002, "windDirection": "SE", "windBearing": 145, "pop": 0, "tempHigh": -5002, "tempLow": -5002, "sky": 12 }, { "weatherSymbol": 2, "dateTime": "2017-10-02 18:00:00", "condition": "High level clouds. Cool.", "temperature": 559, "pressure": -5002, "relativeHumidity": 74, "dewpoint": 476, "visibility": 11000, "windSpeed": 8000, "windGust": -5002, "windDirection": "S", "windBearing": 158, "pop": 0, "tempHigh": -5002, "tempLow": -5002, "sky": 12 }, { "weatherSymbol": 2, "dateTime": "2017-10-03 00:00:00", "condition": "High level clouds. Cool.", "temperature": 536, "pressure": -5002, "relativeHumidity": 79, "dewpoint": 473, "visibility": 10000, "windSpeed": 7000, "windGust": -5002, "windDirection": "S", "windBearing": 173, "pop": 0, "tempHigh": -5002, "tempLow": -5002, "sky": 12 } ] }, "events": [ { "type": "template", "name": "_Default_", "running": false, "startDate": "2035-01-01", "startTime": "00:00:00", "endDate": "2035-01-01", "endTime": "23:59:59", "isOccupied": false, "isCoolOff": false, "isHeatOff": false, "coolHoldTemp": 788, "heatHoldTemp": 644, "fan": "auto", "vent": "off", "ventilatorMinOnTime": 5, "isOptional": true, "isTemperatureRelative": false, "coolRelativeTemp": 40, "heatRelativeTemp": 40, "isTemperatureAbsolute": false, "dutyCyclePercentage": 255, "fanMinOnTime": 5, "occupiedSensorActive": false, "unoccupiedSensorActive": false, "drRampUpTemp": 0, "drRampUpTime": 3600, "linkRef": "", "holdClimateRef": "" } ], "program": { "schedule": [ [ "sleep", "sleep", "sleep", "sleep", "sleep", "sleep", "smart3", "smart3", "smart3", "smart3", "smart3", "smart3", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "sleep" ], [ "sleep", "sleep", "sleep", "sleep", "sleep", "sleep", "smart3", "smart3", "smart3", "smart3", "smart3", "smart3", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "sleep" ], [ "sleep", "sleep", "sleep", "sleep", "sleep", "sleep", "smart3", "smart3", "smart3", "smart3", "smart3", "smart3", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "sleep" ], [ "sleep", "sleep", "sleep", "sleep", "sleep", "sleep", "smart3", "smart3", "smart3", "smart3", "smart3", "smart3", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "sleep" ], [ "sleep", "sleep", "sleep", "sleep", "sleep", "sleep", "smart3", "smart3", "smart3", "smart3", "smart3", "smart3", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "sleep" ], [ "sleep", "sleep", "sleep", "sleep", "sleep", "sleep", "smart3", "smart3", "smart3", "smart3", "smart3", "smart3", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "sleep" ], [ "sleep", "sleep", "sleep", "sleep", "sleep", "sleep", "smart3", "smart3", "smart3", "smart3", "smart3", "smart3", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "smart4", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "home", "sleep" ] ], "climates": [ { "name": "Away", "climateRef": "away", "isOccupied": false, "isOptimized": true, "coolFan": "auto", "heatFan": "auto", "vent": "off", "ventilatorMinOnTime": 20, "owner": "system", "type": "program", "colour": 9021815, "coolTemp": 788, "heatTemp": 644, "sensors": [ { "id": "ei:0:1", "name": "Gathering Room" } ] }, { "name": "Home", "climateRef": "home", "isOccupied": true, "isOptimized": false, "coolFan": "auto", "heatFan": "auto", "vent": "off", "ventilatorMinOnTime": 20, "owner": "system", "type": "program", "colour": 13560055, "coolTemp": 743, "heatTemp": 734, "sensors": [ { "id": "ei:0:1", "name": "Gathering Room" }, { "id": "rs:101:1", "name": "TV Area" } ] }, { "name": "Sleep", "climateRef": "sleep", "isOccupied": true, "isOptimized": false, "coolFan": "on", "heatFan": "auto", "vent": "off", "ventilatorMinOnTime": 20, "owner": "system", "type": "program", "colour": 2179683, "coolTemp": 725, "heatTemp": 716, "sensors": [ { "id": "rs:102:1", "name": "Master BedRm" } ] }, { "name": "Wee Hours", "climateRef": "smart3", "isOccupied": true, "isOptimized": true, "coolFan": "on", "heatFan": "on", "vent": "off", "ventilatorMinOnTime": 20, "owner": "user", "type": "program", "colour": 9021815, "coolTemp": 716, "heatTemp": 716, "sensors": [ { "id": "rs:102:1", "name": "Master BedRm" } ] }, { "name": "Morning", "climateRef": "smart4", "isOccupied": true, "isOptimized": true, "coolFan": "auto", "heatFan": "on", "vent": "off", "ventilatorMinOnTime": 20, "owner": "user", "type": "program", "colour": 9021815, "coolTemp": 734, "heatTemp": 716, "sensors": [ { "id": "ei:0:1", "name": "Gathering Room" }, { "id": "rs:102:1", "name": "Master BedRm" } ] } ], "currentClimateRef": "smart4" }, "houseDetails": { "style": "detached", "size": 3500, "numberOfFloors": 2, "numberOfRooms": 4, "numberOfOccupants": 2, "age": 7, "windowEfficiency": 5 }, "remoteSensors": [ { "id": "rs:100", "name": "Basement", "type": "ecobee3_remote_sensor", "code": "FG2P", "inUse": false, "capability": [ { "id": "1", "type": "temperature", "value": "721" }, { "id": "2", "type": "occupancy", "value": "false" } ] }, { "id": "rs:101", "name": "TV Area", "type": "ecobee3_remote_sensor", "code": "DZ6J", "inUse": false, "capability": [ { "id": "1", "type": "temperature", "value": "716" }, { "id": "2", "type": "occupancy", "value": "true" } ] }, { "id": "rs:102", "name": "Master BedRm", "type": "ecobee3_remote_sensor", "code": "DWV8", "inUse": true, "capability": [ { "id": "1", "type": "temperature", "value": "729" }, { "id": "2", "type": "occupancy", "value": "true" } ] }, { "id": "ei:0", "name": "Gathering Room", "type": "thermostat", "inUse": true, "capability": [ { "id": "1", "type": "temperature", "value": "685" }, { "id": "2", "type": "humidity", "value": "45" }, { "id": "3", "type": "occupancy", "value": "true" } ] } ] } ], "status": { "code": 0, "message": "" } } [ecobee1]
G W Posted October 2, 2017 Posted October 2, 2017 I can see by your room naming convention that you are a Northerner. LOL In US we call that room Kitchen. Sent from my Nexus 6P using Tapatalk
io_guy Posted October 9, 2017 Posted October 9, 2017 Here is the setpoint F/C range restriction. I have no problems selecting inside a realistic C range with other ecobee/NodeLink settings. The problem is only with the setpoint comparison logic statement (right side) that restricts from 32 to 90 degrees. ecobee setpoint.jpg Check you stat type (should say C). You're either running a F node or your ISY config is broken. My guess is you added the node to the ISY before Ecobee received any data, so not knowing your stat config it used the default F.
larryllix Posted October 9, 2017 Author Posted October 9, 2017 Check you stat type (should say C). You're either running a F node or your ISY config is broken. My guess is you added the node to the ISY before Ecobee received any data, so not knowing your stat config it used the default F. statC.JPG statHeat.jpg Thanks. I will work on those clues. My stat displays C, ISY is set for C, and NodeLink is displaying C in the node page. Must be an ISY setup problem then. I thought it was correct before but... Seems all the ISY ecobee scales (pulldown) are based in F ranges now. I only used logic with extremes before so I may not have noticed it before. eg. If ecobee.temp < 40 degrees. Both F/C scales would support a common temp like 40 degrees. For the other problem. I have discovered that the Home,Away, Night controls set the stat as not only Home but permanently. This means the schedule cannot ever resume and makes them, or any further time segments (if remote settable) are basically useless. The Home with hold, and Away with hold, are on the first level quick settings and different than the other schedule time segments. My idea was I could use preset schedule segments for early Adaptive Intelligent Setback and Adaptive Intelligent Recovery without doing too many temperature tracking things inside ISY. Not going to work because the schedule will never resume automatically with these settings.
io_guy Posted October 9, 2017 Posted October 9, 2017 Thanks. I will work on those clues. My stat displays C, ISY is set for C, and NodeLink is displaying C in the node page. Must be an ISY setup problem then. I thought it was correct before but... Seems all the ISY ecobee scales (pulldown) are based in F ranges now. I only used logic with extremes before so I may not have noticed it before. eg. If ecobee.temp < 40 degrees. Both F/C scales would support a common temp like 40 degrees. What do you mean ISY is set for C? Ecobee and NodeLink mean nothing, they'll be C. Look at the description next to the Ecobee node name in the ISY (see my image in my above post). It needs to show © not (F). For the other problem. I have discovered that the Home,Away, Night controls set the stat as not only Home but permanently. This means the schedule cannot ever resume and makes them, or any further time segments (if remote settable) are basically useless. The Home with hold, and Away with hold, are on the first level quick settings and different than the other schedule time segments. My idea was I could use preset schedule segments for early Adaptive Intelligent Setback and Adaptive Intelligent Recovery without doing too many temperature tracking things inside ISY. Not going to work because the schedule will never resume automatically with these settings. No way around this. Setting a climate outside of the schedule has to be a hold - that's the only way a thermostat would work.
larryllix Posted October 9, 2017 Author Posted October 9, 2017 What do you mean ISY is set for C? Ecobee and NodeLink mean nothing, they'll be C. Look at the description next to the Ecobee node name in the ISY (see my image in my above post). It needs to show © not (F). No way around this. Setting a climate outside of the schedule has to be a hold - that's the only way a thermostat would work. If a temperature override is set the ecobee3 has three options to reset it. 1) in X hours, 2) at the next time schedule change, and 3) never = permanent. Schedule segment changes always follow 2). I thought I could pre-empt it. It would have made a nice way to do Intelligent setback/recovery without knowing absolute temperatures. As is, provided all the modes are correct I interrogate the ecobee3 twice per day (4 AM & PM) and grab the current settings for day and night into ISY and use those. This doesn't allow for some other miner things, like severe weather compensation. (0.5C degree only) but I think my ISY program will just re-compensate anyway. I cant believe HVAC can get so complicated. It seems so simple at first glance with the simple bang/bang (HVAC for simple contact on/off style algorithm) thermostat. ecobee3 shows C temperatures on the stat display ecobee3 webpage shows C for all temperatures NodeLink is showing C temperatures. NodeLink is displaying F temperatures in the captured code. See post #7 ISY is only showing temperatures in the F ranges. See post #3 screen capture typically 32-90 degrees, in all program line pulldown menu options. ISY shows temperatures in C on the admin console ecobee3 status page ISY is set for C display in the Admin Console Configuration page
io_guy Posted October 10, 2017 Posted October 10, 2017 I don't think we're talking the same thing... Please take a screen of this: In the next revision I'll add the ability to select the climate type with a permanent or transition hold option.
larryllix Posted October 10, 2017 Author Posted October 10, 2017 I don't think we're talking the same thing... Please take a screen of this: statC.JPG In the next revision I'll add the ability to select the climate type with a permanent or transition hold option. The status page shows Celsius dspite the menus showing only farenheit ranges.
io_guy Posted October 10, 2017 Posted October 10, 2017 You're missing my point. The temperature is not in Celsius, it's just whatever value NodeLink sends. Look at your image. n001_ecobee1 - Ecobee Thermostat (F) F as in not Celsius. The F node was installed, no the C.
larryllix Posted October 10, 2017 Author Posted October 10, 2017 You're missing my point. The temperature is not in Celsius, it's just whatever value NodeLink sends. Look at your image. n001_ecobee1 - Ecobee Thermostat (F) F as in not Celsius. The F node was installed, no the C. Strange! I have never noticed that before but never needed to get an exact temperature either.. click! .LOL How do I go about fixing that one?
io_guy Posted October 10, 2017 Posted October 10, 2017 You don't. The ISY has no way to modify nodes. Delete it and let NodeLink re-add. This all gets back to, in my opinion, the painful way nodes are handled in the ISY. A thermostat node (even though there is such a thing [140]) means nothing. It's not treated special nor does it have any ability to handle units. I might as well call it a blender. The ISY should be able to handle me sending temps in either unit as long as I specify which one it is. But it doesn't. And it should display the stat data in whatever global units I choose. But it doesn't. It should also be able to adjust value limits on the fly (based on units). But it doesn't.
stusviews Posted October 10, 2017 Posted October 10, 2017 If a temperature override is set the ecobee3 has three options to reset it. 1) in X hours, 2) at the next time schedule change, and 3) never = permanent. Info only: According to ecobee support,when changing the temperature using voice and only when using voice, only the 3rd option is executed--or is it never executed
larryllix Posted October 10, 2017 Author Posted October 10, 2017 Info only: According to ecobee support,when changing the temperature using voice and only when using voice, only the 3rd option is executed--or is it never executed Thanks Stu. That is very strange because the option is hard set in the stat only and no remote access to that option is available on their website to change it remotely. I don't change my thermostats via voice. I never and should never have the need to. With all the automatic controls in the stat and via NodeLink access if something isn't self adjusting I better program some more.
larryllix Posted October 10, 2017 Author Posted October 10, 2017 You don't. The ISY has no way to modify nodes. Delete it and let NodeLink re-add. This all gets back to, in my opinion, the painful way nodes are handled in the ISY. A thermostat node (even though there is such a thing [140]) means nothing. It's not treated special nor does it have any ability to handle units. I might as well call it a blender. The ISY should be able to handle me sending temps in either unit as long as I specify which one it is. But it doesn't. And it should display the stat data in whatever global units I choose. But it doesn't. It should also be able to adjust value limits on the fly (based on units). But it doesn't. That's what I figured. I cannot logically determine whether this has always been this way or it changed in ISY later. It may have beenISY installed before connection with the stat. (that seems to be the best logical explanation, so far) Thanks for the info and help. I will report back after working on it.
larryllix Posted October 10, 2017 Author Posted October 10, 2017 You don't. The ISY has no way to modify nodes. Delete it and let NodeLink re-add. This all gets back to, in my opinion, the painful way nodes are handled in the ISY. A thermostat node (even though there is such a thing [140]) means nothing. It's not treated special nor does it have any ability to handle units. I might as well call it a blender. The ISY should be able to handle me sending temps in either unit as long as I specify which one it is. But it doesn't. And it should display the stat data in whatever global units I choose. But it doesn't. It should also be able to adjust value limits on the fly (based on units). But it doesn't. Second response to your post. OK I deleted and reinstalled the Node from NodeLink. All went well and the C is displayed on the device status page as well as the C ranges in the pulldown menus are restored. Despite all programs showing the correct names I had to select and update all program lines affiiated with that node and then Save. I have been caught on this before, text names may agree but the underlying device is not connected after replacing a device. They show up on a later admin console load as not functioning but the programs have not functioned since the change of device. I have determined that this Node was originally installed with the C selected. All my ecobee3 programs to detect changes were using the maximum C temperature from the C ranged pulldown menus. Now it bothers me that it changed in the interimm. As an aside: I also found out programs in a disabled folder cannot be tested. You can manually run Then as many times as you like but they do not actually run and there is no clear indication. I added supefluous Waits to the program sections to see if the avatars change.**YUK** Thanks so much io_guy!!!
io_guy Posted October 10, 2017 Posted October 10, 2017 Despite all programs showing the correct names I had to select and update all program lines affiiated with that node and then Save. I have been caught on this before, text names may agree but the underlying device is not connected after replacing a device. They show up on a later admin console load as not functioning but the programs have not functioned since the change of device. In my opinion this is the worst bug in ISY V5 Node Functionality. How the ISY doesn't alert about a broken/changed node is unacceptable.
larryllix Posted October 10, 2017 Author Posted October 10, 2017 In my opinion this is the worst bug in ISY V5 Node Functionality. How the ISY doesn't alert about a broken/changed node is unacceptable. Agreed. Most go to a lot of trouble to provide heartbeats for any device/software that only reports changes. To break that chain last minute is not good.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.