-
Notifications
You must be signed in to change notification settings - Fork 714
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
[Bug]: rak4631 crashes after ~1 day on latest stable fw #4096
Comments
How do you have the node configured? |
How do I do a remote serial monitor capture? |
There is no way to do this remotely unfortunately. You'll have to use USB and capture with meshtastic --noproto or a serial terminal like tio or putty |
I've been doing battery testing on my RAK node and it has been up and functioning properly for about a week now. Do you have a lot of nodes in your node list? Are you possibly being flooded with MQTT traffic from the default channel? I've definitely learned my lesson about connecting to the default MQTT channel so maybe that is what's going on here. |
I've just now experienced this issue. Upgraded to 2.3.13 and approximately 24 hours later (not sure exactly when because it happened over night) RAK node stops responding and sending telemetry. I'm a little suspicious that I may have fried my solar charging circuits by connecting a panel that output 6.5 volts. I have a new 19007 board coming and I'll see if the issue exists on the new board in about a week. |
Any possibility of posting (or emailing) you battery setup on the RAK? |
Category
Other
Hardware
Rak4631
Firmware Version
2.3.11.2740a56
Description
Sorry about re-post, but #4073 was made into a discussion after concluding that the version was too old.
After a few days of uptime this device stops responding over bluetooth and is no longer reporting full data on meshmap.
I don't have access to any serial logs due to the long time to reproduce and the device living outside on a roof.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: