-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tesla Fleet: MESSAGEFAULT_ERROR_INCORRECT_EPOCH when unlocking charge port #133575
Comments
Hey there @Bre77, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) tesla_fleet documentation |
I have had same message "Incorrect epoch" several times in past weeks when unlocking the charging port. Sometimes it works, sometimes not. Today starting climate also gave "Incorrect epoch", I tried several times and always same error. Then I enabled debug logging and restarted Tesla fleet integration to get some information. But after integration was restarted everything worked as expected, climate heating was turned on without any issues. At least with the last commands that I sent, Tesla was awake all time, so this is unrelated to the wake-up issue. I have created a script that tries to wake Tesla several times to overcome the wake-up issue. According to some document, it may take even 1.5 minutes to wake up the car and I think integration does not wait that long. Does integration expect Tesla to be wakened up manually before executing any command? That's why I have created a wrapper for all critical commands that I need (heating, charging, etc) that first push integration's wake button and wait until the car is online, if the car is not online in 3 minutes it will try to wake again, totally ten times. If the car is still sleeping it will send an error notification to the user. This first logging is from my wake-up&start climate script that shows two errors from integrations:
Even without debug logging there are few lines in the log directly from the Tesla fleet integration and HA:
|
Does this just sort itself out eventually or do you need to reload/restart to fix the epoch? This is going to be a bug in the underlying library as I had to write the command signing implementation myself. |
The problem
I've uploaded my private key to my Tesla Model Y 2024 via Bluetooth and in general the commands like unlocking the charging port are working. However they only work for a limited time and after a while I get the error message "Incorrect epoch". Once I reload the integration its working again for some limited time.
What version of Home Assistant Core has the issue?
core-2024.12.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Tesla leet
Link to integration documentation on our website
https://www.home-assistant.io/integrations/tesla_fleet
Diagnostics information
config_entry-tesla_fleet-01JEQNWPX079X85JMCP3ZBGQZQ.json
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: