P Nelson wrote:
> Months ago I had problems finding my own Wifi network in the available
> network list on the Radio. (This was on my Radio at work and unrelated
> to the WiFi6 issue at home.) The Radio would not show my Wifi network
> that it had previously connected to. It was strange. I
SlimChances wrote:
> I was referring to the -VAP11G-300 - ---AND WHETHER IT COULD BE
> CONNECTED TO THE POWER OUTLET ON THE RADIO WHEN IN BATTERY MODE. NEVER
> MIND-
It won't work on battery. The power-in of the radio is not a power-out
when on battery.
If you want to be mobile, the wlanpoke
mikitil wrote:
> Thnx. Badly it is died even without covering it with tape. Bad luck for
> me ;( But happily with my Re450 Option it is absolute perfectly stable
> now.
I have been running several Vonets during the last couple of months (3
VAP11G-300 and 1 VAP11N-300).
The VAP11N-300 got very
frankd wrote:
> Log files of the script (version 0.73) with two events capture, when the
> script could not reestablish the network (second one around 12:30, first
> one around 11:55).
I guess the neighbor with the annoying WIFI moved out our upgraded his
hardware. There are a
POMdev wrote:
> I am working on solving the Wireless Connectivity issue, but my
> environment here has recently become too quiet, and my 7 radios are not
> failing nearly as much as before (8-15 times/hour), most going all night
> without failure. I set my closest radio to a far away access
Log files of the script (version 0.73) with two events captures, when
the script could not reestablish the network (second one around 12:30,
first one around 11:55).
+---+
|Filename: _log.zip
POMdev wrote:
> This is the first report of the mitigation not working in every case.
> How many times has this happened? What wlanpoke version are you
> running?
>
> To investigate this, the log files are a first step, but they will be
> lost if the radio is rebooted. Could you please upload
slartibartfast wrote:
> I tried installing the patch on my second Radio from /usr and it
> wouldn't install so I moved it to /usr/share and I still needed to add
> -p1 to the patch command. The path inside the patch has no / before
> share so that could be the reason. The patch installer has no
POMdev wrote:
> From what I can read about the chip, it seems pretty capable. It is
> controlled by firmware for the chip's xtensa processor that the driver
> or a support utility downloads to the chip. This firmware is
> proprietary, and its source and environment more than very unlikely to
>
POMdev wrote:
> The latest wlanpoke software is on github to download. Earlier versions
> are on this forum. It doesn't need "activation," but it does need to be
> manually installed. The software has extensive logging, and it handles
> piping its logs to your computer (running ncat) even in
mrw wrote:
> I shall watch this space.
>
> I shall add that later versions of the wpa_ software (i.e. as included
> in the Radio's community firmware release) bring their own
> problems/incompatibilities with the way SqueezePlay has been brought up
> to expect. Not insuperable, I think (I have
POMdev wrote:
> It looks like the automatic gateway detection does not have to be
> overridden, as it seems reliable.
>
> Looking at your logs, what stands out to me is, first of all, the very
> low signal level ...Link Quality:26/94 Signal level:-69 dBm Noise
> level:-96 dBm Tx excessive
Tony T wrote:
> Yes. Cant tape over the case as its the vent...
> but, the case is press fit. Easy to pop open and place a small
> piece of electrical tape directly over the LED.
I tried it with the Vonets VAP11G-300 and the VAP11N-300. For the G
version it worked well, however you have
POMdev wrote:
> Thank's for digging into this. What happened after the failure, did you
> have to reboot? How long was the music interruption? On what service? We
> sometimes notice a couple of second interruptions here, but have
> experienced that for many years.
>
> Edit: Why hard-code the
POMdev wrote:
> I'm not an SB developer, just a user albeit with instrumentation. I
> don't dare to intrude on the development forum. I am unfamiliar with and
> therefore cannot write an automated install and configuration patch, or
> plugin, app, or whatnot. I was hoping one of the senior
P Nelson wrote:
> Here is my set-up at home, two Radios and a Touch. Red Radio (LMS
> reports 100% signal strength as it located on other side of the wall
> from the router) is connected to my primary Arris NVG468MQ. Black Radio
> (LMS reports 90-83% signal strength) and the Touch (LMS
mrw wrote:
> Is this particular element of the problem exclusive to the Radio running
> the Community firmware ?
>
> I ask, because:
>
> a) I believe that your Red Radio is (or was) running Community firmware,
> but perhaps your Black Radio is not.
> b) I believe that I have located a problem
mrw wrote:
> As far I as can see, the Repair network advanced setting on the Radio
> does not restart the wifi kit. I think that might be added in, but needs
> checking. Not a solution, but could be helpful.
That would be a first helpful option at least :)
slartibartfast wrote:
> Of course powerline adaptors and WiFi to ethernet adaptors make the
> Radio a lot less portable.
>
> Sent from my Pixel 3a using Tapatalk
Yes unfortunately, I love to take a radio to my terrace during summer
with built-in batteries.
Thus I still hope we can address
We should move this discussion to the "WiFi connection unstable/lost on
three Radios" thread, as it is the same issue in most of the cases, see
my last post in that thread...
frankd's Profile:
Unfortunately I have joined this club recently when a neighbor upgraded
to a Wifi6 (ax) network. It seems that neighbours with WIFI6 or Asus
Routers (Wifi 5 and 6) interfere with WLAN of Squeezebox Radios. This
will become a broad problem, thus more an more posts in this thread.
Therefore some
See my other post about somebody offering 3D-Printed replacement knobs
for Boom and Radio:
https://forums.slimdevices.com/showthread.php?111561-Sticky-Boom-Knobs-and-rubber-material
frankd's Profile:
mrw wrote:
> Thanks. I can't see an 'obvious' reason for that.
>
> I have, myself, experienced one drop out on each of my two radios. I
> hypothesized at the time that this was because the radios had been
> silent for some time, so the (larger) alsa buffer hadn't had time to
> fill and ride
Thanks a lot for all your work.
I experienced the same problem with my set of radios. I havejust
installed your applet, set all to 30ms and I will report back if it
works (this may take some time as I will test them as they are, not
provoke any bass amp problems - the failures felt pretty
24 matches
Mail list logo
