Bugzilla – Bug 783
wireless signal strength display doesn't auto-update
Last modified: 2008-09-15 14:37:04 UTC
When you're setting up a wireless SB you want to optimize the wireless signal so you don't get dropouts. However, the signal strength display (settings -> info -> player info -> wireless signal strength - I think that's how you get there) does not auto-update. It should update every second at a minimum. I tried disconnecting my antenna just to verify that it indeed wasn't updating and the percentage remained the same. I backed all the way out to the main menu and went back in - % was the same. I turned the SB "off" and then back "on" - % was the same. I had to reboot the SB to get it to update. I have seen it update without rebooting, but as best as I've been able to tell, it must be that after some lengthy period (10 minutes? really not sure), the SB decides it's stale and does a new reading if I back out of the menu and go back in. I see this as a somewhat serious issue for setting up a wireless SB and could possibly affect first impressions of new customers, so my hope is that this will get fixed very soon.
it seems that the only players that are doiing a regular status update, which includes signal strength, are old display types. of the three squeezeboxen running on my system, the two G's are static wireless strength values, old one updates. d_slimproto shows only the nonG player status frames. all are using firmware 40
it turns out we can fix this simply from the server. sending a blank i2cc message to the player will return a STAT update, which includes a signal_strengh update. doing this every time we request the signal strength from Settings->Information->Player Information->Signal Strength will give us a live result. Note: updates would still work before if the player was playing music at the time. We could check this now and only send the i2cc when idle, but the $client->playmode check would probably take just as long anyway. marking as fixed. please re-open if there are further issues.
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006. I am setting them to targets of 6.2.1 to keep them from showing up in my queries.