JLR InControl v1.5.0-beta.4
Pre-releaseYou will need to sign in again after updating — Settings › Devices & Services › Jaguar Land Rover InControl › ⋮ › Reconfigure. Not because of anything in this release; the session you have now has almost certainly already lapsed.
What changed
The owner-portal session that location depends on was being kept alive on the 15-minute housekeeping cycle. That is too slow. Measured on a live account: a portal session was already gone 15 minutes and 4 seconds after an interactive sign-in, and the identity session behind it refused to mint a replacement — both dead, from one emailed code, inside a quarter of an hour. The keep-alive was not preserving the session, it was discovering the loss.
It now runs on its own 4-minute clock, well inside the shortest session life observed. If the portal session has a short idle timeout, this should hold it open indefinitely and location will survive on a single sign-in.
A lost session is also reported the moment the keep-alive finds it, rather than up to half an hour later, and the touching then stops rather than retrying a sign-in that cannot succeed.
This is an experiment, and it may not work
If four minutes is still too slow, or the endpoint being touched does not count as activity on JLR's side, you will still be asked to sign in. Reports either way are genuinely useful — please say how long location kept working before it asked again.
Live vehicle status over the telemetry websocket is unaffected by any of this and keeps working regardless.
What's Changed
- Keep the portal session alive on a four-minute clock
Installation
HACS (recommended)
Add https://github.com/willbeeching/ha-jlr-incontrol as a custom repository (category Integration), install, and restart Home Assistant.
Manual
Download jlr_incontrol.zip, extract into config/custom_components/, and restart Home Assistant.