MQTT sensor topic current temperature

[windmillBart]

I have recently installed the thermostat shield and it is working fine. A DHT22 is connected to a raspberry pi and is publishing the current room temperature. I have also have a topic 'diyless_thermostat/cmnd/things/thermostat/properties/temperature' publishing the room temperature as a float. I also have published 'diyless_thermostat/cmnd/things/thermostat/properties/tempSource = 1' to configure the MQTT sensor,
But it seems not to work, the topic opentherm-thermostat/current-temperature/get = the value of the internal sensor and not the value of the MQTT sensor.
I also can't find any code block in the sketch that would subscribe or listen to the MQTT sensor.
What needs to be added or done to make the MQTT sensor work with the thermostat?
thanks for your feedback.

[diyless]

Hi @windmillBart ,
Did you choose the MQTT sensor option from the thermostat Web interface?
(Menu -> Sensor -> MQTT sensor)

[windmillBart]

Hi, I'm not able to open the Web interface; I have uploaded the sketch from the website https://diyless.com/blog/home-assistant-opentherm-thermostat on a WEMOS D1 mini ESP32; (I did changed the pins and import Wifi.h to make it work for ESP32.) I ordered the shield only with order 2306269569 and I used a WEMOS D1 mini ESP32 from AZ-delivery that I already had bought earlier. In the sketch I used I don't see a webserver, therefore I used the MQTT topic to publish value 1 to configure MQTT Sensor (I tought). Thanks, Bart Op ma 28 aug 2023 om 08:08 schreef DIYLESS Electronics < ***@***.***>:

…

Hi @windmillBart <https://github.com/windmillBart> , Did you choose the MQTT sensor option from the thermostat Web interface? (Menu -> Sensor -> MQTT sensor) — Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7CUJOAD6QJYMWOQZ7NRSYDXXQYUFANCNFSM6AAAAAA373N4CA> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[diyless]

We will update our example to use the latest Arduino core as well as libraries and test if this issue is still active