Everything is down, and icant figure out why, zwavejs has started, but no devices available
Zigbe2mqtt finds all devices, but when i try to start the addon it says
Zigbee2MQTT:info 2022-11-22 20:06:13: Connecting to MQTT server at mqtt://core-mosquitto:1883
Zigbee2MQTT:error 2022-11-22 20:06:17: MQTT error: getaddrinfo ENOTFOUND core-mosquitto
Zigbee2MQTT:error 2022-11-22 20:06:17: MQTT failed to connect, exiting…
Im at a loss here, but nothing is working 
from zwavejs
2022-11-22T19:06:43.372Z CNTRLR « [Node 049] refreshing neighbor list failed...
2022-11-22T19:06:43.372Z CNTRLR » [Node 049] refreshing neighbor list (attempt 2)...
2022-11-22T19:06:43.384Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-11-22T19:06:47.919Z CNTRLR « [Node 045] TODO: no handler for application command
2022-11-22T19:06:49.152Z CNTRLR « [Node 079] TODO: no handler for application command
2022-11-22T19:06:57.688Z DRIVER dropping CC with invalid values (Reason: Unknown sensor type 0x81 or corrupted
data)
2022-11-22T19:07:04.135Z CNTRLR « [Node 049] refreshing neighbor list failed...
2022-11-22T19:07:04.136Z CNTRLR » [Node 049] refreshing neighbor list (attempt 3)...
2022-11-22T19:07:04.147Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-11-22T19:07:05.377Z DRIVER Dropping message because it could not be deserialized: MultilevelSensorCCGet:
deserialization not implemented (ZW0320)
2022-11-22T19:07:24.897Z CNTRLR « [Node 049] refreshing neighbor list failed...
2022-11-22T19:07:24.898Z CNTRLR » [Node 049] refreshing neighbor list (attempt 4)...
2022-11-22T19:07:45.558Z CNTRLR « [Node 049] refreshing neighbor list failed...
2022-11-22T19:07:45.559Z CNTRLR » [Node 049] refreshing neighbor list (attempt 5)...
2022-11-22T19:08:06.211Z CNTRLR « [Node 049] refreshing neighbor list failed...
2022-11-22T19:08:06.211Z CNTRLR [Node 049] failed to update the neighbor list after 5 attempts, healing failed
2022-11-22T19:08:06.213Z CNTRLR » [Node 049] requesting node neighbors...
2022-11-22T19:08:06.226Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-11-22T19:08:06.339Z CNTRLR « [Node 049] node neighbors received: 1, 38, 39, 40, 43, 45, 47, 50, 51, 52, 57,
61, 71, 72, 73, 74, 75, 76, 77, 80, 81
2022-11-22T19:08:06.339Z CNTRLR [Node 050] Healing node...
2022-11-22T19:08:06.339Z CNTRLR » [Node 050] refreshing neighbor list (attempt 1)...
2022-11-22T19:08:06.349Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-11-22T19:08:27.092Z CNTRLR « [Node 050] refreshing neighbor list failed...
2022-11-22T19:08:27.093Z CNTRLR » [Node 050] refreshing neighbor list (attempt 2)...
2022-11-22T19:08:27.106Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-11-22T19:08:47.849Z CNTRLR « [Node 050] refreshing neighbor list failed...
2022-11-22T19:08:47.849Z CNTRLR » [Node 050] refreshing neighbor list (attempt 3)...
2022-11-22T19:08:47.862Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-11-22T19:08:47.967Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2022-11-22T19:09:09.720Z CNTRLR « [Node 050] refreshing neighbor list failed...
2022-11-22T19:09:09.720Z CNTRLR » [Node 050] refreshing neighbor list (attempt 4)...
2022-11-22T19:09:09.733Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-11-22T19:09:30.478Z CNTRLR « [Node 050] refreshing neighbor list failed...
2022-11-22T19:09:30.479Z CNTRLR » [Node 050] refreshing neighbor list (attempt 5)...
2022-11-22T19:09:50.294Z CNTRLR « [Node 071] TODO: no handler for application command
2022-11-22T19:09:51.016Z CNTRLR « [Node 071] TODO: no handler for application command
2022-11-22T19:09:51.136Z CNTRLR « [Node 050] refreshing neighbor list failed...
2022-11-22T19:09:51.136Z CNTRLR [Node 050] failed to update the neighbor list after 5 attempts, healing failed
2022-11-22T19:09:51.137Z CNTRLR » [Node 050] requesting node neighbors...
2022-11-22T19:09:51.158Z CNTRLR « [Node 050] node neighbors received: 1, 38, 39, 40, 43, 45, 46, 47, 49, 51, 52,
57, 61, 62, 66, 67, 71, 72, 73, 74, 75, 76, 77, 79, 81
2022-11-22T19:09:51.158Z CNTRLR [Node 052] Healing node...
2022-11-22T19:09:51.158Z CNTRLR » [Node 052] refreshing neighbor list (attempt 1)...
2022-11-22T19:09:51.165Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-11-22T19:09:51.166Z CNTRLR « [Node 071] TODO: no handler for application command
2022-11-22T19:10:11.911Z CNTRLR « [Node 052] refreshing neighbor list failed...
2022-11-22T19:10:11.912Z CNTRLR » [Node 052] refreshing neighbor list (attempt 2)...
2022-11-22T19:10:11.932Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-11-22T19:10:32.681Z CNTRLR « [Node 052] refreshing neighbor list failed...
2022-11-22T19:10:32.681Z CNTRLR » [Node 052] refreshing neighbor list (attempt 3)...
2022-11-22T19:10:53.336Z CNTRLR « [Node 052] refreshing neighbor list failed...
2022-11-22T19:10:53.336Z CNTRLR » [Node 052] refreshing neighbor list (attempt 4)...
2022-11-22T19:11:08.132Z DRIVER Dropping message because it could not be deserialized: The command class unkno
wn (0x12) is not implemented (ZW0303)
2022-11-22T19:11:13.993Z CNTRLR « [Node 052] refreshing neighbor list failed...
2022-11-22T19:11:13.994Z CNTRLR » [Node 052] refreshing neighbor list (attempt 5)...
2022-11-22T19:11:14.005Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
OK your MQTT issue appears to be name resolution (DNS or something)
THis screenshot lists an error woth MQTT - due to an exception - name does not resolve.
ALL things are name resolution issues until proven otherwise. Figure out why MQTT can’t resolve its name. Maybe whatever you’re using for DNS isn’t available due to the outage?
The other one looks like your ZWave stick may be locked up. HA can communicate with it but it’s not communicating with everything else. Ive seen this happen with mine occassioanlly - I’d pull the zstick for about 60 seconds to let the stick power down and reset (there’s onboard capacitors and things you need to let fully discharge, so if youre not sure the usb bus completely powers down when you kill HA, then pulling the stick is the answer. I have to do this because mine is on a powered usb hub and killing HA does not kill my Zwave stick.) then put it back in and restart HA (Or ZWaveJS if you’re using it as an Add-on) to see if that helps your ZWave side.
Thanks for your tips, i suddenly lost connection to HA while looking at logs, tried restarting and powering the device off and letting it sit for a while, but it seems i cant access it anymore trough a web browser. need to connect to a monitor and see whats happening.
Ew. Sorry to hear. Hopefully it’s just a few strategically applied reboots to get you rolling again.
Hooked it up to a monitor looks fine during boot
Still can’t access it trough dns or ip oh well. Guess I need to reflash and start over
Ended up needing to reflash, nothing worked, ssh, sftp, no external terminal, just local terminal. seems something was royal messed up 
Interesting…
