New plugin pimatic-bluelink

---

Yes, that variable.
I needed to change the 2-state boolean airco to a 3-state string. Could be the reason none of the airco buttons are active.
Do you see any debug info on this?

I found the reason for the blank airco buttons, please update to 0.2.15

Some debug for you:

17:41:54.285 [pimatic-bluelink] debug: _key: temperature, _val: 23
17:41:54.288 [pimatic-bluelink] debug: _key: defrost, _val: true
17:41:54.288 [pimatic-bluelink] debug: _key: windscreenHeating, _val: true
17:41:54.288 [pimatic-bluelink] debug: Unknown command startPlus

Getting a “Bad Request” after pressing airco+

I can’t make any checks at the moment, a remote process is somehow hanging. The app has problem as well, so this is no problem of the plugin. Will try it later again. For such situations I am missing something like an indicator that show if a command is running, answered or the response is missing. When I stay beside the car I can see the reaction, but from remote I can just wait for a status change. At the moment I am verifying this with the UVO app. If you have an idea for this it would be nice.

While a remote service is in progress, no further command can be send. The api returns following:

18:06:35.187 [pimatic-bluelink] debug: Error start car: {
18:06:35.187 [pimatic-bluelink] debug:>  "name": "HTTPError",
18:06:35.187 [pimatic-bluelink] debug:>  "host": "prd.eu-ccapi.kia.com:8080",
18:06:35.187 [pimatic-bluelink] debug:>  "hostname": "prd.eu-ccapi.kia.com",
18:06:35.187 [pimatic-bluelink] debug:>  "method": "POST",
.
.
.
18:06:35.187 [pimatic-bluelink] debug:>    ]
18:06:35.187 [pimatic-bluelink] debug:>  },
18:06:35.187 [pimatic-bluelink] debug:>  "body": {
18:06:35.187 [pimatic-bluelink] debug:>    "retCode": "F",
18:06:35.187 [pimatic-bluelink] debug:>    "resCode": "4004",
18:06:35.187 [pimatic-bluelink] debug:>    "resMsg": "Duplicate request - Duplicate request",
18:06:35.187 [pimatic-bluelink] debug:>    "msgId": "someID"
18:06:35.187 [pimatic-bluelink] debug:>  }
18:06:35.187 [pimatic-bluelink] debug:>}

Would be nice if you could indicate such things.

BTW: The app shows the same error code in this moment

@ortin said in New plugin pimatic-bluelink:

Some debug for you:

17:41:54.285 [pimatic-bluelink] debug: _key: temperature, _val: 23
17:41:54.288 [pimatic-bluelink] debug: _key: defrost, _val: true
17:41:54.288 [pimatic-bluelink] debug: _key: windscreenHeating, _val: true
17:41:54.288 [pimatic-bluelink] debug: Unknown command startPlus

Getting a “Bad Request” after pressing airco+

I fixed the Bad Request error, version 0.2.16

The bad request is gone. Thx! Testing is a bit hard at the moment, because the command runtimes are really long (2 min). I think this is caused by the backend. Almost no command gets executed.

The debug info is:

.
.
.
19:44:29.701 [pimatic-bluelink] debug:>  "body": {
19:44:29.701 [pimatic-bluelink] debug:>    "retCode": "F",
19:44:29.701 [pimatic-bluelink] debug:>    "resCode": "5031",
19:44:29.701 [pimatic-bluelink] debug:>    "resMsg": "Unavailable remote control - Service Temporary Unavailable",
19:44:29.701 [pimatic-bluelink] debug:>    "msgId": "a4e8c37a-ef1f-4640-a060-0153a29da5d6"
19:44:29.701 [pimatic-bluelink] debug:>  }

Will try later!

Ok, i will publish a version with an extra field showing the status -> 0.2.17

pimatic-bluelink version 0.2.22

Pimatic-bluelink is updated with the latest used library and some extra features.
The plugin supports Hyundai and Kia cars that are bluelink enabled.
Gui buttons and info:

More info

Hey bertreb,
is it a big deal to make the available buttons of the device operable via the RestAPI?

.../api/device/kia-esoul/buttonPressed?buttonId=refresh

I am currently lightweight my system, so I could save several rules.
I created a button device in the beginning of your plugin to operate the command from pimatic. Now as you updated the plugin with onboard buttons the old rule based buttons are obsolet, but I still need them to operate the bluelink device via the pimatic RestAPI
Would be nice to be able to press the buttons via api.

Hi, you can use

.../api/device/kia-esoul/changeActionTo?action=refresh

and the other buttons functions can be activated this way.
Replace ‘refresh’ with start, startPlus, stop, unlock, lock, startCharge or stopCharge

Nice, exactly what I need! Haven’t used this till now

Hi, the plugin is working nice but sometimes the data is not refreshed when I click the refresh button.
When I refresh in the bluelink app and after that in pimatic I get the new data.

I had a docker running before and the same “problem” was there.
When I changed line 101 to true it worked.
https://github.com/wranglatang/docker-bluelinky/blob/master/server.js#L101

Hyundai(or bluelinky) seems to have 2 types of request, status from the webserver or status from the car.
https://github.com/Hacksore/bluelinky/blob/fef9c30bbf8089b35d7ef0ae0b9f6210307013c9/src/vehicles/european.vehicle.ts#L197

I looked in the plugin to see if I can find something similair but coffee script and me are not friends

Hi thanks for the tip.
The refresh should query the car and not the status in the cloud.
I will check this.

I updated the plugin to get the realtime car status -> version 0.2.26
@incmve if you could check and hopefully confirm that it works

Hadn’t any problem with the last plugin version, but can confirm, that the update works for me as well!

@bertreb said in New plugin pimatic-bluelink:

I updated the plugin to get the realtime car status -> version 0.2.26
@incmve if you could check and hopefully confirm that it works

Nice, this seems to work

@bertreb said in New plugin pimatic-bluelink:

Am I overlooking something? Because I can’t seem to get the rest api to work.
.../api/device/OS_EV_CZECH_20/changeActionTo?action=refresh

Does the button refresh works?

In pimatic yes.

The gui (pimatic-mobile-frontend) uses the same api, so it should work
Do you have debug on and can you post the log after the api call?