POMdev wrote: > To troubleshoot this, use the ::-d /etc/log/:: to save the log files > where they will not be lost after a reboot, and examine the files as > soon as you notice the radio off.
They are all logging to a server via NCAT, so I have those logs. I'll add the "-d /etc/log" as well. POMdev wrote: > If it tries again too soon, a possible recovery is aborted, a new cycle > begins, and the radio does not recover. This was a problem with weak > signals and heavy interference in earlier versions, where the retry time > was fixed at a relatively short time. Later versions like you are using > have an adaptive retry time that has an upper limit. You might be > hitting that upper limit. I was previously using version 0.6.3.1 (with a fix noted in 2/23/21 post) and 'Back1' seemed to stay online for several days vs. half a day. However, this is just based on my memory. POMdev wrote: > None of your radios have any Options showing. The 'slow' web server is > recommended for monitoring. I set "WSERVER="slow"" in the script. The details I posed here are grabbing the RawFails from each Radio web server. POMdev wrote: > Of your radios, only "Floater" is showing extended full reset recovery > times (possibly from going out of range of the access point) and it > stays on for a week. Floater is about 15 inches from the AP, so it should not be going out of range of the AP.... POMdev wrote: > Your 'Back1' radio reports a signal level of -70 dBm. It may be just out > of range of the AP given your environment. "Floater" had a very high > signal level at the time of measurement, but perhaps that unit had also > been in the hinterlands for a while, which would explain the repeated > failure of the full resets to work, as Floater recovered when brought > into a strong signal area. (Does Back1 recover without rebooting when > moved into a high signal area?) 'Floater' is about 15 inches from the AP and should have great signal. 'Back1' and 'Back2' are in a poor signal area (but up until the last year with the all these drops, had no issues). 'Kitchen' has a good signal. POMdev wrote: > Back1 is failing the most often, so it makes sense to concentrate on > this unit first, and perhaps Floater as well, as it exhibits the > interesting increasing recovery time steps, which might also being > experienced by Back1, but the logs are lost. I've moved 'Back1' temporarily nearby to 'Floater'. Based on earlier tests, 'Back1' should stay online longer now. I can also move 'Back1' to its original location for more testing. POMdev wrote: > And you might try the latest software in the development branch to see > if a quick reset is effective in your environment, and to improve the > Reset report. Still, your 0.8.4.1 should work as is. I updated Radios to the Community build firmware a few weeks ago \, and it made no difference in reducing the issue. ------------------------------------------------------------------------ jc77's Profile: http://forums.slimdevices.com/member.php?userid=71681 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 _______________________________________________ Radio mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/radio
