puterboy
puterboy
OK - I was able to fix the problem of corrupted discovery data by **reverting** one of the recent changes to `ZgatewayRTL_433.ino` ``` //RFrtl_433_ESPdata["origin"] = (char*)topic.c_str(); //handleJsonEnqueue(RFrtl_433_ESPdata); pub(topic.c_str(), RFrtl_433_ESPdata); ```...
**One other thing that may be concerning (but seems to work ok now) is the newly added lines:** ``` char deviceKeyParameter[25]; memcpy(deviceKeyParameter, &pdevice->uniqueId[strlen(pdevice->uniqueId) - strlen(parameters[i][0])], strlen(parameters[i][0])); deviceKeyParameter[strlen(parameters[i][0])] = '\0'; Log.trace(F("deviceKeyParameter:...
The above PR fixes the second of the 2 issues initially listed in this bug report. However, I still can't figure out why the `handleJsonEnqueue` method causes sporadic corruption in...
Fixed as per https://github.com/1technophile/OpenMQTTGateway/pull/2034 and https://github.com/1technophile/OpenMQTTGateway/pull/2014
Is that spam????
Fixed with: https://github.com/1technophile/OpenMQTTGateway/pull/2037
Perhaps instabilities were caused by the memory corruption bug in jsonQueue that is now fixed?
Would still be good to get a way to get more verbose logging via MQTT. For example, this would be important for some of my decoder debugging since the signals...
Please keep open as this is valuable for debugging.
Please keep open