Re: [SlimDevices: Radio] Community Build Radio Firmware
P Nelson wrote: > For the speaker output, does the Both Channels Stereo or Mono have the > same result, or is there actually a sonic difference? The reason I ask > does combining a right and left signal result to the same speaker result > in a canceling or enhancing an audio signal? Not @ralphy, but I would expect the same result. As I recall it, Both Channels (Mono) pushes (L+R)÷2 (i.e. Mid ÷ 2) into each of the L & R components. The Radio speakers DSP mixer simply combines L & R components with L+R, i.e. it makes Mid. Either way, we get the same result, theres no tinkering around with Side. Of course, if the source L & R has been mixed with some phase cancelling/enhancement/effects stuff then Mid could be made to sound odd, or just plain silent. I would suppose that such a source could hardly be a good candidate for monaural reproduction. The Radio headphones DSP mixer does nothing, i.e. it is a pass through. Im too far from my Radio to actually physically test mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
Okay I am guessing, both channels mono, mixes the 2 channels together and then sends that mixed audio to both physical channels? bengaldave's Profile: http://forums.slimdevices.com/member.php?userid=4605 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
Ralphy, Can you please confirm my understanding of the "Output Channel Mode" settings for an SB Radio Both Channels (Stereo) = Stereo output to the headphone jack. Effectively a mono output to the single speaker. Left Channel = Left Channel to the speaker. What is the output of the headphone jack? Right Channel = Right Channel to the speaker. What is the output of the headphone jack? Both Channels (Mono) = Mono output to speaker and headphone jack. The information dialog on the setting in LMS could use an update. For the speaker output, does the Both Channels Stereo or Mono have the same result, or is there actually a sonic difference? The reason I ask does combining a right and left signal result to the same speaker result in a canceling or enhancing an audio signal? P Nelson's Profile: http://forums.slimdevices.com/member.php?userid=58158 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
bengaldave wrote: > Thanks but still do not understand, what is the effect of both channels > mono in contrast to both channels stereo? > Thanks I have not played with these settings so this is a guess. The radio speakers are mixed stereo, pseudo mono. The headphone jack is true stereo. The setting affects the jack, but really does not affect what you hear from the speaker. give it a listen yourself, see what you think. Listen to old beatles where they had instruments in one channel and vocals in the other :) Jim Redrum's Profile: http://forums.slimdevices.com/member.php?userid=33806 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
Thanks but still do not understand, what is the effect of both channels mono in contrast to both channels stereo? Thanks bengaldave's Profile: http://forums.slimdevices.com/member.php?userid=4605 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
bengaldave wrote: > So in the release notes there is this: > >>Add both channels mono output channel mode support. > > Is this related to the server settings/player>audio? > Both channels stereo > Both channels mono > > So for the radio is both channels stereo different than both channels > mono? > > In both cases the radio only has one speaker Yes for the radio's internal speakers both are pretty much the same. You can plug in stereo headphones to the radio or connect the hp jack to a stereo. Ralphy *1*-Touch, *5*-Classics, *3*-Booms, *2*-UE Radio 'Squeezebox client builds' (https://sourceforge.net/projects/lmsclients/files/) 'donations' (https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=LL5P6365KQEXN&lc=CA&item_name=Squeezebox%20client%20builds¤cy_code=USD&bn=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted) always appreciated. ralphy's Profile: http://forums.slimdevices.com/member.php?userid=3484 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
So in the release notes there is this: >>Add both channels mono output channel mode support. Is this related to the server settings/player>audio? Both channels stereo Both channels mono So for the radio is both channels stereo different than both channels mono? In both cases the radio only has one speaker bengaldave's Profile: http://forums.slimdevices.com/member.php?userid=4605 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
Redrum wrote: > Funny this is brought up again. I have never had any luck with "rubbing > alcohol" but here is the US Isopropyl is common. I am told that Ethyl is > more effective, but I have not tried it. Myself, for radio knobs, I pull > them off and sand them, then paint matte black. It doesn't have that > "tactile" feel but it's fine for me. > > There is a long discussion of alot of options including where @chill > sourced the "tactile" finish: > https://forums.slimdevices.com/showthread.php?107531-What-to-do-with-a-Boom-with-sticky-front-panel > > Jim Ethanol (70% solution) + elbow grease worked for me - and the result was very nice... THildebrandt's Profile: http://forums.slimdevices.com/member.php?userid=69370 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
THildebrandt wrote: > Used rubbing alcohol on several radios with sticky knobs - solved > problem. > As i understand it, the radio knobs were covered with a rubber (?) > compund to make them feel softer when used??? and this compound > apparently have a limited lifespan... Funny this is brought up again. I have never had any luck with "rubbing alcohol" but here is the US Isopropyl is common. I am told that Ethyl is more effective, but I have not tried it. Myself, for radio knobs, I pull them off and sand them, then paint matte black. It doesn't have that "tactile" feel but it's fine for me. There is a long discussion of alot of options including where @chill sourced the "tactile" finish: https://forums.slimdevices.com/showthread.php?107531-What-to-do-with-a-Boom-with-sticky-front-panel Jim Redrum's Profile: http://forums.slimdevices.com/member.php?userid=33806 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
sgmlaw wrote: > Thank you. I will look into this. Up to now, we have been using the > baby powder treatment, which can get dusty. Used rubbing alcohol on several radios with sticky knobs - solved problem. As i understand it, the radio knobs were covered with a rubber (?) compund to make them feel softer when used??? and this compound apparently have a limited lifespan... THildebrandt's Profile: http://forums.slimdevices.com/member.php?userid=69370 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
sgmlaw wrote: > Distance of neighboring wireless networks is likely a factor in our > environment. > > Another wireless networking tip, especially for Asus users, is visiting > the smallnetbuilder forum. At least for the North American market, > there are sufficient conversations there where the finer technical > attributes of the various models are discussed (such as chipset and AP > architecture). And that, in combination with some further research, can > help differentiate things in determining what may work, and what doesnt > work, with certain environments and clients. I'd second that advice for Asus users, between smallnetbuilder and this forum I was able to have my Asus AiMesh working fine with my SB radios for several weeks which was great. Unfortunately though I could do nothing about a close neighbour getting a Netgear Orbi which has brought the issues to our three radios :( slurmsmckenzie's Profile: http://forums.slimdevices.com/member.php?userid=69467 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
xrad wrote: > Sorry of the OT follow-up: I recently wiped the knobs of one of my > radios using generous amounts of methylated spirit and they now > absolutely touch as if they were new out of the box. Highly recommend > that treatment. Thank you. I will look into this. Up to now, we have been using the baby powder treatment, which can get dusty. sgmlaw's Profile: http://forums.slimdevices.com/member.php?userid=13995 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
P Nelson wrote: > Interesting. With with an ASUS RX-AT55 and PX-AT56, I had different > results. Turning on Wifi6 in the 2.4 GHz band would cause my radios to > drop very quickly. Turing Wifi6 off helped. I have not done a more > recent test with newer ASUS firmware as I have to move all my equipment > to a location that does not exhibit interference problems. In my case, > I suspect it is a neighbor using WiFi6 which causes random interference > with the Radios. > > You can read my experience here: > https://forums.slimdevices.com/showthread.php?114996-ASUS-RT-AX55-Mesh-Router%92s-Compatibility-with-SB-Radios&highlight=ASUS > > Your experience is good news if newer chipsets/firmware is not causing > problem with older equipment. > > Paul Distance of neighboring wireless networks is likely a factor in our environment. We have a large property (hence the need for a wireless mesh), and it is unlikely that neighboring 5 and 6 Ghz wireless networks (not including cellular protocols, of course) are intruding too deeply. I can imagine in a congested townhouse or condominium setting, that would not be the case. I routinely conduct network surveys to see who is about us, and there are always at least 3-5 other wireless networks in range, but I suspect they are all legacy 2.4 Ghz of one form or another. But that's the helpful paradox of the newer wireless standards. As the standards improve, the frequencies increase, from 5 Ghz, and now slowly into 6 Ghz ranges, and the transmission range naturally declines with most consumer equipment (due to the amplifier constraints). So I hope all our neighboring properties migrate to 6 Ghz Wi-Fi 6E and eventually Wi-Fi 7, as quickly as possible. And I suspect that the chip designers are increasingly not further advancing the 2.4 Ghz band (other than as a fallback limp home mode in auto band switching environments), as there is insufficient bandwidth available there to support the latest and coming standards. As long as they don't remove it from the SoC altogether, the Radio and other 2.4 Ghz legacy clients will still have a home. I was experiencing the dropouts that many here were reporting when allowing the Radio to roam our mesh network. That was likely because of dissimilar chipset and AP standards among the nodes complicating the handoffs. The nodes here are tri-band Asus XT8 models. Binding it to the core router prevented those handoffs, and the drops. Of note is that our core routers have been dual band only (as we run Ethernet backhauls). So the RF architecture that the Radio faces is also less complicated than other clients. Whatever the reasons, the bottom line is that the Radio works in it. sgmlaw's Profile: http://forums.slimdevices.com/member.php?userid=13995 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
sgmlaw wrote: > > In any event, the Radio (increasingly sticky knobs and all) keeps > chugging along on its onboard wireless, even entering 2023. So it can > be done. Sorry of the OT follow-up: I recently wiped the knobs of one of my radios using generous amounts of methylated spirit and they now absolutely touch as if they were new out of the box. Highly recommend that treatment. LMS 8.3.1 on Raspbian GNU/Linux 10 (buster); 3 Radios xrad's Profile: http://forums.slimdevices.com/member.php?userid=71399 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
sgmlaw wrote: > I am happy to report that our Radio so far has tolerated the migration > to a new Wi-Fi 6 router (Asus GT-AX6000). The CPU and AP chipsets are > more recent Broadcom releases (BCM4912/BCM6710). Perhaps the newer > chipsets are becoming a little more legacy friendly. > > But in an AX mesh network that normally causes wireless havoc with > Radios and even Touches, binding the Radio to the router in this > particular environment (preventing node roaming) has maintained a stable > connection. > > Interesting. With with an ASUS RX-AT55 and PX-AT56, I had different results. Turning on Wifi6 in the 2.4 GHz band would cause my radios to drop very quickly. Turing Wifi6 off helped. I have not done a more recent test with newer ASUS firmware as I have to move all my equipment to a location that does not exhibit interference problems. In my case, I suspect it is a neighbor using WiFi6 which causes random interference with the Radios. You can read my experience here: https://forums.slimdevices.com/showthread.php?114996-ASUS-RT-AX55-Mesh-Router%92s-Compatibility-with-SB-Radios&highlight=ASUS Your experience is good news if newer chipsets/firmware is not causing problem with older equipment. Paul P Nelson's Profile: http://forums.slimdevices.com/member.php?userid=58158 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
I am happy to report that our Radio so far has tolerated the migration to a new Wi-Fi 6 router (Asus GT-AX6000). The CPU and AP chipsets are more recent Broadcom releases (BCM4912/BCM6710). Perhaps the newer chipsets are becoming a little more legacy friendly. But in an AX mesh network that normally causes wireless havoc with Radios and even Touches, binding the Radio to the router in this particular environment (preventing node roaming) has maintained a stable connection. Our primary need for the router upgrade was 2.5G WAN and LAN capability to support multigigabit ISP service. Not many prosumer grade routers currently offer multigigabit on both WAN and LAN. But Asus also has a strong reputation for very regular firmware updates and bug fixes, and may have been more responsive to addressing legacy client issues than some other prosumer/consumer makers. Which is why we stuck with them on the upgrade. In any event, the Radio (increasingly sticky knobs and all) keeps chugging along on its onboard wireless, even entering 2023. So it can be done. sgmlaw's Profile: http://forums.slimdevices.com/member.php?userid=13995 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
I will be closely following this thread, and appreciate the efforts of our community to keep the ecosystem running after so many years. I have had a Radio working well in a WiFi 6 "mesh" environment for several years now, but only because it was 'bound' to a first-generation chipset AX router that better accommodated legacy G clients. That router is being retired, and I am fairly certain that the Radio will not behave well with the more modern WiFi 6 replacement router. The worst case workaround is to set up an N repeater (Netgear EX2700) as an AP for just the Radio, as the old SBs seem to have no problem connecting to it, either wirelessly or as a wired media bridge. sgmlaw's Profile: http://forums.slimdevices.com/member.php?userid=13995 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
Recently my Touch , Controller and a Radio have all spontaneously brought up the Software Update screen saying the software is up to date, would I like to reinstall. Any idea why? Sent from my Pixel 3a using Tapatalk slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
P Nelson wrote: > Are you certain someone did not replace their router but use the same > SSID? > > The community firmware and wlanpoke are compatible with each other. I > am using both as I have the interference problem. > You can see the log of the community firmware here: > https://ralph_irving.gitlab.io/lms-community-firmware/changelog.html > In short, the source code for the Radio's wifi chip is unavailable as it > is proprietary, so it has not been replaced. I asked around and no one replaced their router. Thank you for the changelog link. I do not think I have ever found that. I mistakenly thought the community firmware made the wlanpoke redundant. I have installed it on one of the worst offenders (it dropped 3x since yesterday morning) and it has remained connected so far. If I can provide any debug information to help with the investigation just let me know. Proprietary blobs are no fun... Has anyone tried to appeal to the owners of the code. It would be a long shot but I have heard of a few places releasing the fw source years later. Syco54645's Profile: http://forums.slimdevices.com/member.php?userid=73039 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
Syco54645 wrote: > Lately it seems that all of my radios are disconnecting at least daily, > some a few minutes after rebooting. This just started a few weeks ago. > No one in my area has gotten a new wifi device. Did anything change in > the community firmware in regards to the wifi? I accepted an update a > little bit ago and the timing may coincide with my wifi woes. > > I see discussions above regarding wifi issues and a new version of wlan > poke. I thought we were not supposed to use wlan poke if using community > firmware. Are you certain someone did not replace their router but use the same SSID? The community firmware and wlanpoke are compatible with each other. I am using both as I have the interference problem. You can see the log of the community firmware here: https://ralph_irving.gitlab.io/lms-community-firmware/changelog.html In short, the source code for the Radio's wifi chip is unavailable as it is proprietary, so it has not been replaced. P Nelson's Profile: http://forums.slimdevices.com/member.php?userid=58158 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
Lately it seems that all of my radios are disconnecting at least daily, some a few minutes after rebooting. This just started a few weeks ago. No one in my area has gotten a new wifi device. Did anything change in the community firmware in regards to the wifi? I accepted an update a little bit ago and the timing may coincide with my wifi woes. Syco54645's Profile: http://forums.slimdevices.com/member.php?userid=73039 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
[POMdev wrote: > ... This "toxic beacon" theory fits with my experiences investigating > the radio's failure. It explains how the radio, even when solidly > connected to a compatible access point, fails occasionally when exposed > to much weaker signals from neighbor's newer 2019-2020+ systems. I > suspect that the very frequent scanning performed by the radio is > picking up these signals, and, once in a while, crashing something. The > effect is that the radio loses receive sensitivity, misses packets from > the access point, and eventually disconnects. ... And it happens > "rarely" considering the radio is so frequently scanning, which was > evidently increased in a patch to the driver source code, perhaps to > improve performance when moving the radio between rooms or access > points. ... > The research and writing for Tuesday's post led to a thought: What if the system could drastically reduce the other access point scanning so that the so-called rare fault was much less likely to occur? The driver source code was evidently patched to increase the scan frequency. Might there be a way to decrease it using the software we already have? The answer may be yes. The tersely documented command /lib/atheros/wmiconfig --scan --scanctrlflags 0 0 0 0 0 0 controls scanning under some circumstances. Trying this on 5 radios resulted in a dramatic reduction of lengthy gaps and resets, very encouraging. A function to do this was added to an experimental wlanpoke script and deployed on 7 radios. It is executed by the Quick and Full reset functions, and only if they are triggered by a failure. This command is poorly understood. Also, there is likely a very good reason the unmodified software scans as frequently as it does. Inhibiting scanning may cause problems with portable and mobile use. For this reason, the scan reduction is done only when the connection has been lost. For fixed operation with interfering signals, this seems helpful. When moving out of range of one access point into another area, this might delay or prevent connection to another access point. If a connection cannot be made, then a reboot will be required to restore the radio's original scanning behavior. There were mixed results after a day. The radio causing the most complaints has had only 1 reset, 20 gaps 4 second gaps, and 3 wpa_cli script restarts, 3 radios had no resets, and a similar number of 4 second gaps. The south perimeter radio, wired to the Ethernet, was switched over to a strong WLAN (-62). It was reverted to Ethernet after (Qr:35 Fr:10 Wr:6 Wc:2) within a few hours. To continue the investigation into this location, the radio in the most shielded underground position, typically with no resets, was set up adjacent to this unit, and is now being similarly hammered. The second story radio above the "most complaints" unit is also suffering. The latest quick reset method (power cycle) is not very effective. It evidently does not repair the damage caused by the interference even as it helps the radio to reconnect, but mostly only for a few seconds or so, and is no longer the default. After 3 days the improvement is quite good. The worst location was instrumented with a wireless telnet to serial ESP32 module so that the serial console would be available during the frequent outages. However, in this location the wireless serial module also repeatedly fails, a new phenomenon. The interference is evidently fierce! But all the other radios have more or less calmed down and are working normally, an encouraging result. A new experimental version 0.8.7.1a has been uploaded to the 'wlanpoke GitHub Development branch' (https://github.com/PomDev2/wlanpoke/tree/development). It has been tested so far only with fixed locations. This version requires testing and possible refinement to avoid degrading the radio's various other use cases. By the way, this version also supports environments containing access points with apostrophes and other special characters that previously caused the script to fail. Also by the way, a debug version of the frequently failing wpa_cli program could facilitate troubleshooting and fixing that point of failure. POMdev's Profile: http://forums.slimdevices.com/member.php?userid=70558 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
mherger wrote: > ...Their latest dev firmware would break compatibility with the Radio. > They have been able to identify one cause for the failure ... > They believe that the problem is related to 11ax (wifi6?) and WLAN > beacon size. Now they're asking whether the beacon size was limited in > firmware or similar. ... This sounds like progress: the AVM/Fritz!Box vendor identifying one cause for failure as related to 11ax WLAN beacon size. Two questions: 1) how did they come to believe this, and 2) could the 11ax beacon size, if too large, be reduced in their software as a compatibility option? This "toxic beacon" theory fits with my experiences investigating the radio's failure. It explains how the radio, even when solidly connected to a compatible access point, fails occasionally when exposed to much weaker signals from neighbor's newer 2019-2020+ systems. I suspect that the very frequent scanning performed by the radio is picking up these signals, and, once in a while, crashing something. The effect is that the radio loses receive sensitivity, misses packets from the access point, and eventually disconnects. I do not understand how a too large beacon would affect receiver sensitivity, other than overwriting an AGC parameter in the chip's WLAN radio receiver. And it happens "rarely" considering the radio is so frequently scanning, which was evidently increased in a patch to the driver source code, perhaps to improve performance when moving the radio between rooms or access points. Wouldn't it be great if all the other vendors were similarly engaged in this issue? I suppose a first step would be to identify and list the "offending" access points (e.g., wireless routers) make, model (and ideally firmware version). These could be researched for configuration options that might eliminate the interference, and the device owners perhaps be enticed to make these changes. The vendors could be contacted and they might investigate or provide support. Posting these user and vendor contact notes and results could be helpful. Regarding the radio's firmware, I have been involved in investigating the "wireless connectivity loss" issue implementing a troubleshooting logging (and mitigation) script wlanpoke, then 'instrumented my most often failing radio' (https://forums.slimdevices.com/showthread.php?111663-Community-Build-Radio-Firmware&p=990627&viewfull=1#post990627). An early wifi-6 router was obtained and 'wifi-6 implicated' (https://forums.slimdevices.com/showthread.php?111663-Community-Build-Radio-Firmware&p=1018853&viewfull=1#post1018853). Of note is the finding that "... it seems that the wifi-6 is the culprit, and [heavy] wifi-6 traffic makes it much, much worse." Might this imply that not just the beacon is involved? It should be noted that wifi-6 (or something) also disrupts other cheap IOT devices (e.g., cameras), making them unreliable for continuous monitoring. However, these devices reset themselves without intervention. On the other hand, very cheap devices like the ESP32 modules are not affected. Regarding the software, the host (radio) software runs the wlan script, which calls the /lib/atheros/loadAR6000l.sh script. The script loads the kernel driver ar6000.ko, uses bmiloader to set some values, then calls the eeprom.AR6002 app to load calData_ar6102_15dBm.bin. Next, bmiloader loads athwlan.bin and then data.patch.hw2_0.bin, and loadAR6000l.sh returns to the wlan script to configure the system using wmiconfig, then launches the wpa_supplicant and wpa_cli processes. The linux host software is marked open source, but that source has not been made available. Another version of the Atheros chip OS driver was modified to 'partially run' (https://forums.slimdevices.com/showthread.php?111663-Community-Build-Radio-Firmware&p=1020189&viewfull=1#post1020189), not crash, on the radio. After realizing the driver's role in simply passing packets up and down, attention turned to the chip firmware as a means of preventing a failure, rather than more quickly recovering from one. The AR6002 hardware seems quite capable. Its firmware is a combination of the chip's Tensilica Xtensa core software athwlan.bin plus the patch and configuration files. Updating this firmware is likely to completely fix the current issue. Regrettably, both the chip documentation and firmware source are proprietary. The effort to reverse engineer the binary firmware files without chip documentation seemed to be quite daunting. Using another version of firmware might work, but has not been tried. POMdev's Profile: http://forums.slimdevices.com/member.php?userid=70558 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
The posts to your query sum up the current state of the wifi radio driver in the community firmware, there not much more I can add. I have documented what was done to mitigate source code unavailability for the CF near the bottom of the 'changelog' (https://ralph_irving.gitlab.io/lms-community-firmware/changelog.html). Here's the summary. - Use Logitech touch firmware 7.8.0r16754 fab4_bsp.so lua module as the touchscreen Synaptics ChiralMotion API is closed source. - Use Logitech controller firmware 7.8.0r16739 binary marvell gspi8686 wireless modules. - Use Logitech binary AR6002 wireless module from radio firmware 7.7.3r16676. - Use Logitech radio baby dsp alsa module from firmware 7.7.3r16676. Unfortunately I don't have a deep technical knowledge of WLAN but am happy to help if I can. Ralphy *1*-Touch, *5*-Classics, *3*-Booms, *2*-UE Radio 'Squeezebox client builds' (https://sourceforge.net/projects/lmsclients/files/) 'donations' (https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=LL5P6365KQEXN&lc=CA&item_name=Squeezebox%20client%20builds¤cy_code=USD&bn=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted) always appreciated. ralphy's Profile: http://forums.slimdevices.com/member.php?userid=3484 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
mherger wrote: > > Are you saying that the community firmware uses a "blob", whereas the > original _might_ have built from the source? I'll have to poke around > private repositories... >From the looks of it, Id say the original (kernel module and firmware binary blobs) was 99% certainty built from a source package(s). With the exception of, perhaps, calData_ar6102_15dBm.bin. That is my interpretation of the commit history: https://github.com/Logitech/squeezeos/commits/public/7.8/poky/meta-squeezeos/packages/atheros The binary blobs poky recipe, used by the community firmware, was created fairly late in the day. It would not surprise me to find a too small buffer somewhere, but thats just idle speculation. mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
As far as I can tell there are two blobs we are dealing with: ar6000.ko and athwlan.bin. The latter is the actual firmware blob we will probably never see the source for, but for ar6000.ko there really should be some source available. I think 'this' (https://forums.slimdevices.com/showthread.php?111663-Community-Build-Radio-Firmware&p=988724&viewfull=1#post988724) and 'this' (https://forums.slimdevices.com/showthread.php?111663-Community-Build-Radio-Firmware&p=971241&viewfull=1#post971241) sum up the current state of affairs of the ar6k driver. Perhaps you, Michael, can pull some strings to get access to the actual source. Perhaps the license situation is a bit more relaxed now given the age of the component and software. LMS 8.3.1 on Raspbian GNU/Linux 10 (buster); 3 Radios xrad's Profile: http://forums.slimdevices.com/member.php?userid=71399 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
The Radio's Wifi is something of a closed book to us, because the source code (whatever it may hold) is "PRIVATE" - i.e. it requires access to the private subversion repository to review and build. We have to use a "binary only" poky recipe to populate the firmware image. Are you saying that the community firmware uses a "blob", whereas the original _might_ have built from the source? I'll have to poke around private repositories... ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
mherger wrote: > I'm looking for someone who's got a very good understanding of how WLAN > works, in particular in the Radio, or where in the SqueezeOS source the > wlan is being configured. I've been in touch with one vendor of Wifi > routers (AVM/Fritz!Box). Their latest dev firmware would break > compatibility with the Radio. They have been able to identify one cause > for the failure - but are asking questions I can't answer myself. > > They believe that the problem is related to 11ax (wifi6?) and WLAN > beacon size. Now they're asking whether the beacon size was limited in > firmware or similar. Alas... I have no idea how to figure out. I'm not > too familiar with the firmware code base. Would anybody out there know? My thoughts. Others may have more information. The Radio's Wifi is something of a closed book to us, because the source code (whatever it may hold) is "PRIVATE" - i.e. it requires access to the private subversion repository to review and build. We have to use a "binary only" poky recipe to populate the firmware image. Here is a link to the relevant poky build recipes (Logitech repo): https://github.com/Logitech/squeezeos/tree/public/7.8/poky/meta-squeezeos/packages/atheros. (Ralphy's repo: https://github.com/ralph-irving/squeezeos/tree/public/8.0/poky/meta-squeezeos/packages/atheros). The Atheros driver supplied (ar6000.ko) provides a Wext (Wireless extensions) interface to the hardware, and is used by wpa_supplicant to do its thing. The script 'wlan' shows how the firmware is started up. It uses 'loadAR6000l.sh' and 'wmiconfig' to configure the hardware. On the Radio these are are found in '/lib/atheros' with the wlan script in ' /etc/init.d'. I do not have a very good understanding of Wifi nor experience of Wifi drivers. Perhaps access to the source code would throw light. mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
P Nelson wrote: > I am currently listening (streaming) music to three SB Radios. One of > the radios has wlanpoke and I have not experienced any problems with > synchronization. Cheers! I've installed wlanpoke on the radio and rebooted, started a 10-hour holiday playlist, fingers crossed! --- https://ctproduced.com < Creed Taylor/CTI/KUDU http://markcathcart.com/about Running LMS Server, currently v8.0.0, (1600976618) on Headless WIN10 System; music on Netgear ReadyNAS; Transporter(Living Room)+Duet Controller; Squeezebox Touch(Master Bedroom), (2x)Boom(Office, Patio), Radio(Guest Bedroom), Classic(garage), Duet(basement). Also using Squeezeplay on Windows 10. Use Orange Squeeze app on Android. cathcam's Profile: http://forums.slimdevices.com/member.php?userid=43414 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
cathcam wrote: > Does anyone who has WLANPOKE experience have any idea if this will work > effectively on a radio that is synced with five other players via the > same server? > > I have a radio that is failing exactly as described and I'd like to try > wlanpoke as a circumvention, but not if its going to mess up the > syncronization. > > Cheers! I am currently listening (streaming) music to three SB Radios. One of the radios has wlanpoke and I have not experienced any problems with synchronization. P Nelson's Profile: http://forums.slimdevices.com/member.php?userid=58158 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
Does anyone who has WLANPOKE experience have any idea if this will work effectively on a radio that is synced with five other players via the same server? I have a radio that is failing exactly as described and I'd like to try wlanpoke as a circumvention, but not if its going to mess up the syncronization. Cheers! --- https://ctproduced.com < Creed Taylor/CTI/KUDU http://markcathcart.com/about Running LMS Server, currently v8.0.0, (1600976618) on Headless WIN10 System; music on Netgear ReadyNAS; Transporter(Living Room)+Duet Controller; Squeezebox Touch(Master Bedroom), (2x)Boom(Office, Patio), Radio(Guest Bedroom), Classic(garage), Duet(basement). Also using Squeezeplay on Windows 10. Use Orange Squeeze app on Android. cathcam's Profile: http://forums.slimdevices.com/member.php?userid=43414 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
lemmy999 wrote: > I have looked on my cell phone, laptop and other devices and haven't > seen an apostrophe for any of the SSIDs in my area. Ok, so the script if failing for another reason. The so-far noted reasons for exiting after running for a while have been a "sh: =11: bad number...arithmetic syntax error" and failing to launch the ping (radio out of resources?). The script is designed to exit immediately after launch if there are certain problems with its configuration, which is why the original (not simplified) instructions are to test launch it from the ssh shell. > ...Quality:65/94 Signal level:-30 dBm... A very (too?) strong signal. If the music plays for ~10 seconds then pauses, this is odd. You would have to troubleshoot the connection handshakes somehow. What was the source? Are other sources more responsive? Other radios synced to this one, with another radio failing, might be an issue (although not consistently 10 seconds after resumption)? --- Hello Developers: In light of the WiFi Connectivity Issue, it might be a good idea to review the synchronization code to see if it could be made more robust to radio connection dropouts... --- > I also had one instance where wlanpoke successfully reset the wifi link > but the music stopped playing and never started again. This happens here from time to time, and has happened well before the connectivity loss started. > I will try changing it to 3 failed pings. ... Is there any point in > changing the ping time from the default 2 to 1 second? ... I don't think so. It would just save about one second out of 40, a minor improvement at the risk of additional bugs, etc., including taking more time away from the player. The current software has been tested fairly widely, and works mostly, and sometimes fails or just doesn't work. With a record like that, I believe the focus should be on reliability first and then a reliable quick reset method, which could save a lot of outage time. See the development branch. > ... I will set things back up and be sure to capture the the more > detailed log that is stored on the radio this time. At the time I > hadn't read through the manual file yet and wasn't aware that those had > a limited size and I would lose the data after a while. The size and log file location is configurable. It was set to be fairly modest, less than the radio's own logs, but it can be much larger. However, I don't think the logs will help with the exit issue. The exiting entry is particularly unhelpful. What is helpful is a serial connection and launching the script from the console, and the "ash -x" debugging launch with its massive output piped to another process piping it to your desktop. See github. > So far I have only had 2 wlanpoke exits. One was within 8 hours of > playing music, and the other was after 3 days of being on, but not > playing music. "only 2" is 2 too many, and too frequent. I sort of wish one of my radios did this, I could perhaps find the issue. > Ok, I will try the quick option. The "web server" should not fail. This is a clue, but has not led to a solution so far. > I saw one person say they couldn't get wlanpoke to work for them until > they added the -X option to disable the tcp logging. If you do not have > -X (so logging is on) but you do not have anything receiving the log on > the LMS server, does this typically cause problems? I do have ncat > running on the LMS server, but I was just curious about this. I believe it could cause problems with the software waiting for a failed connection to the server, although the case of a failed server and failed receiving nc or ncat has been tested, but perhaps not enough. Also, not every invocation of the nc reporting is turned off by -x (lower case), so in three cases (2 in wpa_cli_check() and after the gateway comes up, the others don't matter) an nc report is attempted anyway, potentially causing more problems. These nc invocations -should- immediately fail with a "can't connect to remote host" message, but, for completeness, those calls could also be disabled. Thanks for your troubleshooting help. POMdev's Profile: http://forums.slimdevices.com/member.php?userid=70558 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
POMdev wrote: > > > -...none of them have an apostrophe...- The logs would not contain > entries with a single quote (a.k.a. used as an apostrophe on a > keyboard), because the single quote would cause a fault in the logging > function, causing the script to exit before the log is written. An > update is planned to address this limitation. To see an SSID with a > single quote, use any other WiFi client, e.g., a cell phone. > > I have looked on my cell phone, laptop and other devices and haven't seen an apostrophe for any of the SSIDs in my area. > > -...music will pause for a while and a \"rebuffering\" message ...- How > long is the pause? What is your signal level and connection speed? Once > the connection is reestablished, there might be some additional > processing to reestablish the music stream. Consider changing the 6 > failed ping threshold to 3 failed pings to reduce the outage by about 8 > seconds (2.6 seconds * 3 fewer ping trials), it may do the trick. > When this happened my signal level was good and reported in the log as: Quality:65/94 Signal level:-30 dBm Noise level:-96 dBm I also had one instance where wlanpoke successfully reset the wifi link but the music stopped playing and never started again. The LMS server just showed the time line for the song going from 2:20 to about 2:26, then jumping back to 2:20 again and repeating. I just stopped the song playback on the radio (held down the pause) then hit play and it started playing again. I don't think this is anything associated with wlanpoke, but some issue with the radio and the LMS Server. I have seen this happen before (rarely) in the past. I will try changing it to 3 failed pings. I noticed from the logs that several times there are 1 or 2 failed pings but no more and the radio continues to work, but almost 100% of the time if there were more than 2 failed pings, it went all the way to 6 and triggered a reset. So I agree that 3 will probably be ideal for me. Is there any point in changing the ping time from the default 2 to 1 second? With it set at 2 it is closer to 2.5-3.0 seconds like you said, so I am not sure changing to 1 would shorten the time that much. > > -...wlanpoke exiting for no reason after a wifi reset attempt- Is > the reset attempt from wlanpoke, or using the radio's UI? In any event, > the script should not have a fault here. Any assistance in finding the > fault would be very helpful. I was running the script in an 'ash shell > with debugging enabled' > (https://github.com/PomDev2/wlanpoke/issues/7#issuecomment-963230049) to > catch an exit that only rarely happened, but it never did before the > power failed and rebooted the radio and stopped the trial run. > It was a wlanpoke reset attempt. I will set things back up and be sure to capture the the more detailed log that is stored on the radio this time. At the time I hadn't read through the manual file yet and wasn't aware that those had a limited size and I would lose the data after a while. So far I have only had 2 wlanpoke exits. One was within 8 hours of playing music, and the other was after 3 days of being on, but not playing music. > > -...the web server with info (i use the slow option) seems to fail with > some regularity- Another user reported this as well on 'github' > (https://github.com/PomDev2/wlanpoke/issues/4). That was perhaps never > resolved. It is quite a mystery. Too bad it doesn't happen here on my > seven radios. For completeness, try the 'quick' option. You can get the > full report, and refresh it to get the most up to date info. > Ok, I will try the quick option. I saw one person say they couldn't get wlanpoke to work for them until they added the -X option to disable the tcp logging. If you do not have -X (so logging is on) but you do not have anything receiving the log on the LMS server, does this typically cause problems? I do have ncat running on the LMS server, but I was just curious about this. lemmy999's Profile: http://forums.slimdevices.com/member.php?userid=9284 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
lemmy999 wrote: > I have checked the logs and when it scans and lists all of the SSIDs > that it finds, none of them have an apostrophe. The only type of > special character I see in any of them is a dash "-" or a space. > > The only issues I am really seeing with wlanpoke are: > > 1. Even with the default settings of 2 second pings, quick reset > disabled, and 6 failed pings before a reset, I usually see the > connection re-established well before the music stops playing. However > 10 seconds or so after the connection is re-established, the music will > pause for a while and a "rebuffering" message will appear. I would > think that if the connection has been re-established, the music wouldn't > need to stop. > > 2. wlanpoke exiting for no reason after a WIFI reset attempt. In the > ncat tcp logs it says nothing but "wlanpoke exiting", but in the logs > stored on the radio there was more info surrounding the exit, but by the > time I got around to saving those logs, they had been overwritten. > > 3. The wlanpoke typically runs for a while before it has an issue, but > the web server with info (I use the slow option) seems to fail with some > regularity. I know that wlanpoke is still running because I can still > see resets happening in the ncat tcp logs. I can SSH in to the radio > and restart the web server and it will start working again. > > BTW, thanks for all of the work on wlanpoke! Thank you for your detailed report: -...none of them have an apostrophe...- The logs would not contain entries with a single quote (a.k.a. used as an apostrophe on a keyboard), because the single quote would cause a fault in the logging function, causing the exit before the log is written. You might see a single quote using any other WiFi client, e.g., a cell phone. A planned update should address this limitation. -...music will pause for a while and a \"rebuffering\" message ...- How long is the pause? What is your signal level and connection speed? Once the connection is reestablished, there might be some additional processing to reestablish the music stream. Consider changing the 6 failed ping threshold to 3 failed pings to reduce the outage by about 8 seconds (2.6 seconds * 3 fewer ping trials), it may do the trick. -...wlanpoke exiting for no reason after a wifi reset attempt- Is the reset attempt from wlanpoke, or using the radio's UI? In any event, the script should not have a fault here. Any assistance in finding the fault would be very helpful. I was running the script in an 'ash shell with debugging enabled' (https://github.com/PomDev2/wlanpoke/issues/7#issuecomment-963230049) to catch an exit that only rarely, but it never did before the power failed and rebooted the radio and stopped the trial run. -...the web server with info (i use the slow option) seems to fail with some regularity- Another user reported this as well on 'github' (https://github.com/PomDev2/wlanpoke/issues/4). That was perhaps never resolved. It is quite a mystery. Too bad it doesn't happen here on my seven radios. For completeness, try the 'quick' option. You can get the full report, and refresh it to get the most up to date info. POMdev's Profile: http://forums.slimdevices.com/member.php?userid=70558 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
POMdev wrote: > > > This "wlanpoke exiting" issue can occur for a variety of reasons, most > of them unknown. However, one reason is the existence of a WiFi access > point SSID containing an apostrophe. This will always cause the current > script to exit because the logging functions do not support an > apostrophe (i.e., single quote) in a name, and the WiFi names are logged > for troubleshooting. This is a limitation of the current software > design, which failed to anticipate things like "Jack's WiFi" as a valid > access point name, oops. > > I have checked the logs and when it scans and lists all of the SSIDs that it finds, none of them have an apostrophe. The only type of special character I see in any of them is a dash "-" or a space. The only issues I am really seeing with wlanpoke are: 1. Even with the default settings of 2 second pings, quick reset disabled, and 6 failed pings before a reset, I usually see the connection re-established well before the music stops playing. However 10 seconds or so after the connection is re-established, the music will pause for a while and a "rebuffering" message will appear. I would think that if the connection has been re-established, the music wouldn't need to stop. 2. wlanpoke exiting for no reason after a WIFI reset attempt. In the ncat tcp logs it says nothing but "wlanpoke exiting", but in the logs stored on the radio there was more info surrounding the exit, but by the time I got around to saving those logs, they had been overwritten. 3. The wlanpoke typically runs for a while before it has an issue, but the web server with info (I use the slow option) seems to fail with some regularity. I know that wlanpoke is still running because I can still see resets happening in the ncat tcp logs. I can SSH in to the radio and restart the web server and it will start working again. BTW, thanks for all of the work on wlanpoke! lemmy999's Profile: http://forums.slimdevices.com/member.php?userid=9284 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
Answer to questions from 'Simplified-instructions-for-Squeezebox-Radio-Wi-Fi-fix' (https://forums.slimdevices.com/showthread.php?114775-Simplified-instructions-for-Squeezebox-Radio-Wi-Fi-fix-(wlanpoke)&p=1039680&viewfull=1#post1039680) lemmy999 wrote: > I am having some success with wlanpoke, but I tried to play music and > after about 8 hours I got the red wifi symbol again. I checked the logs > and during an attempt to reset the wifi, it showed the message "wlanpoke > exiting" or something like that. ... This "wlanpoke exiting" issue can occur for a variety of reasons, most of them unknown. However, one reason is the existence of a WiFi access point SSID containing an apostrophe. This will always cause the current script to exit because the logging functions do not support an apostrophe (i.e., single quote) in a name, and the WiFi names are logged for troubleshooting. This is a limitation of the current software design, which failed to anticipate things like "Jack's WiFi" as a valid access point name, oops. There is a proposed fix, which you can perhaps make yourself as a workaround, shown in a later message on https://github.com/PomDev2/wlanpoke/issues/7. This has not been included into the development or release packages because there have been a couple of other exiting occurrences which are/were being investigated, so far without success. It looks like the development branch should be updated with this fix. To complicate matters, the development branch includes various options for fast reset, none of which are fully satisfactory, but which don't seem to cause any harm, either. This might be easier than simplified instructions for applying the workaround to the existing script. Yeah, I've talked myself into it. Look for the workaround in the development branch. If you don't care to use that branch, apply the workaround manually. Alternately, ask your neighbors to remove their apostrophes (single quotes) from their WiFi SSIDs. A thread was started for simplified instructions, a worthy endeavor, but I'm afraid it is kind of messed up now with all this tech talk. ralphy wrote: > 'POMDev had been working on backporting an atheros driver to support the > radio's wifi hardware' > (https://forums.slimdevices.com/showthread.php?109953-WiFi-connection-unstable-lost-on-three-Radios&p=1014039&viewfull=1#post1014039). > However, I haven't seen any updates on this recently. ... The back-porting sort of works, partially. However, while troubleshooting the code last April, I got the feeling that the driver was too low level, processing packets, and knew very little of the connection condition. The root cause of the failure seems to be in the way the chip firmware works, but this is completely closed source, including the chip documentation. This might be happening during the very (too?) frequent network channel scans. I would consider reverse engineering the firmware code, but, without the chip documentation and understanding of the registers and hardware, this is too daunting. Without manufacturer support, it doesn't seem practical. Accordingly, work on higher level software, such as the client and supplicant, might be the way to go. POMdev's Profile: http://forums.slimdevices.com/member.php?userid=70558 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
rojikewl wrote: > Hi mankan and POMdev. FYI, I have just started a new thread describing, > step-by-step, how I installed wlanpoke on my Squeezebox Radios. The fix > has restored their Wi-Fi connectivity. Good luck mankan and thank you, > POMdev. Thanks for this. I hope it helps those who prefer not to deal with the software's manual.txt's lengthy discussions and instructions. The wlanpoke wireless connectivity loss mitigation software on GitHub has been unchanged since April 18, 2021 (Version 0.8.5.5) on the development branch, with the main branch (0.8.4.1) from April 8, and latest release the same 0.8.4.1. Your instructions download the main branch, which may or may not be ahead of the latest release at any point in time. Downloading the main branch has the great advantage of downloading a zip file with no version information in the file name, which means the instructions don't have to change much or at all for newer versions, unless some new version requires some additional or changed step, which is unlikely, since, for safety, the software by default opts out of most options (e.g., the web server). Still, it may be a good idea to have dated and versioned simplified instructions on a wiki page or other public document, or as an attachment (zip file) on your forum topic in a post introducing a new instructions version. These would include any changes you wanted to make in response to a few pages of queries or comments on 'your forum topic' (https://forums.slimdevices.com/showthread.php?114775-Simplified-instructions-for-Squeezebox-Radio-Wi-Fi-fix-(wlanpoke)). POMdev's Profile: http://forums.slimdevices.com/member.php?userid=70558 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
mankan wrote: > Thanks for your work but I don't understand the installation > instruction. I guess we are many users of the Squeezebox radio that have > the same problem. Could you please try to write an "instruction for > dummies"? Hi mankan and POMdev. FYI, I have just started a new thread describing, step-by-step, how I installed wlanpoke on my Squeezebox Radios. The fix has restored their Wi-Fi connectivity. Good luck mankan and thank you, POMdev. rojikewl's Profile: http://forums.slimdevices.com/member.php?userid=62055 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
If you're already running the community firmware, what does going to LMS > Settings> Advanced > Community Firmware for Touch/Radio/Controller and unchecking the box do? Will it revert to the standard firmware or just not update when a new release comes out? JJZolx's Profile: http://forums.slimdevices.com/member.php?userid=10 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
Heuer wrote: > For the first time ever one of my Radio's lost its bass response this > morning despite it running the latest community firmware. Seems the > issue is still not fixed. OK, so that makes at least two of us ! https://forums.slimdevices.com/showthread.php?104141-Bass-amp-problem&p=997227&viewfull=1#post997227 mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
For the first time ever one of my Radio's lost its bass response this morning despite it running the latest community firmware. Seems the issue is still not fixed. Lounge: Transporter>Audio Synthesis DAX Decade>Audio Research LS22>Krell FPB300>Wilson Benesch Act 1's + 2 x Velodyne SPL1000 sub's Kitchen: Touch>Topping DAC>Arcam Solo>Anthony Gallo Micro's+Sub, Joggler controller Office: DAC32>Acoustic Energy AE1 Active's, Joggler controller Garage: Boom>QAcoustics 7000s subwoofer Bedroom: Radio Shed: Radio Workshop: Boom Garden 1: SB3>JVC amp>Rock outdoor speakers Garden 2: SB3>JVC amp>Rock outdoor speakers Heuer's Profile: http://forums.slimdevices.com/member.php?userid=2543 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
fastfwd wrote: > Well, I feel foolish. That fixed it. > > Thanks! It's a known fix. :cool: *Server - LMS 8.2.0 *Pi4B 4GB/Argon one case/pCP v7.0.1 - 75K library, playlists & LMS cache on SSD (ntfs) *Study -* Pi4/pCP 7.0.1/Topping E30 DAC/Ruark MR1 Mk2 *Lounge* - Pi2/pCP 6.0.0 > HiFiBerry DIGI+ > AudioEngine DAC1 > AVI DM5 *Dining Room* - Pi3B/pCP/Bluetooth/Echo Show 8 *Garage* - DAC32 > Edifier speakers *Spares* - 2xTouch, 1xSB Radio. 1xSB3, 6xRPi kidstypike's Profile: http://forums.slimdevices.com/member.php?userid=10436 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
kidstypike wrote: > Restart LMS? Well, I feel foolish. That fixed it. Thanks! -*lms 8.2.0 + edo* on debian jessie- *touch* --> benchmark dac3 hgc --> counterpoint nps200 mkii + nps400 --> meadowlark heron *touch* --> schiit bifrost 2 --> eddie current aficionado --> sennheiser hd800 sdr, zmf verite ziricote and a third *touch* for remote control, and a *radio*, and a couple *sb3*s and a *transporter* somewhere fastfwd's Profile: http://forums.slimdevices.com/member.php?userid=62073 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
fastfwd wrote: > LMS is the latest nightly of 8.2. > > Squeezebox Radio was running 7.x (the last official firmware) with the > patch to recognize LMS 8.x. All was fine. > > A few days ago, I factory-reset the Radio and updated it to Community > build 8.0.1-r16855. Now the server log shows: > > > Code: > > [21-06-02 00:57:03.3778] Slim::Networking::Discovery::getFakeVersion (131) > You're using a SB Radio with a buggy firmware not recognizing this version of Logitech Media Server. > Please consider patching it. Until then we'll try to play nice and return a fake version number... > > > > > Is that expected? Restart LMS? *Server - LMS 8.2.0 *Pi4B 4GB/Argon one case/pCP v7.0.1 - 75K library, playlists & LMS cache on SSD (ntfs) *Study -* Pi4/pCP 7.0.1/Topping E30 DAC/Ruark MR1 Mk2 *Lounge* - Pi2/pCP 6.0.0 > HiFiBerry DIGI+ > AudioEngine DAC1 > AVI DM5 *Dining Room* - Pi3B/pCP/Bluetooth/Echo Show 8 *Garage* - DAC32 > Edifier speakers *Spares* - 2xTouch, 1xSB Radio. 1xSB3, 6xRPi kidstypike's Profile: http://forums.slimdevices.com/member.php?userid=10436 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
LMS is the latest nightly of 8.2. Squeezebox Radio was running 7.x (the last official firmware) with the patch to recognize LMS 8.x. All was fine. A few days ago, I factory-reset the Radio and updated it to Community build 8.0.1-r16855. Now the server log shows: Code: [21-06-02 00:57:03.3778] Slim::Networking::Discovery::getFakeVersion (131) You're using a SB Radio with a buggy firmware not recognizing this version of Logitech Media Server. Please consider patching it. Until then we'll try to play nice and return a fake version number... Is that expected? -*lms 8.2.0 + edo* on debian jessie- *touch* --> benchmark dac3 hgc --> counterpoint nps200 mkii + nps400 --> meadowlark heron *touch* --> schiit bifrost 2 --> eddie current aficionado --> sennheiser hd800 sdr, zmf verite ziricote and a third *touch* for remote control, and a *radio*, and a couple *sb3*s and a *transporter* somewhere fastfwd's Profile: http://forums.slimdevices.com/member.php?userid=62073 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
Heuer wrote: > Instructions here: > https://forums.slimdevices.com/showthread.php?113479-Announce-Community-Firmware-for-Squeezebox-Radio-Touch-Controller-and-LMS-8 Thanks ! jlnicolas's Profile: http://forums.slimdevices.com/member.php?userid=71811 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
Instructions here: https://forums.slimdevices.com/showthread.php?113479-Announce-Community-Firmware-for-Squeezebox-Radio-Touch-Controller-and-LMS-8 Lounge: Transporter>Audio Synthesis DAX Decade>Audio Research LS22>Krell FPB300>Wilson Benesch Act 1's + 2 x Velodyne SPL1000 sub's Kitchen: Touch>Topping DAC>Arcam Solo>Anthony Gallo Micro's+Sub, Joggler controller Office: DAC32>Acoustic Energy AE1 Active's, Joggler controller Garage: Boom>QAcoustics 7000s subwoofer Bedroom: Radio Shed: Radio Workshop: Boom Garden 1: SB3>JVC amp>Rock outdoor speakers Garden 2: SB3>JVC amp>Rock outdoor speakers Heuer's Profile: http://forums.slimdevices.com/member.php?userid=2543 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
Hello, I am new joiner in this community. I did not find the procedure to install a new firmware on the Radio . Please can you help ? thanks jlnicolas's Profile: http://forums.slimdevices.com/member.php?userid=71811 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
Tape was my second Idea ;) i was thinking i just put the adapter in the empty akku slot. but this thing gets a little warm and i don't feel comfortable with it. Tape was an Idea to, but the lights are exactly where it has a slot for ventilation and cooling. Pi4, Pi3, Radios, Receiver, Duet,... mikitil's Profile: http://forums.slimdevices.com/member.php?userid=68091 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
mikitil wrote: > Only thing i'm not 100% happy with, its a disco light to, its leds ar so > bright and pulsing. Perhaps some of this :) : https://www.amazon.co.uk/AmazonCommercial-Electrical-centimeters-Multi-Color-10-Pack/dp/B07YDSNGCT/ref=sr_1_1_sspa?adgrpid=53419212375&dchild=1&gclid=Cj0KCQjwna2FBhDPARIsACAEc_UN9bqg4Bq9x-UOcrB5xHX4WESPvCbP8E1n5oaLsis9z-k90SoYPlUaAlZbEALw_wcB&hvadid=259087081561&hvdev=c&hvlocphy=9045917&hvnetw=g&hvqmt=e&hvrand=4527009925982921836&hvtargid=kwd-21804356&hydadcr=28150_1724812&keywords=electrical+tape&qid=1621875065&sr=8-1-spons&psc=1&spLa=ZW5jcnlwdGVkUXVhbGlmaWVyPUEzRjJJUjAyUTlNUkhIJmVuY3J5cHRlZElkPUEwNDg4MDI4M1BMQ09MSjE0SDhQTiZlbmNyeXB0ZWRBZElkPUEwNDM4ODc1VkJMUjlLMllPTjU5JndpZGdldE5hbWU9c3BfYXRmJmFjdGlvbj1jbGlja1JlZGlyZWN0JmRvTm90TG9nQ2xpY2s9dHJ1ZQ== mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
After i got again and again this red wifi icon and lost connection even if signal was strong and i changed its place as much as possible and cable is not an option i got me one of those vonets wifi to lan adapters http://en.vonets.es/products/VAP11N/ Nice things it can be powered by the radios power adapter itself, so no need for an extra power adapter. And it works now since a week without any signal loss. Only thing i'm not 100% happy with, its a disco light to, its leds ar so bright and pulsing. Pi4, Pi3, Radios, Receiver, Duet,... mikitil's Profile: http://forums.slimdevices.com/member.php?userid=68091 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
Hello, I really appreciate the efforts of the community to resolve the radio/wifi issues. But I think the 2.5ghz bands are just too congested where I am to get a stable connection any more. If/when the community manages to get the radio firmware updated I'll have another go. In the interim, I've found this which operates on 5ghz: https://www.amazon.co.uk/gp/product/B0118SPFCK/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1 and it appears to be working ok. Londonist's Profile: http://forums.slimdevices.com/member.php?userid=71517 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
mikitil wrote: > I finally installed now after i found out how easy it is (after i found > the extension and then found out to activate it also ;) and waited then > 24hours) Feels really snappier and more stable, less Buffering. > > Had this connection losses with original Firmware to. But now, since i > moved the one Radio 30cm which started to lost wifi again and again > (even with great signal from a very near Hotspot, it is now stable since > 3 Days.) Keep fingers crossed ;) > > Installed on 6 BabyRadios and on 1 Controller. And made a reset to. No > need (and no files to) to update the receiver right? > > Two things i have not found: > > 1. Is it still possible to deactivate RC on one Radio with community fw? > With original it was a patch(?), but now i cant see or get them. Think > it was this way, applet installer >install patch installer > install rc > deactivate patch (or like this) but now i get the message to tick > something in this patch installer part and don't see any patch. > > 2. Is it possible to make one louder the other quieter when they all are > synchronized in loudness and play? Think for internet radio there is a > setting but overall? I use some radios, and want to make 2 of them > quieter, because they are in very small rooms. > > Thnx for this optimized firmware, think i get much less buffering here > and it just works great! ;) > > edit: > Bonus question: Is there maybe also a way to reboot all the Radios in > the Network at once? Think sometimes it helps to reboot them all and > then buffering and such things get better. > > Bonus question 2: I have seen now sometimes one or the other Radio > loosing Bass, don't really know how to say this right. All works on this > Radio and then from one moment to another one is loosing Bass but i hear > what is playing just without the deep tones? Not always the same radio > and not only since firmwareupdare. > > Sorry for so many questions and maybe not very good understandable > English ;) The interesting thing is at least on my radios that when the radio looses connection with wifi very ofter the sound is very thin, so without any bass. This behavior happened after instaling the community firmware ( and the wlanpoke) So it seems more people are experiencing this behavior. seth_space's Profile: http://forums.slimdevices.com/member.php?userid=37717 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
Hi, I've factory reset my Squeezebox Touch (now on firmware 7.8) I installed the Community Firmware Plugin in Squeezebox Server. Checked the checkbox in advanced settings. Waited for a week now but no update higher then 7.8 becomes available. My Touch is connected to wired LAN and all connections work. My Squeezebox Server has in the meantime updated a few times to new beta's. I didn't install any kernel patches I only activated the Hires audio output module. Any ideas what I might have missed to get to the latest CFW? Or how I can solve this? Thanks a lot! Jan janpeeters's Profile: http://forums.slimdevices.com/member.php?userid=64816 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
mikitil wrote:
> Bonus question 2: I have seen now sometimes one or the other Radio
> loosing Bass, don't really know how to say this right. All works on this
> Radio and then from one moment to another one is loosing Bass but i hear
> what is playing just without the deep tones? Not always the same radio
> and not only since firmwareupdare.
If you are referring to the issue raised in this thread ("Bass Amp
problem")
https://forums.slimdevices.com/showthread.php?104141-Bass-amp-problem
then I would expect you to find that the community build firmware
effectively fixes the issue. That has been my experience, anyway. (The
community build firmware has been modified to take account of it.)
mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299
View this thread: http://forums.slimdevices.com/showthread.php?t=111663
___
Radio mailing list
Radio@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
I finally installed now after i found out how easy it is (ofter i found the extension and then found out to activate it also ;) and waited then 24hours) Feels really snappier and more stable, less Buffering. Had this connectoin losses with original Firmware to. But now, since i moved the one Radio 30cm which started to lost wifi again and again (even with greart signal from a very near Hotspot, it is now stable since 3 Days.) Keep fingers crossed ;) Installed on 6 BabyRadios and on 1 Controller. And made a reset to. No need (and no files to) to update the reciever right? Two things i have not found: 1. Is it still possible to deaktivate RC on one Radio with community fw? With original it was a patch(?), but now i cant see or get them. Think it was this way, applet installer >install patch installer > install rc deaktivate patch (or like this) but now i get the message to tick something in this patch installer part and don't see any patch. 2. Is it possible to make one louder the other quiter when they all are synchronized in loudness? Think for internetradio there is a setting but overall? I use some radios, and want to make 2 of them quiter, because they are in very small rooms. Thnx for this optimized firmware, think i get much less buffering here and it just works great! ;) mikitil's Profile: http://forums.slimdevices.com/member.php?userid=68091 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
I've been experiencing wi-fi connection issues with my Radios and I thought I'd document my particular solution. I have two Radios which are synchronised as a L/R pair. Their wi-fi connectivity is generally good, although the one that is furthest away from the router occasionally needs a repair. I decided I would update to the Community firmware a couple of days ago. After the update both Radios would not keep a connection to wi-fi. After a reboot, they would quickly show a blue wi-fi icon, then a red icon, within a few minutes of the reboot. The Radios would also sometimes lockup and display a system error message on reboot. This happened even when I moved both Radios next to my TP-Link AX6000 router. I assumed that this was an issue with the Community firmware so reverted back to stock firmware. I had to do this using an ethernet connection as the wi-fi was unusable. Even on ethernet one of my radios locked up. After I had reverted the issue still remained, which wasn't what I had expected. With stock firmware I didn't see a blue wi-fi icon, it went straight to red. I then started reading some threads on the forum and found the information about connectivity issues and POMDev's wlanpoke script. I gleaned from the forum that the culprit seemed to be other wi-fi devices, possibly ax devices. I then noticed that there was a new SSID in my list of available connections on my phone called MESH_2. I live in a terraced house and the neighbours on one side have recently moved out so there is no wireless network on that side. I know the SSID of the other side's network and that was the same and I would be very surprised if it had changed. I then remembered that I had upgraded the firmware on my TP-Link AX6000 router recently and the Radio wi-fi connection issues had only happened after that. The updated version of the firmware v1.2.1 adds a feature called OneMesh which is enabled by default. It is possible to disable OneMesh, so that is what I did. As a result the Radios connected flawlessly and have been playing successfully for an hour, so back to working as I would expect. badboygolf16v's Profile: http://forums.slimdevices.com/member.php?userid=19486 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
And they're down again. badboygolf16v's Profile: http://forums.slimdevices.com/member.php?userid=19486 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
... and it is happening again today ... blason's Profile: http://forums.slimdevices.com/member.php?userid=8688 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
I have the same issue today on one of my radios. The other radio and the touch are doing fine. Symptoms are also: blue wifi sign, difficult manual re-connection (takes a while and several attempts to see the networks around), and then no playback although it seems connected. Then after 30 seconds it gets blue again. My SSIDs are not hidden. Reverting to stock firmware (using ethernet) solves the issue. blason's Profile: http://forums.slimdevices.com/member.php?userid=8688 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
kllngtme wrote: > okay, so one more thing I wanted to throw out there. Has anyone else had > wifi issues trying to connect to a hidden SSID since the community > firmware updates have been applied? I saw something done with the wpa > configs in the radios but I wasn't sure what it meant exactly. > > My problem is that the radios just disconnect off the wifi. The wifi > logo will go blue sometimes and or red completely. Signal strength isn't > the issue. I'm noticing the radios seem to continue seeing my non hidden > SSID's but the hidden SSID seems to show no signal when the radio gets > disconnected. I can connect to my non hidden SSID it seems though so I'm > thinking it's just an issue with connecting to hidden SSID's? Anyone > else had anything similar? It's conceivable that you might have trouble with a hidden SSID, due to changes in the version of wpa_supplicant used. But I think I know how to fix that. Which said, I have never tried connecting to a hidden SSID. How does one go about doing it ? If you can tell me, I can go about testing the fix that I think may be necessary. If you're seeing a blue icon, the Radio thinks it has a good network connection, but is having difficulty with connecting to LMS. If red, then it believes that there is not a good network connection mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
kllngtme wrote: > Not for security, I have it hidden so my kids don't try and login to the > Music wifi thinking they can get online or try and bypass the kids > network.. I didn't want it causing issues. I guess I'll need to > reconsider that... I didn't realize hiding it would be an issue.Don't tell > them the password [emoji1] Sent from my Pixel 3a using Tapatalk slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
garym wrote: > and hidden SSIDs provide no security anyhow. They are accessible to > anyone with the right free software. Not for security, I have it hidden so my kids don't try and login to the Music wifi thinking they can get online or try and bypass the kids network.. I didn't want it causing issues. I guess I'll need to reconsider that... I didn't realize hiding it would be an issue. kllngtme's Profile: http://forums.slimdevices.com/member.php?userid=30198 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
slartibartfast wrote: > I think but I could be wrong that hidden SSIDs have always been an > issue. > > Sent from my Pixel 3a using Tapatalk and hidden SSIDs provide no security anyhow. They are accessible to anyone with the right free software. *Home:* Pi4B-8GB/pCP7.x/4TB>LMS 8.1.x>Transporter, Touch, Boom, Radio (all ethernet) *Cottage:* rPi4B-4GB/pCP7.x/4TB>LMS 8.1.x>Touch>Benchmark DAC I, Boom, Radio w/Battery (Radio WIFI) *Office:* Win10(64)>foobar2000 *The Wild: *rPi3B+/pCP7.x/4TB>LMS 8.1.x>hifiberry Dac+Pro (LMS & Squeezelite) *Controllers:* iPhone11 & iPadAir3 (iPeng), CONTROLLER, Material Skin, or SqueezePlay 7.8 on Win10(64) *Files:* -Ripping-: dbpoweramp > FLAC; -Post-rip-: mp3tag, PerfectTunes, TuneFusion; -Streaming:- Spotify garym's Profile: http://forums.slimdevices.com/member.php?userid=17325 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
kllngtme wrote: > okay, so one more thing I wanted to throw out there. Has anyone else had > wifi issues trying to connect to a hidden SSID since the community > firmware updates have been applied? I saw something done with the wpa > configs in the radios but I wasn't sure what it meant exactly. > > My problem is that the radios just disconnect off the wifi. The wifi > logo will go blue sometimes and or red completely. Signal strength isn't > the issue. I'm noticing the radios seem to continue seeing my non hidden > SSID's but the hidden SSID seems to show no signal when the radio gets > disconnected. I can connect to my non hidden SSID it seems though so I'm > thinking it's just an issue with connecting to hidden SSID's? Anyone > else had anything similar?I think but I could be wrong that hidden SSIDs have > always been an issue. Sent from my Pixel 3a using Tapatalk slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
okay, so one more thing I wanted to throw out there. Has anyone else had wifi issues trying to connect to a hidden SSID since the community firmware updates have been applied? I saw something done with the wpa configs in the radios but I wasn't sure what it meant exactly. My problem is that the radios just disconnect off the wifi. The wifi logo will go blue sometimes and or red completely. Signal strength isn't the issue. I'm noticing the radios seem to continue seeing my non hidden SSID's but the hidden SSID seems to show no signal when the radio gets disconnected. I can connect to my non hidden SSID it seems though so I'm thinking it's just an issue with connecting to hidden SSID's? Anyone else had anything similar? kllngtme's Profile: http://forums.slimdevices.com/member.php?userid=30198 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
robho wrote: > Do you have the custom clock applet installed? I've had to reinstall > that applet after a firmware update to get the superdatetime screensaver > to work. Before the reinstall it behaves as if the radio can't turn off. Thank you! That was it. Good catch! kllngtme's Profile: http://forums.slimdevices.com/member.php?userid=30198 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
kllngtme wrote: > Has anyone else had issues with updating the radios and now it wont turn > off? With any update of these updates afterwards I've had to factory > restore to fix not being able to turn it off. any ideas? Do you have the custom clock applet installed? I've had to reinstall that applet after a firmware update to get the superdatetime screensaver to work. Before the reinstall it behaves as if the radio can't turn off. robho's Profile: http://forums.slimdevices.com/member.php?userid=69407 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
Has anyone else had issues with updating the radios and now it wont turn off? With any update of these updates afterwards I've had to factory restore to fix not being able to turn it off. any ideas? kllngtme's Profile: http://forums.slimdevices.com/member.php?userid=30198 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
A milestone has been reached. It has taken a while, but a compiled ar6000.ko device driver is now semi-working. This has been delayed by what was the seemingly simple precedent task of updating the mitigation script taking until last week. Also, the whole poky, bitbake recipe thing and insanely long paths were just daunting. The driver provides a working connection that plays music. When used with the original firmware, it complains about not allowed ioctls used by iwconfig, hesitating, then reporting 0 signal strength, noise and other statistics. It returns all zeros to the wmiconfig getTargetStats, and other oddities. Also Squeezeplay reports "no link," although it shows connections to myscqueezebox.com and the local LMS. The Squeezeplay ui is sluggish, although top reported the usual ~60% cpu. Also, the radio was having trouble finding the remote -65 dBm access point despite any "full reset" of unloading and reloading the driver. This has not happened before, although it may be a coincidence. Interestingly, wmiconfig --version does work, reporting: Driver Rev = 0x22010097(2.2.1.151), ROM Rev = 0x2188(2.0.0.392), Firmware Rev = 0x2102003e(2.1.2.62) The mitigation script calls iwconfig, resulting in irritating serial console messages, so a new logging script gaplog.sh was created to just log outages and recoveries. The affected radio has both a serial and Ethernet connection, so a wlan failure is no problem, and will be monitored and compared to the other radios for outages, and possible recovery measures that work. Now that the host software is compiled and can be debugged, a more thorough investigation into the wireless connectivity loss root causes and early mitigation strategies can be made. First, though, the compiled driver has to be made 100% compatible with the hardware and Squeezeplay, and, perhaps, with the mitigation script. POMdev's Profile: http://forums.slimdevices.com/member.php?userid=70558 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
15 inch is pretty close to ap, try 6 feet. What brand/type ap are you using, has this changed? Are neighbors close by? *SqueezeBoxes:* 1x Transporter (Living room) 1x SB2 (shed), 1x Radio (Kitchen), 1x Boom (Dining room), 1x piCorePlayer (jacuzzi), 1x piCorePlayer (Garden) 1x OSMC + Squeezelite (Movie room), 1x Touch (Study 2), few spare unit's (SB2, SB3, Boom, Touch) *Server:* LMS on Pi3B+ 8.1.2 on PcP 7.0.1 *Network:* Draytek, Netgear Smart Switch 24p, Ubiquiti PoE, 3x Ubiquity edwin2006's Profile: http://forums.slimdevices.com/member.php?userid=66926 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
jc77 wrote: > I added this to each of the Radios. The directory /etc/log was created, > but nothing was created in the directory. AND, in eight hours over > night every one of the Radios went lost wireless and I have to reboot to > get them back. > What information should I grab from NCAT -- since nothing was saved in > the /etc/log directory? Talk about going from bad to worse. Was there any information in ncat? The script is supposed to exit with an error message if it cannot write its status and log files. This might happen if the "-d /etc/log/" setting is missing the trailing '/', although those files might be in the /etc folder with names preceded by "log" such as "logwlanerr.log", "logfping.txt", and so on. The script is quite weak on parameter validation, even with 1548 lines of code (how did that happen?). If the script exits, the radios are on their own. The first thing is to get the logging to work. Try launching from the ssh terminal, and observe the messages, and the various log and status files. You may want to increase the log level. Check the permissions on /etc/log. The script runs as root, so they should be ok, but ... POMdev's Profile: http://forums.slimdevices.com/member.php?userid=70558 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
POMdev wrote: > To troubleshoot this, use the ::-d /etc/log/:: to save the log files > where they will not be lost after a reboot, I added this to each of the Radios. The directory /etc/log was created, but nothing was created in the directory. AND, in eight hours over night every one of the Radios went lost wireless and I have to reboot to get them back. What information should I grab from NCAT -- since nothing was saved in the /etc/log directory? 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 Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
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 Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
jc77 wrote: > > Any suggested changes to script to make keep this one from going > completely offline every 12 hours or so? [Back1] ... > This Radio needs to be restarted after 2-3 days [Kitchen] ... > These two stay online for about a week before needing to be restarted: > [Floater & Back2] ... > Wow, this is a lot. Thanks for the report. This is the first report of a radio requiring a reboot to reconnect since a quick reset related bug caused the script to drop out last month, and you have 4 of them!. There is something happening that is out of the ordinary in your environment. Here, the only outages have been from hardware (power supply connector) failures. 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. Generally, the script will keep trying to reconnect forever, but it limits each trial to a specified amount of time before trying again. 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. On the other hand, something else may be happening (e.g., the script may be exiting), so looking at the logs after a reboot is important. You can zip them and upload them into a new GitHub issue. None of your radios have any Options showing. The 'slow' web server is recommended for monitoring. Change launch in /etc/init.d/rcS.local to: ::/etc/wlanpoke/wlanpoke.sh -W slow -d /etc/log/ &:: and check out http://Back1:8080 (use Back1's IP address if needed). Also, ncat is handy. If you are not using it, disable tcp logging with the ::-x:: option. 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. All the others recover right away. You can increase this time by editing the script (no command line option yet) variables FRWaitSecsMax and FRWaitStepPct, increasing one or both. 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?) 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. It would also be useful for you to track the radios as a whole to see about time of day phenomena. The excellent free Wireless Network Watcher and NetworkConnectLog from Nir Software on your Windows pc will capture the status of the devices on your LAN. This would give you an important "last seen" time to correlate with your log files. 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. POMdev's Profile: http://forums.slimdevices.com/member.php?userid=70558 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
seth_space wrote: > ... > But i am very unsure about the locations of the echo arguments in the > files. especially: in arequest.sh > So a complete example file would be nice. I use the standard wlanpoke > files. OK. See the GitHub 'issue' (https://github.com/PomDev2/wlanpoke/issues/4). POMdev's Profile: http://forums.slimdevices.com/member.php?userid=70558 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
No reboot necessary. Just sometimes gaps in the sound. I set the buffer on the max in LMS ( if it really has some effect, not sure) Strange the webserver is stable for hours now. Normally max 2 hours. But i will try the suggestions on github. seth_space's Profile: http://forums.slimdevices.com/member.php?userid=37717 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
seth_space wrote: > For now it works for >95% and that is a lot more then i had. So thanks > for that already. > The webserver keeps crashing after one or two hours. > You suggested some lines added to a script. > Please explain a bit more in detail (pref a example) to find the cause. Does ">95%" mean occasional gaps in the music, or that you have to reboot the radio to restore a connection (hope it is not the latter)? See the new 'issues' (https://github.com/PomDev2/wlanpoke/issues/4) topic regarding the web server. POMdev's Profile: http://forums.slimdevices.com/member.php?userid=70558 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
I've plug in for community firmware in my Squeezebox server but how to install the latest radio firmware, baby_8.0.1_r16855.zip? How do I install wlanpoke? Thanks in advance, Stefan funio's Profile: http://forums.slimdevices.com/member.php?userid=46872 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
For now it works for >95% and that is a lot more then i had. So thanks for that already. The webserver keeps crashing after one or two hours. You suggested some lines added to a script. Please explain a bit more in detail (pref a example) to find the cause. seth_space's Profile: http://forums.slimdevices.com/member.php?userid=37717 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
seth_space wrote: > This is the recent fping.txt > > Ping 2s3q6f Events, Fails[0..12] 108461s :Qr:62 Fr:44 Wr:0 Wc:0 [ > 34178 33 0 1 0 12 39 1 8:1 9:2 10:1 11:1 12:4 ] > Step 0:0, limit:results: [ 12:0,8,0,12,0,0,0,0,0,0,0,0 18:0,0,0,0,0,0, > 26: 37: 53: ] Wlan: Rate=48 Quality:23/94 level:-72 retries:2 > Gaps:95 @1618778959 -Gap+OK secs: > +570,-44+223,-3+1753,-52+5,-21+9,-18+8,-23+17,-10+5,-19+8,-22+52,-26+14,-22+65,-22+92,-21+49,-21+28,-21+1002,-3+1347,-59+2201, > Resets:40 @1618778959 -Gap+OK secs: > +570,-44+1978,-53+2950,-59+2201,-41+2120,-85+2864,-44+1738,-42+1804,-49+2396,-42+2188,-42+4750,-43+2017,-43+1862,-47+3626,-42+1436, You can see some quick resets in the Gaps report, although at 21-26 seconds, they don't look that "quick" (resulting in a music gap?), and they don't last very long before the next gap. Not being so quick might have something to do with your very low signal level of -72 dBm, long lasting seems to be independent of signal level. The quick reset might be more effective only with higher signal levels. Sill, even with the low signal lever, 44 (or 40) resets in 30 hours is not so bad, considering that others have experienced 8-12 per hour. The 0.8.4.1 version from the main branch and release doesn't display the combined quick and full resets clearly. You can try the 0.8.4.2 or now 0.8.5.5 versions in the development branch for a better understanding. POMdev's Profile: http://forums.slimdevices.com/member.php?userid=70558 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
This is the recent fping.txt Ping 2s3q6f Events, Fails[0..12] 108461s :Qr:62 Fr:44 Wr:0 Wc:0 [ 34178 33 0 1 0 12 39 1 8:1 9:2 10:1 11:1 12:4 ] Step 0:0, limit:results: [ 12:0,8,0,12,0,0,0,0,0,0,0,0 18:0,0,0,0,0,0, 26: 37: 53: ] Wlan: Rate=48 Quality:23/94 level:-72 retries:2 Gaps:95 @1618778959 -Gap+OK secs: +570,-44+223,-3+1753,-52+5,-21+9,-18+8,-23+17,-10+5,-19+8,-22+52,-26+14,-22+65,-22+92,-21+49,-21+28,-21+1002,-3+1347,-59+2201, Resets:40 @1618778959 -Gap+OK secs: +570,-44+1978,-53+2950,-59+2201,-41+2120,-85+2864,-44+1738,-42+1804,-49+2396,-42+2188,-42+4750,-43+2017,-43+1862,-47+3626,-42+1436, seth_space's Profile: http://forums.slimdevices.com/member.php?userid=37717 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
seth_space wrote: > webserver keeps crashing so only a short view: > Squeezebox RadioBAD wlanpoke.sh 0.8.4.1 4/6/2021 launched > 2021-04-17_16:41:38 1618670498 Options: -W slow -Wp 80 -Q 3 logging to > /var/log/ > ... > Ping 2s3q6f Events, Fails[0..7] 2028s :Qr:1 Fr:1 Wr:0 Wc:0 [ 675 > 0 0 0 0 0 1 0 ] > Step 0:0, limit:results: [ 12:0, 18: 26: 37: 53: ] Wlan: Rate=54 > Quality:27/94 level:-68 retries:0 > Gaps:1 @1618672526 -Gap+OK secs: +81,-41+1906, > Resets:1 @1618672526 -Gap+OK secs: +81,-41+1906, I launched the script via ssh on the hardest-hit (54268s: Qr:67 Fr:12) machine here: /etc/wlanpoke/wlanpoke.sh -W slow -Wp 80 -Q 3 &, then "pounded" on it from a Firefox browser window, including odd URLs, but it kept working, even through seven quick resets followed by a full reset. (Firefox is pretty aggressive retrying unresponsive sites.) You frequently experience the server not working, and might be in a good position to fix this issue. Adding some logging would give a clue, e.g., adding several echo `date` \"got (here)\" > /var/log/w.log or something, then looking at the log to see where it stopped. If you want to debug this, the GitHub 'issues' (https://github.com/PomDev2/wlanpoke/issues) tab would be a good place to correspond. If not, there is always ssh cd /etc/wlanpoke ; ./awstats.sh to get the current report. BTW, your "Resets" entry does not show the quick reset despite Qr:1 Fr:1. That's odd. What is expected is Resets:1 @1618672526 -Gap+OK secs: +81,-41+-15,-15+1906,, where the 15s are the time taken by the quick reset. Another mystery. Thanks for testing all this. POMdev's Profile: http://forums.slimdevices.com/member.php?userid=70558 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
webserver keeps crashing so only a short view: Squeezebox RadioBAD wlanpoke.sh 0.8.4.1 4/6/2021 launched 2021-04-17_16:41:38 1618670498 Options: -W slow -Wp 80 -Q 3 logging to /var/log/ Sat Apr 17 17:15:50 CEST 2021 ( 17:15:50 up 12:27, load average: 0.94, 1.06, 1.09 ) eth1 AR6000 802.11g ESSID:"HAX3_Wi-Fi5" Mode:Managed Frequency:2.437 GHz Access Point: 5C:78:xx Bit Rate=54 Mb/s Tx-Power=15 dBm Sensitivity=0/3 Retry:on Encryption key:off Link Quality:27/94 Signal level:-68 dBm Noise level:-96 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 Ping: settings, events, and failed pings [0..n]; Step: full reset results, status; Gaps, Resets: # and recents Ping 2s3q6f Events, Fails[0..7] 2028s :Qr:1 Fr:1 Wr:0 Wc:0 [ 675 0 0 0 0 0 1 0 ] Step 0:0, limit:results: [ 12:0, 18: 26: 37: 53: ] Wlan: Rate=54 Quality:27/94 level:-68 retries:0 Gaps:1 @1618672526 -Gap+OK secs: +81,-41+1906, Resets:1 @1618672526 -Gap+OK secs: +81,-41+1906, seth_space's Profile: http://forums.slimdevices.com/member.php?userid=37717 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
castor_fou wrote: > ... any effect in the number of connectivity losses per day... > I don't follow completely your explanation under Log File Analysis. ... > Ping 2s-1q6f Events, Fails[0..7] 8154s :Qr:0 Fr:27 Wr:0 Wc:0 [ > 2299 10 0 0 0 0 27 0 ] > ...Are you confident we could get an actual solution packaged in > community firmware fixing all our disconnection issues? The number of connectivity losses may go up if the quick reset effects don't last very long, but 'hopefully', those brief outages they will not result in music interruptions. You are experiencing 12 resets per hour, that's high, especially considering your very good signal level of -54 dBm. Too bad the script is so complicated as it is. The modest mitigation portion is just detection, a full "brute force" reset, one of many possible 'quick' resets, and making sure that the os software stack is running (e.g. 'wpa_cli' occasionally disappears, and we relaunch it). Most of the script is data capture, which takes a lot of processing time. Some of the data is for validating the script, but most of it is for evaluating the environment and the radio's response to the outages. It is not practical to do other than the most basic analysis on the radio using a script. So we have to do it ourselves, perhaps by processing the captured data with some (e.g., your) desktop analysis code. Explaining the data in an understandable and concise manner is not easy, and there are so many different cases to explain, especially as the software evolves into new areas of investigation. For example, we are not logging actual music interruptions for correlation to outages, but the most important measure is music interruptions, and is critical to evaluating different mitigation methods. "Confident" would be going too far. The attitude is "Hopeful." The real solution would be for Qualcomm/Atheros to investigate and patch their (by necessity closed) chip firmware, if not to prevent loss of receiver sensitivity then at least to monitor it and offer some much quicker method for resetting or adjusting the systems on the chip so that they do not repeatedly fail to respond to packets. What we can do is build on the expressly open yet unavailable source os driver stack to implement detection and mitigation that can work far more quickly and efficiently than the current mitigation script, so that the usual buffering would make very brief degradations or interruptions unnoticeable. Whether the latter mitigation can be adequately justified, tested, and validated and thus be fit for inclusion into an official software release is for others to decide. POMdev's Profile: http://forums.slimdevices.com/member.php?userid=70558 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
seth_space wrote: > I succeeded in changing the other wifi networks to use only B/G/N on the > 2,4Ghz band. ... > At the moment the radio is stable for 24hours. One problem, the wlanpoke > script stopped working, at least the webpage is unavailable. > Is it possible the script crashed? > > Ping 2s3q2f Events, Fails[0..23] 38819s :Qr:19 Fr:13 Wr:0 Wc:0 [ > 12680 13 1 3 5:2 6:15 12:2 13:1 23:1 ] > Step 3:4, limit:results: [ 4:0, 7:6,0,0,0,6, 11:10,0, 16:8,10,8,16, > 23:8, 33: 47: ] Wlan: Rate=48 Quality:25/94 level:-70 retries:15 > Gaps:38 @1618601255 -Gap+OK secs: > +1212,-3+2170,-4+7410,-3+2718,-3+820,-3+2357,-4+201,-62+17,-21+20,-22+5,-21+14,-21+3288,-64+57,-21+8,-21+20,-19+11,-21+15,-21+14, > Resets:9 @1618601255 -Gap+OK secs: > +16908,-62+3429,-64+1766,-64+2089,-160+2465,-31+3468,-33+1854,-30+2114,-59+1500,-28+2696, > > for now i restarted the script (without the Q parameter) and will post > the results later. To test the quick reset, use just the -Q 3 and no -F option. In two instances in the last few weeks over 7 radios subjected to various tortures, the 'slow' web page was not available. The server just stops if there is a script error. The ahttpd.sh server is launched by but completely separate from wlanpoke. You can get the report without the server from ssh cd /etc/wlanpoke ; ./awstats.sh. Running B/G/N on 2,4Ghz is a start. Did you change the neighbor's, too? You reported 13 full resets in ~11 hours, much better than 9 / hour, and none in the last 4.6 hours. My new wifi-6 AP has been on 2.5 GHz mixed ax for several days now, and when transferring 13GB of data, it caused 2 radios to go offline for extended periods of time. Using ssh to add the BSSID of the new AP to the "badAP" list caused them to calm down. (/lib/atheros/wmiconfig --badAP xx:xx:xx:xx:xx:xx --num=0). Too bad there are only two slots 0 and 1 for that to work, otherwise I could add the 10-11 other wifi-6 BSSIDs that are detectable around here (although at low levels). Six of these is from a single ax mesh household. POMdev's Profile: http://forums.slimdevices.com/member.php?userid=70558 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
I succeeded in changing the other wifi networks to use only B/G/N on the 2,4Ghz band. That resulted in two total freezes of the community build. A normal on/off resulted in an extremely slow system. After a few reboots the radio worked again. Never experienced this before. But the result is nice. At the moment the radio is stable for 24hours. One problem, the wlanpoke script stopped working, at least the webpage is unavailable. Is it possible the script crashed? The last var/log fping.txt Ping 2s3q2f Events, Fails[0..23] 38819s :Qr:19 Fr:13 Wr:0 Wc:0 [ 12680 13 1 3 5:2 6:15 12:2 13:1 23:1 ] Step 3:4, limit:results: [ 4:0, 7:6,0,0,0,6, 11:10,0, 16:8,10,8,16, 23:8, 33: 47: ] Wlan: Rate=48 Quality:25/94 level:-70 retries:15 Gaps:38 @1618601255 -Gap+OK secs: +1212,-3+2170,-4+7410,-3+2718,-3+820,-3+2357,-4+201,-62+17,-21+20,-22+5,-21+14,-21+3288,-64+57,-21+8,-21+20,-19+11,-21+15,-21+14, Resets:9 @1618601255 -Gap+OK secs: +16908,-62+3429,-64+1766,-64+2089,-160+2465,-31+3468,-33+1854,-30+2114,-59+1500,-28+2696, seth_space's Profile: http://forums.slimdevices.com/member.php?userid=37717 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
I have just updated wlanpoke from v0.6.3 to v0.8.4. I will see if quick reset will help in my case. If I understand correctly, I should not see any effect in the number of connectivity losses per day but these reconnections should take less time (and maybe not create music interruptions). I don't follow completely your explanation under Log File Analysis. I have to re-read when kids won't be around. Here is my output for one radio: Code: Wireless LAN Statistics Squeezebox Cuisine wlanpoke.sh 0.8.4.1 4/6/2021 launched 2021-04-15_14:28:40 1618489720 Options: -W slow logging to /var/log/ Thu Apr 15 16:44:41 CEST 2021 ( 16:44:41 up 2 days, 20:36, load average: 1.14, 0.98, 0.98 ) eth1 AR6000 802.11g ESSID:"MUSIC" Mode:Managed Frequency:2.412 GHz Access Point: 28:C6:8E:B3:D4:BD Bit Rate=54 Mb/s Tx-Power=15 dBm Sensitivity=0/3 Retry:on Encryption key:off Link Quality:41/94 Signal level:-54 dBm Noise level:-96 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:3 Invalid misc:0 Missed beacon:0 Ping: settings, events, and failed pings [0..n]; Step: full reset results, status; Gaps, Resets: # and recents Ping 2s-1q6f Events, Fails[0..7] 8154s :Qr:0 Fr:27 Wr:0 Wc:0 [ 2299 10 0 0 0 0 27 0 ] Step 0:0, limit:results: [ 12:0,0,0,0,0,0,0,0,0,0,0,0 18: 26: 37: 53: ] Wlan: Rate=54 Quality:41/94 level:-54 retries:2 Gaps:37 @1618497874 -Gap+OK secs: +175,-4+31,-42+145,-4+38,-41+289,-42+134,-42+122,-41+48,-3+241,-42+183,-41+192,-3+200,-42+6,-4+113,-41+126,-41+218,-41+183,-42+183, Resets:27 @1618497874 -Gap+OK secs: +210,-42+187,-41+289,-42+134,-42+122,-41+292,-42+183,-41+395,-42+123,-41+126,-41+218,-41+183,-42+183,-42+187,-42+122,-41+397,-41+184, recent AP scan results Selected interface 'eth1' bssid / frequency / signal level / flags / ssid 28:c6:8e:b3:d4:bd 2412-51 [WPA2-PSK-CCMP][ESS]MUSIC 24:4b:fe:f5:05:b0 2432-53 [WPA2-PSK-CCMP][WPS][ESS] faidherbe 24:4b:fe:f4:c3:21 2432-70 [WPA2-PSK-CCMP][WPS][ESS] faidherbe Thank you very much @POMdev, you're doing a great job in helping us. Are you confident we could get an actual solution packaged in community firmware fixing all our disconnection issues? castor_fou's Profile: http://forums.slimdevices.com/member.php?userid=67321 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
seth_space wrote: > Both neighbors are using it in a mesh system with only one SSID. During > Corona they are heavy users with online schools and team meetings. > So not an option i guess. I will try the settings according to your > advice. > Btw, a Inssider scan found 16 wifi different SSIDs (<-80dBm) and some > "invisible" the curse of the city ;( > so i tried the agressive way.. > /etc/wlanpoke/wlanpoke.sh -W slow -Wp 80 -Q 3 -F 2 -S 1 & > ... > Ping 1s3q2f Events, Fails[0..3] 499s :Qr:0 Fr:1 Wr:0 Wc:0 [ 132 4 > 1 0 ] > Step 1:0, limit:results: [ 2:0, 4: 7: 11: 16: 23: 33: 47: ] Wlan: > Rate=54 Quality:55/94 level:-40 retries:0 > Gaps:5 @1618423770 -Gap+OK secs: +97,-5+7,-31+21,-4+40,-6+244,-5+39, > Resets:1 @1618423770 -Gap+OK secs: +109,-31+359, Your -F 2 full reset is coming before the -Q 3 quick reset. You might try using the quick reset first, leaving the full reset where it was. If you cannot use quick reset, then disable it. Quick reset > full reset has never been tested, although it doesn't look like quick reset was triggered. It looks like the -F 2 is saving about 10-14 seconds or so. Still, 31 seconds 9 times/hour seems like a lot. Can you time the music interruptions? What service? Can you increase the buffering by the interruption time? Does that keep the music un-interrupted? Looking into the neighbors, the free Nirsoft utility WiFiInfoView for Windows will show you your neighbor's access points and protocols, even without a wifi-6 adapter. They may be agreeable to disabling wifi-6 on the 2.4 gHz band and going back to -n or wifi-4 (wifi-5 or -ac doesn't work on the 2.4 gHz band). They may even be suffering themselves. See this 'FAQ' (https://www.asus.com/us/support/FAQ/1042475) for one manufacturer's instructions. They recommend disabling wifi-6 on the 2.4 gHz band, and other settings. To locate the hidden network, walk around with a smart phone WiFi analyzer and look for increasing signal strengths. POMdev's Profile: http://forums.slimdevices.com/member.php?userid=70558 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
Both neighbors are using it in a mesh system with only one SSID. During Corona they are heavy users with online schools ans team meetings. So not an option i guess. I will try the settings according to your advice. seth_space's Profile: http://forums.slimdevices.com/member.php?userid=37717 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
seth_space wrote: > just installed the wlanpoke script.. it works but intermittent Drop out > of approx 40/45sec before reconect after some time.[ed] > I can see logs in /var/log and i activated the webserver -W slow > ... Link Quality:55/94 Signal level:-40 dBm Noise level:-96 dBm > ... > Ping 2s-1q6f Events, Fails[0..7] 3084s :Qr:0 Fr:8 Wr:0 Wc:0 [ 417 > 0 0 0 0 0 8 0 ] > Step 0:0, limit:results: [ 12:0,0,0,0,0,0,0,0, 18: 26: 37: 53: ] Wlan: > Rate=54 Quality:54/94 level:-41 retries:0 > Gaps:8 @1618416002 -Gap+OK secs: > +291,-47+375,-47+296,-45+323,-44+224,-41+393,-43+264,-44+258,-48+301, > Resets:8 @1618416002 -Gap+OK secs: > +290,-48+375,-47+296,-45+323,-44+224,-41+393,-43+264,-44+258,-48+301, Well, you certainly are getting hammered. Eight full resets in 51 minutes, we might say typical for heavy interference. Your signal levels are excellent. No single ping losses. After some experimenting with wifi-6 here, using a 2.5 gHz wifi-6 client copying 15 GB, more or less completely disrupted 2 of the 7 radios here during the copy time, which wasn't particularly quick, not much if at all better than 802.11ac or n. (However, on the 5 gHz band, wifi-6 was awesome.) A full report of these tests will be made as time allows, but it seems that the wifi-6 is the culprit, and wifi-6 traffic makes it much, much worse. Some suggestions: disable wifi-6 on the 2.5 gHz band. Ask your neighbors to do the same. This may be a problem if their router won't let them disable wifi-6 on 2.5 gHz without doing so on 5 gHz. It might be helpful to scan your environment to identify wifi-6 routers and clients on 2.5 gHz. You can get routers from a windows notebook with a ($20 Intel AX200 implementation) wifi-6 adapter running netsh wlan show networks mode=bssid. Scanning for clients requires a promiscuous (monitor) mode wifi-6 adapter plus software. The AX200 driver does not supported this in Windows, but Linux might. You may benefit from enabling the quick reset function with the -Q 3 option to try the quick reset after the 3rd failed ping. The quick reset has been helpful here, although under some circumstances, the relief given is short lived, and multiple quick resets occur in succession only to be followed by a full reset. If it doesn't work at all, there is no harm done because the full reset comes along at its usual time anyway. If the quick reset is not working for you, because your signal is so strong, you could try to speed up the full reset to reduce the outage. You could advance its activation to work after the 2nd failed ping (aggressive) instead of the 6th, for example. With the default 6 trial, the script waits for 6*2.7=16 seconds or so before resetting. You might cut that down to 6. All of this points to the need for progress at the system driver level. POMdev's Profile: http://forums.slimdevices.com/member.php?userid=70558 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
just installed the wlanpoke script.. it works but intermittent Drop out of approx 40/45sec before reconect after some time.)few minutes) I can see logs in /var/log and i activated the webserver -W slow Wireless LAN Statistics Squeezebox Radio wlanpoke.sh 0.8.4.1 4/6/2021 launched 2021-04-14_17:08:38 1618412918 Options: -W slow -Wp 80 logging to /var/log/ Wed Apr 14 18:00:39 CEST 2021 ( 18:00:39 up 56 min, load average: 2.54, 2.03, 2.04 ) eth1 AR6000 802.11g ESSID:"HAX3_Wi-Fi5" Mode:Managed Frequency:2.437 GHz Access Point: E4:26:xxx Bit Rate=54 Mb/s Tx-Power=15 dBm Sensitivity=0/3 Retry:on Encryption key:off Link Quality:55/94 Signal level:-40 dBm Noise level:-96 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 Ping: settings, events, and failed pings [0..n]; Step: full reset results, status; Gaps, Resets: # and recents Ping 2s-1q6f Events, Fails[0..7] 3084s :Qr:0 Fr:8 Wr:0 Wc:0 [ 417 0 0 0 0 0 8 0 ] Step 0:0, limit:results: [ 12:0,0,0,0,0,0,0,0, 18: 26: 37: 53: ] Wlan: Rate=54 Quality:54/94 level:-41 retries:0 Gaps:8 @1618416002 -Gap+OK secs: +291,-47+375,-47+296,-45+323,-44+224,-41+393,-43+264,-44+258,-48+301, Resets:8 @1618416002 -Gap+OK secs: +290,-48+375,-47+296,-45+323,-44+224,-41+393,-43+264,-44+258,-48+301, seth_space's Profile: http://forums.slimdevices.com/member.php?userid=37717 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
I have one Radio (UE edition, the others are previous gen) out of 3 which sporadically has a very hard time connecting to the Wifi. Once it has connected, it is usually fine except for one single incident where it lost the connection. Is a behavior like this related to what is being discussed here? LMS 8.1.2 - 1613284909 on Synology DS115 (ARM); 3 Radios xrad's Profile: http://forums.slimdevices.com/member.php?userid=71399 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
mrw wrote: > No, which was the first word given in my answer. :) Yes, you did. Dont know how I missed it. Tony SBTouch ♪ SBRadio ♬ Tony T's Profile: http://forums.slimdevices.com/member.php?userid=34544 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
Tony T wrote: > ok, but my original question... No, which was the first word given in my answer. :) mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
ralphy wrote: > If you read the first post in this thread, you'll see that I created it > to discuss development of the community firmware. > > The link provided by mrw is the official thread for the community > firmware release. ok, but my original question (unanswered) was "Is wlanpoke now included as part of the CBRF?" (as there are a lot of posts here about wlanpoke) Tony SBTouch ♪ SBRadio ♬ Tony T's Profile: http://forums.slimdevices.com/member.php?userid=34544 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
Tony T wrote: > Thanks, but I guess I still dont understand what this thread is for > then, if not for the the Community Firmware. If you read the first post in this thread, you'll see that I created it to discuss development of the community firmware. The link provided by mrw is the official thread for the community firmware release. Ralphy *1*-Touch, *5*-Classics, *3*-Booms, *2*-UE Radio 'Squeezebox client builds' (https://sourceforge.net/projects/lmsclients/files/) 'donations' (https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=LL5P6365KQEXN&lc=CA&item_name=Squeezebox%20client%20builds¤cy_code=USD&bn=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted) always appreciated. ralphy's Profile: http://forums.slimdevices.com/member.php?userid=3484 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
Londonist wrote: > ...The SBR had not been able to connect for ages, so I spent some time > changing the settings on the Asus router on the 2.4ghz. When I turned > off protected management frames, the SBR connected to the wifi again. > Attached is the logging from the last 20 mins - three drop outs with > successful reconnects. ... (Funny, the same thing happened to my simple dedicated 'bgn' router purchased last year for the SBs: suddenly one day they wouldn't connect at all. Had to move the radios to the main house AP. Fortunately, after a few days, my environment got quiet and the problems were greatly reduced.) Looking at your log files, you have a second AP (...34:b1) with the same SSID on the same frequency with a signal level of -68 dBm. (BTW, very happy to see the signal levels in dBm instead of 0-255.). Your connected access point signal level just prior to failure at 2021-04-10T16:10:49 was -67 dBm (...34:30), which is very low, oddly, nearly the same as your other access point. There is a discrepancy between the scanned signal level of -63 and the current level of -67. The last scan was apparently well before the failures and not updated in the 24 seconds between the earliest (16:10:25) and latest (16:10:49) scan result entry. After the full reset, the scan results 15 nearby APs. Quite a difference from the just one shown prior to failure. Three disconnects in 20 minutes would be about 9 in an hour, not atypical for heavy interference environments. The recovery time of 49 seconds for the full reset is typical of somewhat weak signal conditions. Try to improve your signal levels. The more recent 0.8.3+ versions have improved reporting, and it is safe to re-enable the quick reset method, which may or may not improve your radio's performance. POMdev's Profile: http://forums.slimdevices.com/member.php?userid=70558 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
mrw wrote: > No. There is no "CBRF" per se. > > The "Community Firmware for Squeezebox Radio/Touch/Controller and LMS 8" > thread is here: > https://forums.slimdevices.com/showthread.php?113479-Announce-Community-Firmware-for-Squeezebox-Radio-Touch-Controller-and-LMS-8 > > The first post has a link to the CHANGELOG. Thanks, but I guess I still don’t understand what this thread is for then, if not for the the Community Firmware. Tony SBTouch ♪ SBRadio ♬ Tony T's Profile: http://forums.slimdevices.com/member.php?userid=34544 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
Re: [SlimDevices: Radio] Community Build Radio Firmware
Just by way of providing additional logging. The SBR had not been able to connect for ages, so I spent some time changing the settings on the Asus router on the 2.4ghz. When I turned off protected management frames, the SBR connected to the wifi again. Attached is the logging from the last 20 mins - three drop outs with successful reconnects. When it initially reconnected I updated the firmware: Player Model: Squeezebox Radio Player Type: baby Firmware: 8.0.1-r16844 +---+ |Filename: logging 10Apr2021.txt| |Download: http://forums.slimdevices.com/attachment.php?attachmentid=34130| +---+ Londonist's Profile: http://forums.slimdevices.com/member.php?userid=71517 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 ___ Radio mailing list Radio@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/radio
