[Feature Request] mqtt_shortcut cannot use broker that enabled tls, also self-signed certificate

[imvincent]

I recently setup a mqtt broker to study some ioT project, I found this app very useful for my project, but when I update my broker to use self-signed certificate and enable tls, I cannot use this app to send mqtt msg anymore.

I strongly recommended this feature to be implemented, thanks for all your hard work.

[Waboodoo]

I'll see what I can do. I don't know much about MQTT, so can't yet say how well this will go.

Do you use MQTT Shortcuts or do you do it via the sendMqttMessages Scripting function?

[imvincent]

Thanks for your hard work Waboodoo, sorry for my late reply

I use MQTT shortcuts function, I didn't use sendMqttMessages Scripting function, for your reference, I picked one image of other MQTT app provideded:

[Waboodoo]

What is the error message you get from the app?

[imvincent]

connection lost Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Roland Meyer ***@***.***> Sent: Saturday, January 31, 2026 6:32:57 PM To: Waboodoo/HTTP-Shortcuts ***@***.***> Cc: imvincent ***@***.***>; Author ***@***.***> Subject: Re: [Waboodoo/HTTP-Shortcuts] [Feature Request] mqtt_shortcut cannot use broker that enabled tls, also self-signed certificate (Issue #540) [https://avatars.githubusercontent.com/u/2445563?s=20&v=4]Waboodoo left a comment (Waboodoo/HTTP-Shortcuts#540)<#540 (comment)> What is the error message you get from the app? — Reply to this email directly, view it on GitHub<#540 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AB6MDTL6EJEYOBAFA3BW34L4JSAFTAVCNFSM6AAAAACTN7UCL2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMRYGEZDENRUGY>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[Waboodoo]

I'm adding an option to configure host name verification for MQTT Shortcuts, the same way that it is already possible for HTTP Shortcuts. This option can be found in the "Advanced Technical Settings" when editing the shortcut. These changes are part of the 4.2.0 release, which is now available for beta testing. You can join the beta program here: https://play.google.com/apps/testing/ch.rmy.android.http_shortcuts

Hope this helps with this issue, as I was not fully able to reproduce the original problem.

[imvincent]

Thanks for your kindly help, I will try to test your new implementation

…

________________________________ From: Roland Meyer ***@***.***> Sent: Saturday, January 31, 2026 7:55:01 PM To: Waboodoo/HTTP-Shortcuts ***@***.***> Cc: imvincent ***@***.***>; Author ***@***.***> Subject: Re: [Waboodoo/HTTP-Shortcuts] [Feature Request] mqtt_shortcut cannot use broker that enabled tls, also self-signed certificate (Issue #540) [https://avatars.githubusercontent.com/u/2445563?s=20&v=4]Waboodoo left a comment (Waboodoo/HTTP-Shortcuts#540)<#540 (comment)> I'm adding an option to configure host name verification for MQTT Shortcuts, the same way that it is already possible for HTTP Shortcuts. This option can be found in the "Advanced Technical Settings" when editing the shortcut. These changes are part of the 4.2.0 release, which is now available for beta testing. You can join the beta program here: https://play.google.com/apps/testing/ch.rmy.android.http_shortcuts Hope this helps with this issue, as I was not fully able to reproduce the original problem. — Reply to this email directly, view it on GitHub<#540 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AB6MDTNA2K7J5ZVJ6XUJRGL4JSJZHAVCNFSM6AAAAACTN7UCL2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMRYGIZTMOBXGM>. You are receiving this because you authored the thread.

[imvincent]

I updated to beta version, now the result is: connection reset My broker use a self signed certificate, whether thats the reason Also I cannot change the host vertification method, http shortcut can select from 3 types

…

________________________________ From: Roland Meyer ***@***.***> Sent: Saturday, January 31, 2026 7:54:59 PM To: Waboodoo/HTTP-Shortcuts ***@***.***> Cc: imvincent ***@***.***>; Author ***@***.***> Subject: Re: [Waboodoo/HTTP-Shortcuts] [Feature Request] mqtt_shortcut cannot use broker that enabled tls, also self-signed certificate (Issue #540) [https://avatars.githubusercontent.com/u/2445563?s=20&v=4]Waboodoo left a comment (Waboodoo/HTTP-Shortcuts#540)<#540 (comment)> I'm adding an option to configure host name verification for MQTT Shortcuts, the same way that it is already possible for HTTP Shortcuts. This option can be found in the "Advanced Technical Settings" when editing the shortcut. These changes are part of the 4.2.0 release, which is now available for beta testing. You can join the beta program here: https://play.google.com/apps/testing/ch.rmy.android.http_shortcuts Hope this helps with this issue, as I was not fully able to reproduce the original problem. — Reply to this email directly, view it on GitHub<#540 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AB6MDTNA2K7J5ZVJ6XUJRGL4JSJZHAVCNFSM6AAAAACTN7UCL2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMRYGIZTMOBXGM>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[imvincent]

for your reference

…

________________________________ From: Roland Meyer ***@***.***> Sent: Saturday, January 31, 2026 7:54:59 PM To: Waboodoo/HTTP-Shortcuts ***@***.***> Cc: imvincent ***@***.***>; Author ***@***.***> Subject: Re: [Waboodoo/HTTP-Shortcuts] [Feature Request] mqtt_shortcut cannot use broker that enabled tls, also self-signed certificate (Issue #540) [https://avatars.githubusercontent.com/u/2445563?s=20&v=4]Waboodoo left a comment (Waboodoo/HTTP-Shortcuts#540)<#540 (comment)> I'm adding an option to configure host name verification for MQTT Shortcuts, the same way that it is already possible for HTTP Shortcuts. This option can be found in the "Advanced Technical Settings" when editing the shortcut. These changes are part of the 4.2.0 release, which is now available for beta testing. You can join the beta program here: https://play.google.com/apps/testing/ch.rmy.android.http_shortcuts Hope this helps with this issue, as I was not fully able to reproduce the original problem. — Reply to this email directly, view it on GitHub<#540 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AB6MDTNA2K7J5ZVJ6XUJRGL4JSJZHAVCNFSM6AAAAACTN7UCL2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMRYGIZTMOBXGM>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[Waboodoo]

Did you set the URL's protocol to ssl? Doing so will enable the settings under "Advanced Technical Settings". For starters you can try disabling host name verification there.

[imvincent]

Thanks very much, after use ssl protocal, the option becomes enabled But that's strange my server.crt's checksum is different from app response, I only can disable the verification to finish msg sending.

…

________________________________ From: Roland Meyer ***@***.***> Sent: Saturday, January 31, 2026 9:51:31 PM To: Waboodoo/HTTP-Shortcuts ***@***.***> Cc: imvincent ***@***.***>; Author ***@***.***> Subject: Re: [Waboodoo/HTTP-Shortcuts] [Feature Request] mqtt_shortcut cannot use broker that enabled tls, also self-signed certificate (Issue #540) [https://avatars.githubusercontent.com/u/2445563?s=20&v=4]Waboodoo left a comment (Waboodoo/HTTP-Shortcuts#540)<#540 (comment)> Did you set the URL's protocol to ssl? Doing so will enable the settings under "Advanced Technical Settings". For starters you can try disabling host name verification there. — Reply to this email directly, view it on GitHub<#540 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AB6MDTMEJILNIZDDXWZE7A34JSXOBAVCNFSM6AAAAACTN7UCL2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMRYGU3DMNJRGY>. You are receiving this because you authored the thread.

[Waboodoo]

It's best to use your certificate's SHA256 fingerprint. You can get it by running openssl x509 -noout -fingerprint -sha256 -inform pem -in [your certificate file]

[imvincent]

Thanks for your help, I used crt file checksum as crt checksum. With your kind help, my issue completely solved. Using beta version of http shortcuts, we can handle almost all mqtt cases but one: mqtt server configed to certificate client ca but we have no option to add client ca. Whether my understanding is correct

…

________________________________ From: Roland Meyer ***@***.***> Sent: Sunday, February 1, 2026 5:33:28 AM To: Waboodoo/HTTP-Shortcuts ***@***.***> Cc: imvincent ***@***.***>; Author ***@***.***> Subject: Re: [Waboodoo/HTTP-Shortcuts] [Feature Request] mqtt_shortcut cannot use broker that enabled tls, also self-signed certificate (Issue #540) [https://avatars.githubusercontent.com/u/2445563?s=20&v=4]Waboodoo left a comment (Waboodoo/HTTP-Shortcuts#540)<#540 (comment)> It's best to use your certificate's SHA256 fingerprint. You can get it by running openssl x509 -noout -fingerprint -sha256 -inform pem -in [your certificate file] — Reply to this email directly, view it on GitHub<#540 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AB6MDTNC332L4PSHMEXY47D4JUNSRAVCNFSM6AAAAACTN7UCL2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMRZGM4TKNRYHE>. You are receiving this because you authored the thread.Message ID: ***@***.***>