processing a published valued on a subscribed topic is currently running in a task that is not the task executing the main loop(). that's because the espMqttClient(Secure) was constructed without arguments, which selects the constructor with two arguments priority and core, both of which have default values. that constructor selects espMqttClientTypes::UseInternalTask::YES, causing a task to be created in which context the MQTT client loop is executed. MQTT subscribers assume they are running in the same context as the main loop(). most code assumes exactly that. as the scheduler is preemptive and very little (none at all?) code is interlocked, we have to make sure to meet the programmer's expectations. this changeset calls the MQTT client loop in the context of the main loop() and enforces the use of espMqttClientTypes::UseInternalTask::NO. |
||
|---|---|---|
| .. | ||
| Battery.h | ||
| Configuration.h | ||
| Datastore.h | ||
| defaults.h | ||
| Display_Graphic.h | ||
| helper.h | ||
| HttpPowerMeter.h | ||
| Huawei_can.h | ||
| InverterSettings.h | ||
| Led_Single.h | ||
| MessageOutput.h | ||
| MqttHandleDtu.h | ||
| MqttHandleHass.h | ||
| MqttHandleHuawei.h | ||
| MqttHandleInverter.h | ||
| MqttHandleInverterTotal.h | ||
| MqttHandlePowerLimiter.h | ||
| MqttHandlePylontechHass.h | ||
| MqttHandleVedirect.h | ||
| MqttHandleVedirectHass.h | ||
| MqttSettings.h | ||
| NetworkSettings.h | ||
| NtpSettings.h | ||
| PinMapping.h | ||
| PowerLimiter.h | ||
| PowerMeter.h | ||
| PylontechCanReceiver.h | ||
| README | ||
| SunPosition.h | ||
| Utils.h | ||
| WebApi_battery.h | ||
| WebApi_config.h | ||
| WebApi_device.h | ||
| WebApi_devinfo.h | ||
| WebApi_dtu.h | ||
| WebApi_errors.h | ||
| WebApi_eventlog.h | ||
| WebApi_firmware.h | ||
| WebApi_Huawei.h | ||
| WebApi_inverter.h | ||
| WebApi_limit.h | ||
| WebApi_maintenance.h | ||
| WebApi_mqtt.h | ||
| WebApi_network.h | ||
| WebApi_ntp.h | ||
| WebApi_power.h | ||
| WebApi_powerlimiter.h | ||
| WebApi_powermeter.h | ||
| WebApi_prometheus.h | ||
| WebApi_Pylontech.h | ||
| WebApi_security.h | ||
| WebApi_sysstatus.h | ||
| WebApi_vedirect.h | ||
| WebApi_webapp.h | ||
| WebApi_ws_console.h | ||
| WebApi_ws_Huawei.h | ||
| WebApi_ws_live.h | ||
| WebApi_ws_Pylontech.h | ||
| WebApi_ws_vedirect_live.h | ||
| WebApi.h | ||
This directory is intended for project header files.
A header file is a file containing C declarations and macro definitions
to be shared between several project source files. You request the use of a
header file in your project source file (C, C++, etc) located in `src` folder
by including it, with the C preprocessing directive `#include'.
```src/main.c
#include "header.h"
int main (void)
{
...
}
```
Including a header file produces the same results as copying the header file
into each source file that needs it. Such copying would be time-consuming
and error-prone. With a header file, the related declarations appear
in only one place. If they need to be changed, they can be changed in one
place, and programs that include the header file will automatically use the
new version when next recompiled. The header file eliminates the labor of
finding and changing all the copies as well as the risk that a failure to
find one copy will result in inconsistencies within a program.
In C, the usual convention is to give header files names that end with `.h'.
It is most portable to use only letters, digits, dashes, and underscores in
header file names, and at most one dot.
Read more about using header files in official GCC documentation:
* Include Syntax
* Include Operation
* Once-Only Headers
* Computed Includes
https://gcc.gnu.org/onlinedocs/cpp/Header-Files.html