Check name via official Meshtastic CLI client with --info flag
Name is still what it was before, does not reflect change made in Contact UI
Device is Heltec V3. UI is otherwise working. Haven't tried much else in Settings to see if this is limited to longName/shortName/User Settings/etc.
Also tried rebooting through the settings menu after saving changes. Device successfully rebooted as commanded, but longName / shortName were not set.
Also tried re-flashing device doing "Full Erase and Install" and re-loading my previous config via official Meshtastic CLI. Issue still occurs.
* Settings > User Settings
* Set longName and shortName
* Save Changes
* Check name via official Meshtastic CLI client with --info flag
* Name is still what it was before, does not reflect change made in Contact UI
Device is Heltec V3. UI is otherwise working. Haven't tried much else in Settings to see if this is limited to longName/shortName/User Settings/etc.
Also tried rebooting through the settings menu after saving changes. Device successfully rebooted as commanded, but longName / shortName were not set.
Also tried re-flashing device doing "Full Erase and Install" and re-loading my previous config via official Meshtastic CLI. Issue still occurs.
<!-- github-sync-id:2809829702 -->
Make sure you're using the latest master, i broke and then fixed saving settings yesterday
I assume you're hitting 'Save Changes' after entering a value.
Tested on my end with a V3 with success.
- Make sure you're using the latest master, i broke and then fixed saving settings yesterday
- I assume you're hitting 'Save Changes' after entering a value.
<!-- github-comment-id:2612952310 -->
Pulled up to tips (92790ddca6) - still having problems.
Checked client.log - every time I try to save changes here, I see:
2025-01-24 10:53:33,297 - ERROR - Error saving changes: 'str' object cannot be interpreted as an integer
2025-01-24 10:53:33,298 - INFO - Changes Saved
Are we perhaps assuming that shortName should be interpretable as an int? Or maybe it's some other setting on my device that's tripping it up.
Pulled up to tips (92790ddca64b493328bb4e2c959fa02009b8f3c4) - still having problems.
Checked client.log - every time I try to save changes here, I see:
> 2025-01-24 10:53:33,297 - ERROR - Error saving changes: 'str' object cannot be interpreted as an integer
> 2025-01-24 10:53:33,298 - INFO - Changes Saved
Are we perhaps assuming that shortName should be interpretable as an int? Or maybe it's some other setting on my device that's tripping it up.
<!-- github-comment-id:2612994154 -->
setting any one of long/short/licensed sets all three. A guess it's the is_licensed bool maybe expecting a 1 or 0 but getting "True" or "False". Odd thing is its working fine on my end. I'll try a reset on my node.
setting any one of long/short/licensed sets all three. A guess it's the is_licensed bool maybe expecting a 1 or 0 but getting "True" or "False". Odd thing is its working fine on my end. I'll try a reset on my node.
<!-- github-comment-id:2613036783 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Device is Heltec V3. UI is otherwise working. Haven't tried much else in Settings to see if this is limited to longName/shortName/User Settings/etc.
Also tried rebooting through the settings menu after saving changes. Device successfully rebooted as commanded, but longName / shortName were not set.
Also tried re-flashing device doing "Full Erase and Install" and re-loading my previous config via official Meshtastic CLI. Issue still occurs.
Tested on my end with a V3 with success.
Pulled up to tips (
92790ddca6) - still having problems.Checked client.log - every time I try to save changes here, I see:
Are we perhaps assuming that shortName should be interpretable as an int? Or maybe it's some other setting on my device that's tripping it up.
setting any one of long/short/licensed sets all three. A guess it's the is_licensed bool maybe expecting a 1 or 0 but getting "True" or "False". Odd thing is its working fine on my end. I'll try a reset on my node.
I'm able to reproduce now. I'll push a fix shortly.
Sort of a bandaid solution for now but should be fixed in
978e2942cb