EventGhost + Snapstream Firefly = disabled @ startup!

[stisev]

Does the remote work right with a 100% snapstream setup?

I have never had any kind of issues with my FireFly and I have been using it for over a year at least.

Do you mean with the Firefly Bloat-Software installed? Yes, the remote works fine. It's just with EG.

EDIT: Apparently 0.3.5 has the same problem, BitMonster. Ignore my previous post.

I need to figure out what's going on. If there any debug versions like I mentioned earlier, please let me know.
Thanks
Sev

[stisev]

I THINK I figured out the problem -- the Snapstream Firefly doesn't like to be run on USB2.0 ports. I ended up switching it to a USB1.1 port


Other people apparently had similar problems:
http://forums.snapstream.com/vb/archive ... 17694.html
http://forums.snapstream.com/vb/archive ... 21986.html


I'm still not sure if this completely fixes my problems, but I'll keep you guys posted.

[stisev]

I'm almost positive this is not driver related. Basically, the remote works, but on startup, eventghost doesn't detect the remote. When I close/reopen EG, the remote is detected just fine.

There must be a solution to this.

[CollinR]

Does it complain if you disable the plugin?

If so you might enable it after a startup timer.

[stisev]

Does it complain if you disable the plugin?

If so you might enable it after a startup timer.

Hi Collin,

What do you mean by "disable the plugin"?
Also, how would it enable it after a startup timer?

Thanks
Sev

[CollinR]

Timer plugin must be installed.

The Timer: Should be copy/pasted into the Autostart section.

Code: Select all

<?xml version="1.0" encoding="UTF-8" ?>
<EventGhost Version="908">
    <Action>
        Timer.TimerAction(u'EnableRemote', 0, 1, 30.0, u'EnableRemote', False, True, 1, u'00:00:00')
    </Action>
</EventGhost>

The enable macro:

Code: Select all

<?xml version="1.0" encoding="UTF-8" ?>
<EventGhost Version="908">
    <Macro Name="Enable: Plugin: X10 Remote" Expanded="True">
        <Event Name="Timer.EnableRemote">
        </Event>
        <Action>
            EventGhost.EnableItem(XmlIdLink(6))
        </Action>
    </Macro>
</EventGhost>

Edit: You must disable the X10.Remote plugin BEFORE you save your config, this way EG will startup with it disabled at the next startup. Otherwise this wouldn't do anything. Bitmonster probably knows a better way to do this, maybe he will chime in.

[stisev]

Collin,

I managed to paste that first item (timer). I disabled the Snapstream remote in EG.

Here's the error I get when I reopen EG

Code: Select all

---> Welcome to EventGhost <---
Error in Action: "Timer.TimerAction(u'EnableRemote', 0, 1, 30.0, u'EnableRemote', False, True, 1, u'00:00:00')"
Traceback (most recent call last) (1129):
  File "D:\Applications\EventGhost_equinox\eg\ActionClass.py", line 150, in CallWrapper
  File "D:\Applications\EventGhost_equinox\plugins\EventGhost\__init__.py", line 81, in __call__
  File "<string>", line 1, in <module>
NameError: name 'Timer' is not defined

I have no idea how to insert the second paragraph of code.


BITMONSTER
I think this may be EG related. I found that ON STARTUP when I double clicked
Plugin:X10: Snapstream Firefly, switched from "Snapstream Firefly" to "X10" in remote type then BACK to "Snap.. firefly" and clicked APPLY and OK, the remote worked.

Also, my SS (Snapstream) IR sensor's red light doesn't go on on startup until EG is restarted. Then it runs fine.

[stisev]

Colin, Bitmonster,

Is there any way to do the following:

1) Force EG to WAIT 30 seconds before issuing the following...
2) change the x10 plugin from SS (snapstream) FF(firefly) > Generic X10 > back to SS FF??

Whenever I do this, EG recognizes my remote and works perfectly.

[CollinR]

You might try just adding in a "Wait some time" for 30 seconds and see if that helps.

In your Autostart, reorganize them so the timer loads first then whatever other plugins you use, then insert the wait some time

Code: Select all

<?xml version="1.0" encoding="UTF-8" ?>
<EventGhost Version="908">
    <Action>
        EventGhost.Wait(30.0)
    </Action>
</EventGhost>

then have your Firefly plugin load last.

This will cause 30 seconds of nothing before it loads the FireFly plugin, hopefully you'll get the same basic effect.

Really I should have had you try that first instead of the startup disabled and enable it after some time.

[Bitmonster]

Switching the remote in the plug-in configuration simply has an effect, because it restarts the plug-in and therefore a second attempt to start/connect to the driver is made. The same happens if you disable/enable the plug-in. But this is no solution. To repeat myself: You have a problem with your driver or hardware.

At least dozens of EG users are using X10 based remotes and nobody had a problem like this (or at least it disappeared as soon as they installed a proper driver). And I guess a bunch of them are using a FireFly and also never had any problems like this.

All I can suggest is to reinstall the generic driver (x10setupnovideo.exe) as long as needed. Verify that a single x10nets.exe process (and not two) is starting up correctly as soon as the X10 plug-in starts up.

[CollinR]

2nd on the drivers being the root cause.

My LED comes on as soon as the device is attached, it doesn't care if EG is running or not.

[stisev]

CollinR, just to let you know, I think your 30 second WAIT script worked. Now the driver is recognized at every startup so far. I'll let you guys know if it changes/what happens.

[stisev]

Hi guys,

Special thanks to you Colin for sending over the WAIT script. It seems to have worked on about 12 restarts.

[CollinR]

No problems glad it worked for you, You should probably keep troubleshooting the source though. It's somewhere in MS and it's drivers.

This is just odd, never seen/heard of this before...

[stisev]

No problems glad it worked for you, You should probably keep troubleshooting the source though. It's somewhere in MS and it's drivers.

This is just odd, never seen/heard of this before...

I've seen it once before here: http://www.eventghost.org/forum/viewtopic.php?t=378

His was fixed magically. As long as the wait script works, I'm cool with it . I tried very very hard to get to the root cause, but it didn't help.