Resolved
Jul 31, 2026 at 5:21am UTC
Tesla confirmed that this issue was caused by a change they made, which specifically triggered on unsigned configurations with no expiration. The original root cause should now be fixed, however Teslemetry is going to stay on the signed configuration moving forward.