We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
A get-history node receiving a msg.payload like:
msg.payload
{ "startDate":"2024-01-04T00:00:00.000Z", "endDate":"2024-01-05T00:00:00.000Z", "entityId":"binary_sensor.central_heating_state" }
...fails with an error "ValidationError: "relativeTime" is not allowed to be empty".
"ValidationError: "relativeTime" is not allowed to be empty"
As above.
Not sure why relativeTime is needed if there is a startDate and endDate. Looks like there were changes here in version v0.60.0.
relativeTime
startDate
endDate
No response
Version: 0.62.2
Home Assistant version: 2023.12.4 Companion version: 3.1.2
Node-RED version: 3.1.3 Docker: yes Add-on: no
Node.js version: ? OS: Raspbian GNU/Linux 10 (buster) Linux 5.10.103-v7+
The text was updated successfully, but these errors were encountered:
05e519f
thanks for the fix!
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Describe the bug
A get-history node receiving a
msg.payload
like:...fails with an error
"ValidationError: "relativeTime" is not allowed to be empty"
.To Reproduce
As above.
Expected behavior
Not sure why
relativeTime
is needed if there is astartDate
andendDate
. Looks like there were changes here in version v0.60.0.Screenshots
No response
Example Flow
No response
Environment Information
Version: 0.62.2
Home Assistant version: 2023.12.4
Companion version: 3.1.2
Node-RED version: 3.1.3
Docker: yes
Add-on: no
Node.js version: ?
OS: Raspbian GNU/Linux 10 (buster) Linux 5.10.103-v7+
Additional context
No response
The text was updated successfully, but these errors were encountered: