JuliusFruitfly
JuliusFruitfly
Andrew, I think this problem is fixed in MQTT 3.1.1. The CONNACK has a 'session present' flag which is only set if you have connected to a valid, pre-existing session...
Thanks for getting back to me so quickly. I wasn't clear in my first message - the crash isn't on (or soon after?) every setConfiguration but does occur every few...
Crash probably not directly related to setConfiguration, so closing pending better analysis. Thanks for your help
I'm reopening this issue as I have more context. (Note: now on 2.5.3) In summary: Owntracks seems to disconnect MQTT on a config update, then exits on a second update...
I have modified my app to notify me of a disconnect after a config update. If this works I'll send the log. Usually exits every few days.
The MQTT disconnect maybe part of the cause of the owntracks 'exit' , but it is not a bug of itself. The disconnect is generated by the MQTT server or...
I've been trying to find the trigger for this problem for the last few weeks without progress so far. All I can say for sure is that Owntracks will exit...
Happened again, different stacktrace (attached). [owntracks-log OOM 0210.txt](https://github.com/user-attachments/files/17230688/owntracks-log.OOM.0210.txt)