Z-Wave JS reported as failed to start consistently

[benze (Eric B)]

Every time I log into HA, I see an error message in the Settings tab that the Z-Wave JS failed to start at boot time.

What I do not understand is that I have cleared the error several times already, and my ZWave integration has already started. So I am not sure why I keep seeing the error message.

If I click on Start, it tells me the issue has been resolved, yet the following day I see the same message. System Core Logs are empty as well.

I am running Z-Wave JS UI 3.23.0 and have just updated to home assistant OS HA Core 2025.3.2 (was previously on 2025.3.1).

Any suggestions or recommendations?

Thanks,

Eric

[freshcoast]

@benze

I am running Z-Wave JS UI 3.23.0

You can’t run both add-ons at the same time. The warning is about the core Z-Wave JS add-on. Running both at the same time will result in one of them failing. From the info provided we don’t know which one you are actually using with HA. Check the Server URL in the integration settings panel. If it’s pointing to core, following the migration guide. If it’s pointing to the add-on, delete the core add-on.

Switching Z-Wave JS Addons with Minimal Downtime! Z-Wave JS (Official) to Z-Wave JS UI (Community)

Introduction This guide describes how to switch from the Z-Wave JS official add-on to the Z-Wave JS UI HA Community add-on, without losing any downtime caused by the re-interviewing of nodes. In this guide, Z-Wave JS UI will henceforth be abbreviated as ZUI. Who is this guide for? This guide is for HAOS add-on users who have already installed the official Z-Wave JS add-on and the companion Z-Wave integration, and desire extra functionality that isn’t provided by HA, such as: Adding and remov…

[benze (Eric B)]

@freshcoast

You can’t run both add-ons at the same time. The warning is about the core Z-Wave JS add-on. Running both at the same time will result in one of them failing. From the info provided we don’t know which one you are actually using with HA. Check the Server URL in the integration settings panel. If it’s pointing to core, following the migration guide. If it’s pointing to the add-on, delete the core add-on.

Thanks! I didn’t realize that it was complaining about the core add-on. Had some confusion when I was first setting up ZWave integration an installed the core-addon before realizing that I only needed the JS addon. I guess I completely forgot to delete the Core one and it was still set to start at boot-up.

Thanks!

Eric