Andrew King
Andrew King
Alright the valgrind docker is ready, I will test it too
This is my memory profile on release build Shame I can't replicate this
Not sure about the `BadClientId`, this is an upstream error message comming from `rumqttc`. I'm not enough of an expert on mqtt protocol to know what could cause a `BadClientId`....
With regards to the "Unable to parse Extension XML" this is an issue because I have had to swap the xml parser due to upstream changes. The newer parser is...
I don't suppose you can get a packet capture of the failing ExtensionXML parsing? I haven't seen extension XML fail for me yet and I'd like to know which field...
For the packet dump the proper way is to use wireshark... But I think I added an easier way into neolink by putting `debug = true` into the `[[cameras]]` table...
I'm quite busy tracking the memory leak atm, if you can make a PR for the clientID that would be good
Looks like there's a checkPos and checkValue that I need to add to the extension xml. Thanks for the info, I'll see about adding it soon.
I've added a random Uuid into the clientname perhaps this will be get your mqtt working. Test build is here https://github.com/QuantumEntangledAndy/neolink/actions/runs/8955580354 let me know if it dosen't help.
That is my plan. Don't want to break people scripts. Was just thinking of a bunch of sub topics. We actually already have the needed parts reverse engineered for this...