EU/Hyundai setting heating temperature value not used
memed36 opened this issue · comments
When using start() to trigger hvac heating is started, but temperature value is not used - always defaults to last value set in Bluelink app.
I used the code sample from https://bluelinky.readme.io/reference/start to create a js script "start.js" which works (npm run start shows no error, HVAC in my BEV car starts), but the temp value is ignored. I set temp to 17, 25 and 27 (celsius) bit when verifying with debug.ts (npm start debug) "status raw" shows ""value": "10H"" as temperature value and "status fetched from car" shows "temperatureSetpoint": 22 (Celsius). A working config.json exists and is used for start.js and debug.ts .
Usefull info(please complete the following information):
- OS: Linux (Debian 9, Python 3.7.9, NPM v8.5.0)
- Bluelinky Version v7.6.6
- Region: EU
- Brand: hyundai
- Car model: Ioniq 5 AWD
Additional context
start.js sample script:
const BlueLinky = require("bluelinky");
config = require('../config.json');
const { username, password, pin, vin, region, brand } = config;
const client = new BlueLinky({
username,
password,
brand,
region,
pin
});
client.on("ready", async () => {
const vehicle = client.getVehicle(vin);
const response = await vehicle.start({
airCtrl: true,
igniOnDuration: 10,
airTempvalue: 25,
defrost: false,
heating1: false,
});
});
client.on('error', async (err) => {
// something went wrong with login
});
Status output from debug.ts attached for raw and parsed.
As @PierreLevres pointed out, the start arguments changed, now this interface is expected :
bluelinky/src/interfaces/common.interfaces.ts
Line 419 in 22c3d8e
Thanks, missed that!
My bad.
Thx for the quick help and the great work!