New plugin pimatic-bluelink
THe gui show only the car data. Commands can be sent via rules (which can be linked to buttons!)
The rule commands are
bluelink <KiaDevice/Hyundai device Id>
[start $startOptionsVariable | startDefault | stop |
lock | unlock | chargeStart | chargeStop | refresh ]
Update works for me on the Kia front as well 
I also haven’t faced any error. Browser cache!?
info [pimatic-bluelink]: CarConfig: {
"nickname": "KONA EV",
"name": "KONA EV",
"regDate": "2021-02-22 18:24:02.322",
"brandIndicator": "H",
"id": "5718f427-*****-*****-*****-********4c",
"vin": "TMAK******",
"generation": "2020"
}
Is this the info after your manual config? if not, can you post this info, in the discovery scenario?
@bertreb said in New plugin pimatic-bluelink:
info [pimatic-bluelink]: CarConfig: { "nickname": "KONA EV", "name": "KONA EV", "regDate": "2021-02-22 18:24:02.322", "brandIndicator": "H", "id": "5718f427-*****-*****-*****-********4c", "vin": "TMAK******", "generation": "2020" }Is this the info after your manual config? if not, can you post this info, in the discovery scenario?
This is in the logs after starting discovery and before trying to save the device.
They look the same.
Can you check/post the debug starting with the line 'ClientReady ready, Device starting, requesting vehicle’
And this in the discovery mode, when you save the device
@bertreb In discovery mode “Client ready” is not logged. I get this log for the manually created devices.
11:32:10 debug [pimatic-bluelink]: odo {
"value": 326,
"unit": 1
}
11:32:10 debug [pimatic-bluelink]: location {
"latitude": XX.474811,
"longitude": XX.861789,
"altitude": 6,
"speed": {
"unit": 0,
"value": 0
},
"heading": 177
}
11:32:09debug [pimatic-bluelink]: Switching to passive poll, with polltime of 3600000 ms
11:32:09debug [pimatic-bluelink]: Car status PollTimeActive is false
11:32:08debug [pimatic-bluelink]: Status: {
"airCtrlOn": false,
"engine": false,
"doorLock": true,
"doorOpen": {
"frontLeft": 0,
"frontRight": 0,
"backLeft": 0,
"backRight": 0
},
"trunkOpen": false,
"airTemp": {
"value": "10H",
"unit": 0,
"hvacTempType": 1
},
"defrost": false,
"acc": false,
"evStatus": {
"batteryCharge": false,
"batteryStatus": 48,
"batteryPlugin": 0,
"remainTime2": {
"etc1": {
"value": 56,
"unit": 1
},
"etc2": {
"value": 710,
"unit": 1
},
"etc3": {
"value": 160,
"unit": 1
},
"atc": {
"value": 17,
"unit": 1
}
},
"drvDistance": [
{
"rangeByFuel": {
"evModeRange": {
"value": 0,
"unit": 1
},
"totalAvailableRange": {
"value": 0,
"unit": 1
}
},
"type": 2
}
],
"reservChargeInfos": {
"reservChargeInfo": {
"reservChargeInfoDetail": {
"reservInfo": {
"day": [
1,
2,
3,
4,
5
],
"time": {
"time": "0720",
"timeSection": 0
}
},
"reservChargeSet": false,
"reservFatcSet": {
"defrost": false,
"airTemp": {
"value": "10H",
"unit": 0
},
"airCtrl": 1,
"heating1": 0
}
}
},
"offpeakPowerInfo": {
"offPeakPowerTime1": {
"starttime": {
"time": "1200",
"timeSection": 0
},
"endtime": {
"time": "1200",
"timeSection": 0
}
},
"offPeakPowerFlag": 0
},
"reserveChargeInfo2": {
"reservChargeInfoDetail": {
"reservInfo": {
"day": [
1,
2,
3,
4,
5
],
"time": {
"time": "1200",
"timeSection": 0
}
},
"reservChargeSet": false,
"reservFatcSet": {
"defrost": false,
"airTemp": {
"value": "10H",
"unit": 0
},
"airCtrl": 1,
"heating1": 0
}
}
},
"reservFlag": 1,
"ect": {
"start": {
"day": 9,
"time": {
"time": "1200",
"timeSection": 0
}
},
"end": {
"day": 9,
"time": {
"time": "1200",
"timeSection": 0
}
}
},
"targetSOClist": [
{
"targetSOClevel": 80,
"dte": {
"rangeByFuel": {
"evModeRange": {
"value": 356,
"unit": 1
},
"totalAvailableRange": {
"value": 356,
"unit": 1
}
},
"type": 2
},
"plugType": 0
},
{
"targetSOClevel": 80,
"dte": {
"rangeByFuel": {
"evModeRange": {
"value": 356,
"unit": 1
},
"totalAvailableRange": {
"value": 356,
"unit": 1
}
},
"type": 2
},
"plugType": 1
}
]
}
},
"ign3": false,
"hoodOpen": false,
"transCond": true,
"steerWheelHeat": 0,
"sideBackWindowHeat": 0,
"tirePressureLamp": {
"tirePressureLampAll": 0,
"tirePressureLampFL": 0,
"tirePressureLampFR": 0,
"tirePressureLampRL": 0,
"tirePressureLampRR": 0
},
"battery": {
"batSoc": 69,
"batState": 0
},
"sleepModeCheck": true,
"time": "20210303073409"
}
11:32:08 debug [pimatic-bluelink]: Next poll in 600000 ms
11:32:08 debug [pimatic-bluelink]: requesting status
11:32:08 debug [pimatic-bluelink]: From device start - starting status update cyle
11:32:08 debug [pimatic-bluelink]: ClientReady ready, Device starting, requesting vehicle
@bertreb In the log only the “Client error: Uncaught Type Error: …” shows up. Nothing else.
Client error… is mostly a gui problem. You did all the clear browser cache, etc ?
A way to debug gui errors is to use the ‘inspect element’ of your browser.
You get more details on where the error orginated
@bertreb The dev tools from the browser helped. There is a type in pimatic-bluelink.coffee.
@_discoveryClass = "HuyndaiDevice" //wrong
@_discoveryClass = "HyundaiDevice" //correct
After patching this, the UI provides much more settings for the discovered device and savings works as it should.
@bertreb Workfs for me! Thanks.
I’m trying to control my Hyundai car now via rules. I try to execute a bluelink action after switching a DummyButton.
But I’m not able to set a valid action to execute. In the image you see that the text completion suggests "the " what doesn’t make sense to me.
When I try the following:
“bluelink kona refresh”
I receive: Could not find an provider that provides the next action of “bluelink kona refresh”.
Any hints how to fix that? Thanks.
@bertreb Thanks for fixing and for all the work and time you invest and share with us!
What about adding some controls to the Device to refresh the status, start air condition and start charging?
Do you mean gui controls?
There are no gui command buttons only rule actions. If there a need to have command button i will add them.
The following rule commands are available and you could build easily command buttons with a ButtonsDevice and some rules. Have the command button separate from all the car info, seems also more clearer.
The action syntax:
bluelink <KiaDevice/Hyundai Id> [start $startOptionsVariable | startDefault | stop |
lock | unlock | chargeStart | chargeStop | refresh ]
Commands:
The $startOptionsVariable syntax is a string variable with the following format:
[defrost:[true|false]] | [windscreenHeating:[true|false] | [temperature:number]
See also github
@bertreb sorry, that’s not what I’ve meant.
I know I can control the car via rules. I want to execute the actions directly from the GUI. so it would look like
Of course with other buttons like “refresh”, “charge”, “start airco”.
