Bugzilla – Bug 14209
Fab4 sends "power 1" and "mixer volume" commands every two seconds
Last modified: 2009-09-24 05:33:41 UTC
Fab4 at r7077, SBS 7.4.0 SVN 27258 I have a plugin that intercepts power _newvalue commands via addDispatch. That command is being called every two seconds. Turning on command logging, I see that Fab4 is sending "power 1" and "mixer volume 63" (for example) every two seconds. This seems like needless chatter; shouldn't this only happen when activity on the Fab4 (touchscreen, SP-handled IR codes) trigger *changes*? Fab4 also sends a status command every two seconds, which also seems very chatty.
Peter: is the same thing happening with Baby or Controller with 7.4 firmware?
Baby was misbehaving last night, I couldn't get it to connect to my SBS 7.4 instance even after a reboot (but didn't have enough time to investigate more & file a bug on that, sorry) to check its behavior, and I haven't run 7.4 firmware on a controller in a couple weeks now. IIRC, it's the control.command logging you need to turn on to see this. I think Info level is high enough -- this gives about a half dozen lines per command.
Baby at r7671 does the same thing, even when "off".
This is a bigger problem than I first suspected. It looks like it's not possible to change Baby's volume via the CLI! Here's what I just did with Baby and SBS 7.4.0 (up-to-date SVN) - turn on baby - start playing an Internet Radio stream - set volume at 25 with the knob - connect to the CLI interface - issue the command "subscribe mixer volume" - note the frequent reports of "MyMACHere mixer volume 25" - issue the CLI command "MyMACHere mixer volume 10" - note the frequent reports of "MyMACHere mixer volume 25" (as before) That's right, after I deliberately tell SBS to set Baby at volume 10, Baby keeps resetting the volume to 25. I tried sending the command both with the MAC address URI-escaped ("00%3A04%3A...") and not ("00:04:..."). I tried setting the volume as low as 1 and as high as 75, and Baby always rejected it, and never seemed to change the volume even for a moment.
Tried again with all plugins disabled, works fine then. Will re-open if I see this again and appears to be a problem with SBS 7.4. Otherwise, sorry for the bug noise.
FYI for anyone reading this, the problem stemmed from the power _newvalue _noplay command being redefined in Slim::Control::Request as having tags. I had a few 3rd party plugins that intercepted power _newvalue _noplay with addDispatch() but did not specify the has Tags flag. Changing those addDispatch() calls resolved the problem. Again, sorry to trouble you with something that was not an SBS problem.
Peter: thanks for the extra info, and I'm glad you were able to figure out the issue. :)