When I start RemoteTerm, I see a stream of dozens of messages like app.radio_sync - WARNING - Failed to remove contact 07b19c5c240c: {'reason': 'no_event_received'}. After many of those, it'll say something like app.radio_sync - INFO - Synced 174 contacts, removed 146 from radio.
Each of these takes a while, which results in startup time being measured in minutes instead of seconds. This blocks the radio initialization, so you're unable to send messages until it's done. Restarting the server causes it to try all of this again.
The node hardware is a LoRa V3 flashed yesterday with 1.14, connected over serial.
When I start RemoteTerm, I see a stream of dozens of messages like `app.radio_sync - WARNING - Failed to remove contact 07b19c5c240c: {'reason': 'no_event_received'}`. After many of those, it'll say something like `app.radio_sync - INFO - Synced 174 contacts, removed 146 from radio`.
Each of these takes a while, which results in startup time being measured in minutes instead of seconds. This blocks the radio initialization, so you're unable to send messages until it's done. Restarting the server causes it to try all of this again.
The node hardware is a LoRa V3 flashed yesterday with 1.14, connected over serial.
<!-- github-sync-id:4102943599 -->
Hmmm interesting. That's part of initial load where it empties out radio contacts in prep for the server managing them. That's odd you're having issues with what's a pretty fundamental radio operation. When you use the radio with another client, are you able to easily delete contacts? Are you paired over serial, bluetooth, or TCP? We're using the standard interface library to do our contact management (meshcore_py) so it would be really weird to have issues on mainline firmware that don't repro to other devices.
I assume by lorav3 you mean a Heltec wifi lora v3? I don't have any of those hanging around right now to test with, but would be curious if other's have similar issues. Would you be willing to startup your app, wait until radio becomes OK, then go to Settings -> About -> Debug (at the bottom) and paste me that, at least up to the line where it says STOP COPYING HERE IF YOU DO NOT WANT TO INCLUDE LOGS BELOW (below that will include the application logs which can reveal messages, room names, etc.). If not, no worries, but it'll help me see if the app sees your radio in a weird way.
Hmmm interesting. That's part of initial load where it empties out radio contacts in prep for the server managing them. That's odd you're having issues with what's a pretty fundamental radio operation. When you use the radio with another client, are you able to easily delete contacts? Are you paired over serial, bluetooth, or TCP? We're using the standard interface library to do our contact management (meshcore_py) so it would be really weird to have issues on mainline firmware that don't repro to other devices.
I assume by lorav3 you mean a Heltec wifi lora v3? I don't have any of those hanging around right now to test with, but would be curious if other's have similar issues. Would you be willing to startup your app, wait until radio becomes OK, then go to Settings -> About -> Debug (at the bottom) and paste me that, at least up to the line where it says `STOP COPYING HERE IF YOU DO NOT WANT TO INCLUDE LOGS BELOW` (below that will include the application logs which can reveal messages, room names, etc.). If not, no worries, but it'll help me see if the app sees your radio in a weird way.
<!-- github-comment-id:4091668809 -->
Yeah that's really interesting; looks like we're failing to add or remove contacts to the radio; expected_but_not_found means that we're not even loading them. I've ordered a board to see if I can replicate.
Yeah that's really interesting; looks like we're failing to add or remove contacts to the radio; `expected_but_not_found` means that we're not even loading them. I've ordered a board to see if I can replicate.
<!-- github-comment-id:4092065621 -->
Good news! My v3 arrived, I replicated, and found the issue. It requires an adjustment in the library we use, and I've made a PR to adjust that. Once that's merged (the maintainer is usually very responsive), I'll include their new version. If there's a delay for some reason, I'll just monkey patch their library.
Good news! My v3 arrived, I replicated, and found the issue. It requires an adjustment in the library we use, and I've made a PR to adjust that. Once that's merged (the maintainer is usually very responsive), I'll include their new version. If there's a delay for some reason, I'll just monkey patch their library.
You can track the status of my PR here: https://github.com/meshcore-dev/meshcore_py/pull/67
<!-- github-comment-id:4105417943 -->
Okay I've just monkey patched this in 9de4158, so if you run this from source checkout, just give it a pull (and rebuild your frontend, if you haven't done that in a while; not needed for this change but there is lots of new UI goodness over the last few days) and you should be good to go.
Okay I've just monkey patched this in 9de4158, so if you run this from source checkout, just give it a pull (and rebuild your frontend, if you haven't done that in a while; not needed for this change but there is lots of new UI goodness over the last few days) and you should be good to go.
<!-- github-comment-id:4105611101 -->
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.
When I start RemoteTerm, I see a stream of dozens of messages like
app.radio_sync - WARNING - Failed to remove contact 07b19c5c240c: {'reason': 'no_event_received'}. After many of those, it'll say something likeapp.radio_sync - INFO - Synced 174 contacts, removed 146 from radio.Each of these takes a while, which results in startup time being measured in minutes instead of seconds. This blocks the radio initialization, so you're unable to send messages until it's done. Restarting the server causes it to try all of this again.
The node hardware is a LoRa V3 flashed yesterday with 1.14, connected over serial.
Hmmm interesting. That's part of initial load where it empties out radio contacts in prep for the server managing them. That's odd you're having issues with what's a pretty fundamental radio operation. When you use the radio with another client, are you able to easily delete contacts? Are you paired over serial, bluetooth, or TCP? We're using the standard interface library to do our contact management (meshcore_py) so it would be really weird to have issues on mainline firmware that don't repro to other devices.
I assume by lorav3 you mean a Heltec wifi lora v3? I don't have any of those hanging around right now to test with, but would be curious if other's have similar issues. Would you be willing to startup your app, wait until radio becomes OK, then go to Settings -> About -> Debug (at the bottom) and paste me that, at least up to the line where it says
STOP COPYING HERE IF YOU DO NOT WANT TO INCLUDE LOGS BELOW(below that will include the application logs which can reveal messages, room names, etc.). If not, no worries, but it'll help me see if the app sees your radio in a weird way.Yep, a Heltec LoRa v3 connected using USB.
I moved it to another computer, connected with the MeshCore web app, and was able to delete contacts.
Yeah that's really interesting; looks like we're failing to add or remove contacts to the radio;
expected_but_not_foundmeans that we're not even loading them. I've ordered a board to see if I can replicate.Good news! My v3 arrived, I replicated, and found the issue. It requires an adjustment in the library we use, and I've made a PR to adjust that. Once that's merged (the maintainer is usually very responsive), I'll include their new version. If there's a delay for some reason, I'll just monkey patch their library.
You can track the status of my PR here: https://github.com/meshcore-dev/meshcore_py/pull/67
Okay I've just monkey patched this in
9de4158, so if you run this from source checkout, just give it a pull (and rebuild your frontend, if you haven't done that in a while; not needed for this change but there is lots of new UI goodness over the last few days) and you should be good to go.Gonna close this now as patched, but feel free to reopen if you run into any other issues.
Can confirm the patch works on my end. It now loads and doesn't throw extraneous contact-removal errors.
Thanks!