I ll follow up here on 3 and say that in

[still aurora]

I performed the test with the 3.2 firmware

3.2 --> very unstable - seems to crash when receiving lots of commands - becomes unavailable at that point for some time

3.5.10 --> unstable - becomes unavailable at regular intervals but not so much as the 3.2 version. Also responses to commands seem to be snappier.

So in my testing experience it seems to be improved but not solved.

[jagged timber]

That's interesting. When it crashes what's the behavior in the logs?

Maybe I'm just not recognizing a particular error as crashing