My Zwave devices have been working for long time so don’t deal with it much anymore since got it all working. Then when tried this year noticed Supervisor just get a blank page with blue spinner and it never starts. Everything else will come up on webpage.
Wanted to finally tackle this conversion to JS, have copied the stuff I need like device_path and network_key and template script from the guide for my entities. But without Supervisor working not sure can go any further.
I have seen where someone suggested issuing command: ha core rebuild
to get the supervisor working again.
I do have a working image from years ago could put in the raspberry pi and may that is all I need. I think these updates over the last few years might corrupt it though?
Not sure which ZWave I have or where to get that info. If go to Configuration/Integrations I see Z-wave box without the signal icon and doesn’t say depreciated either. I assume it is 1.4.
So could go to Integrations and delete Z-wave like the guide says but without Supervisor seems like would be a nogo after that.
Any ideas instead of having to completely reinstall?
Oh. Hmm. I mean, I’m very update lazy myself, but that’s quite a jump you’d have to do Maybe reinstalling from scratch would be best in this situation. Make a backup first, so you won’t lose your config.
How many zwave devices do you have ? Technically you don’t need to do any active migration to use ZwaveJS. The network is stored on the stick, so you won’t lose that. You could just have ZwaveJS reinterview your nodes and let it go from there. The only downside is that your entity names will change, so you would have to fix that. If you don’t have too many devices, that may not be such a big deal. If some of your devices use S0 security, it would also be advisable to unpair/repair them with S2 instead (if they’re S2 capable).
I have 19 actual devices. Not sure where to find if the GD00Z-4 GoControl Garage Door Opener is S0 or S2, probably S0.
Well if I have to reinstall from scratch, how different are the names? Hoping that renaming them is easy, cause don’t want it to boot up and do some auto renaming where can’t tell what it is calling them or where had trouble before and had to unpair/repair everyone.
Oh well, start getting all the info together and take the plunge I guess. Guessing will be offline for a bit.
Was hoping could just get Supervisor working again and go from there, but not looking like it.
It wasn’t exactly being lazy, just everytime looked the guides said, still in beta stage for conversion guide, more to come. Then by the time got around to looking again time had passed. Until recently when the automation scripts stopped I noticed again that better do something.
That’s not too bad. I would go the clean reinstall route if I were you.
I think you can assume that the names will be totally different from what they were before. You will have to manually rename them. Renaming them is easy. Annoying for sure, but with only 19 devices it should not be that much work. You won’t have to unpair/repair anything, unless you want to switch from S0 to S2. Make sure to keep your previous encryption keys. You will need them if you opt to not repair previously encrypted nodes.
To be honest, the migration wizard kinda never made it out of beta. I never used it, but seeing the feedback on the forums around that time, it looked like the wizard never really worked correctly. The general consensus was, do it manually if you can.
Thanks for the input. Looks like that is my route.
If the names are totally different how do you no what is what? Maybe the Node numbers are the same hopefully.
On the migration guides: Ya, was hoping they would have been completed and functional, and was praying on that. Went thru a unpair/repair before and it wasn’t fun. Glad I won’t have to do that at least.
I’ll tackle this and hope for the best. Thanks guys!
Well mostly back up again. Still have a lot to do.
Just incase someone else is in the same boat.
Had to use GParted for the SD card cause was in partitions, so deleted the partitions and reformated.
The Etcher wouldn’t work from the URL got errors right away. Downloaded the URL to the comptuer and worked.
Watched all the devices being discovered from previously known nodes so could give them an area and know what they might be. Since didn’t know what kinda mess was walking into.
Luckily found a script for the developer template area later that listed them all so could put them in a text file.
Had one WADWAZ-1 (Nortek Security & Control LLC / Door/Windows Sensor) that wasn’t working all the way. It was sorta there, but didn’t get a name, but had all the info. Still it was sorta talking, but with it’s mouth taped. And it wouldn’t update if window opened. Tried Healing the network but that didn’t work. So Excluded it and then added Device to Include again. That worked! Then added the new node to my list.
Not sure about my GD00Z-4 GoControl Garage Door Opener. Will try to put back what had before and see if can get working. I got it working, but tilt sensor isn’t. Worked until installed ZwaveJS
Maybe reinstalling from scratch would be best in this situation. Make a backup first, so you won’t lose your config.