Please fix this error

[randy]

Dirk;

Your program created an error type so large that it now has screwed up my entire log display.



If you notice the "Type" field is actually the error, so now my type filter dropdown is so wide as to make the page hard to read.

[dcorsus]

Dirk;

Your program created an error type so large that it now has screwed up my entire log display.

[ATTACH]58819[/ATTACH]

If you notice the "Type" field is actually the error, so now my type filter dropdown is so wide as to make the page hard to read.

Unless there is a typo somewhere in this specific error, the error logging has been the same for the last 6~8 years, so I fail to see how it screws up anything unless an issue in HS.
I'll dig up this specific error and make sure there isn't a typo in the call. Had it in the past that the # parameters in the call was wrong and the compiler didn't catch it.

Dirk

[dcorsus]

Dirk;

Your program created an error type so large that it now has screwed up my entire log display.

[ATTACH]58819[/ATTACH]

If you notice the "Type" field is actually the error, so now my type filter dropdown is so wide as to make the page hard to read.

Randy, is this complete error, meaning all text? I just checked my code and I can't find this being reported from the Sonos PI, my suspicion is that this might be from the embedded HS server.

The code actually doesn't try to read .wav files but there is a check to see if the file exists and deletes it if it does. However, the action is embedded by catching any exception and there is no error reporting. Then it calls the HS speaker subsystem to convert text to a file (so that subsystem might report an error). After that I tell the Sonos player the URL and now Sonos directly with HS embedded server transfers the file from your HS PC to the Sonos player, so this is the only real place where a read of that file might happen. If you were to key in the URL, you might be able to simulate this.

Dirk

[randy]

Randy, is this complete error, meaning all text? I just checked my code and I can't find this being reported from the Sonos PI, my suspicion is that this might be from the embedded HS server.

The code actually doesn't try to read .wav files but there is a check to see if the file exists and deletes it if it does. However, the action is embedded by catching any exception and there is no error reporting. Then it calls the HS speaker subsystem to convert text to a file (so that subsystem might report an error). After that I tell the Sonos player the URL and now Sonos directly with HS embedded server transfers the file from your HS PC to the Sonos player, so this is the only real place where a read of that file might happen. If you were to key in the URL, you might be able to simulate this.

Dirk

You might be right. Let me dig further before you spend any more time on it.

[randy]

This is all of the errors before the one above.


Jan-09 2:45:15 PM Sonos MyTcpListener.DoAccept received Error = Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

Jan-09 2:45:05 PM Error reading file C:\Program Files (x86)\HomeSeer HS3\html\Sonos\Announcements\Ann_TIME_1.wav: The process cannot access the file 'C:\Program Files (x86)\HomeSeer HS3\html\Sonos\Announcements\Ann_TIME_1.wav' because it is being used by another process.

Jan-09 2:45:00 PM Event 'Run Event' action execution skipped, the conditions applied were not met: Sonos Media Room Rear Speakers ON
Jan-09 2:45:00 PM Event 'Run Event' action execution skipped, the conditions applied were not met: Sonos Master Bedroom Rear Speakers ON
Jan-09 2:45:00 PM Event 'Run Event' action execution skipped, the conditions applied were not met: Sonos Living Room Rear Speakers ON
Jan-09 2:45:00 PM Event Event Trigger "Sonos Sonos Announce"
Jan-09 2:45:00 PM Event Event Trigger "Speak - Announcements Time - Sonos"

The first event triggers a time and temperature announcement, the second takes care of some speaker switching that has nothing to do directly with sonos, it simply tells speakers that are doing something else to connect to the correct Sonos Amp. THe next three events are triggered by that second event and evaluate whether the home entertainment is running in any of three rooms and invoke speakers switching as needed. I Hope to post in detail on my layout as soon as I have the time.

Then the long error followed by a Sonos Error.

Since I can't figure it out, for now I deleted the error so that my log display becomes normal again.

[dcorsus]

This is all of the errors before the one above.


Jan-09 2:45:15 PM Sonos MyTcpListener.DoAccept received Error = Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

Jan-09 2:45:05 PM Error reading file C:\Program Files (x86)\HomeSeer HS3\html\Sonos\Announcements\Ann_TIME_1.wav: The process cannot access the file 'C:\Program Files (x86)\HomeSeer HS3\html\Sonos\Announcements\Ann_TIME_1.wav' because it is being used by another process.

Jan-09 2:45:00 PM Event 'Run Event' action execution skipped, the conditions applied were not met: Sonos Media Room Rear Speakers ON
Jan-09 2:45:00 PM Event 'Run Event' action execution skipped, the conditions applied were not met: Sonos Master Bedroom Rear Speakers ON
Jan-09 2:45:00 PM Event 'Run Event' action execution skipped, the conditions applied were not met: Sonos Living Room Rear Speakers ON
Jan-09 2:45:00 PM Event Event Trigger "Sonos Sonos Announce"
Jan-09 2:45:00 PM Event Event Trigger "Speak - Announcements Time - Sonos"

The first event triggers a time and temperature announcement, the second takes care of some speaker switching that has nothing to do directly with sonos, it simply tells speakers that are doing something else to connect to the correct Sonos Amp. THe next three events are triggered by that second event and evaluate whether the home entertainment is running in any of three rooms and invoke speakers switching as needed. I Hope to post in detail on my layout as soon as I have the time.

Then the long error followed by a Sonos Error.

Since I can't figure it out, for now I deleted the error so that my log display becomes normal again.

If you display all involved actions and/or scripts I could have a look at it. I'm a little suspicious that there is a race condition somewhere in what you try to do. I think the mistake people make is assuming that when the "speak" action completed (even when you set to wait for speak to finish), all of this happens asynchronously. Think of it this way, the "speak action" is being analyzed by the PI and all relevant parameters are placed on a queue. There is a separate queue for each linkgroup. Once the action pops off the queue, players are linked, text is converted to speech, player is instructed to play, wait until the player is done, unlink. If in the mean time announcements come in for other linkgroups, all if this happens in parallel and the timing of it all depends on the execution speed of all involved actions. If an announcement comes in for the same linkgroup, it gets queued and treated when all other prior queue items have completed. So just relying on "waiting for speech action to finish" has no meaning to this PI, I'm sure it has all meaning for HS speak functions.

I suspect the sequence of actions you are executing on, are not following all the time the sequence you may have intended.

So some food for thought for you, hope this helps to think about where the issue is caused. If you turn your debug flag on (and log to disk), look for the playuri action. You see a URL in there. Key that into any browser and try to "lock" the .wav file when you do it. See if you can generate the error. If you can, you should post to HS to fix this because it would mean it is somewhere in their server code.

Dirk

[randy]

Since it has only ever happened once, I think it is not worth either of us expending our valuable time. I have deleted the record from the log database.

If it happens again, I will pursue it further.