# MQTT client with TLS verification

**URL:** <https://community.homey.app/t/mqtt-client-with-tls-verification/142745>\
**Category:** Apps\
**Created:** [September 9, 2025, 6:13am UTC](https://community.homey.app/t/mqtt-client-with-tls-verification/142745 "2025-09-09T06:13:25Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Simon\_Ojstersek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/simon_ojstersek/32/75199_2.png) [@Simon\_Ojstersek](https://community.homey.app/u/Simon_Ojstersek)\
**Post date:** [September 9, 2025, 6:13am UTC](https://community.homey.app/t/mqtt-client-with-tls-verification/142745/1 "2025-09-09T06:13:26Z")

</div>

Hi. Is there any chances that with homey publish and subscribe topic with client TLS verification (with .cer/.crt/.pem/.key certificate and key)?

Best regards, Simon

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [September 9, 2025, 10:47am UTC](https://community.homey.app/t/mqtt-client-with-tls-verification/142745/2 "2025-09-09T10:47:01Z")

</div>

Yes, the app is called

 ![Screenshot_20250909_124557_Firefox](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/d/7d5ba8d464a51d2f935fda5429543097d2db7578.jpeg)

MQTT Broker & MQTT Hub apps are available as well.

 ![Screenshot_20250909_125123_Chrome](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/5/e5114409004dcaf6001a8a13e566c5ed22fd588c.jpeg)

---

<div class="post-metadata">

**Author:** ![Simon\_Ojstersek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/simon_ojstersek/32/75199_2.png) [@Simon\_Ojstersek](https://community.homey.app/u/Simon_Ojstersek)\
**Post date:** [September 9, 2025, 11:01am UTC](https://community.homey.app/t/mqtt-client-with-tls-verification/142745/3 "2025-09-09T11:01:45Z")

</div>

Hi Peter.

With “MQTT client app” can not load certificate and key, just disable checking.

Thanks anyway.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [September 9, 2025, 11:38am UTC](https://community.homey.app/t/mqtt-client-with-tls-verification/142745/4 "2025-09-09T11:38:35Z")

</div>

The Broker should provide for the secure connection and certificate

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [September 9, 2025, 11:57am UTC](https://community.homey.app/t/mqtt-client-with-tls-verification/142745/5 "2025-09-09T11:57:08Z")

</div>

Client-side certificates are meant for identification, so the broker is certain that it’s talking to a particular client.

---

<div class="post-metadata">

**Author:** ![Simon\_Ojstersek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/simon_ojstersek/32/75199_2.png) [@Simon\_Ojstersek](https://community.homey.app/u/Simon_Ojstersek)\
**Post date:** [September 9, 2025, 12:01pm UTC](https://community.homey.app/t/mqtt-client-with-tls-verification/142745/6 "2025-09-09T12:01:26Z")

</div>

And this is not possible with “mqtt client app” for now.