Jump to content
Flirc Forums

yawor

Administrators
  • Content count

    938
  • Joined

  • Last visited

  • Days Won

    64

yawor last won the day on May 22

yawor had the most liked content!

Community Reputation

77 Excellent

2 Followers

About yawor

  • Rank
    Forum Support
  • Birthday 03/03/1983

Profile Information

  • Gender
    Male
  • Location
    Warsaw, Poland

Recent Profile Visitors

5,668 profile views
  1. yawor

    FLIRC v1 Sleep/Wake

    The device log is only for Flirc v2. Flirc v1 doesn't have that capability (and that firmware version), so you can just ignore that message. As for the window size, it's because your scaling configuration in Windows. You can't assign the same remote button two times. If it works with one remote and doesn't with the Harmony, then it seems to be an issue with Harmony configuration, not the Flirc itself. What profile are you using on the Harmony?
  2. @EvilWayz please check your apt sources if they are all correct. https://packages.ubuntu.com/bionic/libqt5xmlpatterns5 According to this, the libqt5xmlpatterns5 in Ubuntu 18.04 depends on qtbase-abi-5-9-5, not qtbase-abi-5-9-0 like in your case. Is this a fresh install or did you upgrade from a previous Ubuntu version? From what I see, the qtbase-abi-5-9-0 was provided by Ubuntu 17.10.
  3. yawor

    FLIRC v1 Sleep/Wake

    I've just tested on a Flirc v1 and seems to be working. The wake/suspend key from the Media Keys controller is only able to suspend the computer though. The WAKE key from the Full keyboard controller wakes the computer properly. Make sure you have the Sleep detection enabled in advanced options in Flirc GUI. Also check the Power tab on each USB keyboard device in Device Manager and make sure that they all are allowed to wake your PC.
  4. Yeah the MiBox protocol is a little complicated. Guys at the JP1 forum were able to create a protocol executors for few types of microcontrollers used in UEI remotes (like I've said, I'm using a Nevo C2 which can be programmed using RMIR). As for the Flirc, you need to remember that it emulates a standard USB HID keyboard. So it should be able to control anything that accepts an USB keyboard input. On the IR side, it can be used with many (but not all) standard protocols, but from my experience it works best with NEC family protocols. So if you program your MX-500 to some device which uses one of the NEC protocols, then it should work.
  5. I'm using Flirc with MiBox but in a mixed way. I'm using a Nevo C2 remote and I've set it up so it uses MiBox's native IR for the keys it supports and custom IR via Flirc for more keys (for example to directly control some features in Kodi). This setup works really well. It should also work with just the Flirc (without native IR) with some work. Btw what options do you have when you program your URC? Can you enter custom pronto hex codes? If yes then I could try generating codes for the MiBox.
  6. yawor

    eye-TV

    I don't really know that software nor I have even access to a mac, but a quick Google search for Eye-TV gave me this page: https://www.geniatech.eu/faq/what-are-the-keyboard-shortcuts-for-eyetv/ It contains a list of keyboard shortcuts needed to control the Eye-TV using a keyboard (a requirement with Flirc). Having that list, you should install and open Flirc application and map selected functions to your remote. For example, if you want to map a Select function (which is controller by enter/return key), you should open a Full keyboard controller in the Controllers menu in the Flirc app, click on the enter key on the virtual keyboard and, when asked by the software, press a button on the remote you want to assign to the enter key. You should repeat this for other buttons on the remote.
  7. yawor

    Transmit IR signal over Flirc in a Raspberry

    Sorry it took so long. I've been able to sit down to this today. First of all, the protocol used by your Sagemcom remote is known as Nokia32. I've been able to decode the IR codes included in the attached file. I've also been able to transmit then from my Flirc and the received signal is correct (I've built myself a little Arduino based IR analyser, so I can record and analyse signals). On the other hand, I can't decode the IR signal data from your first post. The software I'm using doesn't recognise it neither a Nokia32 nor any other known protocol. I think may be somehow malformed. Try sending other signals, for example the ones from the file you've attached, and check if your box reacts to them.
  8. Do you use multimedia keys on the Flirc? If yes then this is probably your window manager on Ubuntu informing you that the key is not mapped to any function or can't be used right now. You can test this by connecting a normal keyboard with multimedia keys and try pressing some of them like Play/Pause etc. The same happens on my Arch Linux with Cinnamon when I press the Play button on the keyboard and no player is running. If, for example, I open the Spotify app, then the Play button on the keyboard works on doesn't show that symbol. This is not a Flirc issue but your OS configuration issue. You need to make sure that the software you're using can properly use multimedia keys or change OS configuration to somehow force them. I rarely use multimedia keys and had no issues with them, so I won't be able to help more than this. --edit-- Alternatively you can check what keyboard shortcuts are supported by the software you're using and map them properly to your remote using Flirc GUI.
  9. yawor

    Added functions to Kodi Profile

    Yeah, there's no notion of controller in the Flirc itself. It only stores key codes and IR hashes. Many people get the wrong idea that they can use only a single controller in the GUI, where in fact the controllers in GUI are only to group different key sets (for example the Kodi controller is just a set of predefined keyboard shortcuts). I think this is more of a documentation issue than anything else.
  10. yawor

    Transmit IR signal over Flirc in a Raspberry

    Could you also try checking the exact model of the box? Does it have a model name or number on the bottom of the device?
  11. yawor

    Transmit IR signal over Flirc in a Raspberry

    Can you open the log window with IR debugging turned on, press some buttons multiple times, then save the log to the file and post it here?
  12. yawor

    Flirc backup and restore

    The configuration on the device is updated automatically every time you record or delete a key or change something in advanced options. Yes, restoring the backup (using load configuration options in the GUI) overwrites previous config stored on the device.
  13. yawor

    On screen keyboard in Windows Media Center?

    Well, Flirc is a keyboard, so maybe WMC thinks it doesn't need to open an on-screen keyboard, because it got the event from the "real" one (to the system there's no difference between real keyboard event and Flirc events). But this is only a theory. I've never used WMC.
  14. yawor

    Transmit IR signal over Flirc in a Raspberry

    Hi, What TV box is that? I'm trying to decode the signal data you've used by I don't recognise the protocol. Is the Flirc IR window pointing in the TV box's direction? Flirc has really good IR receiver but the IR transmitter is not very powerful.
  15. yawor

    Flirc backup and restore

    @Bob Sutton you can name your config files any way you want. The name of the config file doesn't matter to Flirc. It is only a backup of the config. Flirc doesn't load its config from a file as the config is stored ON the device. To make it clear: save configuration is used to backup Flirc's internal config area to a file and load configuration is used to restore Flirc's internal config area from a previously saved file. You don't need to save the config for Flirc to work. The "invalid length" has nothing to do with config files. Can you send me your log with that message?
×