I've used this plugin for a long time, and it's been super-reliable. BUT recently - possibly after a recent Eisy upgrade - the plug-in has been working perfectly only after it is restarted. At some point after it is restarted, it seems to hang. One crisp symptom is that the 'Update' button works flawlessly after the plugin is restarted, but then a short while later (usually less than an hour), when you click on 'Update' you get a "TCP client read response failed" error. My system is on the latest production version of everything, and I've tried deleting the plugin and reinstalling it in a new slot.

Something must be corrupting the plugin? Any ideas as to what might be causing this?

I love this plugin, in part because it's the only plugin that lets you directly set a specific listening mode (e.g. Dolby Atmos).

It's possible that the plugin isn't compatible with the latest isy firmware release. The author isn't on the forum so there's no way to reach him.

Take a look at github: Repository search results · GitHub

and GitHub - TangoWhiskey1/OnkyoAvrNodeserver: Onkyo/Pioneer AVR Node Server for Polyglot V2

The author is TangoWhiskey1. It looks like he hasn't updated the node server in quite awhile as it was written for PG2

I believe I ported that from PG2 to PG3.

To debug, set the logging level to debug, restart the plug-in and the next time you notice it has hung, download the log and either attach it here are send it to me in a PM. The log does clear and start over at midnight so if it hangs on a Tuesday and you don't notice till Wednesday, the Wednesday log won't show what caused it to hang.

Bob, thank you so much. An unexpected result. An hour after seeing your post, I set the logging level to debug, and restarted the plug-in. Things ran flawlessly for almost 2 days, which was weird because it had not gone that long in recent times. So an hour ago I set the logging level to 'info' and restarted the plug-in. Ten minutes later I once again had the error that I posted above. I guess the good news is that I now have a work-around, i.e. keep the logging level set to 'debug'. Any thoughts? Thanks again for offering to help -Barry

That's kind of the opposite of what I would expect. Setting debug just makes the plug-in add more messages to it's log.

Possibly it's a timing issue, but the error you're seeing indicates that when IoX sends the command to the plug-in, the plug-in never acknowledges it.

If the plug-in is crashing, even the log when it's set to 'Info' should provide some information.