Jump to content
Flirc Forums

Leaderboard

Popular Content

Showing content with the highest reputation since 02/19/2024 in Posts

  1. I have had some similar experiences. I have macros on three of the color buttons that shut off a box and switch to another HDMI, then I would press the new activity key, then do the same color button to power on the box for the new activity. I think I went a little too quick pressing the activity button before the macro had finished and the remote locked up. If I make sure to wait until the LEDs stop before continuing my sequence, it seems okay.
    2 points
  2. There is evidence on the website of there once being Linux support for this Flirc USB thing but the guides are from 2012 and all the links are dead. Will it be coming back? EDIT: after looking more into at the site and these forums support for this thing looks to be dead regardless of platform. back in the box it goes, not sure why it was sold with the skip remote if its no longer supported. EDIT2: Found the latest release at http://apt.flirc.tv/arch/x86_64/ and figured out it needed libhidapi-dev installed from apt sudo apt install libhidapi-dev and running the program with sudo from the terminal. sudo ./Flirc
    1 point
  3. Switch back to the public. Only way to know. I have not done due dilligence with the alpha.
    1 point
  4. Completely off-topic, but nice username, @ytsejam1138 :)
    1 point
  5. it's in the set top box category.
    1 point
  6. Thank you very much ytsejam1138! You were correct, it was not only the default pop-up blocker, but some of the domains/urls being called were getting caught in the pi-hole. Once I had those identified and whitelisted, and enabled pop-ups for the site, only then could I download them. Thank you very much for taking the time to point me in the right direction ^.^
    1 point
  7. Thanks for all the hard work! I'm looking forward to the switching to free up my color buttons for other functions! One other thing I really like about the Skip 1s remote is that the plastic is brushed and not reflective. In my family room, the overhead lights will reflect off reflective remotes, or the screen of the X1, into the corner of my eye, which is distracting. That does not happen with the Skip 1s. Also makes it look more premium in my opinion.
    1 point
  8. Thank you for the update. Learning is just about done and I’ll post a release candidate today or tomorrow. However, what I have posted is very stable. I’m going to work on smart activity switching the second it’s released. Thank you again
    1 point
  9. I am on the latest alpha and the learning function has been very responsive and I am not seeing any hitching or lagging in the app. It seems to be pretty responsive. Few things that could be worked on: It would be nice to have a resizable custom button option to accommodate larger remotes. There is a power on and a power off button, but a power toggle would be a fantastic addition to the button option for remote design. When updating one of the installed devices, it seems to trash prior button combo configs and it would be nice to have them persist. I know the function is still in alpha, it would be nice to have a way to submit learned remotes for db review directly in app. Over all I am quite happy with the functionality and am quite excited to see the future updates. Also, I have attached the json files from the the remotes I had the Skip learn. Ultimea - Poseidon D60.json Vizio - XRT140L (2020).json
    1 point
  10. I'm guessing the simplest way to deal with this issue is when we add long press functionality (or whatever we end up doing). Make a quick tap play and a long press of the same button pause. Or vice versa.
    1 point
  11. Almost done. Finishing and testing.
    1 point
  12. 1 point
  13. Shot in the dark. Go to Settings, Accessibility. Enable Advanced Admin Panel. Click on the wrench in the top right corner that is now there. Go to brands, and add this. Let me know if it works. Peachtree - INova.json
    1 point
  14. To operate logically and according to the user's expectations (from the perspective of a Harmony user), the Skip1s needs to: - Store the state information about the devices it last set - The activity buttons need to be changed so that they can be programed to also initiate the activity The existing activity button functionality only sets the remote's buttons to correspond to given devices for control after which the power button is used to carry out the activity. This is what takes Harmony users by surprise. Their expectation is that an activity button should perform all actions necessary to set up the devices and in addition, the odd behavior when one wants to switch between activities which is the result of having to use the power button to initiate activities. Unless I'm missing something, the Skip1s must power off the devices being used for the current activity before switching to another activity because the power button is used to initiate the activity. First push of the power button turns on and sets inputs etc of the needed devices for the activity and the second push turns them off. This if fine except for when you intend to switch from one activity to another rather than turn the system completely off. If instead the A B C activity buttons initiated the activity AND the Skp1s stored the state information of what it has previously set then one could go from Activity A to Activity B by pushing the corresponding activity buttons. In this case, the Skip1s would know what (if any devices) it turned on last so that if devices needed for Activity B are on it would leave them that way, or if off turn them on. Additionally it would turn off any devices not needed for activity B that had been used for Activity A. The Power button on the Skip1s could retain its ability to be programmed but in general would be used as a global power off for all devices. The only time I use the power button on a Harmony remote is to turn things off, and when I select an activity button on a Harmony all devices needed are turned on or left on and those not needed are turned off. I can understand that the Skip1s may not have been designed to work this way for what ever reason, such as patents, but failing that, the logic for how the remote must be used is not intuitive nor beneficial for most if not all use cases. None-the-less, I really like the Skip1s, but getting my wife to use it has been problematic. Best regards, Brian
    1 point
  15. SkipApp 09.92: When I change an activity with the wizzard, all manually assigned commands are removed from the buttons. This makes only sense for removed devices, but not for still existing devices. Please save the manually assigned commands, so we don't have to assign them again and again.
    1 point
  16. Hello! I've been playing with the macOS app a bit and have had an overall good experience for a beta version! A few crashes did occur but I never lost data so it's only a minor inconvenience. Also, I thought about using the export/import functionality to enter my own Pronto IR codes as premade databases tend to be of poor quality but it isn't the case here, my needs are pretty much covered. One thing did make the experience less than ideal for quick iteration: I could not find a way to add or remove devices without totally overwriting the remote's button mapping. I tried to work around the problem with the import/export functionality (export config -> remove/add device -> import config) but that obviously didn't work as the exported config also contains the list of devices selected. I'm sure using the wizard was a dev time-saving decision for the beta but I just wanted to highlight that a better UX here would be valuable for me and probably other users too! Thank you
    1 point
  17. One thing that's really frustrating is having to add the same devices to each activity over and over again. This is particularly annoying when it doesn't work with the selected configuration (which can only be chosen at random because it's a group of devices and there's no way to figure out which group your device belongs to without trying it), so you have to go through each activity to remove and then re-add the device with the issues described above. Couldn't the app take the more versatile approach of adding and testing the devices in one section, and then assigning those devices to each activity instead?
    1 point
  18. Hi, Would like to echo this request. A better solution would be to create a "Device Management" tab where you can store default layout profiles of specific devices (i.e. TVs, streaming boxes, receivers etc). And to select from this preset list when creating activities. After all, it's going to be a fixed device pool. Also, would be good if there can be a full display of remote functionality codes when selecting the device group. For now its against generic naming conventions (Group 1, 2) so some guesswork is needed on which code profile suits best. Although I understand the remote database will include specific model convention going forward?
    1 point
  19. Yes, that's exactly what I'm reporting @theboomr, thank you for clarifying my explanation! It is only an improvement suggestion, I managed to do everything I wanted but the limitation mentioned above made things less straightforward than they could be.
    1 point
  20. I think what @LouP is saying is that if you have an activity already setup on the remote with, let's say, a TV, and an A/V receiver, for example, but then later you realize you want to add another device to that same activity, like an Xbox or streaming stick or something, the only way to add another device is to go back into the wizard, but then once you've selected the new device and continued through the steps of the wizard, any custom button mappings you had set up (like assigning rare misc functions to number keys or something like that) get reset to their default mappings. I have experienced this several times as well while fiddling and tweaking my setup.
    1 point
×
×
  • Create New...