Skip to content
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

get-history startDate/endDate/relativeTime #1239

Closed
dgthomson opened this issue Jan 4, 2024 · 1 comment · Fixed by #1207
Closed

get-history startDate/endDate/relativeTime #1239

dgthomson opened this issue Jan 4, 2024 · 1 comment · Fixed by #1207
Labels
Type: Bug Something isn't working

Comments

@dgthomson
Copy link

Describe the bug

A get-history node receiving a msg.payload like:

{
   "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".

To Reproduce

As above.

Expected behavior

Not sure why relativeTime is needed if there is a startDate and endDate. 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

@zachowj zachowj added the Type: Bug Something isn't working label Jan 4, 2024
@zachowj zachowj closed this as completed in 05e519f Jan 9, 2024
@dgthomson
Copy link
Author

thanks for the fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants