AcuarioCat
AcuarioCat
Digging a little deeper, it appears the string 'force' is the culprit. 'force' returns error 0, 'forc', 'forces', 'esp force' and 'xforces' all return non zero error (as expected). So...
Thanks for confirming. It was pure chance I found the bug when trying to solve something else. Yes it crashes as it doesn't see an error in an incomplete/incorrect json...
Great, thanks for the guidance.
Here is the log with a couple of reconnects, hope this helps! ``` 2021-12-07 16:08:47: Client xbcfmbew already connected, closing old connection. 2021-12-07 16:08:47: Socket error on client xbcfmbew, disconnecting....
yes, just added my credentials
Ah, maybe I have found something - using usernames rather than the default account seems to stop the disconnects..
It seems odd. I'm using CloudMQTT which is commercial so I would expect it to behave properly.
I was trying to build the server for testing. I can build the BK7231 firmware without problem.
If I had a working starting point then I would be happy to try but as there are files missing that appear to be fundamental, and they aren't in either...
See my post here: https://github.com/tuanpmt/esp_mqtt/issues/98