I checked now which version of the
mqtt package n8n uses in which version.
The latest n8n version uses
4.2.4. That version of the package got used the first time with [email protected] The version before [email protected] used
4.2.1 which is the same version that got used with [email protected] they are using
So you can check if it works with [email protected] and if it then breaks with [email protected] If that is the case, it is definitely the underlying
mqtt package. In this case you can report the issue here:
They will then have a better understanding what changed and how to repair it. I personally have sadly literally no experience with MQTT at all. If it is really a bug and the fix it, it will then also automatically find its way into n8n.