T-beam Supreme seems to go to sleep when set to be REPEATER, and so Bluetooth contact is lost and can only be regained by pressing a button on the node over and over. Then I set it back to CLIENT. (I was trying to set up store and forward, and was failing, so was testing setting it to ROUTER to see if that fixed the problem, which it did not I think.) Anyone get this behaviour too? The firmwear is 2.5
Update: going back to firmwear 2.4 solved the problem I was testing to solve. 2.5 will not let you use a secondary channel where the PSK key is default AQ==, which was my case,
then, with node as client store & forward works fine.
This is intended behavior. ROUTER mode nodes should be placed in extremely high-profile locations. As such, they are generally not trivial to access. So why keep the bluetooth radio (and CPU) on if it’s not going to be used?
If your T-BEAM is not being installed at the top of a mountain, you should NOT be using ROUTER mode. You should be using client. Even if it’s on your roof. Client will still repeat packets it receives! It just is lower priority compared to ROUTER nodes that may be in prominent locations. You should leave the the ROUTER mode available to those nodes to help your messages travel farther. Because of how the mesh operates, ROUTER mode nodes that are not in absolutely prime locations are detrimental to the mesh’s performance.
This behavior was implemented to save battery power. However I think we should add a tool-tip to the app when enabling it to warn the user what they’re doing.
If this doesn’t make sense, watch this video: https://www.youtube.com/watch?v=htjwtnjQkkE
It explains the importance of your node’s mode very well.
1 Like