#iain-dev->#stage

[iainbullock]

Get ready for next production release by rolling up all #iain-dev updates as below:

0.4.3-dev

• Development release to improve robustness, and fix various things identified in previous dev releases:

  • Terminate tesla-control processes that run longer than $TC_KILL_TIMEOUT seconds. Discussion: body-controller-state: Error: failed to find a BLE device: .... tesla_ble_mqtt_core#142
  • Wait for tesla-control processes to finish before moving on with the sequence. There is now no need to sleep after each command is sent, so the $BLE_CMD_RETRY_DELAY environment variable is deprecated. Credit to BogdanDIA for this. https://github.com/BogdanDIA
  • Don't make body-controller-state calls every $PS_LOOP_DELAY as it's too hard on the bluetooth. The preferred means of determining presence is confirmed as the original passive bluetooth scanning, not body controller state. Awake sensor is not now updated every $PS_LOOP_DELAY secs but only when state is read or a command is sent
  • Function teslaCtrlSendCommand() is deprecated in favour of the improved sendBLECommand()
  • Patch vehicle-command to allow BT versions <=5.0, and to specify the hci device number using environment variable $BLE_HCI_NUM. Credit again to BogdanDIA. Discussion: Specify minimum BT version tesla_ble_mqtt_core#125
  • Use the latest version of vehicle-command (v0.3.3 at the time of writing), which amongst other things adds 'Refactor BLE connecting to allow scanning for vehicle presence' Refactor BLE connecting to allow scanning for vehicle presence teslamotors/vehicle-command#353, though I'm not sure how this gets used in practice. More importantly it claims to fix 'ble.NewConnection sometimes never returns' ble.NewConnection sometimes never returns teslamotors/vehicle-command#272, which if it works will improve robustness for some users

• NEW Features:

  • New poll_state_loop delay and tesla-command timeout environment variables added, to allow the user to fine tune settings which may affect speed versus robustness
  • Environment Variable $IMMEDIATE_UPDATE. If this is set to true (default), then after a command has been successfully sent to the car, the state_topic for the relevant entity is immediately updated. If set to false, this doesn't happen automatically, the state_topic is updated at the next polling occurence or a force update button press. See Entities do not update after command #82

• Fixes:

  • Standardize on Celsius #144 (_core). This deprecates the $TEMPERATURE_UNIT_FAHRENHEIT environment variable, and removes associated code. Thanks to https://github.com/aneisch for the suggestion and for modding and testing the code. In doing so, he found an error in the HA MQTT Number entity code MQTT Number Entity Native Unit Comparison Error home-assistant/core#135619
  • Odometer sensor now has a device_class defined, so units can be selected in the Settings dialog for the entity in HA After setting to < than 5 amps, car go back to 5amps #79
  • Rear heated seats didn't respond to commands
  • If a user has two cars and has one device per car, commands would be received and attempted to be sent by both devices. Thanks to @dettofatto for identifying this, see 0.22 vs 0.4x vs Tesla Fleet vs HA 2025.x #78 (comment)

0.4.2

• RELEASE NEW Feature: Automatic Polling is now possible for state

• NEW Feature: The following new states / entities are added:

  • Sensors: Awake (updated approx every 30 secs from body-controller-state) see note for v0.4.3
  • Binary_Sensors: Presence_BC (experimental presence detection updated approx every 30 secs from body_controller_state rather than listening for BLE mac) see note for v0.4.3
  • Switches: Polling
  • Numbers: Polling Interval
  • Buttons: Force Update buttons for individual state categories

• NEW Feature: Environment variable NO_POLL_SECTIONS is provided to disable updating of various state categories during polling. This speeds up state updates, though less state entities are updated by the polling. The entities can still be manually updated by pressing the Force Update button for the relevent state category

• Changes:

  • 'Force Data Update' Button is renamed to 'Force Update All'
  • Errors which occur whilst reading state will not automatically prevent the next state or state category being read. This will fix an issue reported in #135 below where a user doesn't have a Heated Steering Wheel. This previously prevented any states after this one from being read

• Fixes:

  • [ Dev ] Bad variable name [Dev] Bad variable name #75 (_docker). Many thanks to aneisch and dettofatto who really helped to track down this bug
  • parse error: Invalid numeric literal parse error: Invalid numeric literal #74 (_docker). Many thanks to jipema who also helped a lot in identifying this issue
  • All my sensor entities are "unknown" #131 (_core)
  • Any potential to "read state" via bluetooth? #115 (_core)