-
-
Notifications
You must be signed in to change notification settings - Fork 261
[Bug]: notification for every Node connection #1933
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
Comments
Thanks for your quick respons. As i understand this doesen't realy help me. So this issue sholud rather be an feature request to ad in appsettings to manage notification settings. |
Thanks this helped a lot. But the behafiour is saw was in my eyes worng. The app keept notifing me for the same Nodes it reached. I find this very anoying and would think of this feature more in kind of notifing me if ther was a connection to a new Node (one witch has never been seen). |
You are also running the app from January. I suggest updating from 2.5.16 app to 2.6.3 in the beta channel. A lot has changed in 5 months. |
I am now running 2.6.2 but saw the same issue. |
I think there is a plan for the firmware to check the app node database (which can be unlimited in size) before it "sees a new node". But regardless, at this point I just turned off the new node notifications until everything is worked out. |
Uh oh!
There was an error while loading. Please reload this page.
Contact Details
go.pro.profi@gmail.com
What happened?
App notifies for every Node Clnnection, even for previously seen Nodes. Further more ther is no way go seperatly manage Notification settig s for the App.
App Version
2.5.16
Phone
Galaxy S24+, Android 15, One-UI 7.0
Device
Lilygo T-Echo /
Firmware
2.6.4.b89355f Beta
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: