0.30.0 released

[tillsteinbach]

Fixed

• Requests tracking behaviour
• Catch error when token could not be fetched

Changed

• Requests changed from list to dict

Added

• Possibility to use temperature when startng climatisation
• Added fail_no_external_power to generic request status
• Added chargeType attribute to chargingStatus
• Added chargingSettings attribute to chargingStatus

---

This discussion was created from the release 0.30.0.

[diplix]

i like the new requests tracking behaviour. i catch it in home assistant with a mqtt sensor:

sensor:
  - platform: mqtt
    state_topic: weconnect/vehicles/+/domains/climatisation/climatisationStatus/request/+/status
    name: weconnect_climate_request_status
    unique_id: EB517498-A4B0-4ACB-9F45-DCD0579D0D9A
    availability_mode: all
    availability:
      - topic: weconnect/mqtt/weconnectConnected
        payload_available: "True"
        payload_not_available: "False"

the new possibility to use temperature when startng climatisation raises a problem for me. i set temperature in home assistant with a mqtt hvac device and when i restart home assistant or reload my mqtt settings, the integration sends the temperature to the write topic — which then triggers the heating in the car.

(it’s the little dots in the screenshot, always at reloads/reatarts set to 19°C)

can this new behavior be disabled with a settiing/start option? or could heating the car be only triggered when the temperature changes?

[diplix]

i get a new topic for each request, too. but the + wildcard in … request/+/status… catches them all and it works fine.

the thing with the targetTemperatur_c_writetopic is: i do not want to start heating the car when i restart home-assistant or reload the mqtt integration. but that’s whats happening, because home assistant fires the previously set temperature into the write topic when restarted.

so i asked if there’s an option that either firing the previously set target temperature or a changed target temperature into the write topic would not start heating the car — as it was pre version 0.30.0.

(i found a way to work around this with a couple of home assistant automations, so a solution to my request is not really urgent or necessary. but i think an option to disable the new „possibility to use temperature when startng climatisation“ could make it easier for others)

[tillsteinbach]

Hmmm, but writing a temperature to targetTemperatur_c_writetopic should never cause the heating to start. I can try that out tomorrow, but if that is the case it might be a changed behavior in the car or a bug on my side. The heating should only start with writing to controls/climatisation_writetopic

[diplix]

indeed, it doesn’t. i tried setting the target temperature in mqtt explorer and it doesn’t start heating. i guess home assistant continues to confuse me. however something changed with latest release, i guess i have to refine my debugging.

(found it, it’s an automation firing start into .../controls/climatisation)

[tillsteinbach]

So you can fix it in home assistant?

[diplix]

yes, i had a couple of denkfehler/errors in reasoning. fixed it in my automation-scripting.