API changed (yesterday) about weconnect-cli HOT 5 CLOSED

Hmmm, that is strange, I don't have any issues right now. Do you have any logfiles showing the problem? You can increase verbosity with -vvv

from weconnect-cli.

DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): login.apps.emea.vwapps.io:443
DEBUG:urllib3.connectionpool:https://login.apps.emea.vwapps.io:443 "GET /refresh/v1 HTTP/1.1" 200 3833
INFO:weconnect:Token refreshed
Traceback (most recent call last):
File "/usr/local/bin/wc-cli", line 8, in
sys.exit(main())
File "/usr/local/lib/python3.8/site-packages/weconnect_cli/weconnect_cli.py", line 157, in main
weConnect.fillCacheFromJson(args.cachefile, maxAge=args.interval, maxAgePictures=args.pictureCache)
File "/usr/local/lib/python3.8/site-packages/weconnect/weconnect.py", line 241, in fillCacheFromJson
self.__cache = json.load(file)
File "/usr/local/lib/python3.8/json/init.py", line 293, in load
return loads(fp.read(),
File "/usr/local/lib/python3.8/json/init.py", line 357, in loads
return _default_decoder.decode(s)
File "/usr/local/lib/python3.8/json/decoder.py", line 340, in decode
raise JSONDecodeError("Extra data", s, end)
json.decoder.JSONDecodeError: Extra data: line 1 column 671877 (char 671876)

That is what I get with -vvv.

from weconnect-cli.

Somehow your cache became corrupted. This is easy to fix, you just delete the cache file. I will implement that the cache will be deleted in this case.
Thank you for reporting this issue!

from weconnect-cli.

Thanks, that worked!
Great tool!

from weconnect-cli.

Fixed in 0.15.1.
The cache is now deleted automatically if corrupted. A message should still be shown to inform the user.

from weconnect-cli.