Add support for Europe CCS2 request (v2)#290
Conversation
|
@Hacksore can we push this forward? |
|
Is this a breaking change or backwards compat and can land in 8.x version? |
|
For cars supporting the new ccs2 protocol, the unparsed payload of full status will change. The parsed status keeps the same format, but is missing a few data points compared to the old endpoint data. Overall, these changes should only affect the new ccs2 enabled cars, like Kia EV3, EV6 facelift etc. |
|
Just to be safe ill bump major version and we Thanks for the contribution! |
.
|
could somebody also bump the NodeRed integration to the new Version @Hacksore thx a lot |
|
@bausi2k Have not yet tested it, but should not be needed, as it uses the latest bluelinky release on install: https://github.com/SondreNjaastad/node-red-contrib-bluelinky/blob/77d43ad8ee2d14cab0a638959cf22ea1c1232160/package.json#L36 |
|
seems not to - i've removed the NR palette restartet the conatiner, installed it again and the detail data has no EV Infos yet… |
|
Probably best if you open an issue at https://github.com/SondreNjaastad/node-red-contrib-bluelinky |
3 participants
As #283 seems to be stuck, I started all over again. Anyways, thanks @arteck for the preparatory work!
The
ccuCCS2ProtocolSupportgets stored and is used to prefer the/ccs2/carstatus/latestover the/statusAPI. I also added parsing the data intoVehicleStatus, although I was not yet able to interpret every parameter from the old model.While trying to implement the refresh via
/ccs2/carstatus, I got an error stating, that this is not yet available for the Europe region. So it might be able to add it in again at a later point in time.