A couple of things in play here. I recently installed a new router. New internal IP addresses. 192.168.68.1 instead of 192.168.1.1. I have HA installed on a Dell mini with Proxmox. HA has been running fine. I was trying to get a matter device to work. In doing so, I turned off IPV4 (really dumb). Since then, I am unable to access anything. HA does appear to be running on proxmox. However, proxmox is giving me an old IP address to access it. A 192.168.1.XX number. I have no idea how to proceed. My new router does not show the Dell computer as being connected. Please advise.
#Messing around with Matter. Turned off IPV4. Now cannot access HA.
golden reef
fallow sun
not aware of standard route after ipv6, reboot?
can you ping ip?
if you cant ping then googly thing "how to re-enable ipv4 home assistant using cli"
sounds like you had set static ip for haos
remove static ip from router (if set)
also, router ipv6 configured right?
can ping -6 hostname?
golden reef
thanks for the replies. let me try these thing
things
I do have a keyboard and monitor connected
I am not seeing the HA prompt
fallow sun
thats a good start
what do you see?
are you subscribed to nabu casa cloud?
and have backup?
golden reef
yes and yes
pve login
at pve login it give me a wrong ip address to access the pve gui
fallow sun
so if nothing else goes, you could install new vm to proxmox using install script HAOS in PM...and put backup back
what happens if enering that ip :8123
golden reef
site cannot be reached
i was going to go down the backp route but I cant even access PM
fallow sun
underlying network issues though? DNS/DHCP/NTP
golden reef
yes. i guess.
fallow sun
reboot modem, wait for online, then router>online and reboot clients
fallow sun
ok
golden reef
back
no real progress rebooting
what a mess
maybe I somehow start from scratch. I have a backup from yesterday for HA
having broken proxmox is disturbing
any thoughts on starting completely over?
fallow sun
install proxmox, use install script HAOS, put back backup
first check internal network though..
golden reef
ok
will report back. thanks
hmm. I dont remember this proxmox hostname fqdn
OK. I'm back into proxmox. whew. progress
back into HA
fallow sun
ok sounds good so far
golden reef
backup is loading. says it can take 45 min
I'm in HA now but it's a mess. I'm assuming bc stuff is laoding
loading
Not sure how I know if it's done
golden reef
everything is back up except for z-wave js
which is a big part of my setup
wow. z-wave looks like a huge rabbit hole. fml
plush mirage
How did you disable it exactly?
golden reef
disable what?
plush mirage
IPv4.
golden reef
In HA. Settings - System - Network - IPv4
plush mirage
Please share ha network info.
To re-enable you can use
ha network update INTERFACE_NAME_FROM_HA_NETWORK_INFO --ipv4-method auto
thanks
i am stuck trying to get z-wave js going
have 16 devices which is 90% of what I use HA for
not working
plush mirage
Unfortunately i don't use Zwave. That's not a lot of information though.
golden reef
no idea why a simple restore from backup would break everything
plush mirage
Did you reboot (not restart) after restoring?
plush mirage
What does not working mean here?
golden reef
'failed setup will retry"
all 16 enitites failed status
it's time to either take a break or put the whole damn thing in the dumpster
Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK
from the controller (ZW0200)
at Driver.sendMessage (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts
:7057:23)
at ZWaveController2.queryCapabilities (/opt/node_modules/zwave-js/src/lib/
controller/Controller.ts:1064:37)
at Driver.initializeControllerAndNodes (/opt/node_modules/zwave-js/src/lib
/driver/Driver.ts:1970:46)
at Immediate.<anonymous> (/opt/node_modules/zwave-js/src/lib/driver/Driver
.ts:1696:16)
2025-08-24 15:21:36.078 INFO Z-WAVE: Restarting client in 8 seconds, retry 4
2025-08-24 15:21:36.079 DRIVER destroying driver instance...
2025-08-24 15:21:36.080 DRIVER driver instance destroyed