Return time from UPB

[rtarver]

Sat down tonight and wired (well, plugged in a coax) my Sonos Connect to my AV processor so I could get minimal Sonos in the media room. That took all of 5 minutes to connect and define in my Sherbourne. For once, something went super quick and works.

While here in the media room I decided to try and code some more function into my Harmony remote. I'm using a USB-UIRT to receive commands from the Harmony Hub. What I've noticed is that it seems to take ~10 seconds to come back from sending a UPB lighting command. I had to change the FailOnError to False, otherwise the series of commands would die after the first. Now they all execute in series, but there's a huge delay. It seems like the driver is waiting for a response and doesn't get it so fails (or not if I have False set).

Any thoughts on if this is a UPB issue or what? I get similar feeling results if making changes through the field browser.

PS Dean... I'm waiting for Ex Machina to hit the used market. Watched Chappie the other night and it was pretty good too.

[Dean Roddey]

Are you getting the same delays if you just do a command via the field browser?

[rtarver]

Yeah, seems to take 5-8 seconds to get an action, and then another 5 or so seconds for the dialog to return to active.

[Dean Roddey]

Has this not been the case in the past? If not, then it would seem something has changed wrt to the UPB setup or something?

[rtarver]

Pretty sure not (98%?). I have my front landscape lighting of three switches set to go at 2 second intervals. They always worked as designed when triggered.

[Dean Roddey]

That wouldn't have necessarily shown up the problem. If the old one was still struggling along, the event server would just start up a new thread to service the new one, and four or five would be going at the same time, all but the most recent one just waiting until it gives up.

Turn on logging for that one, which logs the start/end times, and see how long they are taking.

[rtarver]

This was simply brightness setting from the field browser

Code:

07/31 23:05:12-Theater, CQCServer, CQCDrv_UPB16Thread10
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.1646, Status/App Status
    Request Report State, DeviceID: 2
}
07/31 23:05:12-Theater, CQCServer, CQCDrv_UPB16Thread10
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.854, Status/App Status
    Sending: SendReportState
}
07/31 23:05:12-Theater, CQCServer, CQCDrv_UPB16Thread10
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.485, Status/App Status
    Sending: <DC4>07146802FF304C<RET>
}
07/31 23:05:15-Theater, CQCServer, CQCDrv_UPB16Thread10
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.854, Status/App Status
    Sending: SendReportState
}
07/31 23:05:15-Theater, CQCServer, CQCDrv_UPB16Thread10
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.485, Status/App Status
    Sending: <DC4>07146802FF304C<RET>
}
07/31 23:05:17-Theater, CQCServer, CQCDrv_UPB16Thread10
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.854, Status/App Status
    Sending: SendReportState
}
07/31 23:05:17-Theater, CQCServer, CQCDrv_UPB16Thread10
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.485, Status/App Status
    Sending: <DC4>07146802FF304C<RET>
}
07/31 23:05:20-Theater, CQCServer, CQCDrv_UPB16Thread10
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.854, Status/App Status
    Sending: SendReportState
}
07/31 23:05:20-Theater, CQCServer, CQCDrv_UPB16Thread10
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.485, Status/App Status
    Sending: <DC4>07146802FF304C<RET>
}
07/31 23:05:22-Theater, CQCServer, CQCDrv_UPB16Thread10
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.854, Status/App Status
    Sending: SendReportState
}
07/31 23:05:22-Theater, CQCServer, CQCDrv_UPB16Thread10
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.485, Status/App Status
    Sending: <DC4>07146802FF304C<RET>
}
07/31 23:05:27-Theater, CQCServer, CQCDrv_UPB16Thread10
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.854, Status/App Status
    Sending: SendDeviceGoToC
}
07/31 23:05:27-Theater, CQCServer, CQCDrv_UPB16Thread10
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.485, Status/App Status
    Sending: <DC4>0A146809FF2264FF00ED<RET>
}
07/31 23:05:30-Theater, CQCServer, CQCDrv_UPB16Thread10
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.854, Status/App Status
    Sending: SendDeviceGoToC
}
07/31 23:05:30-Theater, CQCServer, CQCDrv_UPB16Thread10
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.485, Status/App Status
    Sending: <DC4>0A146809FF2264FF00ED<RET>
}
07/31 23:05:32-Theater, CQCServer, CQCDrv_UPB16Thread10
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.854, Status/App Status
    Sending: SendDeviceGoToC
}
07/31 23:05:32-Theater, CQCServer, CQCDrv_UPB16Thread10
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.485, Status/App Status
    Sending: <DC4>0A146809FF2264FF00ED<RET>
}
07/31 23:05:35-Theater, CQCServer, CQCDrv_UPB16Thread10
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.854, Status/App Status
    Sending: SendDeviceGoToC
}
07/31 23:05:35-Theater, CQCServer, CQCDrv_UPB16Thread10
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.485, Status/App Status
    Sending: <DC4>0A146809FF2264FF00ED<RET>
}
07/31 23:05:38-Theater, CQCServer, CQCDrv_UPB16Thread10
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.854, Status/App Status
    Sending: SendDeviceGoToC
}
07/31 23:05:38-Theater, CQCServer, CQCDrv_UPB16Thread10
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.485, Status/App Status
    Sending: <DC4>0A146809FF2264FF00ED<RET>
}

[Dean Roddey]

Oh, no, I meant enable logging on that front yard light event. That will tell us now long the event is taking to do its thing. That's an option you can set on any event, to cause the event server to log start/end events.

[rtarver]

Done, and tested. But not sure where to find the logged info.

[Dean Roddey]

It goes the logs. You should see the event server posting start/end msgs each time it runs the event.