-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Config checker fails 0.107.5->0.107.6 - pyozw 0.1.10 not found #1194
Comments
Hey there @home-assistant/z-wave, mind taking a look at this issue as its been labeled with a integration ( |
Are you sure the environment in the OP shouldn't be (considering the subject): Environment
I'm on 0.107.5 and running the config checker against latest (0.107.6) and getting the same issue as you posted above. But when I run config checker against 0.107.5 (the same version as HA is currently running on my pi3) there are no issues (as expected). Could it be an Add-on issue (Check Home Assistant configuration)? I don't dare to update to try it out. |
same problem |
Same problem when, on 0.107.5, running the config checker for upgrade to 0.107.7 |
@pvizeli Do you have any thoughts on this issue? |
Yes, is a add-on issue, let me fix that |
Excellent, glad you found it have the same problem. But Ive already installed 107.6 :-( |
Not sure if this helps, I forgot to do an apt-get update before I upgraded to 107.6, so after doing that all my z-wave devices magically came back. I'm using a pi 4 with buster and HA is installed by hand. |
@mickt34 That is good news. I did that before running the config checker again. It doesn't fix the issue with the config checker for me (pi 3, buster and HA manually installed). And I'd like to wait to update before that is fixed. |
This is from my error log:
|
In 107.7 still the same error:
|
@sutyagin The way I understand it, major parts of the Home Assistant development is done by volunteers and you get it for free. A bit of patience is therefore the least we (who don't contribute much) can show. |
@pvizeli - Could this be more than just an addon issue? I'm having the same issue as well except I'm still running Home Assistant Core from virtualenv. I first noticed this starting with In my case I was able to fix this by manually installing Stop Home Assistant ## Exec these commands as the homeassistant user
source /srv/homeassistant/bin/activate
pip3 install --upgrade homeassistant-pyozw==0.1.10
deactivate Restart Home Assistant |
Thanks for fixing! I updated HA to 0.107.7 without problems. |
The problem
It seems that pyozw 0.1.10 is not available?
Environment
Problem-relevant
configuration.yaml
Traceback/Error logs
Additional information
The text was updated successfully, but these errors were encountered: