Jump to content
Flirc Forums

c.dennis

Members
  • Posts

    35
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
     Belgium

Recent Profile Visitors

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

c.dennis's Achievements

Explorer

Explorer (4/14)

  • One Year In Rare
  • Reacting Well Rare
  • Collaborator Rare
  • Dedicated Rare
  • One Month Later Rare

Recent Badges

3

Reputation

  1. Hi, I’m a big fan of the Skip 1s, I just recently bought my second Skip 1s (from Raspberry Pi Shop dk), I’m using my first one now just for over one year. My first Skip has firmware version 4.12.11-13 with ring timeout set in the app at 1s, when I press the color button, the color wheel always led up for 6s. But when I press the color button again before the 6s are passed it will deactivate the color wheel immediately, what I personally find very handy, instead of waiting before it auto timeout. My second Skip has firmware version 4.13.4-0 also with ring timeout set in the app at 1s, again when I press the color button, the color wheel always led up for 3s. But with this firmware version, pressing the color button again before the 3s are passed will not deactivate the color wheel immediately, and that is not handy anymore. This way I needlessly have to wait until it auto timeout. Ring brightness and activity letter brightness and timeout are well respected by the Skip 1s. So, my question is dual... - Could it be possible to respect the Ring timeout set in the app? - Could it be possible to reimplement the ability to press the color button again to directly deactivate the color wheel mode, like it was in firmware 4.12.11-13? That would be very handy. Keep up the good work. Best regards, Dennis Edit, extra info: My first skip remote is model: SKIP.1S.RELEASE.A05 My second skip remote is model: SKIP.1S.RELEASE.A06
  2. It's a bug in the Windows version, will be fixed very soon, see (one of) the latest posts in the topic below...
  3. Software can be downloaded directly from http://flirc.tv/products/skip1s-remote go to download.
  4. I'm a customer that is very happy with the way it is now. Activity A, B and C just switching between activities and nothing more.
  5. Personally I found € 9,90 a reasonable price, had no problems paying that. I guess import taxes are normal if you buy something outside the EU.
  6. Hi, I'm also from Europe Belgium. Two weeks after I received my remote I got a letter from FedEx to pay € 9,90 additional import taxes.
  7. It just happened again, I pressed power, no response from the remote, after that i pressed activity A, again no response, then attached the remote to the computer and downloaded the logs, attached to this message. Edit: after i downloaded the remotes logs, the remote worked normally when connected to the computer, after disconnecting the remote from the computer the remote continued not responding, I then replaced the batteries and the remote again worked normally. I then realized... maybe the occasionally remote is not responding is an indication of an almost empty battery? Perhaps a good idea to have a battery indication ? Just a wild thought to a battery indication. Press color wheel + center button = send the action to this combo + light up the 4 wheel leds = full battery, light up 1 of the 4 led = low battery, color can be the personal color. flirc-remote-control20230219.log
  8. I just downloaded 0.9.6, the led settings are grayed out, but it is possible to change the values with the mouse. Is it safe to change these values and sync with the remote? The remote has firmware 4.12.10
  9. Yes i did that, pressed several buttons to get it work again and then downloaded the logs. If it happens again what is the best action to do, again press several buttons to get it work again and download the logs. Or immediate downloading the logs if it happens? I also have to mention I'm experiencing it not that often, definitely not daily.
  10. After i noticed the remote wasn't responding for about 10 seconds, i then downloaded the remotes log... maybe you can analyse and find an error why it stopped responding for a few seconds. I'm using firmware 4.12.10 flirc-remote-control20230217.log
  11. It would be a great addition if it would be possible to manually set the timeout when color wheel mode is active, with the options to choose from 1 to 8s. + the option to leave color wheel mode directly after pressing a button in color wheel mode. Now when you press the color wheel it is active for about 8s., I can leave it faster by another press on the color wheel mode but that feels not so intuitive. I guess most of the time people will only use one, two or three button presses at a time when in color wheel mode, personally I use maximum 3.
  12. Maybe a possibility to add a 10% or 5% brightness option, or just let users enter they desired percentage freely? That way there is more power for the ir transmitter, totally turning off the LEDs is not so interesting in my honest opinion as it is very handy to see what profile is active pressing a button.
  13. I'm now also using v4.12.10, no problems detected so far.
  14. Maybe it's a possibility to view the remotes color by pressing left and right the same time or activity a+c the same time, or some other combination (in normal mode, not color wheel mode, personally I don't need to see the remotes color, because I only have one) that way the center button is back available to use in color wheel mode. Another possibility is to leave it as it is but also send the code assigned to the center button in color wheel mode. Just brainstorming ;-)
  15. Brightness is currently set to 25% in skipapp and synced with the remote, the remote works normal for me now, no problems scrolling through items or other things. If the remote should go idle again I will try to hook it up to the computer and download the log.
×
×
  • Create New...