custom-components / grocy

Custom Grocy integration for Home Assistant
Apache License 2.0
156 stars 47 forks source link

Validation errors during entity update #226

Closed grossqx closed 2 years ago

grossqx commented 2 years ago

Unless all relevant information is provided, I can't help you

Describe the bug Some entities fail to update. State is unknown. The entities that don't work are represented in the log.

sensor.grocy_meal_plan and sensor.grocy_tasks are working alright and reacting to changes on grocy. ex. when meal added, state changes from 0 to 1. So i exclude that something is set up wrong in installation.

Expected behavior all entities are updated according to grocy's state To Reproduce Steps to reproduce the behavior:

  1. Installed everything according to the tutorial.
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

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? all 10 sensors available in the integration

What is your installed versions of Home Assistant, Grocy and this integration? Home Assistant Core 2022.6.4 Home Assistant Supervisor 2022.05.3 Home Assistant OS 8.1 Grocy Version 3.2.0 Grocy custom component v4.2.2

How do you have Grocy installed? Add-on or external? hass add-on

Have you added debugging to the log, and what does the log say?

Update of Missing_products failed with 1 validation error for CurrentVolatilStockResponse due_products -> 0 -> product -> product_group_id value is not a valid integer (type=type_error.integer) Update of Overdue_chores failed with 'hourly' is not a valid PeriodType Update of Chores failed with 'hourly' is not a valid PeriodType Update of Shopping_list failed with 1 validation error for ProductDetailsResponse product -> product_group_id value is not a valid integer (type=type_error.integer) Update of Stock failed with 1 validation error for CurrentStockResponse product -> product_group_id value is not a valid integer (type=type_error.integer)

Hope this is enough information to help me out. Thanks in advance

grossqx commented 2 years ago

Updated to 4.3.4 and the issue is gone. Sorry to bother you. Maybe if the version is not numbered as "b" it also shouldn't be flagged in hacs as beta? because I had to turn on beta toggle to see this version