Conversation
Hacksore
left a comment
Hacksore
left a comment
There was a problem hiding this comment.
We can also remove all he files from dist/ that were committed too.
| node_modules/ | ||
| .DS_Store | ||
| .rpt2_cache | ||
| dist/ |
| format: 'cjs', | ||
| name: 'index', | ||
| file: 'dist/index.cjs', | ||
| file: 'j:/source/ioBroker/SmartHomeEnt/node_modules/bluelinky/dist/index.cjs', |
| name: 'index', | ||
| exports: 'named', | ||
| file: 'dist/index.esm.js', | ||
| file: 'j:/source/ioBroker/SmartHomeEnt/node_modules/bluelinky/dist/index.esm.js', |
|
|
||
| const fullStatus = cachedResponse.body.resMsg.vehicleStatusInfo; | ||
|
|
||
| const ccs2Response = this.updateRates( |
There was a problem hiding this comment.
This means we'd do one request for the old endpoint and another on for CCS2, do we want that?
I'm pretty out of the loop regarding the new API.
|
@arteck could you share some information about how you managed to discover this new API endpoint? I would like to make an extension that allows for controlling the vehicle to load (V2L) capability and for that I need to find the proper endpoint and the request body shape. |
lol.. google helps...and other GIT repos you can also use wireshark and check the app communication |
|
The CCS2 API seems to be a new standard for vehicles equipped with a ccNC infotainment. A sample integration in Python is available here |
|
seems to be related to my issue: #287 |
|
Also affects the Kia EV3, can we push that forward? Need a hand @arteck? |
I'm getting my EV3 in 2 weeks. Will be able to test and develop from then on. Where are we at the moment regarding the CCS2 endpoints? Where is help needed? |
Hi @PierreLevres, I made good progress for the car status, see #290. |
7 participants
No description provided.