Describe the bug
Adding a manual, adaptive, or hourly chore, causes the chores sensor to become unknown. After removing said chore, or changing it to daily ... yearly the sensor recovers.
With manual chore added:
--> GET /chores
2022-05-28 13:28:36 DEBUG (SyncWorker_7) [pygrocy.grocy_api_client] <-- 200 for /chores
2022-05-28 13:08:23 DEBUG (SyncWorker_7) [pygrocy.grocy_api_client] b'[{"id":"1","chore_id":"1","chore_name":"chore1","last_tracked_time":"2022-05-23 00:00:00","next_estimated_execution_time":"2022-05-28 23:59:59","track_date_only":"1","next_execution_assigned_to_user_id":"1","is_rescheduled":"0","is_reassigned":"0","next_execution_assigned_user":{"id":"1","username":"username","first_name":"","last_name":"","row_created_timestamp":"2022-05-07 17:25:42","display_name":"username","picture_file_name":null}},{"id":"2","chore_id":"2","chore_name":"chore2","last_tracked_time":"2022-05-08 00:00:00","next_estimated_execution_time":"2022-06-03 23:59:59","track_date_only":"1","next_execution_assigned_to_user_id":"1","is_rescheduled":"0","is_reassigned":"0","next_execution_assigned_user":{"id":"1","username":"username","first_name":"","last_name":"","row_created_timestamp":"2022-05-07 17:25:42","display_name":"username","picture_file_name":null}},{"id":"3","chore_id":"3","chore_name":"chore3","last_tracked_time":"2022-05-23 00:00:00","next_estimated_execution_time":"2022-06-04 23:59:59","track_date_only":"1","next_execution_assigned_to_user_id":"1","is_rescheduled":"0","is_reassigned":"0","next_execution_assigned_user":{"id":"1","username":"username","first_name":"","last_name":"","row_created_timestamp":"2022-05-07 17:25:42","display_name":"username","picture_file_name":null}},{"id":"4","chore_id":"4","chore_name":"chore4","last_tracked_time":null,"next_estimated_execution_time":"2022-06-05 23:59:59","track_date_only":"1","next_execution_assigned_to_user_id":"1","is_rescheduled":"0","is_reassigned":"0","next_execution_assigned_user":{"id":"1","username":"username","first_name":"","last_name":"","row_created_timestamp":"2022-05-07 17:25:42","display_name":"username","picture_file_name":null}},{"id":"8","chore_id":"8","chore_name":"chore8","last_tracked_time":"2022-05-16 00:00:00","next_estimated_execution_time":"2022-05-28 23:59:59","track_date_only":"1","next_execution_assigned_to_user_id":"1","is_rescheduled":"0","is_reassigned":"0","next_execution_assigned_user":{"id":"1","username":"username","first_name":"","last_name":"","row_created_timestamp":"2022-05-07 17:25:42","display_name":"username","picture_file_name":null}},{"id":"9","chore_id":"9","chore_name":"chore9","last_tracked_time":null,"next_estimated_execution_time":null,"track_date_only":"1","next_execution_assigned_to_user_id":"2","is_rescheduled":"0","is_reassigned":"0","next_execution_assigned_user":{"id":"2","username":"user","first_name":"","last_name":"","row_created_timestamp":"2022-05-14 15:46:23","display_name":"username","picture_file_name":null}}]'
2022-05-28 13:58:15 ERROR (MainThread) [custom_components.grocy] Update of Chores failed with 1 validation error for CurrentChoreResponse
next_estimated_execution_time
none is not an allowed value (type=type_error.none.not_allowed)
Describe the bug Adding a manual, adaptive, or hourly chore, causes the chores sensor to become unknown. After removing said chore, or changing it to daily ... yearly the sensor recovers.
With manual chore added:
Setting manual chore to yearly:
Expected behavior Manual, adaptive, hourly chores are showing up with to daily ... yearly chores, in the chores sensor.
To Reproduce Steps to reproduce the behavior:
General information to help debugging:
What sensors do you have enabled? Are they working and/or what state are they in? Do you have the corresponding functions enabled in Grocy?
What is your installed versions of Home Assistant, Grocy and this integration? Grocy: 3.3.0 Home Assistant Core: 2022.5.0 Grocy inegration: v4.2.2b
How do you have Grocy installed? Add-on or external? External via docker
Have you added debugging to the log, and what does the log say? Log was enabled:
Full log can be seen above in the bug description.
JSON service data (if related to using a service) N/A
Additional context N/A