fermulator
commented
4 years ago Took a stab at things today ... I fear we're in another API backwards compatibility breakage.
The best thing to do atm is to get down into the POST ... I've tried varying permutations of posting to the API endpoint without success.
as a start:
$ cat params.json
{
"RegionCode": "NCI",
"UserId": "someuser",
"custom_sessionid": "",
"initial_app_str": "9s5rfKVuMrT03RtzajWNcA"
}and then try....
2$ curl -v --data "@params.json" --data-urlencode "Password=foobar" -X POST https://gdcportalgw.its-mo.com/api_v190426_NE/gdc/UserLoginRequest.php
Note: Unnecessary use of -X or --request, POST is already inferred.
* Trying 54.199.141.237...
* Connected to gdcportalgw.its-mo.com (54.199.141.237) port 443 (#0)
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 604 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_RSA_AES_256_GCM_SHA384
* server certificate verification OK
* server certificate status verification SKIPPED
* common name: *.its-mo.com (matched)
* server certificate expiration date OK
* server certificate activation date OK
* certificate public key: RSA
* certificate version: #3
* subject: C=JP,ST=Tokyo,L=Minato-ku,O=ZENRIN DataCom Co.\,LTD.,OU=Engineering Section(1),CN=*.its-mo.com
* start date: Wed, 25 Sep 2019 01:24:23 GMT
* expire date: Wed, 23 Dec 2020 14:59:00 GMT
* issuer: C=JP,O=Cybertrust Japan Co.\, Ltd.,CN=Cybertrust Japan Public CA G3
* compression: NULL
* ALPN, server did not agree to a protocol
> POST /api_v190426_NE/gdc/UserLoginRequest.php HTTP/1.1
> Host: gdcportalgw.its-mo.com
> User-Agent: curl/7.47.0
> Accept: */*
> Content-Length: 137
> Content-Type: application/x-www-form-urlencoded
>
* upload completely sent off: 137 out of 137 bytes
< HTTP/1.1 200 OK
< Date: Wed, 19 Feb 2020 01:30:13 GMT
< Server: Apache
< Strict-Transport-Security: max-age=15768000
< Connection: close
< Transfer-Encoding: chunked
< Content-Type: text/html; charset=UTF-8
<
* Closing connection 0
{"status":404,"message":"INVALID PARAMS"}What's interesting though is that I'm not sure if the data should be binary or not .. either way nothing is working
$ curl --data-urlencode "@params.json" --data-urlencode "Password=foobar" -X POST https://gdcportalgw.its-mo.com/api_v190426_NE/gdc/UserLoginRequest.php
$ curl --data-binary "@params.json" --data-urlencode "Password=foobar" -X POST https://gdcportalgw.its-mo.com/api_v190426_NE/gdc/UserLoginRequest.php
.,..all result in
{"status":404,"message":"INVALID PARAMS"}Helper Refs:
- https://gist.github.com/subfuzion/08c5d85437d5d4f00e58
- https://virantha.com/2016/04/07/updated-reverse-engineering-nissan-connect-ev-protocol/
- https://programtalk.com/vs2/python/6154/pycarwings2/pycarwings2/pycarwings2.py/
- https://www.reddit.com/r/leaf/comments/5sxzd5/trouble_with_carwings_getting_data_from_my_leaf/
- https://community.home-assistant.io/t/nissan-leaf-component-s-platform/38663/338
- https://github.com/BenWoodford/home-assistant/blob/nissanleaf/homeassistant/components/nissan_leaf.py
linuscorin
niklasosth
muldy
Kalkran
avleen
mzakharo
Good day,
Initially tried this via https://www.home-assistant.io/integrations/nissan_leaf/, however it didn't work with:
Reproduced it with my account hitting Canada NCI portal using latest
pycarwings2:As per the
README.md, did the basic install, and copied down some examples w/my_config.ini.Had to tweak
get-leaf-info.pyto hit my python3 directly (notenv python), otherwise it is left unmodified.After that, it ran, and repro'd the problem:
Open to working through/debugging (just filing the issue report for now). If anyone has guidance happy for it to get a jump start.
It may be worth noting (since I'm not sure if different regions have different account rules):
@,-)