DevSecOps
Well-Known Member
- First Name
- Todd
- Joined
- Sep 22, 2021
- Threads
- 69
- Messages
- 4,764
- Reaction score
- 11,624
- Location
- Sacramento, CA
- Vehicles
- '21 Audi SQ5 / '23 Rivian R1T / '23 M3P
- Occupation
- CISO
Yes I'm fairly certain from other posts and my own experience that if you set the schedule on the car you'll get some funky results. When the car is set to always charge you get the best results, however this error message is common when setting it up that way with an EVSE that has it's own schedule.Yeah I went into charge settings on the car and re-entered some info and I think that probably fixed it since my tests afterwards worked. But ended up taking off schedule anyways since I get no benefit at all from it and now I don’t have to worry about that bug again.
Sponsored