@vlad, @yvesracine - Can you please let me know how you specified TLSv1.2 with httpPost? I tried this and did not work. I have an API that I’m trying to connect and it requires TLSv1.2. Any help on this is appreciated!
@yvesracine
Hello,
I was getting “unauthorized at api.automatic.com/vehicle” so I updated to the latest service manager and devite type (1.7.1 and 2.7.1)
But the issue persists so I went to the service manger to login with my creds and keep getting below error.
I double checked all instructions and Keys etc. Screenshot_20180320-180843|277x500
P.S. In certain cases, due to some ST platform issues, you may need to delete the device and restart from scratch when you have unauthorized issues.
My own Automatic device is working well, except that there are some read socket exceptions from time to time between Automatic and ST (timeouts) in the logs. This is probably an Automatic backend issue and my code cannot do anything about it.
@ yvesracine
Hi, I recently brought Automatic Pro.
Will the current DTH and Apps work fine with Automatic Pro ?
Will go ahead and make the purchase then.
Thanks.
Any inputs on Google Home integration after getting Automatic added as a device in ST and ST added to GHome ? Will it be able to respond just like it does for officially supported Alexa (or "Ok Google, Where is [my Car] ? / fuel level ? ")
No sorry. I’ve done a tighter integration with Amazon echo (via messages received in Ask Alexa), but Google Home doesn’t allow this kind of integration.
FYI, the auth tokens at Automatic are usually valid for about a year… Your last post was about a year ago, so I assume that your auth tokens are now expired… You just need to re-login at Automatic within MyAutomaticServiceMgr under Automation/smartapps in the ST classic mobile app.
When I went to the admin portal it didn’t show any apps at all…
I did try to re-authenticate in the app and always got “something went wrong” which is why I started looking further.