-
Notifications
You must be signed in to change notification settings - Fork 676
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
1.3 Testing Punchlist #1590
Comments
Testing on 1.3.29.7afc149, with tlora-v2-1-1.6 Configuring from command line with meshtastic: meshtastic --set wifi.ap_mode false $ meshtastic --set wifi.ssid "Localnet" $ meshtastic --set wifi.password SecretPass47 There are several more, very similar to this. Attempting to configure from the IOS app crashes the IOS app as well. |
the right command for wifi password is set wifi.psk "password" |
When you see the localconfig errors the command is wrong Aborting due to: 'LocalConfig' object has no attribute |
Only Config Sections and Module Config are working for setting in my testing, I would not expect any of the convenience methods that are setting things to work. |
I think there is a case for adding an enabled Boolean property to the wifi config. |
Ok, thanks - I was using https://meshtastic.org/docs/settings/config/wifi as my reference. |
Thanks! Fixed meshtastic/meshtastic#386 |
Configuring via the web interface (via wifi) fails when attempting to save changes in the User configuration panel. Changes are rejected with a status message "hwModel must be a valid enum value" in red by the (unchangeable) Hardware field. In my case, the field shows TLORA_V2_1_1p6 |
This is now fixed |
In my testing on 1.3.44 both --sendping and --reply are already working.
|
Checked off! :-) |
This issue has been mentioned on Meshtastic. There might be relevant details there: |
Closing this list and making issues for the remaining 4 items |
Config Sections
lora.region does not seem to be saving properly to esp32 devices.LoRa Config now causes a reboot after saving and is working much more consistently. Advanced settings still need testing.Module Config
Required Configuration Reboots
Test inconsistencies in reboots being required when changing settings and determine the appropriate action for each Config Section, Module Config and User
New Features / Bug Fixes / Broken Features
Load Testing
With range test and telemetry working nicely in 1.3, if you want to create a lot of mesh activity with any device you can turn up the telemetry updates to 15 seconds and use the range test from an ESP32 to create messages. This is a much more reliable way to test and revert then messing with position features.
Telemetry Configuration
Range Test Configuration
The text was updated successfully, but these errors were encountered: