Reply to thread

Message

<blockquote data-quote="and-81" data-source="post: 235847" data-attributes="member: 11844">OK,I think I see the problem.The blast is failing because the device access has not been started.&nbsp; But there is no error message about why it failed to start ... which means that it was told not to start.This is the code that determines whether to start the device interface.Basically it says this:If you have put the plugin into message mode, don't start the device.If you have enabled the MCE remote (checkbox in config) or you are using the &quot;different remote&quot; feature then start the device.I'm guessing that you have the MCE remote disabled in the plugin, but enabled in MediaPortal...This logic is not applied when in the configuration app, only when MediaPortal itself starts.That is why it's failing.To get the plugin to work you will need to disable the MediaPortal built-in MCE remote support and enable the plugin's remote support.Cheers,</blockquote>

[QUOTE="and-81, post: 235847, member: 11844"] OK, I think I see the problem. The blast is failing because the device access has not been started. But there is no error message about why it failed to start ... which means that it was told not to start. This is the code that determines whether to start the device interface. Basically it says this: If you have put the plugin into message mode, don't start the device. If you have enabled the MCE remote (checkbox in config) or you are using the "different remote" feature then start the device. I'm guessing that you have the MCE remote disabled in the plugin, but enabled in MediaPortal... This logic is not applied when in the configuration app, only when MediaPortal itself starts. That is why it's failing. To get the plugin to work you will need to disable the MediaPortal built-in MCE remote support and enable the plugin's remote support. Cheers, [/QUOTE]

Verification