airco is the standard heating config from the device and airco+ is the config which can be defined with $startOptionsVariable
[defrost:[true|false]] | [windscreenHeating:[true|false] | [temperature:number]
I create a separated config for this:
New plugin pimatic-bluelink
airco is the standard heating config from the device and airco+ is the config which can be defined with $startOptionsVariable
[defrost:[true|false]] | [windscreenHeating:[true|false] | [temperature:number]
I create a separated config for this:
If i understand correctly. You are using 2 x switch and 1 x variablesInput, to set the content of $startOptionsVariable. With the airco+ button you want to switch the airco on with the option string $startOptionsVariable.
I will make the variable name configurable in the device config. To make it more generic.
Yes that is correct. The current variant works for me.
I am using a script which decides, depending from the outside temperature which mode (airco or airco+) will be send to the car.
To I like to keep two buttons, one for each mode.
But if you any nice idea you like to implement, I will test it.
Can you give a short info how to use the new optionsVariable
?
So you mean the variable which contain.
[defrost:[true|false]] | [windscreenHeating:[true|false] | [temperature:number]
Will try it when the car is back home. Currently I am expecting the aircon is OFF. But the off
button is not active after the update, as it is for the other functions which are off.
EDIT: My wife is driving the car in this moment. So the air con is on. I will test all this later. Will report then.
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?
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!
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:
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
Follow my domotica project on http://maredana.nl