Zwave-JS-UI can not connect to MQTT problem

[fjuppe]

Hello,
I am a complete newbie to setting things up in Linux. I have just installed a new Aeon Z-wave USB stick on my RPi 4B+ running standard Debian version 11. I have manage to set up Zwave-JS-UI, my USB stick is working, I have included one switch.

I also run Domoticz where I want to control all Z-wave devices. I have followed the installation guidelines but I dont get any devices under the Domoticz "MQTT Auto Discovery Client Gateway with LAN interface". Domoticz log says "Z-Wave: Connecting to 192.168.0.28:1883" without any error.

In Zwave-JS-UI I get the below error when debugging. I suspect this is causing the problem but I dont have knowledge to solve this.
Please give me some commands to let me be able to get this working. If you need more info, please give detailed instructions how to obtain this since I am not so familiar with Linux. I.e. where to check for MQTT client details......?
Thanks in advance for your help!

2023-09-26 10:03:50.477 INFO MQTT: MQTT client reconnecting
2023-09-26 10:03:50.482 ERROR MQTT: Mqtt client error Connection refused: Not authorized
ErrorWithReasonCode: Connection refused: Not authorized
at handleConnack (/snap/zwave-js-ui/239/lib/zwave-js-ui/node_modules/mqtt/src/lib/handlers/connack.ts:47:15)
at handle (/snap/zwave-js-ui/239/lib/zwave-js-ui/node_modules/mqtt/src/lib/handlers/index.ts:43:17)
at work (/snap/zwave-js-ui/239/lib/zwave-js-ui/node_modules/mqtt/src/lib/client.ts:725:17)
at Writable.writable._write (/snap/zwave-js-ui/239/lib/zwave-js-ui/node_modules/mqtt/src/lib/client.ts:749:4)
at writeOrBuffer (/snap/zwave-js-ui/239/lib/zwave-js-ui/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:334:12)
at _write (/snap/zwave-js-ui/239/lib/zwave-js-ui/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:283:10)
at Writable.write (/snap/zwave-js-ui/239/lib/zwave-js-ui/node_modules/mqtt/node_modules/readable-stream/lib/internal/streams/writable.js:286:10)
at Socket.ondata (node:internal/streams/readable:754:22)
at Socket.emit (node:events:390:28)
at addChunk (node:internal/streams/readable:315:12)
2023-09-26 10:03:50.485 INFO MQTT: MQTT client closed

[robertsLando]

Mqtt client error Connection refused: Not authorized

You have inserted wrong credentials in mqtt settings. Correct them

[fjuppe]

Yes, I can understand this. But I dont remember entering any credentials during MQTT installations. Where/how can I find or change these. Are there any default credentials ?? Remember I am a newbie in Linux.......
Thanks in advance!

[robertsLando]

@fjuppe What broker are you using?

[fjuppe]

I am using Snap.Med vänlig hälsning/Best regardsTorbjörn Hall26 sep. 2023 kl. 16:57 skrev Daniel Lando ***@***.***>: @fjuppe What broker are you using? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[robertsLando]

I am using Snap.Med

Never heard, you should check if there are auth settings there so

[fjuppe]

OK, I will try to locate the credentials file…Thank you for your supportI will close the discussion and do some homework…Med vänlig hälsning/Best regardsTorbjörn Hall26 sep. 2023 kl. 17:08 skrev Daniel Lando ***@***.***>: I am using Snap.Med Never heard, you should check if there are auth settings there so —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[robertsLando]

MQTT auth is handled on broker side so you should check if that broker has some default username/password or if there is a file where you declare available clients credentials

[fjuppe]

I will do my homework regarding the MQTT credentials,

[fjuppe]

OK, I will check in Snap environment then…Med vänlig hälsning/Best regardsTorbjörn Hall26 sep. 2023 kl. 17:43 skrev Daniel Lando ***@***.***>: MQTT auth is handled on broker side so you should check if that broker has some default username/password or if there is a file where you declare available clients credentials —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: ***@***.***>