MQTT Discovery Problems - Enable Debugging / Logging

[jwiesel]

Hi everyone,
first of all: This is a great project! Exactly what I was looking for after several tasmota devices went into reset and I had to manually set them up again.

I just set up the docker container.
I am using MQTT and disabled the HTTP-API in my tasmota devices. Furthermore each tasmota webUi has a different password.
Unfortunately I only find one device via MQTT discovery and try to find out why.

I tried enabling debugging in phpMQTT.php, but these logs are not shown in the container logs or on screen.

Is there any possibility to enable debugging in the application to identify the root cause of my issue?

[patrickdk77]

it can support a different password per device, but the web interface doesn't support that at this time.
The mqtt function is just for searching, it uses the http-api to validate what it found, exists and that it can do a backup. If the http-api doesn't work, with the password, the device will not be found, and it will not do a backup.

I am not sure if it changed over the last few months, but backups where only supported via the http-api interface, and not via mqtt, so http-api being enabled and working is a requirement.

The mqtt interface is to lower the load on http requests, since tasmota is much more happy with them, and we can quickly find devices instead of searching every single ip address. We do collect the needed information from mqtt if we can, otherwise it will fallback to http-api for it. But we always do backups via http-api

[jwiesel]

Hi @patrickdk77,
thanks for your swift and detailed response! Good to know, that the backups work only via http-api.
By using trial & error I realized, that the only device found via discovery did not contain a password for web-ui.

Where can I set individual passwords per device?

I did some php programming in the past with bootstrap. Do you know, if this project still accepts PRs to be merged into master? Looping in @danmed as well.
I'd be interested to contribute (e.g. readme, settings dialog, log-output / error messages), if the project team is interested.

[jwiesel]

Alright. Found a workaround for individual passwords. If I add my devices to database table "devices", they become visible in WebUI and I can maintain the individual passwords per device there via "Edit".