MQTT Broken in v24.12.23 ?

[AdmiralRaccoon]

Hi all,
anyone else have MQTT issued after updating to the latest version? I get no updates in Home Assistant anymore, reverting to the previous version helps.
I wanted to create a bug report, but there seems to be some github issues right now, i can´t create a topic. I already set the logs to debug, but when filtering for "MQTT´ i get to really useful information or error messages:

`15:59:03 [Plugin utils] display_name: MQTT publisher
15:59:03 [Plugin utils] description: A plugin to publish a notification via MQTT to Home Assistant.
15:59:04 [Config] Plugins to load: ['ARPSCAN', 'AVAHISCAN', 'INTRNT', 'NMAPDEV', 'NSLOOKUP', 'MQTT', 'CSVBCKP', 'DBCLNP', 'MAINT', 'NEWDEV', 'NTFPRCS', 'SETPWD', 'SYNC', 'UI', 'VNDRPDT', 'WORKFLOWS']
15:59:06 [Plugin utils] display_name: MQTT publisher
15:59:06 [Plugin utils] description: A plugin to publish a notification via MQTT to Home Assistant.
15:59:07 [Config] Plugins to load: ['ARPSCAN', 'AVAHISCAN', 'INTRNT', 'NMAPDEV', 'NSLOOKUP', 'MQTT', 'CSVBCKP', 'DBCLNP', 'MAINT', 'NEWDEV', 'NTFPRCS', 'SETPWD', 'SYNC', 'UI', 'VNDRPDT', 'WORKFLOWS']`

Anyway, for now i´m restoring the Backup with the previous version. Maybe someone has same issues,
Thanks and bye,
Philipp

[jokob-sk]

Hi @AdmiralRaccoon ,

I just enabled MQTT for testing and it seems to be working for me:

It's possible something went wrong during the upgrade.

If you try again, can you set LOG_LEVEL debug or trace and post the logs?

From the above logs it looks like MQTT isn't executed at all.

Can you also check Docker logs / potrtainer logs? Maybe the backend is constantly restarting due some bug.

Thanks,
j

[jokob-sk]

Oh, also check this thread: #921 the /app/log/plugins folder might have wrong permissions or might be missing

[AdmiralRaccoon]

Well, now it seems to work again
I only changed the MQTT setting "When to run" from "on_notification" to "always after scan", i havn´t changed anything else right now.
Does this help in any way?

08:19:56 [MQTT] Sending MQTT topic: system-sensors/device_tracker/mac_c4_4f_33_9f_37_47/attributes
08:19:56 [MQTT] Sending MQTT message: {"last_ip": "192.168.1.66", "is_new": "0", "vendor": "Espressif Inc", "mac_address": "c4:4f:33:9f:37:47", "model": "party-bar-eingang", "last_connection": "2024-12-14T17:31:32+00:53", "first_connection": "2024-03-15T19:41:04+01:00"}
08:19:56 [MQTT] Existing, skip Device Name: tasmota24
08:19:56 [MQTT] Publishing sensor number 0
08:19:56 [MQTT] Existing, skip Device Name: tasmota24
08:19:56 [MQTT] Publishing sensor number 0
08:19:56 [MQTT] Existing, skip Device Name: tasmota24
08:19:56 [MQTT] Publishing sensor number 0
08:19:56 [MQTT] Existing, skip Device Name: tasmota24
08:19:56 [MQTT] Publishing sensor number 0
08:19:56 [MQTT] Existing, skip Device Name: tasmota24
08:19:56 [MQTT] Publishing sensor number 0
08:19:56 [MQTT] Existing, skip Device Name: tasmota24
08:19:56 [MQTT] Publishing sensor number 0
08:19:56 [MQTT] Sending MQTT topic: system-sensors/sensor/mac_70_03_9f_17_c3_c5/state
08:19:56 [MQTT] Sending MQTT message: {"last_ip": "192.168.1.124", "is_new": "0", "vendor": "Espressif Inc", "mac_address": "70:03:9f:17:c3:c5", "model": "tasmota24", "last_connection": "2024-12-14T17:31:32+00:53", "first_connection": "2024-03-15T19:41:04+01:00"}
08:19:56 [MQTT] Existing, skip Device Name: tasmota24

[jokob-sk]

Glad to hear that!

• "on_notification" runs only the plugin if there is something to notify about
• "always after scan" as the name suggests, is run always after any scan finishes.

[AdmiralRaccoon]

Yes, but that is the odd thing. I had the "on_notification" option set since mqtt was introduced was introduced in NetAlertX, and everything the same way like "always_after_scan"
But anyway, works like it should again & thank you for your help