Help with Migration to Home Assistant OS

Background: Been using some version of HA for many years, first as a VENV on PI3, then as a docker on PI4 w SSD Boot. Now convinced Home Assistant OS is the way to go, to just use the plugins, etc. Spent all day wrestling with getting an SSD to boot with Home Assistant OS. And finally SUCCESS. Copied my backup config today from my old docker system. Much of it came up OK.

Where am I now: I was running the deprecated openzwave in docker. So I installed the deprecated openzwave in HA OS. I figured this was the easiest path to get things working, then do the migration to JS from there.

What I am having trouble with: I am running a Aeotec ZW090 Z-Stick Gen5 US. The STATES page shows this device as UNAVAILABLE. Device appears to be at ttyACM0 where it was before.

I looked at root/config/.storage/.core.config_entities and it shows the expected path (ignore spacing in this sample, it is correct in the file):

{
“entry_id”: “20d05ffe850744d3bbeec7b0ea8f6a0f”,
“version”: 1,
“domain”: “zwave”,
“title”: “Z-Wave (import from configuration.yaml)”,
“data”: {
“network_key”: null,
“usb_path”: “/dev/ttyACM0”
},
“options”: {},
“pref_disable_new_entities”: false,
“pref_disable_polling”: false,
“source”: “import”,
“unique_id”: null,
“disabled_by”: null
},

Have tried rebooting a lot, even switched to ttyAMA0 out of desperation, with no luck.
Hit a wall and uncertain what to try next. Possibly I’m stumped due to differences between the docker install I’ve lived with for so long and the differences with HA OS.

Any suggestions on what to try next?

UPDATE UPDATE UPDATE

I’ve fooled around installing, uninstalling, reboots, whatever…
At this point I do NOT have the deprecated zwave integration installed.
I commented out any mention of zwave in my configuration.yaml file.
On reboot I get: “Setup failed for zwave: Integration not found.”
What’s making the system think zwave is there at this point?
Perhaps whatever this is, is what is driving the error and halting progress?

Commenting out zwave in your configuration.yaml file doesn’t do anything anymore I don’t think. Notice how that config entry says “import from configuration.yaml”. I believe that means what you had in configuration.yaml has been imported into a config entry and you can simply remove the YAML at this point, it doesn’t do anything anymore.

If you go to the integrations dashboard do you see zwave listed there? If so can you just delete it?

If that doesn’t work then I think you’ll have to edit .storage/.core.config_entities unfortunately. Shut down HA, remove that section of JSON and then turn it back on. Might also be wise to do a cat .storage/.core.config_entities | jq from the commandline after your change just to make sure you still have valid JSON after your change otherwise HA won’t start at all.

Thanks. I just finished taking Zwave out of core.config_entities when your message came in. I rebooted and the error “Setup failed for zwave: Integration not found was gone”. Rebooted again for good measure, same result.

Then I tried to reinstall deprecated zwave. Configured. Rebooted. Now the add-on has a green dot in upper right corner (which I gather means it is working). Went into the log for the add-on, and I see activity (sample below):

[20220407 13:30:01.380 EDT] [ozw.logging] [debug]: popping Log Mesages
[20220407 13:30:01.383 EDT] [ozw.library] [info]: Info - Node: 19 ApplicationCommandHandler - Unhandled Command Class 0x31
[20220407 13:30:01.383 EDT] [ozw.logging] [debug]: popping Log Mesages
[20220407 13:30:01.538 EDT] [ozw.library] [debug]: Detail - Node: 24 Received: 0x01, 0x07, 0x00, 0x13, 0xa9, 0x00, 0x00, 0x12, 0x50
[20220407 13:30:01.538 EDT] [ozw.logging] [debug]: popping Log Mesages
[20220407 13:30:01.541 EDT] [ozw.library] [debug]: Detail - Node: 24 ZW_SEND_DATA Request with callback ID 0xa9 received (expected 0xa9)
[20220407 13:30:01.542 EDT] [ozw.logging] [debug]: popping Log Mesages
[20220407 13:30:01.545 EDT] [ozw.library] [info]: Info - Node: 24 Request RTT 184 Average Request RTT 163
[20220407 13:30:01.546 EDT] [ozw.logging] [debug]: popping Log Mesages
[20220407 13:30:01.549 EDT] [ozw.library] [debug]: Detail - Node: 24 Expected callbackId was received
[20220407 13:30:01.549 EDT] [ozw.logging] [debug]: popping Log Mesages

So it looks to be communicating with the devices I have around the house. Then I decide to go look at the main HA log. Guess what it says? “Setup failed for zwave: Integration not found.”

That really confuses me! Add-On Appears to be doing “something”, but the main log says it can’t be found.

I’ll bag this and just try for straight to JS and deal with whatever problems I find there. I guess going to deprecated Zwave first was a bad idea.

Ha! Even using Zwave-JS brings back:
Logger: homeassistant.config_entries
Source: config_entries.py:736
First occurred: 2:13:32 PM (1 occurrences)
Last logged: 2:13:32 PM
Cannot find integration ozw

Now I’m starting to think I need to go back to scratch install and assume restoring is impossible due to zWave. ZWave just isn’t happy.

So I’m not sure what’s up with that last error, zwave js and ozw don’t have anything to do with each other.

But the main problem you’re facing is that 2022.4 removed zwave. It was previously deprecated, this release was end of life. That integraiton is gone from HA now hence the “integration not found” message.

The addon is a totally separate thing. That can obviously still be installed if you track it down but HA has no idea what to do with it anymore since the integration it’s expecting to exist doesn’t.

This is actually a bit of a pickle. There was a migration option but I’m not sure what to do with migrating both at once. Might need someone with more in-depth knowledge of zwave to help here, sorry.

Thanks, probably will give up and rebuild from scratch. Been using HA since 2017, so maybe cleaning out 5 years of junk will be a good thing. I’ll consider things for a while.

I had same problem but restoring the backup solved the problem (but I need to migrate now)

Good luck with your migration. I got everything up and running now.

is it a pain to migrate?

Well, mine was a bit of a pain, but more my fault than anything. I decided to change install types at same time and messed some stuff up, leading to all of my zwave entities being renamed. So I had to fix that all up manually, which took a while. However, I used this to clean up a whole lot of stuff I accumulated since 2017 in HA. Again, my fault.

what do you mean by the following ?

I was running HA Core under docker. Then I changed to running Home Assistant OS. I did this change of HA install types at the same time as my planned deprecated OpenZwave to Zwave-JS upgrade.