Open Cglass-1234 opened 3 years ago
blakevh
commented
3 years ago Hi, Carl,
Tesla recently implemented a new authentication method for their API. We are aware of the issue, but do not yet have an implementation that supports the new authentication method.
Thanks
Cglass-1234
commented
3 years ago Yes, I'm aware. I also use TeslaFi.com and recently had to generate a new API token for proper authentication. Is it as simple as adding an API field to your nodeserver?
blakevh
commented
3 years ago The authentication method is radically different from the previous version. The new method supports both multi-factor authentication and non-multi-factor authentication and has a different workflow. From the user perspective, if we continue to support username/password entry, we will also have to add a multi-factor device name and a transient multi-factor code. Rather than re-implementing the authentication from scratch I am looking for a compatible authentication library. So far I have only found one library that is compatible with our environment and works. Even that library I had to fix to get to work in a simple test-bed. And with a working library, there is still work that needs to be done to hook it into the Tesla nodeserver.
Cglass-1234
commented
3 years ago Robert
I see that you have released 3.0.0 and 3.0.1 of the Tesla Nodeserver. I installed, and the nodeserver promptly appeared. But my vehicle hasn’t appeared yet. I’m only using email and password in the nodeserver config page. I also input a lat long and true security. Only one node named “controller” is shown in pgc.
Must I use mfa, and if so, how do I configure that. I can’t find any instructions.
Thx!
Carl
From: Robert Blake Von Haden @.> Sent: Saturday, February 13, 2021 3:06 PM To: UniversalDevicesInc/tesla-nodeserver @.> Cc: Cglass-1234 @.>; Author @.> Subject: Re: [UniversalDevicesInc/tesla-nodeserver] Nodes do not populate in isy (#23)
The authentication method is radically different from the previous version. The new method supports both multi-factor authentication and non-multi-factor authentication and has a different workflow. From the user perspective, if we continue to support username/password entry, we will also have to add a multi-factor device name and a transient multi-factor code. Rather than re-implementing the authentication from scratch I am looking for a compatible authentication library. So far I have only found one library that is compatible with our environment and works. Even that library I had to fix to get to work in a simple test-bed. And with a working library, there is still work that needs to be done to hook it into the Tesla nodeserver.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/UniversalDevicesInc/tesla-nodeserver/issues/23#issuecomment-778690953 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AS23Q4ZLLXEUYFYNINKHWBTS64AW3ANCNFSM4XSKPOPQ . https://github.com/notifications/beacon/AS23Q4YMHO37442DZF35MALS64AW3A5CNFSM4XSKPOP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFZU6DCI.gif
blakevh
commented
3 years ago @Cglass-1234 so far I have only succeeded in getting the Tesla nodeserver to work on a Polisy device with the new authentication protocols. Like you described, the Tesla nodeserver fails to load on the Polyglot cloud.
Both regular and MFA logins should work on a Polisy device.
If you want to use an MFA login, you need to set up MFA on your Tesla account. Go to https://www.tesla.com/support/multi-factor-authentication and follow the instructions. If you set up only one MFA device, when you configure the nodeserver you just need to enter the MFA code. If you setup up two MFA devices, you need to enter the MFA device name as well.
Cglass-1234
commented
3 years ago Ok, thx for the reply. I’ll delete the nodeserver for now and wait for explicit confirmation that it works on pgc.
Thx
Carl
From: Robert Blake Von Haden @.> Sent: Sunday, April 18, 2021 5:45 AM To: UniversalDevicesInc/tesla-nodeserver @.> Cc: Cglass-1234 @.>; Mention @.> Subject: Re: [UniversalDevicesInc/tesla-nodeserver] Nodes do not populate in isy (#23)
@Cglass-1234 https://github.com/Cglass-1234 so far I have only succeeded in getting the Tesla nodeserver to work on a Polisy device with the new authentication protocols. Like you described, the Tesla nodeserver fails to load on the Polyglot cloud.
Both regular and MFA logins should work on a Polisy device.
If you want to use an MFA login, you need to set up MFA on your Tesla account. Go to https://www.tesla.com/support/multi-factor-authentication and follow the instructions. If you set up only one MFA device, when you configure the nodeserver you just need to enter the MFA code. If you setup up two MFA devices, you need to enter the MFA device name as well.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/UniversalDevicesInc/tesla-nodeserver/issues/23#issuecomment-821986204 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AS23Q47OKQXEQZZAD2RBJELTJLH3JANCNFSM4XSKPOPQ . https://github.com/notifications/beacon/AS23Q46MZJZEYU4LRH6SZV3TJLH3JA5CNFSM4XSKPOP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGD7IHHA.gif
Recently I noticed that the data in the Tesla nodes in my ISY was not correct, or missing altogther.
Regardless of how I queried the node, or updated the node, the data did not change.
I deleted the node from the PGC. Reinstalled. Several times. I am now noticing the following:
2021-02-13 16:43:19 info: NS: Discovering new vehicles 2021-02-13 16:43:19 info: NS: Tesla API: /api/1/vehicles 2021-02-13 16:43:19 info: NS: Getting new tokens 2021-02-13 16:43:19 error: NS: Tesla API /api/1/vehicles returned: 400 - {"response":null,"error":"Endpoint deprecated: Please update your App.","error_description":""} 2021-02-13 16:43:19 error: NS: Error discovering vehicles: StatusCodeError: 400 - {"response":null,"error":"Endpoint deprecated: Please update your App.","error_description":""} at new StatusCodeError (/app/nodeserver/node_modules/request-promise-core/lib/errors.js:32:15) at Request.plumbing.callback (/app/nodeserver/node_modules/request-promise-core/lib/plumbing.js:104:33) at Request.RP$callback [as _callback] (/app/nodeserver/node_modules/request-promise-core/lib/plumbing.js:46:31) at Request.self.callback (/app/nodeserver/node_modules/request/request.js:185:22) at Request.emit (events.js:193:13) at Request. (/app/nodeserver/node_modules/request/request.js:1154:10)
at Request.emit (events.js:193:13)
at IncomingMessage. (/app/nodeserver/node_modules/request/request.js:1076:12)
at Object.onceWrapper (events.js:281:20)
at IncomingMessage.emit (events.js:198:15)
Please advise.
Regards
Carl