You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Home Assistant custom components volkswagencarnet and volkswagen_we_connect_id that uses weconnect are firing errors.
To Reproduce
Steps to reproduce the behavior:
Let the custom component run... Frequent error log in Home Assistant
Expected behavior
Handle the error
Logs
2024-05-09 13:24:46.632 WARNING (SyncWorker_35) [weconnect] /vehicles/WVWZZZCDZNW306902/domains/charging/chargingStatus/chargeType: An unsupported chargeType: unsupported was provided, known values are [invalid, off, ac, dc, unknown charge type] please report this as a bug
2024-05-09 13:29:55.971 WARNING (SyncWorker_9) [weconnect] /vehicles/WVWZZZCDZNW306902/domains/charging/chargingStatus/chargeType: An unsupported chargeType: unsupported was provided, known values are [invalid, off, ac, dc, unknown charge type] please report this as a bug
OS: [e.g. Windows, Linux, MacOS, ...] Linux
Version used [e.g. 0.6.2]: 0.58.0
The text was updated successfully, but these errors were encountered:
Describe the bug
Home Assistant custom components volkswagencarnet and volkswagen_we_connect_id that uses weconnect are firing errors.
To Reproduce
Steps to reproduce the behavior:
Let the custom component run... Frequent error log in Home Assistant
Expected behavior
Handle the error
Logs
2024-05-09 13:24:46.632 WARNING (SyncWorker_35) [weconnect] /vehicles/WVWZZZCDZNW306902/domains/charging/chargingStatus/chargeType: An unsupported chargeType: unsupported was provided, known values are [invalid, off, ac, dc, unknown charge type] please report this as a bug
2024-05-09 13:29:55.971 WARNING (SyncWorker_9) [weconnect] /vehicles/WVWZZZCDZNW306902/domains/charging/chargingStatus/chargeType: An unsupported chargeType: unsupported was provided, known values are [invalid, off, ac, dc, unknown charge type] please report this as a bug
The text was updated successfully, but these errors were encountered: