re: preferences not saving in 1.1.8
Hmm - alas, Iām having a hard time reproing this behavior here. To anyone who saw this issue in 1.1.8 (@DintheNorth) would you mind adding a comment here based on a couple of questions I listed:
Thanks for the report - clearly something is off.
Hi, I added to the bug report. I was able to get the preferences saved to one tbeam, but no luck with my other unit. It is hard to reproduce.
Thanks.
Could it be a function of the upgrade path? Maybe try go back to 1.0.0 through USB, then back to 1.1.8 though USB.
I tried going back to f/w 1.0.0 and the preferences save successfully. Flashing to 1.1.8 and the preferences donāt save. (@geeksville)
Also, there are a few more default preferences in 1.0.0. Only 2 in 1.1.8. Not sure if that is normal.
f/w 1.0.0
preferences {
position_broadcast_secs: 900
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
}
f/w 1.1.8
preferences {
ls_secs: 300
region: US
}
Just hit the āReport Bugā button - assume its this thread to notify you in? Otherwise please advise and Iāll take action (create a thread??)
1.1.8 and sat in mesh for 3 days - phone leaving location occasionally, yet re-connecting to BT automatically each time.
Then 08:00 this morning, no more bluetooth comms. āDevice Sleepingā - Radio shows connection to other node on OLED. Sent message through app and cloud with up arrow for past 30 mins or so. Pushed middle button on Tbeam and no BT response with phone.
EDIT: Just force stopped app and re-opened and it now sees radio - pressed report bug again. Hope this helps?
Not sure if itāll helps but I ran the same commands on my Tbeam and ill upload the what I got. I ran --info again after rebooting I donāt have 2 tbeams but Iāll try to run them again on my other boards and see if i can get the same thing.
**python@ubuntu:~$** sudo chmod 666 /dev/ttyUSB0
**python@ubuntu:~$** meshtastic --set position_broadcast_secs 60
Node changed: {'num': 2988082472, 'user': {'id': '!ac67b21a8528', 'longName': 'Unknown 8528', 'shortName': '?28', 'macaddr': 'rGeyGoUo'}, 'position': {'altitude': 346, 'latitudeI': ******1982, 'longitudeI': -******1952, 'time': 1605550667, 'latitude': ***71982, 'longitude': -***91952}}
Node changed: {'num': 3221004200, 'user': {'id': '!3c71bffc9fa8', 'longName': 'Dji Heltec', 'shortName': 'DH', 'macaddr': 'PHG//J+o'}, 'snr': 8.5}
Node changed: {'num': 2443305892, 'position': {'altitude': 366, 'batteryLevel': 73, 'latitudeI': ******1783, 'longitudeI': -******4010, 'time': 1605550756, 'latitude': ***7178299999996, 'longitude': -***9401}, 'snr': 11.25}
Connected to radio
Setting position_broadcast_secs to 60
Writing modified preferences to device
**python@ubuntu:~$** meshtastic --set wait_bluetooth_secs 28800
Node changed: {'num': 2988082472, 'user': {'id': '!ac67b21a8528', 'longName': 'Unknown 8528', 'shortName': '?28', 'macaddr': 'rGeyGoUo'}, 'position': {'altitude': 346, 'latitudeI': ******1982, 'longitudeI': -******1952, 'time': 1605550667, 'latitude': **.8471982, 'longitude': -**3691952}}
Node changed: {'num': 3221004200, 'user': {'id': '!3c71bffc9fa8', 'longName': 'Dji Heltec', 'shortName': 'DH', 'macaddr': 'PHG//J+o'}, 'snr': 8.5}
Node changed: {'num': 2443305892, 'position': {'altitude': 366, 'batteryLevel': 73, 'latitudeI': ******1783, 'longitudeI': -******4010, 'time': 1605550756, 'latitude': ***47178299999996, 'longitude': -***69401}, 'snr': 11.25}
Connected to radio
Setting wait_bluetooth_secs to 28800
Writing modified preferences to device
**python@ubuntu:~$** meshtastic --info
Node changed: {'num': 2988082472, 'user': {'id': '!ac67b21a8528', 'longName': 'Unknown 8528', 'shortName': '?28', 'macaddr': 'rGeyGoUo'}, 'position': {'time': 1605550787}}
Node changed: {'num': 3221004200, 'user': {'id': '!3c71bffc9fa8', 'longName': 'Dji Heltec', 'shortName': 'DH', 'macaddr': 'PHG//J+o'}, 'snr': 8.5}
Node changed: {'num': 2443305892, 'position': {'altitude': 366, 'batteryLevel': 73, 'latitudeI': ******1783, 'longitudeI': -******4010, 'time': 1605550756, 'latitude': ***178299999996, 'longitude': -***9401}, 'snr': 11.25}
Connected to radio
my_node_num: 2988082472
has_gps: true
num_channels: 13
region: "1.0-US"
hw_model: "tbeam"
firmware_version: "1.1.8"
packet_id_bits: 32
current_packet_id: 217677114
node_num_bits: 32
message_timeout_msec: 300000
min_app_version: 172
preferences {
position_broadcast_secs: 60
wait_bluetooth_secs: 28800
ls_secs: 300
region: US
}
channel_settings {
modem_config: Bw125Cr48Sf4096
psk: "\324\361\273: )\007Y\360\274\377\253\317Ni\277"
name: "Default"
}
Channel URL https://www.meshtastic.org/c/#GAMiENTxuzogKQdZ8Lz_q89Oab8qB0RlZmF1bHQ=
Nodes in mesh:
{'num': 2988082472, 'user': {'id': '!ac67b21a8528', 'longName': 'Unknown 8528', 'shortName': '?28', 'macaddr': 'rGeyGoUo'}, 'position': {'time': 1605550787}}
{'num': 3221004200, 'user': {'id': '!3c71bffc9fa8', 'longName': 'Dji Heltec', 'shortName': 'DH', 'macaddr': 'PHG//J+o'}, 'snr': 8.5}
**python@ubuntu:~$** sudo chmod 666 /dev/ttyUSB0
**python@ubuntu:~$** meshtastic --info
Node changed: {'num': 2988082472, 'user': {'id': '!ac67b21a8528', 'longName': 'Unknown 8528', 'shortName': '?28', 'macaddr': 'rGeyGoUo'}, 'position': {'altitude': 351, 'latitudeI': ******2287, 'longitudeI': -******1590, 'time': 1605551102, 'latitude': **.***28699999995, 'longitude': -****69159}}
Node changed: {'num': 3221004200, 'user': {'id': '!3c71bffc9fa8', 'longName': 'Dji Heltec', 'shortName': 'DH', 'macaddr': 'PHG//J+o'}, 'snr': 8.5}
Node changed: {'num': 2443305892, 'position': {'altitude': 366, 'batteryLevel': 73, 'latitudeI': ******1783, 'longitudeI': -******4010, 'time': 1605550756, 'latitude': **.***178299999996, 'longitude': -**.***9401}, 'snr': 11.25}
Connected to radio
my_node_num: 2988082472
has_gps: true
num_channels: 13
region: "1.0-US"
hw_model: "tbeam"
firmware_version: "1.1.8"
packet_id_bits: 32
current_packet_id: 2021394803
node_num_bits: 32
message_timeout_msec: 300000
min_app_version: 172
preferences {
position_broadcast_secs: 60
wait_bluetooth_secs: 28800
ls_secs: 300
region: US
}
channel_settings {
modem_config: Bw125Cr48Sf4096
psk: "\324\361\273: )\007Y\360\274\377\253\317Ni\277"
name: "Default"
}
Channel URL https://www.meshtastic.org/c/#GAMiENTxuzogKQdZ8Lz_q89Oab8qB0RlZmF1bHQ=
Nodes in mesh:
{'num': 2988082472, 'user': {'id': '!ac67b21a8528', 'longName': 'Unknown 8528', 'shortName': '?28', 'macaddr': 'rGeyGoUo'}, 'position': {'altitude': 351, 'latitudeI': ******2287, 'longitudeI': -******1590, 'time': 1605551102, 'latitude': ***28699999995, 'longitude': -****69159}}
{'num': 3221004200, 'user': {'id': '!3c71bffc9fa8', 'longName': 'Dji Heltec', 'shortName': 'DH', 'macaddr': 'PHG//J+o'}, 'snr': 8.5}Looks like it works correctly for you.
Yeah, But when I get home tonight ill try my other boards and see if I can get one of them to do what yours did. just out of curiosity is there any differenceās between your two Tbeams? IE. do they both have screens, same type of antenna connector? donāt know it its relevant but mine doesnāt have a screen installed yet and uses the IPEX connector.
My two tbeams are the same model. The one that saved correctly has a screen. The one that isnāt saving does not have a screen.
I am not confident that the one that saved is ok. It just happened to save and I just stopped changing it once it worked.
Iām having trouble with 1.1.8
My older TBeam1 works OK on it, but the newer TBeam1 (uBlox M*N and ipex) doesnāt flash its red GPS led, only a steady dim glow, and they donāt report their position
Even when Bluetooth connected to a new TBeam1 (896c), which is seeing ~16 sats and showing its own LatLong, but the app map shows only the other two (older TBeam and a TLora2), but not the new one.
Is anyone else having trouble like this?
I sent up a bug report around 23:00UTC.
The same āBT hungā scenario happened again. I turned BT off and the app asked to turn it back on - now all ok. Pressed Report Bug button
I have 1 Heltec v2 and 2 TBeam v1.0 -433. firmware 1.1.8
Very bad reception of gps. Messages are unstable. One device accepts the other no, then everything is fine, then vice versa. In early firmware versions, roughly 1.1.4 was much better.
upd: It seems to me that the developers are guided by 900 megahertz boards and some new boards. Maybe we need to finish the old before developing new equipment. Tbeam433 megahertz do not have time to communicate (lower transmission speed)my guess, I donāt know the reasons. Also, earlier there were Bluetooth errors on heltec, and now on tbeam.
Hi I have thought about how all the versions have worked versus my boards.
Unfortunately with lockdown although I have loaded all the software versions I have never tested them in a real life situation! I have two types of board - all tbeams T22_V1.1 20191212 (M8N and 6M) and T22_V1.0 20190612 (6M). I only have an android running 7.0 but this works very well with the app version 1.1.8.
For me the best version has been 1.1.0 - this did everything I needed - easy BT connection, good texting, nicely located on mapbox, fast to gps fix and then a constant gps fix. I have not checked battery drain but sitting at home this might not be a good test.
I do not stretch the devices too much - so I feel that maybe I am missing out on all the advantages and work that went into 1.1.8!
Just hit the report button on a Samsung G S10 - last seen times on the node page are updating as between 4 - 7 minutes in advance of system time (on the phone)
For instance, just updated and one node says last seen 12:08 - however, the time is actually 12:02.
I just upgraded two mesh devices and tablets from 1.1.5 to 1.1.8 but now the Android app is quitting on both tablets the moment I open it. The BLE firmware update worked OK. Everything worked for a while, Iāve not been able to get back to working despite reboots.
Mesh devices are LILYGO TTGO 915MHz SX1276 ESP32 LoRa
ESP32-D0WDQ6 (revision 1)
Tablets are Samsung Active Tab2 running Android 9.0 and Nvidia Shield running Android 7.0
I used the Android bug report mechanism. LMK if I can help with anything else.
Hi I did solve this problem. It was an issue with the tiny radio antenna socket on this board. It looked like I had correctly positioned the plug in the socket but apparently not so. I need to buy some more adaptors - does anyone know where to buy these? Thanks.
You can buy them from Amazon or other shops you like. Just search for āipex sma adaptorā and you get plenty results. Hopefully this was your question 
This thread has become super long, so Iām starting a new one to take its placeā¦ If you can help with alpha testing please join us there!
https://meshtastic.discourse.group/t/want-to-help-alpha-test-this-build-1-1-20/