-
Notifications
You must be signed in to change notification settings - Fork 4
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
ValidationError('Not a valid datetime.')] #38
Comments
Researching this further, I find that my HomeAssistant now has (https://github.com/agronholm/typeguard/blob/master/docs/versionhistory.rst)
Smells like a "smoking gun" there but I'm unsure which project ultimately uses |
As noted in https://github.com/agronholm/typeguard/blob/master/docs/versionhistory.rst and toreamun#38 installing `victorsmartkill` module encounters an error. Simply blocking the behaviour of "blindly install the latest" of `typeguard` causes @toreamun's module to install and become active, immediately appearing on the "Integrations" page in HomeAssistant.
I think it's this: |
Upstream seems to be stuffing a human-readable comment where a date is expected (and, you know, that date has a format)
(confirmed: no pre-existing issue)
On configuration of a new install of 2023.1.7 HA with Integration 2023.1.0, victor-smart-kill==1.1.1
I've confirmed credentials, they do work.
Version of Home Assistant
2023.1.7
Version of the custom_component
2023.1.0 with "victor-smart-kill==1.1.1" in requirements
Describe the bug
On configuration, and the authentication is accepted, the configuration integration periodically shows "Retrying setup: None" and seems to keep reconnecting. The remote service is online, as a manual connection does connect, and the App connects.
It seems to be that the fetched data is doing that old "we'll just record a human-readable comment there, because schema doesn't matter?" Yeah, I hate sloppy schema, totally blame the upstream:
I mean, hey, "No maintenance records exist", you mean that's not ISO8601? :-/ grrr
I do see that your schema is a union, so this is probably beyond what I can figure out for why the validation is enforcing a data time schema -- it's like it's choosing the date time rather than string, then detecting that it's not a string.
Debug log
The text was updated successfully, but these errors were encountered: