@Jotto, @newshoes
Just as FYI, I’ve contacted ST support about this recurrent authorization issue as this is causing me headaches for my Custom Ecobee device integration work that I’ve done with SmartThings (and sometimes few ecobee users blame my code about it).
Apart from the regular scheduling issues that we all experience with ST, it seems that there is also a specific issue related to the security certificate with ecobee…
I’ve seen this exception in my logs:
2015-06-30 10:30:09.211 AM UTC (2015-06-30T10:30:09.211Z) |
| description | My ecobee Kitchen verbose trace is refresh_tokens>exception javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed at https://api.ecobee.com/token? |
P.S. If you have authorization issues with Ecobee, please contact ST support and open a ticket so that this issue will get more visible to them.
This is the email I sent to ST support (ticket # 109635)
Yracine
Jun 30, 10:59 AM
Hello,
On a regular basis, My custom ecobee device loses its authorization token with ecobee.
The problem is not unique to the My Ecobee device, but also occurs for the stock ST device as stated in this forum thread:
Having to authorize Ecobee 2-3 times a day
This is the exception that I found in my logs following a refresh_tokens() request:
| 2015-06-30 10:30:09.211 AM UTC (2015-06-30T10:30:09.211Z) |
| description | My ecobee Kitchen verbose trace is refresh_tokens>exception javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed at https://api.ecobee.com/token? |
Could you investigate what is wrong with the security certificate between SmartThings and Ecobee? It looks like the security certificate’s timestamp is outdated.
Regards.
Here is the answer from ST support.
Chris Porter (SmartThings)
Jun 30, 6:02 PM
Hi Yves,
Thanks for letting us know what you are seeing. My developers have been aware of this happening for a little while now also, and have worked on it. I will let them know your thoughts about it being the security timestamp being outdated.
I don’t have an ETA around implementing a revision to the code, but developers do currently know it is not working consistently for users, and are addressing it.
Thanks for the heads up, and the suggestions.
-Chris P.
SmartThings Support