Skip to content

Changelog plugin Tesla BLE

IMPORTANT

If there is no information about an update, it means that update only concerns documentation, translation or text changes.

10/08/2026

  • Added: the commands of a new vehicle are arranged by theme (status, charging, climate, openings, vehicle, monitoring, then actions) and a command added by an update joins its group without moving the others; the order of existing vehicles and your manual settings are kept
  • Documentation: the documentation describes the vehicle tile (content, states, return to the standard widget and return to the tile), generic types and the precaution to take when using them with summary actions, the model image (replacement and permanent removal) and the order of commands, with dedicated troubleshooting
  • Change: the plugin description is now available in German and Spanish, in addition to French and English, and the plugin declares these four languages
  • Added: the plugin interface is available in English, German and Spanish: configuration and equipment pages, messages, widget and names of the created commands follow the Jeedom language, with a fallback to French for any missing translation.
  • Documentation: the plugin documentation (full guide and proxy installation) and the version history are now available in English, German and Spanish, and links within the documentation now lead to the intended section
  • Documentation: the documentation explains how to choose between the stable and beta versions and switch back to stable, how to read the changelog, which languages are available and how to change the Jeedom language, and how to report a problem on the Jeedom community forum

10/07/2026

  • Added: four new infos “Odometer” (visible, historized), “Gear”, “Speed” and “Power” (hidden by default) are read when the vehicle is awake, without ever waking it up; they only appear with a proxy able to provide them (fork 2.3.0-tb.2 or more recent) and are created automatically after the proxy update
  • Added: four new infos “Front left tire pressure”, “front right”, “rear left” and “rear right” (in bar, visible, not historized by default) are read at most every quarter of an hour when the vehicle is awake, without ever waking it up; a pressure that is not reported does not replace the previous value; they only appear with a proxy able to provide them (fork 2.3.0-tb.2 or more recent) and are created automatically after the proxy update
  • Added: three new infos “Software update” (None, Available, Downloading or Installing), “Offered version” (visible) and “Progress” (in %, hidden by default) indicate whether a vehicle software update is offered or in progress; they are read at most every quarter of an hour when the vehicle is awake, without ever waking it up, only appear with a proxy able to provide them (fork 2.3.0-tb.2 or more recent) and are created automatically after the proxy update
  • Added: new info “At home” (visible, 1 if the vehicle is within the home radius, 0 beyond), along with “Latitude” and “Longitude”, hidden and not historized by default; home is set in the equipment configuration (Jeedom position and 100 m radius by default); the position is read at most every quarter of an hour when the vehicle is awake, without ever waking it up or appearing in the plugin logs, and these infos only appear with a proxy able to provide it (fork 2.3.0-tb.2 or more recent)
  • Documentation: extended data guide (model, odometer, tire pressure, software update, position): proxy prerequisites, why a piece of data is missing, position privacy (home, radius, logs) and troubleshooting
  • Added: the vehicle commands (battery, lock, interior and exterior temperatures, doors, trunks and charge port, tire pressures, locking and unlocking, starting and stopping charging) now carry their Jeedom generic type, which lets the mobile app, voice assistants and summaries recognize them; the type is set automatically on creation and on plugin update, and a type you chose yourself is never overwritten
  • Added: new vehicle tile on the dashboard and on mobile: battery, charge limit, range, charging status, lock, presence and data age at a glance, with the charge, lock, wake-up and refresh buttons, updated in real time; the other visible commands remain displayed below, and you return to the standard widget by unchecking “Widget template” in the advanced configuration of the equipment (already unchecked if you had customized the display).
  • Added: each vehicle displays the image of its model (Model S, 3, X, Y or Cybertruck) in the equipment list and on its dashboard tile, unless you have chosen or removed its image yourself.

10/06/2026

  • Added: preconditioning scheduled by Jeedom: per vehicle, choose a departure time, the days, the lead time and the maximum duration; Jeedom starts the climate control before departure then stops it at the end of the duration, without ever contradicting a climate control that you started or stopped yourself (“only if plugged in” option, Owner role key required)
  • Fix: off-peak hours charging: the vehicle sleep state is now properly taken into account, a sleeping vehicle whose displayed charging status is stale no longer receives a stop-charging command
  • Documentation: climate and comfort guide: summary of commands (required proxy version, key role, effect on the vehicle), scheduled preconditioning example and troubleshooting of symptoms without a message
  • Added: eight new infos indicate whether each door, the rear trunk, the front trunk (frunk), the charge port and the tonneau cover are open (1) or closed (0), read without waking the vehicle.
  • Added: two new infos, “Occupant present” and “Detailed lock state” (unlocked, locked, locked from inside, selective unlock), read without waking the vehicle; “Vehicle lock” keeps its behavior
  • Added: unlock doors, Open charge port and Sentry Mode now ask for confirmation before sending on the dashboard and mobile, including on existing equipment; it can be removed or restored with the “Confirm action” checkbox in the command configuration (your choice is kept across updates); scenarios are not affected, but a JSON-RPC API client must now send confirmAction=1 for these three commands
  • Added: two new actions, “Open rear trunk” and “Open frunk”, created hidden and with confirmation (fork proxy 2.3.0-tb.2 required); the rear trunk is only opened if it is read as closed, so as never to close a power liftgate.
  • Added: two new infos, “Sentry” (Active, Inactive or Unknown) and “Sentry source” (Actual or Last order), indicate the state of Sentry Mode: read on the awake vehicle with the fork proxy 2.3.0-tb.2 or more recent, otherwise deduced from the last order sent from Jeedom (a change made from the Tesla app is then not seen); the state is kept after a Jeedom restart
  • Added: prolonged opening alerts, disabled by default: per vehicle, choose a duration; Jeedom warns you in the message center, and through two new infos usable in scenarios, when an opening stays open or the vehicle stays unlocked with no occupant beyond that duration
  • Documentation: openings and security guide: summary of functions and their prerequisites, confirmation of sensitive actions, example of an alert for a trunk left open and troubleshooting
  • Added: two new infos “Model” and “Model year” are deduced from the VIN of each vehicle, without any network call, and filled in automatically when the plugin is updated.

10/05/2026

  • Added: the “Charge limit” and “Charge current” sliders automatically take the bounds accepted by the vehicle, published in three new infos (“Minimum charge limit”, “Maximum charge limit”, “Maximum charge current”); a Min or a Max that you set yourself takes priority and is no longer modified
  • Change: a charge limit or charge current setpoint outside the slider bounds is now refused with a message indicating the expected values, without sending anything to the vehicle (previously, a current above the vehicle maximum was accepted then brought back down by the vehicle); a Max already raised by hand is kept
  • Added: ten new charging infos are available (raw battery level, rated and estimated range in km, power, actual current, phases, energy added, cable, fast charging and charging status translated into French), hidden by default: display the ones you need from the Commands tab of the equipment
  • Added: new info “Cumulative charge energy” (kWh, historized): a counter that only increases, usable in the Jeedom Energy plugin, even if the vehicle resets the session energy to zero at each charge
  • Added: new action “Adjust to surplus” (hidden by default): a scenario sends it the available power in watts, and the plugin sets the current, starts or stops charging while limiting the number of commands sent to the vehicle; its settings (voltage, phases, step, hysteresis, interval, start and stop thresholds, hold time) are in the equipment configuration
  • Added: three new infos, hidden by default (“Scheduled charge time”, “Off-peak hours end”, “Scheduled preconditioning”), display in HH:MM format the schedules set in the vehicle and stay empty when the schedule is disabled
  • Added: with the fork proxy, two new actions (hidden by default) let you schedule the days and start time of charging from a scenario, then delete that schedule; with proxy 2.3.0, they are refused without sending anything to the vehicle.
  • Added: off-peak hours charging: within the chosen time range, Jeedom starts charging a plugged-in vehicle and stops it at the target SoC (and, if the option is checked, at the end of the range), without depending on the vehicle schedules
  • Documentation: advanced charging guide: summary of the new infos and actions, step-by-step solar charging example, step-by-step off-peak hours charging configuration, limits, key roles and troubleshooting
  • Added: fourteen new climate infos (auto climate, preconditioning active, front and rear defrost, fan speed, climate keeper dog or camp, overheat protection, rear seat heaters, steering wheel heat level, adjustable min. and max. temperatures, battery heater) are available, hidden by default, without any additional request to the vehicle
  • Added: with the fork proxy, two new actions (hidden by default) “Driver setpoint” and “Passenger setpoint” set the requested temperature on each side, in half-degree steps between 15 and 28 °C within the range accepted by the vehicle; with proxy 2.3.0, they are refused without sending anything to the vehicle
  • Added: with the fork proxy (version 2.3.0-tb.2 at minimum), six new actions set the heating of the front left and right seats, rear left, right and center seats (Off, Low, Medium, High) and of the steering wheel (Off or On); they are created hidden, to be displayed by yourself from the Commands tab, and are refused without sending anything to the vehicle with proxy 2.3.0
  • Added: with the fork proxy (2.3.0-tb.1 or later), new action “Max defrost” (hidden by default) to start or stop the vehicle maximum defrost, which wakes it up and consumes battery; with proxy 2.3.0, it is refused without sending anything to the vehicle
  • Added: new action “Climate keeper mode” (Off, Keep, Dog mode, Camp mode), hidden by default, available with fork proxy version 2.3.0-tb.1 or more recent; while a climate keeper is active, data reading is no longer suspended by the sleep window, to keep the interior temperature up to date

10/04/2026

  • Documentation: the recommended proxy is now the fork image ghcr.io/superdcat/tesla-ble-http-proxy (version 2.3.0-tb.2): installation, switching from the wimaha image without new pairing, image update (manual recommended or automatic), new proxy settings and troubleshooting; the proxy apiToken token must not be enabled with Jeedom
  • Added: the plugin detects the functions that your proxy version does not support: the action concerned is refused right away with the message “Not supported by your proxy version” instead of a false failure, flagged “Function unavailable” in the Commands tab, and the proxy version is displayed in the equipment page; with the fork image, these functions are known from the start.
  • Added: each vehicle exposes the infos “Proxy reachable” (1/0) and “Proxy version”, updated at each cycle without querying the vehicle: a scenario can alert you when the Raspberry Pi or the proxy goes down, without confusing this failure with a vehicle out of range or asleep
  • Added: when the vehicle refuses a command reserved for Owner keys (lock, honk, lights, Sentry Mode, climate control), a clear message explains it, the new info “Key role” indicates the probable role of the proxy key and these commands are flagged in the Commands tab of the equipment
  • Added: the equipment page offers a “Pair my key” help: link to the proxy dashboard, VIN to copy, pairing steps, and a “Check pairing” button that indicates, without waking the vehicle, whether the key is accepted, missing from the proxy, not paired, or whether the vehicle is out of range or the proxy unreachable
  • Added: each vehicle exposes the infos “State read duration” and “Data read duration” (in seconds, without additional requests), and the plugin log warns only once when the proxy reads become abnormally slow (Raspberry Pi too far away, overloaded or poorly powered)
  • Added: a “Proxy logs” button in the plugin configuration displays the last proxy log lines in a refreshable window, without an SSH session on the Raspberry Pi; VINs are masked there
  • Added: the plugin warns you in the message center, only once per episode, when the Bluetooth adapter of the Raspberry Pi seems frozen (vehicle reads timing out while the proxy responds); “Last error” also indicates it, and the threshold is set in the plugin configuration (3 reads by default).
  • Added: each vehicle can now use its own proxy (“Proxy URL of this vehicle” field and “Test this proxy” button in the equipment page), to manage several garages; left empty, it uses the URL from the plugin configuration as before.
  • Change: when several requests target the same proxy, a command, a “Refresh” or a pairing check now takes precedence over the automatic reads of the other vehicles (resumed at the next cycle), and a “Refresh” that could not read the vehicle because the proxy stayed busy indicates it in “Last error”
  • Change: with several vehicles on the same proxy, a vehicle whose key is not paired now displays “Request refused by the vehicle: proxy key not paired with this vehicle” in “Last error” without bothering the others, and the log only reports once per episode a shortened read cycle (then an Info line when a full cycle resumes)
  • Added: new “Proxy API token” field in the plugin configuration: the plugin can now use a fork proxy protected by a token (apiToken), saved encrypted and never displayed again; the Test button indicates whether the token is accepted, refused or missing, and “Last error” reports a refused token
  • Documentation: enabling the proxy apiToken token with Jeedom, new messages of the Test button and troubleshooting a refused token
  • Change: with several proxies, the refresh cycle now reads the proxies in parallel: a slow, frozen or powered-off proxy only delays its own vehicles (those of the same proxy are still read one after the other). No action required.
  • Documentation: several vehicles and several Raspberry Pis (diagrams, adding a second vehicle on the same proxy or a second proxy for another garage), why exchanges with the same proxy happen one after the other, table of numerical limits, step-by-step example of an alert scenario when the proxy stops responding and extended troubleshooting
  • Added: each vehicle has a “Refresh interval” setting (1, 2, 5, 10, 15 or 30 minutes, 5 by default, unchanged for existing vehicles): the plugin checks every minute which vehicles need to be re-read and only reads those whose interval has elapsed, without ever waking them up or stacking two cycles
  • Added: each vehicle can now “let itself be forgotten” in order to fall asleep: awake but idle (not charging, no occupant, unchanged data), it is no longer queried for its charging and climate data during a sleep window adjustable in the equipment page (enabled by default, including on existing vehicles: 3 unchanged reads then 30 minutes); an activity (unlock, door, charge port, occupant), a command or a “Refresh” immediately resumes full reading, and the Info log indicates the opening and end of each window
  • Added: new “Interval while charging” setting (disabled by default): during charging, the vehicle is re-read more often (up to every minute), then the normal rate resumes as soon as charging ends, without ever waking the vehicle
  • Added: new “Refresh (with wake-up)” command: it wakes the vehicle if needed then updates its charging and climate data, on demand or from a scenario; the automatic refresh still never wakes the vehicle.
  • Added: after a successful command (charge limit, current, lock…), the vehicle is automatically re-read 30 seconds later (delay adjustable per vehicle) to display its actual state, without waking it up and without slowing down the command.
  • Added: new per-vehicle setting “Also read the climate”: when disabled, only charging data is requested from the proxy, which lightens the read; the climate infos then keep their last value.
  • Added: new info “Data age (min)”: the number of minutes elapsed since the last read of the vehicle data (0 after each read, 99999 as long as no read is known), to condition your scenarios on data freshness.
  • Documentation: wake-up and rate guide: how the vehicle sleep works, summary table of settings with their default values, recommendations by use (monitoring, solar control), example of a scenario that only acts on recent data thanks to “Data age (min)”, and troubleshooting “the vehicle no longer falls asleep”, “values do not change at night”, “the value displayed after a command is the old one”

10/03/2026

  • Documentation: choice and installation of the Raspberry Pi, key role (Charging Manager or Owner), proxy network security and known limitations of version 0.1
  • Change: the plugin now requires Jeedom 4.5, Debian 11 or 12 and TeslaBleHttpProxy 2.3.0 minimum: Jeedom 4.4 and Debian 10 are no longer supported
  • Fix: under PHP 8, an empty proxy URL or a missing VIN no longer interrupts the refresh of vehicles: the anomaly is reported in the plugin log
  • Change: internal cleanup of the plugin code, with no change in behavior: existing equipment, commands and scenarios remain unchanged
  • Change: during plugin updates, existing equipment is now upgraded automatically, only once per evolution and without touching your settings; the level reached is indicated in the plugin log
  • Documentation: new minimum versions, procedure to check and update the TeslaBleHttpProxy proxy, and how an update from version 0.x proceeds (commands, histories and scenarios kept)
  • Added: the proxy URL is now cleaned up when the configuration is saved: the trailing slash is added, spaces are removed, and an invalid URL or one containing credentials is refused with an explicit message
  • Change: exchanges with the proxy now have maximum timeouts (5 seconds at most when the proxy is off, instead of a 60-second block) and errors are classified by cause in the plugin log (proxy unreachable, vehicle out of range or asleep, proxy without key, request refused by the vehicle), with the VIN masked
  • Added: a “Test” button in the plugin configuration checks that the proxy responds and displays its version, with a warning if it is lower than 2.3.0, as well as a link to the proxy dashboard for key pairing
  • Added: the VIN of a vehicle is now converted to uppercase and stripped of its spaces when saved; an invalid VIN or one already used by another equipment is refused with an explicit message, and the VINs of existing equipment are normalized on update (anomalies reported in the message center)
  • Change: saving an equipment no longer triggers a refresh: the page responds immediately, even with the proxy off; data arrives at the next cycle or with the Refresh command
  • Fix: your command settings (name, visibility, historization, unit, bounds) are no longer overwritten when saving an equipment or reactivating the plugin, and the “Charge port open” info now exists next to the charge port opening action; on an existing equipment, this action may be called “Trappe de Charge Ouvert”: you can rename it
  • Added: the commands of a new vehicle carry corrected French labels (“Démarrer la charge”, “Arrêter la charge”, “Rafraîchir”…); on update, existing equipment keeps its names and receives at the end of the list the new infos “Charge time remaining”, “Last error” and “Last data read”
  • Fix: with TeslaBleHttpProxy 2.1.1 and more recent (2.3.0 required), the vehicle state is again read without waking it up: awake or asleep, locked (including from inside) or not; charging and climate data are therefore read again when the vehicle is awake
  • Change: vehicle presence no longer drops to 0 when the proxy is stopped, without a key or too slow, but only when the vehicle is out of range; with a proxy older than 2.1.1, the infos are no longer modified and the plugin log indicates only once “Version du proxy non prise en charge : 2.3.0 minimum” (Proxy version not supported: 2.3.0 minimum)
  • Fix: range and charge rate are now converted to km and km/h (the vehicle sends them in miles), temperatures keep their decimal, an info missing from the proxy response no longer prevents the update of the others, and a vehicle that falls asleep between two reads no longer produces an error in the log
  • Change: the “Scheduled departure time” info now displays the time in HH:MM format, empty without a scheduled departure, instead of a timestamp: adapt a scenario that compared the old value; the infos “Charge time remaining” (in minutes) and “Charge port open” are now populated
  • Fix: commands sent to the vehicle now report their failure instead of a false success: a refusal by the vehicle (for example a key with the Charging Manager role), an unreachable proxy or an exceeded timeout is displayed in red and in “Last error”; after a successful command, the charge limit, current and lock are updated immediately, and commands go to the proxy one by one without freezing the interface
  • Change: command values are checked before sending: whole charge current within the Min/Max bounds of the command (0 to 32 A by default), whole charge limit between 50 and 100 %, Sentry Mode Enabled or Disabled (the “None” option is removed from existing equipment); a scenario that sends another value now receives an error, and the executeCmd function usable in a Code block is removed
  • Change: the refresh every 5 minutes is more robust: a cycle still running is no longer doubled, its duration is limited to 4 minutes (the remaining vehicles are read at the next cycle), a vehicle in error no longer prevents the others from being read and the log names the vehicle concerned.
  • Added: the infos “Last error” and “Last data read” now indicate why the data no longer moves (proxy unreachable, proxy without key, vehicle out of range…) and since when it has been stale; “Last error” returns to “None” as soon as a refresh succeeds, and the log only keeps one line at the start and one at the end of a problem
  • Change: an internal plugin error when saving an equipment or the configuration, or during the proxy test, now displays a readable message (the detail is written in the plugin log) instead of leaving the page without a response; the plugin page also has a description in English
  • Documentation: complete guide for version 1.0: proxy and Raspberry Pi installation, URL configuration and Test button, unique VIN, key role (Charging Manager or Owner), tables of commands with their identifiers, types and units, and message-by-message troubleshooting
  • Change: update reminder: the “Scheduled departure time” info goes from the numeric sub-type to the Other sub-type (time in HH:MM format); if it was historized, it stays numeric and is no longer updated until you change its sub-type to Other in the Commands tab of the equipment
  • Documentation: new “Install the BLE proxy” page, step by step on a Raspberry Pi Zero 2 W (card preparation, Docker, key pairing, maintenance, security, troubleshooting, references)
  • Fix: a powered-off or unreachable proxy is again reported as “proxy unreachable”, and no longer as a simple timeout

09/23/2026

  • Complete plugin documentation

03/31/2025

  • Plugin renamed to Tesla BLE (identifier TeslaBLE)
  • Added hardware compatibilities (Smart, Luna, Atlas, Raspberry Pi, Docker, DIY...)
  • Default visibility of commands on the widget
  • Various fixes

03/15/2025

  • Version 0.1 beta, first version
  • Reading of the vehicle state (presence, lock, sleep) without waking it up
  • Reading of charging, battery, range and climate when the vehicle is awake
  • Commands: wake-up, start and stop charging, charge current and limit, climate control, charge port, lights, horn, door locking, Sentry Mode
  • Automatic refresh every 5 minutes