I created a first version of the buttons for airco, doors, charging and refresh.
Version 0.2.11
-
Hi,
looks good, just the “refresh” button do not work for me. I am getting following error on the UI
The other buttons works fine.
-
How I am running into this
-
Works for me. Thx for the update!
-
A thing I was thinking about is a device provided button for the second aircon mode which can be realized with $startOptionsVariable like
airco+
.
I could imagine not every user is using it, so it should be an option to have it on the UI.
My idea is to keep the two fields button as it is now >airco|off
and to get the option for a three fields buttonairco|airco+|off
.Maybe you like it
-
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