Hi

This is new issue that I have not seen before. On my R8.1 frontend using XBMC my Firefly remote stops working (Linhes forgot which remote I have?)

2 different senario can happen
A.) Selecting a specific show
B) Exiting out of the TV Shows category.

It does not affect my wireless keyboard or XBMC .

To work around I use the keyboard and go back into \Setup \Linhes \ Remotes\ and then I have to reinstall the remote and reprogram the channel id.
I do not have to reboot so that good but I have had to do this a couple of times this week.

Any thoughts on this...

You might need to make some changes to your XBMC lircmap.xml

It controls remote functions within XBMC.

http://wiki.xbmc.org/index.php?title=Us ... ircmap.xml

Thanks for responding to my issue. The solution is as it turns out is rather silly. My remote has a power light on the top which flashes when you press a key. So here is the kicker, I always figured that if the batteries got low the light would get dimmer or completely go out. Nope, unique id in on the remote so when the batteries get tired it forgets the config.

Go figure

I have a different problem with my (RF) Snapstream Firefly...

I have used Hauppauge and Streamzap remotes for years ('cuz they 'just work') Now I have a setup with the Mythbox in the next room so I dusted off the (IR) Firefly used on some early KnoppMyth iterations. (Where it worked fine)

Using the Firefly setup my Firefly works (mostly) but is missing the all-important Escape (and a few other buttons...) which appear (from net research) to be the "code number above 255 is ignored" problem. It seems Lirc exists but that new kernels have remote codes in them too.

Trying to reprogram 'Esc" to lesser needed buttons in 'lircrc-snapstrm.txt' is ignored .... the buttons still perform their original programming ...
Am I going to have to mess with the kernel table /usr/lib/modules/3.6.7-1-ARCH/kernel/drivers/media/rc/keymaps : rc-snapstream-firefly.ko.gz
??

If you are watching a show and want to leave it just press the back button. It will take you backwards thru each screen. If you want to go back and then get to the shutdown menu go back thru as far as your can go thru the screens and press the menu button and there will be options for shutdown, standby, etc...

Unfortunately 'Back' [Backarrow] is one of those buttons that don't work either. I did a button survey and don't have any way out with the remote, and have to use the Mythweb remote to back up or get out.

scancode 0x0000 = KEY_VENDOR (0x168)
scancode 0x0001 = KEY_HELP (0x8a)
scancode 0x0002 = KEY_CLOSE (0xce)
scancode 0x0003 = KEY_TV (0x179)
scancode 0x0004 = KEY_DVD (0x185)
scancode 0x0005 = KEY_IMAGES (0x1ba)
scancode 0x0006 = KEY_AUDIO (0x188)
scancode 0x0007 = KEY_VIDEO (0x189)
scancode 0x0008 = KEY_VOLUMEDOWN (0x72)
scancode 0x0009 = KEY_VOLUMEUP (0x73)
scancode 0x000a = KEY_MUTE (0x71)
scancode 0x000b = KEY_CHANNELUP (0x192)
scancode 0x000c = KEY_CHANNELDOWN (0x193)
scancode 0x000d = KEY_1 (0x02)
scancode 0x000e = KEY_2 (0x03)
scancode 0x000f = KEY_3 (0x04)
scancode 0x0010 = KEY_4 (0x05)
scancode 0x0011 = KEY_5 (0x06)
scancode 0x0012 = KEY_6 (0x07)
scancode 0x0013 = KEY_7 (0x08)
scancode 0x0014 = KEY_8 (0x09)
scancode 0x0015 = KEY_9 (0x0a)
scancode 0x0016 = KEY_BACK (0x9e)
scancode 0x0017 = KEY_0 (0x0b)
scancode 0x0018 = KEY_KPENTER (0x60)
scancode 0x0019 = KEY_A (0x1e)
scancode 0x001a = KEY_UP (0x67)
scancode 0x001b = KEY_B (0x30)
scancode 0x001c = KEY_MENU (0x8b)
scancode 0x001d = KEY_LEFT (0x69)
scancode 0x001e = KEY_OK (0x160)
scancode 0x001f = KEY_RIGHT (0x6a)
scancode 0x0020 = KEY_EXIT (0xae)
scancode 0x0021 = KEY_C (0x2e)
scancode 0x0022 = KEY_DOWN (0x6c)
scancode 0x0023 = KEY_D (0x20)
scancode 0x0024 = KEY_REWIND (0xa8)
scancode 0x0025 = KEY_PLAY (0xcf)
scancode 0x0026 = KEY_FORWARD (0x9f)
scancode 0x0027 = KEY_RECORD (0xa7)
scancode 0x0028 = KEY_STOP (0x80)
scancode 0x0029 = KEY_PAUSE (0x77)
scancode 0x002a = KEY_NEXT (0x197)
scancode 0x002b = KEY_PREVIOUS (0x19c)
scancode 0x002c = KEY_ZOOM (0x174)
scancode 0x002d = KEY_MODE (0x175)
scancode 0x002e = KEY_INFO (0x166)
scancode 0x002f = KEY_OPTION (0x165)
Enabled protocols: NEC RC-5 RC-6 JVC

The color-marked codes are the buttons that are ignored.

I see you are missing this change

http://lists.linhes.org/pipermail/linhe ... 00481.html

The old one missing a lot of buttons but the new one is good

Thanks!

Where does that list go ? You install XBMC, put that list in the xbmc config file, and the remote will work from that list while doing mythtv functions ?

First Assuming R8 or R8.1

Go to

Service Menu\Linhes Settings\Remotes

Remote Cllass: ATI
Remote: snapstream_firefly_all

Receiver: Default

Then click Next and let it find the firefly. If I remember right that is all you have to do to get a single remote working in Myth.

THANK YOU !

THAT was the solution, & got the pertinent buttons working !

The setup I had was Class: Other
Remote: Snapstream firefly

Which produces a partially working Firefly. Your setup got 'em all working !

My problem, of course, was I didn't know the ATI class, & that there were two Firefly solutions !

There was an enhancement last year to enhance firefly functionality and allow for support of up to six remotes via channel id.

http://linhes.org/issues/854

Glad to see your success, The firefly is now supported in Linhes R8 better than ever and all the buttons work!!!

Q. Does the second Firefly setup (that didn't fully work for me) support something, or should it be removed to avoid the sort of confusion I had ?

Anyone that doesn't know it's an 'ATI' is gonna jump on the setup I used.

My net research came across the 'channels' for the Firefly, but I was happy to get one working. As noted, I needed to go through a wall, but usually use a Streamzap and a Hauppauge in the same room.

After a long successful run, I changed out the computer noted above for an IBM 9229, and set it up running 8.1.1.
Setup through 'remotes' was successful and I had the 'firefly' working on HDHR tuners.

Then I added a Hauppauge HD-PVR which works too.

The problem that cropped up is adding an serial port IR blaster for my Dish settop box caused the 'Firefly' to quit working and the IR blaster doesn't change channels either. I used a change_channel.sh code that works in two other (Mythbuntu) machines.

Anyone got some pointers on how the 'Mythvantage' 'remotes' files should refer to each other ?

I appear to have a lircd0 and lircd1 running.

Can run this?

I'll stick the drive with Linhes 811 back in the machine and get back with ya ... thanks !