Ian Hubbertz

Ok, as the homie-device shall reread its own values, its up to the device to set retained flag and the QoS level.

No. An additional "one-time" subscription for the property-topic without set. I use my thermostat for an example: homie/wz_thermo/Thermostat/$properties SetTemp:settable,Mode:settable Both Properties of the "ThermostatNode" has been set by my controller...

The feature to reread values from sustained message is meant for a restart of the Homie device - not a restart of the MQTT broker. In detail: @Nzbuu Thats exactly...

It seems to be related to the initialization order... If I call `setDefaultValue(false)` later (e.g. in `setup()` it works as expected. It seems that the constuctor of my `TouchCtrl::printSerial` is...

Not really, just more confusion.... The stack overflow question/answer did not help, as I was already aware of the problem in general and its potentional solutions. However, playing around with...

Looks nice, but why do you wrap around HomieNode instead of deriving from it? What is the benefit?

I don't use config mode, so I did not tested it yet. What happesn, if you upload a `homie/config.json` to SPIFFS?

Oh.. doesn't look good. Maybe a heap corruption?