Changes made in ecobee Developer Community

In order to preserve the promise of transparency and open communication, the change log records changes to topics made by both customers and employees. Anyone can dispute a change by clicking the "Dispute" link and entering additional details.


  • September 14, 2017 18:47
    system, a community manager for Get Satisfaction:
    Reason: ban
    Dispute this change
  • July 27, 2017 23:55
    kuperson, the poster:
    Reason: removed by the poster
  • July 08, 2017 00:43
    dborn, the poster:
    Reason: removed by the poster
  • June 06, 2017 15:03
    Paris Rand, the poster:
    Reason: removed by the poster
  • June 06, 2017 15:03
    Paris Rand, the poster:
    Reason: removed by the poster
  • December 23, 2016 18:36
    Eugene
    Changed reply in topic of We cannot connect to your thermostat by Eugene to Dear customer!<br /><br />Sorry to hear your thermostat is having troubles connecting to ecobee servers.<br /><br />However this forum is used to support development questions regarding ecobee API and not discuss customer support line performance or internet connectivity issues. <br />For all questions apart of API, please contact support line. You can find phone number and email address on ecobee website. If you are not satisfied with wait time on a phone support, please use email address.<br /><br />Eugene..
  • November 10, 2016 15:25
    Eugene
    Changed reply in topic of runtimeReport - accurarately pulling multiple requests by Eugene to Eric: this is now a confirmed bug. I can't provide any ETA right now. <br />Your workaround with overlapping days would solve the problem for now. .
  • September 23, 2016 21:07
    MarkK
    Reason: duplicate
    Dispute this change
  • August 01, 2016 17:54
    Jerrill Johnson, the poster:
    Reason: removed by the poster
  • August 01, 2016 17:54
    Jerrill Johnson, the poster:
    Reason: removed by the poster
  • June 01, 2016 22:53
    John S, the poster:
    Reason: removed by the poster
  • May 24, 2016 17:00
    Richard Noordhof, the poster:
    Reason: removed by the poster
  • May 22, 2016 16:49
    Richard Noordhof, the poster:
    Reason: removed by the poster
  • May 22, 2016 16:26
    Richard Noordhof, the poster:
    Reason: removed by the poster
  • May 13, 2016 18:53
    Jari
    Changed reply in topic of Requests to Ecobee getting Timeout by Jari to Thanks Pedro. I was hoping this might be related to a special case for MSIE where the socket keep alive and shutdown behaviour has been altered. However, that doesn't seem to be the case here. Fortunately, I've managed to reproduce the problem and have a hunch as to what may be causing it. I might need a few more days to come up with a solution..
  • May 13, 2016 18:53
    Jari
    Changed reply in topic of Requests to Ecobee getting Timeout by Jari to Thanks Pedro. I was hoping this might be related to a special case for MSIE where the socket keep alive and shutdown behaviour has been altered. However, that doesn't seem to be the case here. Fortunately, I've managed to reproduce and the problem and have a hunch as to what may be causing it. I might need a few more days to come up with a solution..
  • May 04, 2016 23:23
    ScottF
    Changed reply in topic of Recognizing a user-initiated hold by John D Boyd to Here's the JSON I'm using to create a named setHold event: { "selection": { "selectionType":"thermostats", "selectionMatch":"XXXXXXXXXXXX" }, "functions":[ { "type":"setHold", "params":{ "name":"john", "heatHoldTemp":"700", "coolHoldTemp":"840", "holdType":"nextTransition" } } ] } However, when I retrieve the lists of events for this tstat, event.name is reported as "auto". Thanks! John.
    Dispute this change
  • April 26, 2016 05:44
    Reema Patel, the poster:
    Reason: removed by the poster
  • April 14, 2016 12:51
    Jari
    Changed reply in topic of developer.ecobee.com website is not configured properly by Jari to Hi,<br /><br />It seems that a few browsers (IE, Firefox, Tor) picked up a commit to the Chrome HSTS preload list where our domain was briefly listed a few months back. These browsers seem to lag the Chrome list in removing our site. It appears that new nightly builds of IE and Firefox have removed us from their lists. In the meantime, you can visit <a href="https://ecobee.com" rel="nofollow" target="_blank" title="Link https//ecobeecom">https://ecobee.com</a>&nbsp;(note, no 'www')&nbsp;to have your browser remove the HSTS entry for our domain. Following that you should be able to visit <a href="http://developer.ecobee.com/api" rel="nofollow" target="_blank" title="Link http//developerecobeecom/api">http://developer.ecobee.com/api</a>&nbsp;without any browser warnings.<br /><br />We're working on implementing&nbsp;HSTS support across all our sub-domains, but at present HTTPS is not supported across all our&nbsp;vendors. We hope to have this resolved in the near future. Thanks, and please let us know if you have any further problems after taking the above steps!<br /><br />Jari.
  • April 13, 2016 20:32
    Jari
    Changed reply in topic of Requests to Ecobee getting Timeout by Jari to Hi Pedro,<br /><br />I can confirm that I don't see your IP or netblock in any block lists on our side.<br /><br />It looks like you ran a 'tracepath' which does PMTU discovery instead of a 'traceroute'. Can you run 'traceroute' instead? Also, can you confirm if you're able to ping api.ecobee.com or not? You should be able to ping us, if not then there may be a network connectivity issue between us. Finally, you may want to try 'traceroute' with TCP SYN's, do a 'traceroute -T -p 443 api.ecobee.com'. It would also be helpful if you can include tcpdump output while running the ping and traceroute commands.<br /><br />Alternatively, if your traceroute doesn't support the '-T' option then you may want to look at tcptraceroute.<br /><br />Also, is the problem intermittent? I show that you last connected to us on the 11th at approx. 18:00 UTC-4. Is that when the problem began for you? Does the problem occur from any other hosts or networks that you are using?<br /><br />Thanks,<br /><br />Jari.
next » « previous