I’m having a strange problem when using the android app on my samsung S22 connected to a v3 model t-beam using bluetooth and running the 2.24 (latest) firmware. I’ve kept the default LongFast channel 0 and added an admin channel 1 and a neighborhood channel 2. When i try to send a message on channel 2, my t-beam reboots. I can send messages on other channels just fine, and if i enable wifi and go that route it works also, its only this one channel and only from bluetooth on my phone. (bluetooth from a spare android tablet works fine). I dont even know where to begin to troubleshoot this. any ideas?
update: disabling MQTT uplink for that channel seems to stop the rebooting… (note: i have a raspberry pi mqtt server) misconfig or bug?
update: it seems to be related to the ‘proxy to client enabled’ function, if i put my t-beam on wifi and use it that way it works fine. but when using bluetooth and proxying through my phone it causes the crash on message send
well it looks like setting ‘JSON output enabled’ to off fixed the problem.