[SOLVED] Observing the Indigo log

How can my plugin get notified that a message was posted to the Indigo log? I know of indigo.server.getEventLogList(returnAsList=True), but how do I know that there are new messages to be read, and how do I read (just) "messages since last time I checked"?

Is there a "subscribeToChanges" variant I missed?

How does SQL Logger do it? I just noticed it doesn't seem to have a plugin.py file at all (it has plugin.so instead). Interesting…

Cheers
-- perry

[matt (support)]

Hi Perry,

I think this is what you want:

Code: Select all

   indigo.server.subscribeToLogBroadcasts()

   def eventLogLineReceived(self, entry):
      ts = entry["TimeStamp"]      # datetime
      typeval = entry["TypeVal"]   # integer
      typestr = entry["TypeStr"]   # str
      message = entry["Message"]   # str
      iserror = (typeval == 1)   # bool

Hi Perry,

I think this is what you want: […]

Yes. Great. Thanks.

Is there any meaning to be squeezed from the typeVal, beyond the error indication?

How hard would it be to get fractional seconds in the timestamp? (It's a datetime which has microseconds, but they're all zero.)

Cheers
-- perry

[matt (support)]

Is there any meaning to be squeezed from the typeVal, beyond the error indication?

The typeVal enumeration is documented on this thread.

How hard would it be to get fractional seconds in the timestamp? (It's a datetime which has microseconds, but they're all zero.)

Internally the Indigo Server doesn't try to track with a resolution smaller than 1 second. This is partially intentional (I don't want to create the illusion that Indigo is meant for realtime control since its scheduling engine isn't and neither are INSTEON or Z-Wave). That said logging with more precision would be useful, especially when trying to debug hardware communication timing problems. So I'll add it to the feature request list.

The typeVal enumeration is documented on this thread.

Oh, that thread. Ah, yes...

Internally the Indigo Server doesn't try to track with a resolution smaller than 1 second. This is partially intentional (I don't want to create the illusion that Indigo is meant for realtime control since its scheduling engine isn't and neither are INSTEON or Z-Wave). That said logging with more precision would be useful, especially when trying to debug hardware communication timing problems. So I'll add it to the feature request list.

That's basically the reason. I hope everybody understands that with all the IPC involved, clocks are, well, approximate. Offering timestamp.microsecond values does not promise microsecond resolution, obviously; but even hundredths of a second would be useful.

There's no practical way to sort log messages with second-resolution timestamps, so we'll just have to assume that they're ordered properly upon retrieval, and delivered in order to the callback. These are reasonable expectations, I hope…

Cheers
-- perry

[matt (support)]

Indigo v6.0.12 is now available and shows more time precision in the Event Log file (but not the Event Log window).