Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Lora T3S3 sleeps immediately once router mode is enabled. #3501

Closed
shleeable opened this issue Mar 27, 2024 · 3 comments
Closed

[Bug]: Lora T3S3 sleeps immediately once router mode is enabled. #3501

shleeable opened this issue Mar 27, 2024 · 3 comments
Labels
bug Something isn't working expected behavior This behavior is expected.

Comments

@shleeable
Copy link

Category

Hardware Compatibility

Hardware

T-Beam S3

Firmware Version

2.2.24

Description

Detail: I've added a battery and plugged in USB to a dedicated powerbrick to power the router

Replication: On a fresh install of my two new T3S3s. I've configured all of the setting to be correct using the web via serial and iOS via bluetooth.

Once I set the unit from client mode to router mode. It "bricks" itself by sleeping immediately after booting.
This drops the bluetooth and usb serial connection.... clicking a button triggers the resuming screen, and it boots, then immediately sleeps again.

I've replicated this multiple times and it is the client to router step which seems to trigger bad defaults regarding power/sleeping.

This is a router, I never want it to sleep while it has any power via battery/USB.

Relevant log output

No response

@shleeable shleeable added the bug Something isn't working label Mar 27, 2024
@Holyszewski
Copy link

This is the correct router behavior in my opinion and in accordance with https://meshtastic.org/docs/configuration/radio/device/ .
In the ROUTER role, only the CPU is asleep, the LoRa transceiver is active and when a message arrives the device wakes up, resolves and broadcasts what is needed and goes back to sleep.

@thebentern thebentern added the expected behavior This behavior is expected. label Mar 28, 2024
@thebentern
Copy link
Contributor

If you don't want the device to sleep, I recommend using the ROUTER_CLIENT role.

@shleeable
Copy link
Author

If this is expected behaviour, why doesn't it match the behaviour from other devices like the RAK?

That's running router mode without the autosleep.. How can I meant to administrator a node if it auto sleeps?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working expected behavior This behavior is expected.
Projects
None yet
Development

No branches or pull requests

3 participants