installed the ZWave-JS-UI. Initalliy access via 8091. Topic is solved

[PA3FAT]

Managed to get things started up using ZWave-JS-UI.

Had access to my pi-ip:8091.

Managed to give all (seem identical id's) a name in the interface.

Did a reboot a now this access via port 8091 is no longer working.

followed the method by Andrehj
viewtopic.php?p=297829#p297829

What can be the cause?
On the command prompt of the pi: zwave-js-ui.help this still works.
So it looks like zwave-js-ui is running.

Other thing i noticed. I did not see any new devices comming via the mqtt new hardware definition.

[waltervl]

The snap install method is not the most stable one it seems. Advised is to use the docker install...

[PA3FAT]

Tried the docker method yesterday but did not get far with that.

[PA3FAT]

it is working again. Repeated some snap related commands. But not sure it is stable.

What i noticed is that i cannot find the replace device button.

[PA3FAT]

Found it under swithes/utility. Seems to work.

[FireWizard]

@waltervl,

You wrote:

The snap install method is not the most stable one it seems. Advised is to use the docker install...

For approx. a year I'm running ZWaveJS-UI on a separate Raspberry Pi 3, installed, using snapd. During installation I did not see any issues and it ran "out of the box" and I did not see any stability issues.

Where do you get that information, that is is not the most stable solution, from.

In my opinion it does not make any difference, whether it is installed in a docker container or through snapd. It is the same software.

Regards

[waltervl]

If I see zwavejs installation issues here on the forum it is almost always with snap install.

[FireWizard]

Hi @waltervl

So it is your conclusion, based on issues on this forum.
Okay
But are it "Installation issues" or "Stability issues"?

I have to confess, that I use only 2 ZWave (Fibaro) Smoke detectors, so it is not a big network.
But I do not understand, that a docker installation is more stable than an installation, installed by snapd (on a separate PI)

Regards

[PA3FAT]

Keep getting errors in Domoticz on MQTT.

2023-08-14 22:44:20.567 [6adfc220] Error: MQTT: Failed to start, return code: 14/Connection refused (Check IP/Port)
2023-08-14 22:45:03.751 [6adfc220] Error: MQTT: Failed to start, return code: 14/Connection refused (Check IP/Port)
2023-08-14 22:45:33.827 [6adfc220] Error: MQTT: Failed to start, return code: 14/Connection refused (Check IP/Port)
2023-08-14 22:46:03.884 [6adfc220] Error: MQTT: Failed to start, return code: 14/Connection refused (Check IP/Port)
2023-08-14 22:46:33.928 [6adfc220] Error: MQTT: Failed to start, return code: 14/Connection refused (Check IP/Port)
2023-08-14 22:46:52.575 [6adfc220] Error: MQTT: Failed to start, return code: 14/Connection refused (Check IP/Port)
2023-08-14 22:47:21.616 [6adfc220] Error: MQTT: Failed to start, return code: 14/Connection refused (Check IP/Port)
2023-08-14 22:48:51.743 [6adfc220] Error: MQTT: Failed to start, return code: 14/Connection refused (Check IP/Port)
2023-08-14 22:49:21.783 [6adfc220] Error: MQTT: Failed to start, return code: 14/Connection refused (Check IP/Port)
2023-08-14 22:49:51.820 [6adfc220] Error: MQTT: Failed to start, return code: 14/Connection refused (Check IP/Port)

Seems not to differ if using localhost or the ip of the PI.

Any tips?

[FireWizard]

Hi, @PA3FAT,

Do you try to access ZWaveJS-UI with port 8091 from Domoticz?

Regards

[PA3FAT]

yes. And i have access to this gui.

Note: i am on stable release. Was on beta but then zwave was no longer working. Quickly reverted to stable.
In parallel now getting the zwave-js-ui and mqtt working....

[PA3FAT]

Think i solved it.

Replace the mosquitto.conf with the default mosquitto.conf.dpkg-dist and added
"listener 1883" and "allow_anonymous true" again to the conf file.

Now the errors are gone.

Solved it based on checks done via this thread:
viewtopic.php?t=39565

[FireWizard]

Hi, @PA3FAT,

So at the end, it had nothing to do with ZWaveJS-UI. That has probably been working fine from the beginning.
But it was a wrong configuration for Mosquitto.

So it is good that this issue has been solved.

Regards

[waltervl]

The problem accessing port 8091 after reboot was solved "by repeating some snap commands". After that the Mosquitto conf issue (clearly mentioned in the Domoticz MQTT wiki).