Z-Wave JS MQTT Driver: "path" is not defined:

Configuration Z-Wave
1

I just set up a test Pi and loaded HA via flashing a microSD and all appears updated, yet when I open the Z-Wave JS (MQTT) control panel I get the notice that Driver: “path” is not defined:

Z-Wave JS Integration is there. Z-Wave JS add-on was not installed, only the Z-Wave JS MQTT add-on.

ZWave MQTT doesn’t see any devices and I suspect the path issue to be the problem.

But also - I can add devices within the integration and they appear in my Lovelace and can be controlled.

Its a brand new install using the Zooz S2 stick.

Any ideas here?

1 Like
2

Same problem as described above

3

I wanted to respond earlier but got side-tracked.

At least for me, the issue arose from not having the security keys defined. Once those were populated the error went away and I was able to use the interface In total.

Check that next.

4

I just did a fresh install of HA with everything from scratch: flashed a new 32GB SD card with Balena Etcher, using the current image from the HARaspberry Pi page: github.com/home-assistant/operating-system/releases/download/7.4/haos_rpi3-64-7.4.img.xz

Powered up the RPi, did not restore a backup, but rather set up the HA location et al as a new install. Installed nothing else but went directly to the Addons store and installed ZwaveJS2MQTT. Following the instructions, I then STARTed the addon, and looked at the log. The beginning of the log is at the end of this post. Note the lines:

[14:23:39] INFO: Starting the Z-Wave JS to MQTT…
/bin/sh: git: not found

I never got further. After that, things go downhill with things “not found” and repetitive failures:

2022-02-18 14:29:25.699 INFO ZWAVE: Connecting to
2022-02-18 14:29:25.712 WARN ZWAVE: Retry connection in 3 seconds…
2022-02-18 14:29:28.729 INFO ZWAVE: Connecting to
2022-02-18 14:29:28.742 WARN ZWAVE: Retry connection in 3 seconds…

Curiously, the addon’s Web UI works, but shows the “path not defined” error in red. It seems the “git not found” error is not considered fatal?

Perhaps git is needed during the install to download more installation data, such as json files, from github? But since it’s not in the SD Card disk image the install can’t get anything using git. I suspect if I installed on some other machine, e.g., my Ubuntu desktop, everything might work, because git is already there.

Any other ideas? This is a fresh install with new SD card, current HA image file for RPi, and a known working RPi.

Here’s the log from STARTing the JS2MQTT addon:

[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing…
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] configuration.sh: executing…
[cont-init.d] configuration.sh: exited 0.
[cont-init.d] nginx.sh: executing…
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[14:23:39] INFO: Starting the Z-Wave JS to MQTT…
/bin/sh: git: not found
2022-02-18 14:23:47.948 INFO APP: Version: 6.5.1
2022-02-18 14:23:47.962 INFO APP: Application path:/opt
…
2022-02-18 14:23:48.052 WARN STORE: scenes.json not found

5

New info…

I decided to ignore the errors in the addon ZWaveJS2MQTT log, and just continue setting things up as if the install went well. After using the UI to pick the proper device for my Zwave stick (new HUSBZB-1), the “path not defined” and repetitive failing retries errors disappeared. So I installed the ZwaveJS integration, and then successfully just included a new device.

So I’m good to go. My problem was that I looked at the addon log and thought the continuous errors meant the install didn’t work. Turns out it did! i was just misled by the instructions…