A number of people have asked for this feature.
It is coming to the android in the next weekish, but you can do it now with the python tool . Here’s an example:
You can also use this tool to set any of the device parameters which are stored in persistent storage. For instance, here’s how to set the device to keep the bluetooth link alive for eight hours (any usage of the bluetooth protcol from your phone will reset this timer)
pip3 install --upgrade meshtastic
meshtastic --setpref wait_bluetooth_secs 28800
Connected to radio...
Setting preference wait_bluetooth_secs to 28800
Writing modified preferences to device...
2 Likes
btw - I (just noticed) apparently lied
bigbug
August 28, 2020, 11:45am
3
I tried to change the preferences (wait_bluetooth_secs, screen_on_secs and position_broadcast_secs) using this method, but they do not change. Any ideas?
~# meshtastic --device /dev/ttyS7 --setpref position_broadcast_secs 890
~# meshtastic --device /dev/ttyS7 --info
preferences {
1 Like
claesg
August 28, 2020, 1:23pm
4
Hi,
~$ meshtastic --setpref position_broadcast_secs 890
Trigger powerFSM 9
Connected to radio
Setting preference position_broadcast_secs to 890
Writing modified preferences to device
~$ meshtastic --info
Trigger powerFSM 9
Connected to radio
my_node_num: 3220213000
num_channels: 10
region: "1.0-EU865"
hw_model: "tlora-v1"
firmware_version: "0.9.3"
packet_id_bits: 32
current_packet_id: 383638496
node_num_bits: 32
message_timeout_msec: 300000
min_app_version: 172
preferences {
position_broadcast_secs: 890
send_owner_interval: 4
wait_bluetooth_secs: 120
screen_on_secs: 300
phone_timeout_secs: 900
phone_sds_timeout_sec: 7200
mesh_sds_timeout_secs: 7200
sds_secs: 31536000
ls_secs: 3600
}
channel_settings {
modem_config: Bw125Cr48Sf4096
psk: "\324\361\273: )\007Y\360\274\377\253\317Ni\277"
name: "Default"
}
Nodes in mesh:
{'num': 3220213000, 'user': {'id': '!3c71bff08d08', 'longName': 'Unknown 8d08', 'shortName': '?08', 'macaddr': 'PHG/8I0I'}, 'position': {'batteryLevel': 80, 'time': 1598602175}}
{'num': 681022624, 'user': {'id': '!246f289794a0', 'longName': 'Claes', 'shortName': 'C', 'macaddr': 'JG8ol5Sg'}, 'position': {'altitude': 87, 'batteryLevel': 100, 'latitudeI': 594479827, 'longitudeI': 134290121, 'time': 1598602087, 'latitude': 59.4479827, 'longitude': 13.4290121}, 'snr': 9.5}
1 Like
bigbug
August 31, 2020, 8:54am
5
I tried updating python meshtastic and device to 0.9.3, but still not working…
claesg
August 31, 2020, 9:21am
6
Lets see if @geeksville has an idea to what could be wrong in your case.
Hmm. Can you post what your device shows when running the two commands @claesg used?
bigbug
September 1, 2020, 7:53am
8
~# meshtastic --device /dev/ttyS7 --setpref position_broadcast_secs 890
~# meshtastic --device /dev/ttyS7 --info
preferences {
Nodes in mesh:
bigbug
September 1, 2020, 1:00pm
9
Im using Python 3.6.9 if that could be related?
claesg
September 1, 2020, 1:58pm
10
I am running Python 3.8.2
what is the output frompip3 install --upgrade meshtastic
I get
bigbug
September 1, 2020, 3:43pm
11
~# pip3 install --upgrade meshtastic
about this coming next week. It got pushed out of the 1.0 bucket. But ‘someday’ after 1.0 is out there will be a GUI to either do this in the android app or we will have a cross platform app with this feature.