On HA version 2023.06, the grocy custom component fails to load

[Greenphlem]

Describe the bug On HA version 2023.06, the grocy custom component fails to load, receiving this:

Logger: homeassistant.setup
Source: setup.py:207
First occurred: 7:59:45 PM (1 occurrences)
Last logged: 7:59:45 PM

Setup failed for custom integration grocy: Requirements for grocy not found: ['pygrocy==1.4.1'].

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? HA: 2023.06 Custom Component: 4.8.0

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

[Sarnog]

Same error:

Logger: homeassistant.util.package
Source: util/package.py:107
First occurred: 08:29:37 (3 occurrences)
Last logged: 08:29:55

Unable to install package pygrocy==1.4.1: ERROR: Cannot install pygrocy==1.4.1 because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

[MrAlucardDante]

While waiting for an update to the custom component, I've found a temporary fix.

Looking at the manifest.json on the master branch, it looks like pygrocy was updated to 1.5.0.

Manually editing manifest.json in /config/custom_components/grocy fixes the issue.

[michaeltryl]

While waiting for an update to the custom component, I've found a temporary fix.

Looking at the manifest.json on the master branch, it looks like pygrocy was updated to 1.5.0.

Manually editing manifest.json in /config/custom_components/grocy fixes the issue.

thanks it works perfect. after reboot i just have to reload the integration, to get it to work again

[MrMoblys]

This fix works great ! Thanks :-)

[karwosts]

The other thing you can do if you don't want to edit manually is just enable "beta" versions in HACS and update to v4.9 or later.

https://github.com/custom-components/grocy/releases/tag/v4.9.0

[VNRARA]

Gotta commend the dev for already having a solution ready :)

[Medicalmusings]

The other thing you can do if you don't want to edit manually is just enable "beta" versions in HACS and update to v4.9 or later.

https://github.com/custom-components/grocy/releases/tag/v4.9.0

Did that (on version 4.10.0) but still didn't work. Resolved by deleting and reinstalling the whole installation. If it makes any difference Im running Grocy itself inside docker on another host elsewhere on the LAN. Looks like just updatingthe version didn't flush everything out of the configuration. A full delete and reload fixed it. Thanks.

[mattte]

The other thing you can do if you don't want to edit manually is just enable "beta" versions in HACS and update to v4.9 or later.

https://github.com/custom-components/grocy/releases/tag/v4.9.0

For anyone that is a dummy like me -- you can browse to the HACS integration page (ie /hacs/repository/182915754) and then in the top right triple dot icon, there's an option redownload and then from there you can select the beta version

[MrAlucardDante]

The other thing you can do if you don't want to edit manually is just enable "beta" versions in HACS and update to v4.9 or later. https://github.com/custom-components/grocy/releases/tag/v4.9.0

For anyone that is a dummy like me -- you can browse to the HACS integration page (ie /hacs/repository/182915754) and then in the top right triple dot icon, there's an option redownload and then from there you can select the beta version

That works, but don’t forget to change it back when/if the fix is released. Otherwise you would always be on the beta channel.

And keep in mind that the beta channel might be unstable, whereas changing the dependency allows you to stay on the stable version (but it’s a tiny bit technical I agree)