To hopefully save some people some pain, don't update Home Assistant Core until the Lucid support gets updated. This core update breaks things again.
Thanks for the heads up! Which core version breaks the integration? I'm on 2026.9.4 and still working fine.To hopefully save some people some pain, don't update Home Assistant Core until the Lucid support gets updated. This core update breaks things again.
Same. 2026.10.0 is the latestThanks for the heads up! Which core version breaks the integration? I'm on 2026.9.4 and still working fine.
Yes, I updated to 2026.10.0 yesterday, and the Lucid integration no longer loads.Same. 2026.10.0 is the latest
@segbrk is currently enjoying an extended road trip in his Gravity, and @borski has a day job now. We may have to wait a bitHere’s the error:
Unable to install package lucidmotors==1.4.1: error: No solution found when resolving dependencies cause: Because lucidmotors>=1.4.1 depends on protobuf>=6.31.1,<7.0.0 and protobuf==7.36.0, we can conclude that lucidmotors>=1.4.1 cannot be used. And because you require lucidmotors==1.4.1, we can conclude that your requirements are unsatisfiable.
Thanks everyone for your patience, and thanks especially @opdx and everyone else for your contributions.Fix status:
Testing: I ran the fix using my account (read-only: login and vehicle fetch), and it worked on both. I didn't test write commands like lock or climate but I assume they're fine.
- The library fix is open at nshp/python-lucidmotors#31. It allows protobuf 7 and bumps the version to 1.4.2.
- The integration-side change is a draft at borski/ha-lucidmotors#52. It points the integration at 1.4.2, and it can’t merge until the library is published to PyPI.
- Tracking issue: borski/ha-lucidmotors#51
Nothing fixes this until Nick publishes 1.4.2 for python-lucidmotors. Once that's there, @borski can fix the Home Assistant integration. Until then, either hold off on HA 2026.10 or roll back to 2026.9.