agners
commented
1 year ago Did you try to rollback to HAOS 9.0 as suggested in https://github.com/home-assistant/core/issues/80146#issuecomment-1276665516?
Closed Chef-de-IT closed 1 year ago
agners
commented
1 year ago Did you try to rollback to HAOS 9.0 as suggested in https://github.com/home-assistant/core/issues/80146#issuecomment-1276665516?
agners
commented
1 year ago Also, can you share the Z-Wave JS Add-on configuration and logs?
Chef-de-IT
commented
1 year ago Did you try to rollback to HAOS 9.0 as suggested in home-assistant/core#80146 (comment)?
Yes, just did it. The issue does go away under HAOS 9.0
Chef-de-IT
commented
1 year ago Also, can you share the Z-Wave JS Add-on configuration and logs?
Some logs as of 9.2 & config are on my original report on the https://github.com/home-assistant/core/issues/80146#issuecomment-1276665516
This is after the downgrade to 9.0; some strings replaced with [...]:
Logger: homeassistant.config_entries Source: config_entries.py:1049 First occurred: 3:15:22 PM (1 occurrences) Last logged: 3:15:22 PM Config entry 'Z-Wave JS' for zwave_js integration not ready yet: Failed to connect: Cannot connect to host core-zwave-js:3000 ssl:default [Connect call failed ('172.30.33.0', 3000)]; Retrying in background
========================
StonyManager
commented
1 year ago Z-Wave JS flaked out on me about a two months ago after an upgrade. I didn't see any related changes in the release notes, but after tinkering with the version and backups, I found a combo that worked again. I'm not upgrading again until I see this issue resolved. Glad to test and help if that is useful.
agners
commented
1 year ago @Chef-de-IT it seems that those logs are the host logs & logs of the Core about the Z-Wave JS integration. The Add-on logs are missing, and the host logs in the non-working (HAOS 9.2) are not present in the link.
Ideally, I need the following information so I can diff the before/after:
@StonyManager what hardware are you using?
The problem must be quite hardware specific, as we have more than 40k users on OS 9.2, 15.4% use Z-Wave, that means approximately 6000 people are running this combination. I am not saying that your problem does not exist, I am just saying its not a generic problem, it must be some combination of circumstances.
There are also not that much changes between 9.0 and 9.2. The most likely cause is the updated LTS Linux kernel. I usually pick the latest kernel from kernel.org to get the latest bugfixes. But sometimes these "bugfixes" break certain setups, unfortunately.
@Chef-de-IT @StonyManager maybe before testing too much, can you try and see if the latest HAOS 9.3 release fixed this problem?
Chef-de-IT
commented
1 year ago @agners Stefan,
There are also not that much changes between 9.0 and 9.2.
Your commit comment on 9.2 mentions "improve virtual hw support" - I'm not sure if that's even relevant but it sounds so to someone with my level of HAOS code familiarity which is none
@Chef-de-IT @StonyManager maybe before testing too much, can you try and see if the latest HAOS 9.3 release fixed this problem?
I don't have a dev HA instance where I can test 9.3 - that'll be changing soon, as I've rolled out several pilot HA installations to clients (that have to operate stably / I can't risk just "trying something") and HA overall is a winner when stable (THANK YOU!)
The pilot instances all had the same issue (expected as they're all the same HW as well - over-spec'd Dell OptiPlex HW and 700series Zooz stick on up-to-date FW).
The problem must be quite hardware specific, as we have more than 40k users on OS 9.2, 15.4% use Z-Wave, that means approximately 6000 people are running this combination.
It's possible, although one must take into account what % of those 6K people have consistently opened github tix in cases of past issues that affected all? It stands to reason, NOT 100% of them, and, looking at git history, I suspect not even 1% of end-users open tix every time they have an issue. Which isn't a bad thing :-) so long as we don't conflate it to the issue affecting fewer people than it in fact might.
Again, thank you for all your work; unfortunately I had to roll back all the 9.2 installations of mine in double-quick time before collecting logs, and I promise to have a dev/lab instance up and running shortly.
agners
commented
1 year ago Your commit comment on 9.2 mentions "improve virtual hw support" - I'm not sure if that's even relevant but it sounds so to someone with my level of HAOS code familiarity which is none
This change (https://github.com/home-assistant/operating-system/pull/2138) only affected the image optimized for virtualization (ova). The image you are using generic-x86-64 did not get that change.
Again, thank you for all your work; unfortunately I had to roll back all the 9.2 installations of mine in double-quick time before collecting logs, and I promise to have a dev/lab instance up and running shortly.
:hugs: :+1:
StonyManager
commented
1 year ago My Z-Wave hardware is Z-Wave HUSBZB-1, hosting HA on an ODroid. I'm going to upgrade to latest 9.3 and see what happens.
StonyManager
commented
1 year ago I upgraded to latest Z-Wave JS UI, HA 2022.11.1, Supervisor 2022.10.2, OS 9.3, Frontend 20221102.1 Everything appears to be working correctly although most of my automations don't run until sunset (in a few hours). Thanks.
github-actions[bot]
commented
1 year ago :wave: @Chef-de-IT, thanks for reporting an issue!
This issue is assumed to be fixed in the latest stable release. Please reopen in case you can still reproduce the issue with the latest stable release. You can find the latest stable release at https://github.com/home-assistant/operating-system/releases/latest
Describe the issue you are experiencing
After upgrade to OS 9.2, Z-Wave JS no longer finds the USB stick.
Related issue with specifics on the Z-Wave JS github: https://github.com/home-assistant/core/issues/80146
What operating system image do you use?
generic-x86-64 (Generic UEFI capable x86-64 systems)
What version of Home Assistant Operating System is installed?
9.2
Did you upgrade the Operating System.
Yes
Steps to reproduce the issue
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System information
No response
Additional information
No response