EventGhost

jonib wrote:

eman457 wrote: No man, it keeps scrolling down endlessly without connecting to XBMC again as you can see in the log.

The log show it has connected to XBMC. Are you trying to connect to a different XBMC and that don't work? Sorry, I just don't see/understand the problem.

jonib

Yes exactly, that's what I mean. When doesn't "process the events" then I switch over to another XBMC in the XBMC2 plugin config.
That's where you see the yellow event showing "On start". Then what follows is what you underneath it. Continuous logs scrolling!

eman457.

eman457 wrote: Yes exactly, that's what I mean. When doesn't "process the events" then I switch over to another XBMC in the XBMC2 plugin config.
That's where you see the yellow event showing "On start". Then what follows is what you underneath it. Continuous logs scrolling!

OK, try this debug2 version. Hopefully it can show what you are seeing.

Edit: Updated to debug3, hopefully fixed the problem when you change XBMCs to control. So now hopefully we can get back to the original problem.
Edit2: removed debug3 attachment.

jonib

Hi jonib,

The new debug file continues to scroll even when not connected to XBMC.
It does connect/disconnect though, with the same errors as before but continues to fire up events but the scrolling doesn't give me enough time and log space to show you what's happening.
This happened when I started the local XBMC.

eman457 wrote: The new debug file continues to scroll even when not connected to XBMC.
It does connect/disconnect though, with the same errors as before but continues to fire up events but the scrolling doesn't give me enough time and log space to show you what's happening.

You can increase the timeout so it don't scroll as much, change the 3 to for example 10 (seconds) on line 1491 and 1534. Some stuff like disabling the events will take longer after that.

This happened when I started the local XBMC.

I have not seen any problems when getting that error, but I'm trying to fix them, have several already. They are weird as they don't happen always just sometimes.

Looks like you want to find all the bugs, a real bug hunter.

jonib

Hi jonib,

This test is the same before and after I change the time.
eman457.

eman457 wrote:This test is the same before and after I change the time.

Hmm, the volume event seem to be multiple events in one, have not seen that before looks like I need to add support for that. The volume events seem to be the same did you change the volume multiple times or did it repeat by itself?

I should have fixed the OnQuit handling right away, but I was focused on the locking, I'll fix it right away.

Edit: Try this debug4. should fix both of these problems.(hopefully)

jonib

Yes jonib,
I will test it and let you know. Away from the machines at the moment.

eman457.

Hi jonib,

This one (debug4) seems sweeeeeeet
If can stop the ones with "wait for events": "timed out" at the green arrow. See image below for results.
Nice work man!

Regards.

eman457.

eman457 wrote: This one (debug4) seems sweeeeeeet

Nice, but I don't think your original problem is fixed?

If can stop the ones with "wait for events": "timed out" at the green arrow. See image below for results.

Easy, just change "debug = True" to "debug = False" on line 1465.

jonib

Hi jonib,

There is a little bit of a niggle though. It doesn't auto reconnect after reboot.
See image below:

eman457 wrote: There is a little bit of a niggle though. It doesn't auto reconnect after reboot.

And I need the "debug = True" to hopefully see what's happening.

jonib

Ok,
This is what happens. Looks normal with no errors but I believe the plugin is locked, so to clear you have to restart the plugin or Eventghost.

eman457.

eman457 wrote:This is what happens. Looks normal with no errors but I believe the plugin is locked, so to clear you have to restart the plugin or Eventghost.

Based on your log I don't think the plugin has locked up, it just can't detect that XBMC has started again. Try debug5, it should give more info in the log when XBMC starts.

jonib

Hi jonib,
(debug5_file)
The plugin starts up and runs perfect on the local XBMC. See below images for info.
I also noticed a little something when I do an auto search for XBMCs. The plugin doesn't detect the remote XBMC's port no.
Don't know if it's anything to do with it. See below:
Hence???

eman457.

eman457 wrote: I also noticed a little something when do an auto search for XBMCs. The plugin doesn't detect the remote XBMC's port no.
Don't know if it's anything to do with it. See below:

I think we're getting close now, the missing port is probably the problem, as both use the SSDP protocol to detect XBMC, there seems to be something different.

The new debug6 will create a ssdp.log in %appdata%\eventghost\plugins\xbmc2. Please do the "Search" and the other tests you have done. Then attach(or PM me the file) as it should contain the information I need to finally fix the problem. I don't think there is any private/personal information in the ssdp.log file but you can open it and look before sending.

jonib