Jump to content
Flirc Forums

Leaderboard


Popular Content

Showing content with the highest reputation since 12/07/2018 in all areas

  1. 3 points
    Is there a way to have a profile created that assigns Android Keycodes to remote buttons? I am using an Inteset remote and want to use the android keycodes in the link below to map each button. This will be for full funtionality on a Nvidia Shield TV. https://elementalx.org/button-mapper/android-key-codes/
  2. 3 points
    1) Had the Flirc software loaded on my Windows 8.1 machine and it worked fine, upgraded to Windows 10 and it STILL works. 2) Did NOT have Flirc program loaded on another Windows 8.1 machine, upgraded to Windows 10, installed Flirc program and it will NOT work. When I check the device manager it says that there is a driver problem with the Flirc device. If I start the Flirc program it does not show the device as connected and when I exit it tells me that the program is not working properly and forces a program shut down. Anyone else having this problem or know how to correct the driver problem? Can I obtain the Flirc drives so I can point Windows 10 to them? Thanks in advance
  3. 3 points
    OK. I was able to get it working by right clicking the Flirc device in the Device Manager and select Update Driver Software. Then select Browse My Computer and point it to Program Files (x86) > Flirc > Driver > usb_driver All working good now.
  4. 3 points
    100% confirmed. I just got my own copy of windows 10 yesterday and I will work on solving this over the weekend. I'm very sorry for the inconvenience. The biggest lesson for me, is that I need to start signing up for developer access for windows and mac. Thanks so much, hang in there. I believe you can pair it on another machine and use it in windows 10 just fine, can you confirm? Very Sincerely, Jason
  5. 3 points
    See our knowledge base for help and information https://flirc.zendesk.com/
  6. 2 points
    No, the two are currently virtually identical as far as features. I'll help figure this out. It's likely due to something I didn't catch. Please post a picture of your device manager when you have a moment.
  7. 2 points
    I recently purchased a flirc usb off Amazon.ca. I can't seem to get it working on my Windows 10 32bit system. I've tried manual driver installation, wiping drivers with ghostbuster, and zadig. The flirc usb I have looked different from the one that's sold on the site. I'm guessing Amazon.ca sells an older model? Is this the problem?
  8. 2 points
    Sorry for resurrecting an old thread, however I thought this was sort of related: I recently (few months ago) upgraded my MS Surface Pro 3 to Win10. I also have another SP3 that came with Win10 installed by MS. I also have a Windows7 nano-pc (amd fusion e350 apu based nettop) on which I run Kodi and WMC, which is where I primarily use my FLIRC. Recently, I tried to program the FLIRC on one of my surfaces (don't recall which one). I installed the FLIRC software/gui on the surface and plugged the flirc into it. I was able to program it normally. However, when I then plugged the flirc back into the Win7 htpc box to use as I normally do, it wouldn't work. The solution was to load the FLIRC gui software onto the Win7 htpc box, program it there, and then it worked fine. I know that in the past I had programmed the flirc on the Surface when it was running Win8.1. So something changed with Win10. I've got a decent work-around here, so I'm not complaining or requesting a fix, but I thought this might be a good FYI for you.
  9. 1 point
    I'm looking to buy just the thermal pads for the Flirc Raspberry Pi 3b (regular) case Kodi version, but I can't find them anywhere online.
  10. 1 point
    Is it possible to assign keys from numeric keypad? In full keyboard there's no numeric keypad at all. And second thing, how to list in software every programmed shortcuts (i.e. for editing).
  11. 1 point
    I'm just curious. Did you solve it?
  12. 1 point
    As for me, on https://topspyingapps.com/parental-control-android/ you can find really useful info about android parental control. It's really important to know
  13. 1 point
    Hi guys, If you can't connect to your Flirc (Generation 1) on Windows 10, this guide might help you.If you are uninterested about the possible cause of this problem go ahead and scroll down to "Try this"From the beginning I thought the issue was caused by the software/firmware, plain and simple. As it turns out, that's not it... I've tried versions from v.3.10.0 to latest 3.22.4.and all reported the same thing.After troubleshooting all day long I believe this particular issue has risen all of the sudden, in my case. After two major Windows updates.Everytime A feature update is installed all USB Devices are re-installed. But not always in the same place. If you ever used the Device Manager and checked "Show hidden devices" You've probably seen some grayed out devices. These are devices that aren't currently connected OR they've been installed in another location. So if Flirc was installed on location A prior to an feature update. Flirc might now be installed on location B. Where on location B some other device was previously installed and are now casing mayhem...that is my theory anyways after doing what I did which you now will read about. Try this1. Open the Device Manager by Right-Clicking the Windows Logo on the Taskbar.2. In Device Manager, select View and "Show Hidden Devices"3. Remove Flirc from the USB port and uninstall the software, then remove the Flirc folder.4. In Device Manager, uninstall (Delete, Enter) any grayed out devices in all the areas shown on the picture.5. Restart.6. Install latest Flirc.7. Connect the Flirc.8. If it doesn't work. Try using different driver for your USB controller* Then repeat 1-7.9. Let me know how it goes. * especially If you have an ASMedia controller with native drivers from 2016 Flirc GUI will not work. Confirmed on a fresh Windows install.
  14. 1 point
    Hi all, I bought a Flirc SE. It works great for controlling Kodi, etc. However, I'm trying to use the "SE" functionality of it and actually have it power off/on the computer. When I go into the Flirc software though, to bind power toggle to a button on my harmony remote, the software says that the Flirc is disconnected, in the title bar. Which is weird, given that it definitely works. I've tried fully uninstalling/reinstalling the software and drivers, but no luck. Anything I can try?
  15. 1 point
  16. 1 point
    Ok @jason, I think I figured out what is causing this... I decided to take advantage of my 5 FLIRCs and several computers to swap around different FLIRCs on different computers. It looks like it's an incompatibility between an (older?) BIOS and the newer FLIRC firmwares. The problematic FLIRC actually works fine IN ALL MY OTHER COMPUTERS. I even have another computer that happily uses the newer firmware! (most recently acquired FLIRC) This is what I found: The older firmware FLIRCs (I have 3 out of 5) show this in the dmesg logs (this is from an ACER laptop that accepts the new FLIRC firmware): [ 2.684173] usb 3-1: Product: flirc [ 2.684179] usb 3-1: Manufacturer: flirc.tv [ 3.175146] hid-generic 0003:20A0:0006.0001: hiddev0,hidraw0: USB HID v1.11 Device [flirc.tv flirc] on usb-0000:00:1d.1-1/input0 [ 3.178524] input: flirc.tv flirc Keyboard as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.1/0003:20A0:0006.0002/input/input9 [ 3.240745] input: flirc.tv flirc Consumer Control as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.1/0003:20A0:0006.0002/input/input10 [ 3.241127] input: flirc.tv flirc System Control as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.1/0003:20A0:0006.0002/input/input11 [ 3.241493] hid-generic 0003:20A0:0006.0002: input,hidraw1: USB HID v1.01 Keyboard [flirc.tv flirc] on usb-0000:00:1d.1-1/input1 The 2 newer FLIRCs show this: [ 2.657673] usb 3-1: Product: flirc [ 2.657678] usb 3-1: Manufacturer: flirc.tv [ 3.175787] hid-generic 0003:20A0:0006.0001: hiddev0,hidraw0: USB HID v1.11 Device [flirc.tv flirc] on usb-0000:00:1d.1-1/input0 [ 3.181080] input: flirc.tv flirc Keyboard as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.1/0003:20A0:0006.0002/input/input9 [ 3.240721] input: flirc.tv flirc Consumer Control as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.1/0003:20A0:0006.0002/input/input10 [ 3.241115] input: flirc.tv flirc System Control as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.1/0003:20A0:0006.0002/input/input11 [ 3.241510] hid-generic 0003:20A0:0006.0002: input,hidraw1: USB HID v1.01 Keyboard [flirc.tv flirc] on usb-0000:00:1d.1-1/input1 [ 3.243629] hid-generic 0003:20A0:0006.0003: hiddev1,hidraw2: USB HID v1.11 Device [flirc.tv flirc] on usb-0000:00:1d.1-1/input2 Notice that extra last line? (hiddev1,hidraw2.../input2) all my other computers are happy with that extra device but not that particular one. Other computers have varying dmesg output concerning the recognized device, based on the various BIOSes but this last line is the consistent difference between the new firmware and the older one. Incidentally, the computer with the problem, using an older firmware FLIRC shows this at boot-up: [ 2.910197] usb 2-6: Product: flirc [ 2.910202] usb 2-6: Manufacturer: flirc.tv [ 3.004565] hid-generic 0003:20A0:0006.0001: hiddev0,hidraw0: USB HID v1.11 Device [flirc.tv flirc] on usb-0000:00:04.0-6/input0 [ 3.005672] input: flirc.tv flirc as /devices/pci0000:00/0000:00:04.0/usb2/2-6/2-6:1.1/0003:20A0:0006.0002/input/input5 [ 3.064504] hid-generic 0003:20A0:0006.0002: input,hidraw1: USB HID v1.01 Keyboard [flirc.tv flirc] on usb-0000:00:04.0-6/input1 Notice it doesn't identify the "Keyboard", "Consumer Control" nor the "System Control" devices? but it does recognize input,hidraw1 as "USB HID v1.01 Keyboard". Ok, I hope this helps because I think I'm at the end of what I can contribute here ;-) I guess if no solution is found, I can always swap out an older FLIRC and never upgrade the firmware until this issue is resolved..? Thanks, Daniel P.S. Is it just me but each time I want to log in to this forum, my password isn't recognized and I have to go through the "Forgot password" mechanism. I can then just re-enter the same password again and I am good to go until I log out!?
  17. 1 point
    This is not working, we're messaging hours a part. I'll DM you my private contact info.
  18. 1 point
    ffs! I've been searching for more then 1 hour for an older version of flirc. Because... " [v3.22.4] [gui] Windows driver fixes for gen1 products Does the opposite. Now Flirc software does not work. Says device disconnected BUT ITS NOT! works just fine. So why did I update then, well. I wanted to adjust the input repeat or whats its called but that's impossible now ... so PLZ for the love of GOD dont wipe the net of older version of Flirc. It's always a good idea to have a couple of versions live. So, can I please have, and older version, Unsure on when it stopped working. Haven't updated Flirc for a while. Not sure with generation I have. Mine is see through plastic. Running on Windows 10 latest update. flirc_log.txt
  19. 1 point
    yes, that's exactly how flirc-se works. Also, if you have a regular flirc, record the 'wake' key, and it'll only wake the computer with that paired key. It's on the keyboard controller next to F12
  20. 1 point
    Use volume keys on Media Keys controller in the GUI.
  21. 1 point
    I changed the inter-key delay and the flirc debug still has it at e24. Inter-key at 100 or 1000 doesn't change the value in the debug window.
  22. 1 point
    It can't be zero, that's impossible. Try zero, and then go to advanced, and go to device log. Here is what we are looking for: :e:6221 0,4915,4792,892,1579,893,1578,889,1582,893,741,918,1548,893,1579,892,1579,893,4374,864,769,888,746,866,767,919,719,888,741,892,741,893,1578,1727,1581,891,771,867,766,863 :e:24 0,4938,4792,837,1657,841,1631,841,1630,810,824,841,1630,863,1631,814,1657,836,4401,841,793,815,823,837,797,837,797,836,798,836,797,841,1657,1674,1631,837,797,841,794,815 The :e:24 stands for 24ms since the last pulse train. The :e:6221 stands for 6,221 seconds since the last pulse train ( button press). You want to get that 24ms up to 75, and you're good. Keep playing with the number, checking the Flirc gui, and keep me posted.
  23. 1 point
    You can display all programmed keys using a command line tool. It's been installed together with the GUI. It's called flirc_util. What OS are you using? Regarding the numpad, I'll try to prepare a "plugin" version of it over the weekend.
  24. 1 point
    I finally downloaded the new version but still there's no Full Keyboard with numeric keypad :( And lack of viewing all programmed keys is so awkward. I wonder why it's not implemented? It's so obvious functionality in program like Flirc.
  25. 1 point
  26. 1 point
    Should I look for the new version here: https://flirc.tv/downloads or in another place?
  27. 1 point
    Yes, I've been super swamped with black friday and cyber monday. Super swamped. We have an update that should allow you to do this. I'll try and push this in the next day or so. all credit to @yawor, who whipped up all the code to allow a plugin style architecture.
  28. 1 point
    The basics of how it all works, just in case: Start with the Harmony config since this seems to be tripping you up. You only need to pick one device for your Shield profile, and (ironically enough) you don't want to pick "Shield TV" WITH the Harmony since that profile is for models that have IR (or WiFi/BT if you have the Harmony hub) and you don't want that since you are using a FLIRC. Just pick something that has a lot of buttons available (for flexibility) and won't interfere with any other devices you have. A lot of us here us the ViewTV AT-163 profile. Pick it and name it whatever you want, like "Shield TV" :) Now your Harmony is programmed to send IR signals for all (or at least most) of it's buttons. *It doesn't matter what those signals are* as long as they are each unique and don't accidentally trigger other equipment (which is why the AT-163 is a good choice....unless of course you have one :) ). All that matters is that when you press a button, a unique IR command is blasted out. The FLIRC will do the rest. Now, the FLIRC. The FLIRC dongle takes those discreet IR signals and translates them to commands the Shield TV understands. When you program the FLIRC via its application and assign IR commands to buttons you want to make sure you use the Shield layout first, for the basics, because Jason updated the software with the correct commands the Shield needs. Specifically, the "ok" button now functions correctly cross-app. So choose that profile and manually (don't click "Go" and have it do it automatically, that will map some commands you want for Kodi later twice) click each button, then press the corresponding button on your Harmony remote to map it. Basically, the 4 directions, the "ok" button, the back button, and the home button. Pick the buttons on your Harmony you want to do those functions (should be obvious) and have at it. Once you've done that, bring up the Kodi layout. Now you can program buttons for things like Play, Pause, ff/rw, etc. If you want even more control, skip the Kodi layout and use the full keyboard layout instead. Pull up (or print) this page for reference: http://kodi.wiki/view/Keyboard_controls . That's a complete list of keyboard shortcuts for Kodi. You can assign buttons to whatever keys on the keyboard you want. Don't forget that with most Harmony's you can also create custom buttons if you want to map advanced stuff, like for subtitles. Again, it doesn't matter what IR commands are assigned to the Harmony for each button, as long as it is discreet! The FLIRC is going to take whatever IR signal you sent it and translate that to the correct keyboard command. Doing this will give you: Basic Shield remote functionality across all applications (except voice control, since there's no mic on the Harmony.) Advanced keymap control for apps that support full keyboard commands - like Kodi. Get it?
  29. 1 point
    Okay, no issues here. Maybe let's try and get on a team viewer session.
  30. 1 point
    This is probably unsupported in any way by Jason so please don't report bugs in other threads when using this solution. If you have any problems with this setup it is better to post them here and I'll try to help if I have time to do so. Hi, This how-to is for users who want to build more advanced control schemes using their Flirc devices. It is mainly directed to Windows users because there is no way in Windows to capture input from a single keyboard, but can be done in Linux. But it should be also applicable in other OS-es when used with correct software. The problem is that not everything can be done just by defining a single key combinations. There are applications like AutoHotKey (AHK) or EventGhost (EG) that can capture specific key combinations but there is a problem. Having many buttons on the mapped remote it is sometimes hard to find key combinations that are not used as OS or other apps shortcuts already. By capturing the specific key combination in AHK or EG user basically blocks this combination even on a normal keyboard connected to the PC (as there is no way in Windows to capture only input from one specific keyboard). Here comes HID standard for the rescue. HID keyboards are just one of the many usages of this standard. Because of that the HID standard has been split into multiple usage tables. Standard keys on keyboards use table 7 and in Windows codes from this table are immediately captured by HID keyboard filter driver and are converted into key presses. On the other hand keys like multimedia keys are defined in usage table 12. Codes from this table are not captured by the Windows. Only a few of them are natively supported (like volume, mute, play, pause etc). Flirc GUI and CLI util provide the ability to map only a few of the keys from table 12. Those keys when mapped are not recognized by AHK or EG when used with keyboard input plugins. This gave me an idea to do some experiments. I needed to find out how these multimedia keys are stored in the Flirc which can be checked by inspecting saved config file. After that I checked if I can assign any HID code from the table 12 and I was successful. I've found out that there is a key code which acts as a marker for Flirc to send usage 12 instead o 7. When this marker is found then the actual HID key ID is stored as a modifier. It is possible to use flirc_util to map almost any code from table 12: flirc_util.exe record_api 176 102 where 176 is decimal value of key ID (Play key in this case) and 102 is a marker that tells Flirc that this is key from table 12. Table 12 has more than 256 keys defined but unfortunately Flirc can only hold a single byte value so there is still a restriction in the number of keys. There are also holes in the list of keys in this table which I've used in my own config so I don't have any conflicts with other hardware and software. These are the usable values: 4-31, 34-47, 55-63, 73-95, 103-127, 159, 165-175. There are probably more but I've stopped looking other codes that are not mentioned by the standard. I think that other keys that are in the standard are also usable. Most of them are not natively supported by the Windows but I used these ranges in my case to be on the safe side. The way to record these keys is to change the first value to one in these ranges and record a button to them incrementally. In my setup I've used EventGhost to capture HID events and map them to things I want them to do. It provides some nice features like programmable on screen menus and many plugins for specific apps like XBMC (it uses XBMC RPC API). To capture events from HID device a Generic HID plugin must be used. Unfortunately there is a small problem with this plugin and it sometimes sends multiple HID events on single button press (this is not the same problem as with repeated keys). I have a modifier Generic HID plugin that works very well with Flirc in this mode of operation. I can share it if there is a demand for it. I can also extend the how-to to some basic EG configuration. I haven't used AHK but I know that there is also a way to capture HID events in it and use them to control things. All the numbers I'm referring to are taken from this document http://www.freebsddiary.org/APC/usb_hid_usages.php
  31. 1 point
    Actually, since I'll be tied up most of today, you can give this a shot: https://flirc.zendesk.com/hc/en-us/articles/200712548 The utility has been updated for windows 10. Very Sincerely, Jason
  32. 1 point
    By "modified Generic HID plugin" I mean that I've copied original Generic HID plugin code, changed its internal ID and name (added a suffix to its name) so both plugin versions can coexist in a single EventGhost install and changed the code so it works better with Flirc sending custom HID codes. The EventGhost differentiates between single events (short events) and enduring ones, which can have extended length. The original HID plugin for EG uses only short events so when you hold down the remote button you get a lot of short events. I've modified the code so HID plugin is generating an enduring event for as long as you keep the button pressed, so you only get a single event but it is active as long as you keep holding the button down. That way you can define repeats and long-press actions in the EventGhost without any problems. You can download the plugin here: https://www.dropbox.com/s/j7ajh7rvoa2qpa9/MyHID.zip?dl=0 Go to the folder where you have EventGhost installed. You'll find plugins folder there. Unpack the downloaded zip to the plugins folder (it should create a MyHID folder). You can compare the __init__.py file with the original plugin code in the plugins\HID folder. There are only a few changes so it's easy to check that there is nothing malicious added in the code (even for non-programmers I think). To use the plugin in EG you need to first restart EG for it to see new plugin. Then you add "Generic HID (mod)" plugin to Autostart folder in your EG config. You need to select Flirc from the device list in the plugin config window. There can be more than one device there so you need to do some testing which one works. You can also enter a prefix into Event prefix text input (I've set it to Flirc). I'm also using Remote event mapper plugin where I map Flirc.Button.X (where X is the HID code) events as Remote.YYYY (where YYYY is given button name like Play, Pause etc). That way I don't need to remember under which HID code I have a specific button mapped in Flirc. The rest of the EG config is very specific to my needs. Of course I use XBMC2 plugin to control Kodi using remote API and also I use Task Create/Switch Events plugin to enable/disable actions groups depending on the app in focus (you don't need that if you want to control Kodi out of focus).
  33. 1 point
    Sweet. And it plays Monsters Inc. :)
×
×
  • Create New...