[Feature Request]: Always allow Client API access when on Linux Native platform

[turnrye]

Platform

Linux Native

Description

For nodes running on Linux Native (meshtasticd), allow a runtime configuration to ensure that client API access is always available. I believe this primarily means disabling power saving features regardless of the device's role.

Why?

Linux Native nodes by definition have higher computing capabilities, and often higher power needs. This means more often compared to other platforms, Linux Native nodes would be expected to have mains power and not benefit from power saving features. Compounding to that, due to their additional computing capabilities, often Meshtastic users will host unattended applications that rely on the Client API. This also makes them good candidates as the platforms of choice for routers where there is existing infrastructure, such as out of band management and grid power.

Two examples of applications that leverage the client API on linux devices, which frequently may coexist on Linux Native platform devices, are:

• General-use bots like https://github.com/SpudGunMan/meshing-around
• BBS systems to extend Meshtastic's native store-and-forward capabilities, like https://github.com/TheCommsChannel/TC2-BBS-mesh

These applications also benefit from having the broadest user reach, which is best achieved by having them run on the main node itself.

In these scenarios too, these high powered, centrally located, well managed nodes are also candidates to leverage the ROUTER role. But today, for various reasons, when leveraging the router role the client API is unreliable. This is noted in some client applications as a limitation.

What workarounds exist?

Just use router_late role instead

This then precludes other nodes from leveraging that role for its intended purpose.

This also means in instances where there are some routers that are Linux Native and some that aren't, the Linux Native devices would be negatively impacted (and potentially in turn creating more hidden node problems) by having to unfairly move to router_late role.

Just use a second device

This increases capital and operating expense. And depending on how you evaluate the service you offer, this may impact your reslliency.

This increases channel utilization. This is particularly problematic for sites that are candidates for routers.

Appendix

• This issue was created by request of @vidplace7 in this discord thread.