Then tried WebUI again. Contacts and channels were not deleted that time.
Then did this test. After some time, something has crashed: Device was not ping-able anymore. After restarting WiFi and reconnecting to WebUI, contacts and channels were gone once again. And reappeared shortly after.
Which device are you using
LilyGO T-Deck Plus
Which Firmware are you using
v0.9.12.3
**Describe the bug**
After fiddling around with #285 I finally could enable the WebUI.
Upon connecting to it, I see _no_ public channels except of `Public`. But on device, I had several channels, and _not_ `Public`.
Also, I see only one contact, although on device I had many contacts.
Now, going back to device, I see that all my channels and contacts are gone.
Could this be related to #271?
---
I restored (seemingly successfully) from backup.
Then tried WebUI again. Contacts and channels were not deleted that time.
Then did [this test](https://github.com/dabeani/meshcoreterm/issues/201#issuecomment-4605835158). After some time, something has crashed: Device was not ping-able anymore. After restarting WiFi and reconnecting to WebUI, contacts and channels were gone once again. And reappeared shortly after.
**Which device are you using**
LilyGO T-Deck Plus
**Which Firmware are you using**
v0.9.12.3
<!-- github-sync-id:4573745997 -->
Maybe it's not directly the WebUI but some other stuff going on, just incidentally beeing triggered by WebUI? https://github.com/dabeani/meshcoreterm/issues/306#issuecomment-4614479661.
<!-- github-comment-id:4614510305 -->
The severe version here (contacts actually gone, needed a restore) matches #271/#332/#333, which had two confirmed root causes fixed in v0.9.14 (an NVS key-length bug, and repeater login rewriting the whole contact store). The milder version you saw later — empty, then reappearing after WiFi/WebUI reconnect — looks like a display race at boot (WebUI can answer before contacts finish loading from SD) rather than real data loss; nothing writes an empty contact list to disk just from that. The actual crash during the #201 stress test is the open thread — if you can reproduce it, a serial log from the point it goes unresponsive would let us root-cause that specifically.
The severe version here (contacts actually gone, needed a restore) matches #271/#332/#333, which had two confirmed root causes fixed in v0.9.14 (an NVS key-length bug, and repeater login rewriting the whole contact store). The milder version you saw later — empty, then reappearing after WiFi/WebUI reconnect — looks like a display race at boot (WebUI can answer before contacts finish loading from SD) rather than real data loss; nothing writes an empty contact list to disk just from that. The actual crash during the #201 stress test is the open thread — if you can reproduce it, a serial log from the point it goes unresponsive would let us root-cause that specifically.
<!-- github-comment-id:5919595641 -->
I won't use the WebUI anymore due to my bad experiences with it & it was only for playing around since I want to use the device standalone. So I do not test if this (#286) is resolved. I just assume "yes".
I also won't do a test for #201 for the same reason.
So, closing.
I won't use the WebUI anymore due to my bad experiences with it & it was only for playing around since I want to use the device standalone. So I do not test if this (#286) is resolved. I just assume "yes".
I also won't do a test for #201 for the same reason.
So, closing.
<!-- github-comment-id:6057799667 -->
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.
Describe the bug
After fiddling around with #285 I finally could enable the WebUI.
Upon connecting to it, I see no public channels except of
Public. But on device, I had several channels, and notPublic.Also, I see only one contact, although on device I had many contacts.
Now, going back to device, I see that all my channels and contacts are gone.
Could this be related to #271?
I restored (seemingly successfully) from backup.
Then tried WebUI again. Contacts and channels were not deleted that time.
Then did this test. After some time, something has crashed: Device was not ping-able anymore. After restarting WiFi and reconnecting to WebUI, contacts and channels were gone once again. And reappeared shortly after.
Which device are you using
LilyGO T-Deck Plus
Which Firmware are you using
v0.9.12.3
Maybe it's not directly the WebUI but some other stuff going on, just incidentally beeing triggered by WebUI? https://github.com/dabeani/meshcoreterm/issues/306#issuecomment-4614479661.
The severe version here (contacts actually gone, needed a restore) matches #271/#332/#333, which had two confirmed root causes fixed in v0.9.14 (an NVS key-length bug, and repeater login rewriting the whole contact store). The milder version you saw later — empty, then reappearing after WiFi/WebUI reconnect — looks like a display race at boot (WebUI can answer before contacts finish loading from SD) rather than real data loss; nothing writes an empty contact list to disk just from that. The actual crash during the #201 stress test is the open thread — if you can reproduce it, a serial log from the point it goes unresponsive would let us root-cause that specifically.
I won't use the WebUI anymore due to my bad experiences with it & it was only for playing around since I want to use the device standalone. So I do not test if this (#286) is resolved. I just assume "yes".
I also won't do a test for #201 for the same reason.
So, closing.