subscribe to external MQTT device (e.g shelly)

[raibisch]

Is there a way (maybe with the 'my_custom' extension) to direct subscribe to an external MQTT device. In my case it is a shelly HT3 that sends temp. and hum. then goes to deep-sleep until value-change. I want to subscribe this JSON-value pair and view as a label or var.
something like this (in an other ESP32 project):
mqtt.subscribe("shellies/status/temperature:0", [](const char * topic, const char * payload)

...yes this could done in in a homeautomation system like HASS, but it is more comfortable to get the value direct without external systems and I don't use HASS.

any Ideas ?

[fvanroie]

The project depends on a Home Automation controller to do these types of things, so there is no way to do that with the out-of-the-box firmware.

But, you can customize the firmware to fit your needs and implement it in custom code.

[raibisch]

that's the core of my question, how to integrate a mqtt subscribe to custom code ?

[fvanroie]

Your question is a use-case that is out of the scope of this project. I haven't looked into this, specifically so you'll have to look at the example code in this project to see if it fits your purpose.

openHASP is basically an Arduino sketch, so if you can do it in Arduino it should be possible to add it to the code... "How" is too broad of a question... as I can not explain this in detail without doing the actual coding work. There are several options to solve each problem and it depends on your requirements, time and coding skills.

[raibisch]

You are absolutely right, my request is “out of scope”!

However, I appreciate the broad hardware base and the flexible UI configuration of your project. That's why I took it as the basis for my project. My question was just to get some information about the internal structure of the source code. In a project with thousands of lines of code and complex configuration options, it is not always easy to understand the code, even for an experienced software developer (especially in the MQTT part, several alternative libs are integrated) and I speak for my self 'the code is self explaining' ;-)

In the meantime, however, I have realized my adaptation and will (after some tests and code cleanups) publish a fork with adapted “my_custom” code in Github. Feel free to adapt this to your project.

Thanks again for your work !