Jump to content
Flirc Forums

patrick

Members
  • Posts

    5
  • Joined

  • Last visited

  • Days Won

    1

patrick last won the day on June 24 2023

patrick had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

patrick's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Week One Done Rare
  • One Month Later Rare
  • Conversation Starter Rare

Recent Badges

1

Reputation

  1. Yes. I already have the udev file from the AppImage installed; before that it would never report as connected in the bottom left. I also tried running the AppImage as root but the behaviour is the same. When I connect the remote the usb Product string says it is in DFU mode. I take it that is some device firmware update mode? Sep 19 16:16:41 localhost kernel: usb 1-5: new full-speed USB device number 23 using xhci_hcd Sep 19 16:16:41 localhost kernel: usb 1-5: New USB device found, idVendor=20a0, idProduct=0007, bcdDevice= 6.03 Sep 19 16:16:41 localhost kernel: usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 19 16:16:41 localhost kernel: usb 1-5: Product: Skip 1s (DFU Mode) Sep 19 16:16:41 localhost kernel: usb 1-5: Manufacturer: Flirc Inc. Sep 19 16:16:41 localhost kernel: usb 1-5: SerialNumber: 97A646775055344A352E3120FF0B0D0E Sep 19 16:16:41 localhost kernel: hid-generic 0003:20A0:0007.007E: hiddev97,hidraw6: USB HID v1.11 Device [Flirc Inc. Skip 1s (DFU Mode)] on usb-0000:00:14.0-5/input0
  2. When I connect it to the Skip App it shows as connected but clicking 'Sync' says 'An error occurred while synchronizing'. It doesn't seem to log anything to the console when this is happening.
  3. I was able to get the latest AppImage (SkipApp-0.9.95-Beta-x64.AppImage) working using these horrible udev rules cribbed from the ones that ship with Flirc: `SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTR{idVendor}=="20a0", MODE="0666" SUBSYSTEM=="hidraw", ATTRS{idVendor}=="20a0", MODE="0666"` The productID seems to be 0007 but when I included that limit in the rules the app didn't see remote but it worked when I removed it. So keep in mind the above will match any flirc product like the flirc IR dongle thing. The app seems to run okay and sees the remote when it is plugged in. It did crash once at some point but upon restart it didn't crash in the same place. Also, if anyone cares, it seems to store userdata in two places: `~/.config/com.flirc.skip-app/` and `~/.local/share/com.flirc.skip-app/`.
  4. One moment the remote was working fine and then the next time I tried to use it the middle ring light flashed red three times and seemingly no IR signal is sent. I've tried replacing the batteries but that hasn't made a difference. What does three red blinks mean? Is there a way to fix it?
  5. The skip remote and flirc usb arrived. I am able to run the Flirc linux app in fedora but I cannot get it to "see" any button presses from the skip remote. Out of the box, do any of the buttons on the remote actually send a signal? The A B C and light buttons light up as expected (I think) but when the Flirc app is in learning mode it never reacts to any button presses of the skip remote. At the moment I would simply like remote/flirc to do the basic multimedia key events like play/pause etc.
×
×
  • Create New...