Question: Does the ST mode/My Ecobee device and smartapps override the Ecobee3 schedule (the one set via the thermostat)? I ask because I just recently changed My Ecobeee device to automatically change modes based on an ST mode change. Last night it changed to night mode in conjunction with ST. This morning the furnace did not come on based on the Ecobee3 scheduled “home” time. It didn’t come on until the ST mode changed to home.
Hi,
Please refer to the holdType preference parameter and how to set it up at the ST community wiki (step 3b):
http://thingsthataresmart.wiki/index.php?title=My_Ecobee_Device#Configuration
By default, the ecobee APIs use the ‘indefinite’ hold value.
The holdType parameter was also mentioned in the README file at the github (step 7):
Regards,
Thanks; however, it was already set to nextTransition. I’m going to see what it does tonite/tomorrow morning. Hopefully it was just an anomoly??
Hi @mjsutt66,
Are you using the ecobeeChangeMode smartapp for the ST hello mode change? If so, make sure that you’re have set it up correctly (the right ST hello mode has to be set at the hub to trigger an ecobee change mode). You can also test it manually.
In any case, If you have set your holdType parameter to ‘nextTransition in MyEcobee device’, then your scheduled ‘Home’ program at ecobee will override any temporary holds (manual or done by smartapps) at your thermostat.
MyEcobee device cannot override the ecobee transition on its own. It’s just an interface (DTH) between ST and ecobee using the ecobee APIs.
Regards.
Hi,
Using the ecobeeChangeMode smartapp, I have the following error message in the live logging when triggering the action manually (play button):
groovyx.net.http.HttpResponseException: Internal Server Error @ line 1814
The same error is happening when trying to change the thermostat mode from the smartthing My ecobee device.
I dont think it has ever been working for me. I am running the 5.7.8 version and had the same problem with 5.7.7
I just emailed you the trace.
Am I doing anything wrong ? It indeed doesn’t change anything on my ecobee thermostat settings.
I also had the following error few minutes after:
java.lang.RuntimeException: java.util.concurrent.ExecutionException: com.datastax.driver.core.exceptions.ReadTimeoutException: Cassandra timeout during read query at consistency LOCAL_ONE (1 responses were required but only 0 replica responded) @ line 5441
Thank you
Hi,
See my post above:
The 1st generic exception by itself is not significant, if you have issues, send me some detailed logs at
services@maisonsecomatiq.com.
Please refer to the ST community wiki for more details on how to get some detailed tracing (item 9) at:
http://thingsthataresmart.wiki/index.php?title=My_Ecobee_Device#Troubleshooting
Regards.
P.S. If you are using the ecobeeChangeMode smartapp for the ST hello mode change, then make sure that you’ve set it up correctly (the right ST hello mode has to be set at the hub to trigger an ecobee mode change).
Yes I am using that smart app. Just started yesterday so that could be it. Il try to play with it. I’m only using it for away though.
Unfortunately I’m experiencing the same issue… Pressing any key in the primary app works maybe 30% of the time. It’s been going on since the initial install back a month or so ago but I just managed to get time to sit down and look closer at it today. Ran init again and updated to the latest version.
Sure I’m missing something but not sure what. Under the device itself all of the parameters report correct - temperature, humidity, etc. so I seem to have connectivity.
8:19:22 PM: debug refreshLocalAuthToken>about to refresh auth token
8:19:22 PM: debug isTokenExpired> expired…
8:19:22 PM: error groovyx.net.http.HttpResponseException: Bad Request @ line 3712
8:19:22 PM: debug refreshLocalAuthToken>refreshParams=[method:POST, uri:https://api.ecobee.com, path:/token, query:[grant_type:refresh_token, code:xxxxxxxxxxxxxxxxxx client_id:xxxxxxxxxxxxxxxxx]]
8:19:22 PM: warn refresh_tokens>warning: local tokens still expired after refreshParentTokens() call
Hi @dwolfenbarger,
Please refer to my previous post:
All the information required to fix the unauthorized issues are indicated under the Troubleshooting section (item 6).
Please take note of the watchdogs section in MyEcobeeInit and ecobee3RemoteSensorInit.
MyEcobee device’s code has all the mechanisms to avoid the unauthorized issues due to some ST scheduling issues or ST timeouts. You may need to enable watchdogs to work around the ST scheduling issues.
As I said, if you want some peace of mind, just contribute to one of my support packages and I will take care of everything for you. Otherwise, you need to follow all the guidelines specified in the troubleshooting section.
Regards.
N.B. I did again a quick check of the many user sites all over the US and Canada that I monitor as part of my support packages, and none of them are experiencing any authentication issues which leads me to believe that you have either some localized ST account or configuration issues. Please take note that some of my contributors have multiple ecobee thermostats and remote sensors at their locations.
Also, looking at the logs you posted (next time please send them at services@maisonsecomatiq.com), it looks like you have edited some user preferences (which you shouldn’t) as you’re using MyEcobeeInit (service manager).
Please take note that you should not enter any serial number or appKey in the device’s preferences section as my code will assume that you’re not using the Service Manager (which can be optional). You have to leave those fields blank as indicated in the header.
You need to follow the installation steps specified at the readme as indicated in the zip file (rft installation file). If you edit the user preferences without reason or modify the existing code, it won’t work!!
Regards.
No change in user preferences. Serial #, App Key and ecobee TstatType are all blank. Only enabled tracing and changed holdType to nextTransition. Been through the documents many times in the last few weeks but thanks for the link. I cut and pasted the code verbatim from the last update you sent out w/o changes… really odd.
Shard is correct, ecobee device and remote sensor were pasted raw into the DTH as well as the remote and ecobeeinit under applications, authenticated against Ecobee from the init and re-authenticated during the process.
Just out of curiosity I know you’ve mentioned you’ve checked your user base for authentication errors but haven’t found anything. Appreciate you looking but just an observation: there are several reports and mine has been doing this for several weeks but didn’t show in your logs… not sure if that points to anything specific or not but…
As I said earlier, my code itself has all the required mechanisms to avoid authentication issues provided that you
follow all the guidelines that I’ve thoroughly documented and configure MyEcobee device correctly.
If you have persistent authentication or UI issues in your ST account. I can fix them for you as soon as you contribute to one of my support packages.
Regards.
No issue with any of the many other apps or DHs. I responded to your e-mail.
Thanks for your time.
Hi,
I’m sorry that you’re having some kind of issues with My ecobee Device.
You seem to think that there are some issues with the code. I can assure you that there are none.
The code has been proven solid for hundreds of contributors over the years.
That’s why I still believe that you have some configuration issues or some localized issues within your ST or ecobee account.
BTW, I have solved all the issues above in the previous posts. It’s always a question of not following the installation/configuration steps and/or the prerequisites and misunderstanding the design of some specific smartapps… In very few cases, the ST or Ecobee account had some technical issues that needed some special intervention from my part or from ST/ecobee support.
That’s also why I took the time to document all the most common installation/configuration issues here:
http://thingsthataresmart.wiki/index.php?title=My_Ecobee_Device#Configuration
http://thingsthataresmart.wiki/index.php?title=My_Ecobee_Device#Troubleshooting
As I wrote earlier, the ST platform is fairly technical and should be more user friendly for all users out there especially for custom development like mine.
I’ve been pushing (and other community developers) for a ST appstore for years to no avail. I guess ST has other issues to solve first. A good ST appstore would solve many of these installation/configuration issues for end users. Custom DTHs are a bit of a challenge right now (compared to smartapps which are typically simpler to install).
And, extra support for cases like yours takes some time to investigate and that’s why I ask for a support contribution. My support packages sell for few bucks and your specific problem would be solved. It’s not possible for me to look at few exceptions (mostly coming from ST or ecobee) in some logs and know immediately what’s wrong with your configuration or ST account. I need to know how many thermostats and remote sensors (if any) you have, what’s your thermostat model, do you have HW issues with your remote sensors, on which shard you are, what’s your polling interval for My ecobee Device, have you tried before to delete everything and restart from scratch, etc. In brief, I need temporary access to your ST account to know what’s your specific configuration.
P.S. If I were just monitoring my own ST account, I would not be so confident about the code, but I’m looking at several ST accounts with many ecobee thermostats and remote sensors in different user locations running smoothly all over America and Canada…
I’d be happy to help you to solve your specific issues as soon as you contribute to one of my support packages.
Regards
I have to admit I’m a bit surprised to see this response, although I do appreciate your edits from the original one I saw in my inbox, since I chose to have this conversation privately. I won’t present my resume here but I can assure you my technical skills are more than fine.
This is really simple… I fundamentally have an issue with your approach to support and the perceived attitude by me of ‘RTFM and pay me’ w/o a single question despite multiple complaints on the same issue and your own acknowledgement that you have ‘recently received a higher number of complaints than usual about MyEcobee device’s unauthorized exceptions.’.
Since I respect your efforts and many people here do not seem to have the same concern, as you have great detailed responses to many of the users here and a very supportive community which you deserve, I chose to have my conversation with you in private and stated we should go our separate ways. I believe it was a respectful but clear picture of how I felt and in no way was simply about the money aspect. I’ve personally contributed monetarily to other developers here who’s work and time I benefit from and I believe everyone should do the same.
As I stated in the e-mail I wish you the best and continued success with your impressive efforts. We simply have a different philosophy on the developer / user engagement in this instance and should move on.
1 Like
Yes, clearly we have a different support approach and that’s fine. There are many happy ecobee users who enjoy the DTHs right now (as you can see in this thread). Sadly, I cannot make everybody happy, but it’s the best support approach I’ve chosen for myself and my family.
My development and support time is limited and this is just a side hobby for me.
And, don’t forget that I’ve been doing that for almost 3 years now… There are reasons why I decided to take that approach and I’m here for the long run…
Regards
EDIT: And, I sent this email because there are no exceptions caused by my code normally (apart from the ST exceptions caused by its backend), so anything above 0 is unusual…
1 Like
Wow, if you have any questions about how to integrate MyEcobee device with iRule. Here
is a good post:
You can also see how solid MyEcobee’s implementation is (no disconnect issues).
Regards.
1 Like
FYI, I was able to fix my issue by clearing the holdType field and setting it to nextTransition. No more error and the thermostat is acting as requested.
1 Like
Well, according to the Trace log I think I keep on loosing the Token.
I used a Motion sensor in the bedroom as a Watchdog but it didn’t help.
If I re-launch the My Ecobee Init, it always creates another device and anyway end up loosing the token after a while.
Do you think I should I reinstall the whole thing?
Yes, try that and you should consider my support packages if it does not work.
Go under Automation/Smartapps and remove all instances of MyEcobeeInit.
When you re-execute MyEcobeeInit, you need to do it -under the ST mobile app- at
Automation/Smartapps in the bottom menu. I suspect that you keep creating new instances
of MyEcobeeInit and you shouldn’t. That’s why you keep creating new devices.
If it doesn’t work, there must be something wrong with your ST account for sure. I haven’t seen any authentication issues for more than a year in the ST accounts I supervise. And, apart from some isolated case(s) like yours, I haven’t received any complaints from my pool of contributors about it.
Also, be careful about the logs, try to manually refresh the device, and check if the data is updated. You may interpret that the tokens are lost, but they are not: the trace could be just the regular token processing (especially if you set the logFIlter to 4 and above). Some people PM me detailed logs from time to time and there is nothing abnormal about them.
The code has been solid since the beginning of 2016 based on all the defensive coding mechanisms I’ve implemented. Actually, at home, I don’t even use watchdogs as it’s not even necessary. If you use a watchdog, you need to use a regular polling device (which polls every 5-10 minutes). This watchdog acts like a ‘heartbeat’ to work around the ST scheduling issues.
P.S. BTW, at the same time, please always upgrade to the latest version, which is v5.7.9 now.
EDIT: If you’re so worried about the tokens, just set handleException flag to true in MyEcobeeInit, the smartapp will then notify you proactively when there are serious exceptions in its processing. See the ST community wiki troubleshooting section under item 15:
http://thingsthataresmart.wiki/index.php?title=My_Ecobee_Device#Troubleshooting
Regards.