teslamateapi: EndDate Can Be NULL, Causing Failed Charges Endpoint
It’s possible to have incomplete charges with missing EndDate. These aren’t always valid objects either, but they shouldn’t prevent the Charges endpoint from providing data. I believe this can happen when TeslaMate is offline when the charging cycle ends. I am not sure if it’s also possible if the vehicle is actively charging.
Error:
sql: Scan error on column index 2, name "end_date": converting NULL to string is unsupported
Pull Request https://github.com/tobiasehlert/teslamateapi/pull/40
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 16 (16 by maintainers)
Commits related to this issue
- Prevent fatal error when detailed charge malformed Following up on https://github.com/tobiasehlert/teslamateapi/issues/43 *Reason* A detailed charge is malformed if the end_date is missing in SQL... — committed to alecdoconnor/teslamateapi by alecdoconnor 6 years ago
- Update Charges API to Allow Valid Empty Response API should fail gracefully if an empty response is sent. Example reason: an API consumer should be able to traverse the pages until empty data is ret... — committed to alecdoconnor/teslamateapi by alecdoconnor 6 years ago
Totally fine with separated issues and pull requests 😃