Charmed Quark Systems, Ltd. - Support Forums and Community

Full Version: Sonos Log Message
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi 

My logs are filling up with "Some fields of this driver got no initial values. Up to the first 8 are displayed". (An entry for each of my sonos speakers)

Is there any way to get rid of this message?

Thanks
Karen
(09-13-2021, 03:04 AM)karenlee Wrote: [ -> ]Hi 

My logs are filling up with "Some fields of this driver got no initial values. Up to the first 8 are displayed". (An entry for each of my sonos speakers)

Is there any way to get rid of this message?

Thanks
Karen
Hi Karen,

This is what happens any time the driver is reset or restarted.  I get them from time to time on a few, but only on startup for the Sonos drivers (I use both of them).  I have learned to ignore them other than possibly a warning sign of something not right if the driver is resetting often.

Blake
They are just a diagnostic, to make it known that some fields are not getting set initially on startup, so that over time they can be found and updated. it won't hurt anything per se, but it does leave them not representative of the state of the device until such time as they get a value set.

If you are seeing a lot, as Blake indicated, then the driver is cycling for some reason.
(09-18-2021, 04:54 PM)Dean Roddey Wrote: [ -> ]They are just a diagnostic, to make it known that some fields are not getting set initially on startup, so that over time they can be found and updated. it won't hurt anything per se, but it does leave them not representative of the state of the device until such time as they get a value set.

If you are seeing a lot, as Blake indicated, then the driver is cycling for some reason.

I've never seen them before the last CQC update - only since I upgraded.  Is there any way to stop them?  I have around 10 speakers, so it fills up my log file and makes it hard to see real issues.
I'd have to update the driver to give those fields initial values. But, the real issue is that the driver is cycling. That can't be good, and if that is fixed then the other issue isn't really important, though it would be good to fix that as well.

Are there any log msgs that would indicate why it might be cycling? What version are you running?
(10-23-2021, 09:56 AM)Dean Roddey Wrote: [ -> ]I'd have to update the driver to give those fields initial values. But, the real issue is that the driver is cycling. That can't be good, and if that is fixed then the other issue isn't really important, though it would be good to fix that as well.

Are there any log msgs that would indicate why it might be cycling? What version are you running?


Fixed with version 6.0.7   Smile Heart