EventGhost

I'm not using Windows any more and as EventGhost is Windows-only I'm not actively developing the plugin any more.
I do accept patches though, so go ahead and send me a pull request!

If I knew what was wrong or even how to start looking into how to figure out what the problem is, then I would!

To keep everything active I've forked the repo and plan to support it for the time to come
https://github.com/WoLpH/EventGhost-Onkyo-ISCP-plugin

It's basically abraxxa's plugin with some things fixed and it uses the same guid so the plugin should replace the existing one.

Let me know if anyone has any issues. For the best results, report the issues at Github: https://github.com/WoLpH/EventGhost-Onk ... gin/issues

Install:

1. Download: https://github.com/WoLpH/EventGhost-Onk ... master.zip
2. Unzip the master.zip file to

   Code: Select all

   C:\Program Files (x86)\EventGhost\plugins

3. Restart EventGhost
4. Add the plugin to autostart
5. Configure the plugin so the IP and ports are correct. The default port is 60128

Thanks for taking this on! I've tried it and it works well, thanks.

One thing that would good to fix if possible is, that if the NIC is disconnected it locks up EG, (2nd image), and on restarting it won't connect, (1st image). This means if the PC, or EG locks up then it has trouble re-connecting. You can simulate the crash just by disabling/re-enabling the NIC under adapter settings.

Thanks again!

Well, took a while to get a working testcase up and running but I believe it's fixed with the latest release. Can you see if the issue is solved for you?

To install:

1. Download: https://github.com/WoLpH/EventGhost-Onk ... master.zip
2. Unzip the master.zip file to

   Code: Select all

   C:\Program Files (x86)\EventGhost\plugins

3. Restart EventGhost
4. Add the plugin to autostart
5. Configure the plugin so the IP and ports are correct. The default port is 60128

WoLpH wrote:Well, took a while to get a working testcase up and running but I believe it's fixed with the latest release. Can you see if the issue is solved for you?

Great work, it doesn't get stuck in a loop any more and kill EventGhost.

I can't get it to reconnect, after it loses the connection though. I've tried restarting EG, disabling/enabling plugin, and switching inputs using the http commands on the receiver's IP webpage.

As soon as you send a single command it should reconnect. It did for me at least...

After sending another PWRQSTN command it reconnected and everything worked as before again.

PS: I've tested this in a Windows 8.1 virtual machine

WoLpH wrote:As soon as you send a single command it should reconnect. It did for me at least...

After sending another PWRQSTN command it reconnected and everything worked as before again.

PS: I've tested this in a Windows 8.1 virtual machine

After testing some more, it eventually does reconnect, but I'm not sure if it's just a time thing, or my fiddling.

I didn't try PWRQSTN, but rather the volume up & down, and I'm using Windows 7.

The command shouldn't matter, trying to send any command should trigger a reconnect automatically.

What is the result when it can't reconnect? Perhaps I can automatically have it retry when you get anything like that.

WoLpH wrote:What is the result when it can't reconnect? Perhaps I can automatically have it retry when you get anything like that.

Exactly the same as the 1st image in my post above:

error sending, retrying
failed to connect
error sending, timeout

download/file.php?id=4551&mode=view


Edit: I left it for quite a while and only disabled/enabled my HDMI output of HTPC and got this:

WoLpH wrote:Well, took a while to get a working testcase up and running but I believe it's fixed with the latest release. Can you see if the issue is solved for you?

To install:

1. Download: https://github.com/WoLpH/EventGhost-Onk ... master.zip
2. Unzip the master.zip file to

   Code: Select all

   C:\Program Files (x86)\EventGhost\plugins

3. Restart EventGhost
4. Add the plugin to autostart
5. Configure the plugin so the IP and ports are correct. The default port is 60128

Thanks for this...I'm about to grab it now. I just came here to ask about this exact issue. I've been using EG for about 3 years with my HTPC setup and I have had this issue happen a handful of times, but couldn't always reproduce it.
One time it appeared I might have had an IP conflict and at least one other time there was something funny about the receiver networking that only a full receiver reset solved.

Today, it happened again and a quick investigation turned up that the network control option on my receiver was disabled! This is really strange because no one touches this and it was working fine last night.
I clearly never went into the setup to disable it, and I don't have any macros that could have done this. It is almost like it disabled itself.

Anyway, I've re-enabled it...and it works, but I hated that EG crash so I'm hoping this fix solves that.

I'll report back with anything else I find, though the issue happens infrequently (though it does appear to have happened twice in 2 days).

While the Onkyo's are great receivers in terms of audio quality and all, the networking system and the menu system are definitely buggy at times. Not much you can do about it however, just hope it doesn't break too often and if it does just remove the power for a couple of minutes and it will work again.

I've been seeing the following get logged in my EG log every 15 seconds:

2015-10-08 17:01:33 EVENT: OnkyoISCP.NLS 'C-P'
2015-10-08 17:01:33 EVENT: OnkyoISCP.NLSC-P

According to the ISCP sheets "NLS" is Net/USB List Info.

It appears that C = "Cursor Updated Info" and that P = "Page information update", but I really don't know what these mean

I have no idea why these started appearing, I don't recall they used to be there. This is happening when the receiver is on or off (standby) and tuned to my HTPC input (not Net or USB).
It probably happens on other inputs, point being it isn't on Net/USB, so why is it constantly sending updates about NLS?

Does anyone else see this? Is it a normal? Any idea to disable?

It doesn't appear harmful so I'd suggest just leaving it...

It's probably just some random broadcast

WoLpH wrote:It doesn't appear harmful so I'd suggest just leaving it...

It's probably just some random broadcast

That i didn't get before.... so trying to figure out what's causing it...
I'm thinking there is a good chance a setting changed on my receiver to start it, but not sure what it could be.