# MQTT discovery Supla-PL problem **URL:** \ **Category:** Questions & Help\ **Created:** [December 23, 2025, 8:01am UTC](https://community.homey.app/t/mqtt-discovery-supla-pl-problem/147655 "2025-12-23T08:01:18Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Marcin\_Krysk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marcin_krysk/32/120753_2.png) [@Marcin\_Krysk](https://community.homey.app/u/Marcin_Krysk)\ **Post date:** [December 23, 2025, 8:01am UTC](https://community.homey.app/t/mqtt-discovery-supla-pl-problem/147655/1 "2025-12-23T08:01:18Z")
Hello. I have devices from Poland running Supla software that share data based on MQTT discovery. I’m trying to integrate them with Homey Self-Server. I have an external broker, Mosquitto. I tried to do it this way. I installed the MQTT Client, and for example, Tasmota devices can be clearly seen which ones are added to this client. They load in the Tasmota MQTT application. Generally, it doesn’t seem to subscribe to the Supla topic at all, only to the Topic Tele where the Tasmota devices are located. Can anyone suggest something? ---
**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:** [December 23, 2025, 11:20pm UTC](https://community.homey.app/t/mqtt-discovery-supla-pl-problem/147655/2 "2025-12-23T23:20:36Z")
Maybe this tutorial gets you going > [@\[Tutorial\]\[Pro\] Basic MQTT setup & connect Itho Daalderop NRG.watch interface](https://community.homey.app/t/tutorial-pro-basic-mqtt-setup-connect-itho-daalderop-nrg-watch-interface/139521): > > This tutorial is about setting up a basic MQTT system. (and yes I know there’s several other MQTT tutorials around grimacing) Additionally, it tries to explain how to connect a system like the NRG.watch [interface](https://www.nrgwatch.nl/product/itho-cve-rft-wifi-add-on/) for Itho airboxes (no need for the Homey NRG.watch app) Feel free to add missing info, or correct any possible errors. (This is a wiki) Homey: 1 Install 3 MQTT community apps: MQTT Broker [[1]](#footnote-641566-1) MQTT Client MQTT Hub ¹) The broker may run anywhere, but we stick to Homey for now … ---
**Author:** ![Marcin\_Krysk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marcin_krysk/32/120753_2.png) [@Marcin\_Krysk](https://community.homey.app/u/Marcin_Krysk)\ **Post date:** [December 24, 2025, 8:12am UTC](https://community.homey.app/t/mqtt-discovery-supla-pl-problem/147655/3 "2025-12-24T08:12:19Z")
So, am I looking correctly? To connect an external MQTT broker, I need to buy an additional physical device module? ---
**Author:** ![JPe4619](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jpe4619/32/9017_2.png) [@JPe4619](https://community.homey.app/u/JPe4619)\ **Post date:** [December 24, 2025, 4:41pm UTC](https://community.homey.app/t/mqtt-discovery-supla-pl-problem/147655/4 "2025-12-24T16:41:05Z")
> [@\[Tutorial\]\[Pro\] Basic MQTT setup & connect Itho Daalderop NRG.watch interface](https://community.homey.app/t/tutorial-pro-basic-mqtt-setup-connect-itho-daalderop-nrg-watch-interface/139521/1): > > Homey: 1 Install 3 MQTT community apps: MQTT Broker [[1]](#footnote-641566-1) MQTT Client MQTT Hub ¹) The broker may run anywhere, but we **stick to Homey** for now … So, it is installed on Homey this way, no external needed. ---
**Author:** ![Marcin\_Krysk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marcin_krysk/32/120753_2.png) [@Marcin\_Krysk](https://community.homey.app/u/Marcin_Krysk)\ **Post date:** [December 30, 2025, 12:42pm UTC](https://community.homey.app/t/mqtt-discovery-supla-pl-problem/147655/5 "2025-12-30T12:42:13Z")
I managed to do it partially because when I add a virtual device in conjunction with the mQTT hub, the command even arrives when I send setTopic to the mQTT server where I have my suppl. From what I’ve read, the problem is the sending format—retain. I see the message arrives in mQTT Explorer, but nothing happens. The problem is solved when I do it using Flow Advanced, and I send it anyway, and then everything is fine.