Best practises, event subscription?

[jishi]

Originally Posted by ratty

http://x.x.x.x:1400/status/opt/log/anacapa.trace

If the timestamps matter you'll need to compute the offset of the internal clock from wall time using http://x.x.x.x:1400/status/date

I can't understand why the timestamps isn't correct, and why they don't fix it... It obviously manage to time sync because my alarms fire at the right time...

[ratty]

Originally Posted by jishi

I can't understand why the timestamps isn't correct, and why they don't fix it... It obviously manage to time sync because my alarms fire at the right time...

Sure, the system keeps accurate time via NTP.

I guess the answer to the "why not fix it?" question is "why bother?". These are undocumented internals after all. My guess is that where necessary the tool which Sonos Support uses to mine the diagnostic can do timestamp offset correction. It's pretty trivial.

[controlav]

Originally Posted by ratty

http://x.x.x.x:1400/status/opt/log/anacapa.trace

Totally awesome! Is there a similar log for event errors themselves? (I know I can see the error counts on status/upnp). I'm still having trouble getting the ACKs to work correctly on events longer than a couple of packets in size.

[ratty]

Originally Posted by controlav

Is there a similar log for event errors themselves?

No idea. Application type / subscription errors appear in anacapa.trace. Low level stuff is in dmesg.