ESP Home Zwave Coordinator

I have a tubes-zw ESP POE coordinator that has worked fine for several years. I regularly update the ESP home builder but do not always update the devices unless there is a specific firmware update for them.

I tried to update the device 2 weeks ago as there was an update (2026-8-1) from my current version 2026-6-5 and it failed with the following error:

I followed the ESP home builder instructions to clean the build folder and reset the environment but it did not work. I waited for a few more ESP home updates to see if they would clear the error but that has also not worked.

I am not much of a programmer but the error seems to indicate there is a syntax error in the build code for the device in relation to how ESP home now compiles the build file.

Can anyone help?

Tubes probably can. He’s very responsive: Contact – TubesZB

Thanks Tom, I have sent him a message.

Thanks for the ping, Feel free to ping me here, I’m not on here as much as I once was, but check back whenever mentioned.

Be sure you are using the latest config from https://github.com/tube0013/TubesZB-ESPHome-Builder/tree/main/manifests and be sure you clear your esphome build dir and cache as this was fixed last month for the 2026.7 esphome release.

One note on the newest yaml, it changes the connection for zwave to use the esphome zwave-proxy component so stream server is not used at all on the zwave side anymore. It does require changing the port address from tcp:// to esphome:// and removing the port.

https://tube0013.github.io/tube_gateways/getting-started/z-wave-proxy-update/

Thanks for this, but I have a few questions.

From the following link, which actual yaml file should I be using:

Should I just use the tubes-zw.yaml ?

In the yaml files they contain:

js_include: ../www3TZB.js

Which produces an error and will not compile.

From this link should I be making this change in the zwave.js UI app:

Ok, I used the tubes-zw yaml file and commented out the 2 js settings, this compiled and downloaded.

I then changed the connection in the zwavejsui setting from tcp to esphome and restarted, comms all good.

What are the implications of commenting out the 2 js parameters in webserver?

the custom JS adds a warning on the web frontend about not leaving it open as it consumes resources.

Cheers, so not required for opertion then.