jason
-
Posts
3,733 -
Joined
-
Last visited
-
Days Won
229
Posts posted by jason
-
-
I'm on it, thanks for letting me know.
-
Skip1s doesn't have RF. Reading on their site, you can use a xbox 360 profile in skip, and then enable that in their administration. Should work with those codes.
-
Just now, jason said:
There were a lot of bugs in the first alpha, and I have a terrible bug in the last one and can't trust 100% what's being recorded. Please check for alpha 5 next week, it should be pretty close to a release candidate.
Also, in your remote, change all your button settings to repeat at least 3 times for sony devices. Let me know if that helps, a lot of your codes in your json look okay.
-
On 12/19/2023 at 6:25 AM, desmando said:
Sony-X91J-TV.jsonI have a Sony X91J that I can't get to work with my remote. I configured the TV for IR rather than Bluetooth. I learned all of the remote commands and I put them into the attached JSON, but I still can't even control the power of the TV.
Any advice?
There were a lot of bugs in the first alpha, and I have a terrible bug in the last one and can't trust 100% what's being recorded. Please check for alpha 5 next week, it should be pretty close to a release candidate.
-
On 1/24/2024 at 1:55 PM, mrak said:
Would it be possible to add support for the OSMC remote that can be used with KODI ? https://osmc.tv/store/product/osmc-remote-control/
I didn't find this remote in list in the app, and choosing flirc/kodi (which I thought would be similar) didn't work. I also tried to record the OSMC remote using the Alpha-4 software, but it wasn't able to detect any of the buttons.
Thanks!
I think their remote is RF.
-
Bryce, I'm really sorry, I missed a lot of messages on this forum. I'm appreciative of the feedback and patience. We've been trying to improve things a lot and are nearly done with the learning portion, which was a technical marathon.
I don't have any intentions of going open source, although, I will publish my libraries and a bunch of sample apps. So you can create your own, similar to the flirc USB.
The wizard is next on the list once we are done with learning. While that's going on, I'm going to be working on smart activity switching.
Yes, once I'm happier with the maturity of software, I'm going to get this on Amazon. Although our database is commercially licensed, as you can see, the 'one size' fits all device approach isn't great. I don't want it on amazon and spending 90% of my time with 'help, I can't find my device'. So learning has to be rock solid. https://forum.flirc.tv/index.php?/topic/13858-skipapp-09955-with-ir-learning-alpha-4/I think the next release (alpha 5) will be a release candidate.
-
On 1/17/2024 at 3:13 PM, c.dennis said:
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,
DennisEdit, extra info:
My first skip remote is model: SKIP.1S.RELEASE.A05
My second skip remote is model: SKIP.1S.RELEASE.A06It should reset the timeout when you press a color button. I'll double check.
Yes, I'll make it so the color button forces off the feature.
Thanks for the kind feedback, really appreciate it.-
1
-
-
-
-
28 minutes ago, asyba said:
it happen again, I tried this time holding a button and no tacking the batteries, but still nothing connected to de pc, but it did't turn on, then hold again button but nothing, and after a few seconds it light up, and then I check logs but no errors and no low battery message this time.
<2>task_start(41): Hypnos: v4.13.4
<1>malloc_addblock(61): Heap Block: 0x200030E8 - 0x20007BFF (18k)
<1>log_rcause(383): BOD33 BOD12 SYST WDT EXT POR
<1>log_rcause(390): F F F T F F
<1>init_remote(280): Initializing Past Profile: A
<3>usb_hotplug(46): Connected
<2>default_handler(163): 1 pressed
<2>default_handler(163): 1 released
<3>learn(85): learn called with: Enable
<3>learn(85): learn called with: Disable
<2>default_handler(163): RW pressed
<2>default_handler(163): RW released
It's the batteries. Can you go to the public version of software, you'll be prompted to 'upgrade' your firmware where it will restore the latest public stable. Also, when and where did you get the remote?
*EDIT*
I'm removing most of these conversations. They have nothing to do with learning.
-
35 minutes ago, randycatster said:
rebooted, reinstalled: tried advanced/upgrade firmaware, it got better :(
Sat Jan 27 2024 17:53:22
Flirc GUI Version v3.27.10
Operating System: Windows
ERROR. Firmware upgrade required. (fw >= 4.1.0)
*** Device Connected ***
<1>malloc_addblock(49): Heap Block: 0x20001AD0 - 0x20003BFF (8k)
<3>iospirit_eep_init(286): module missing hw
<3>read_eep(183): eeprom not found: (null)
<3>rb_get_settings(105): eeprom not found
<3>rb_cache_update(59): cache update fail
<3>read_eep(183): eeprom not found: (null)
<3>rb_get_hash(191): could not read hash
ERROR. Firmware upgrade required. (fw >= 4.1.0)
*** Device Connected ***
<1>malloc_addblock(49): Heap Block: 0x20001AD0 - 0x20003BFF (8k)
<3>iospirit_eep_init(286): module missing hw
<3>read_eep(183): eeprom not found: (null)
<3>rb_get_settings(105): eeprom not found
<3>rb_cache_update(59): cache update fail
<3>read_eep(183): eeprom not found: (null)
<3>rb_get_hash(191): could not read hash
ERROR. Firmware upgrade required. (fw >= 4.1.0)
*** Device Connected ***
<1>malloc_addblock(49): Heap Block: 0x20001AD0 - 0x20003BFF (8k)
<3>iospirit_eep_init(286): module missing hw
<3>read_eep(183): eeprom not found: (null)
<3>rb_get_settings(105): eeprom not found
<3>rb_cache_update(59): cache update fail
<3>read_eep(183): eeprom not found: (null)
<3>rb_get_hash(191): could not read hash
ERROR. Firmware upgrade required. (fw >= 4.1.0)
*** Device Connected ***
<1>malloc_addblock(49): Heap Block: 0x20001AD0 - 0x20003BFF (8k)
<3>iospirit_eep_init(286): module missing hw
<3>read_eep(183): eeprom not found: (null)
<3>rb_get_settings(105): eeprom not found
<3>rb_cache_update(59): cache update fail
<3>read_eep(183): eeprom not found: (null)
<3>rb_get_hash(191): could not read hash
You can ignore those. Firetv doesn’t have remote buddy support.
-
15 minutes ago, Cape said:
I have tried to record buttons from three different remotes with alpha 1, 2 and now 4. Sometimes the progress bar seems to move all the way and record the button but then I am asked to record again, other times the progress bar just goes half way or does not move at all. Either way i never seem to be able to move forward in the setup process. What could be causing this? As mentioned, i have tried 3 different remotes, and have had them faceing the Skip 1s one inch or less apart.
Most of the work that we've been doing is this. Improving accuracy, decoding, and user feedback. I was hoping to have this up tonight, but there is one more bug we're trying to solve. Early next week. But hopefully the next one will be a release candidate. Very sorry. We are working hard on it.
-
1
-
-
6 hours ago, asyba said:
@jason could be that my control configuration is corrupted?
I added some delays because is wasn't working properly lately , and is working kind of bad, like is not waiting.
not sure if its the battery or the config. but connected to the PC it works.
https://pastebin.com/VfP2w6mn
https://youtube.com/shorts/nSbAEpoiorA?si=iSOBRPcleDUDw0MQIt's the battery, and they don't look like 30%... Looks like full brightness. I tried your config, and it was fine here.
The reason why the colors don't work, is because each quadrant is 3 leds. So 3*4 is 12 LEDs. Plus the Profile. It uses much more current. The batteries you are using are not good. Do you have a battery tester? When they. are new, they read 1.5-1.6 Volts. When they are dead, they are around 1.2V.
-
What?
-
18 hours ago, matthewh said:
App Installer was already installed. This confirmation screen indicated that the Skip App did install successfully:
But when I tried launching the app, I see the start screen for a few seconds, then it disappears:
I was able to install and open the app on an older Windows 10 desktop, so I'll just use that to configure the remote.
Try to see if there are logs here: %localappdata%\Packages\1ee3f564-2cd0-4ef3-af35-da985b1d7f00_sddpyax1dmvqm\LocalState
-
On 11/28/2023 at 6:59 PM, LucasMertens said:
I just received my Flirc Skip 1s and Flirc receiver today, and I’m experiencing the exact same issue. I managed to install about 4 or 5 different required dependencies through PowerShell, but I’m unable to proceed further because it seems to want this exact dependency version, and I assume even if I managed to get this dependency installed, it will still probably request further dependencies thereafter in order to install the .msix file.
I’m also unable to install the Microsoft App Installer, as I do not have the Microsoft Store to begin with - my PC is running Windows 10 IoT LTSC, a version of Windows 10 that does not include the Microsoft Store (and as far as I’m aware, doesn’t offer a simple method of installing it).
I really wanted to like this remote, and up to this point, I did, but after an hour of utterly fruitless attempts to install the software needed to begin programming/using the remote, I’m admittedly left with quite a sour taste in my mouth.
I don’t mean to sound rude here, but I have to ask - why not just provide a standalone .exe or .msi installer for the software? Why do you need to explicitly use the .msix format here?
React Native doesn't compile to an exe. This is microsoft's new format, and they are forcing everyone to use it. You can bitch to them, because I hate it, and other apps on the system fuck up our own app.
-
7 hours ago, asyba said:
here managed to put the complete version https://pastebin.com/8i0u9PbS
It doesn't happen with the other batteries?
Is it plugged in at the time? -
1 hour ago, matthewh said:
I was attempting to set up a new Skip S1. I installed the Windows version of the app (SkipApp-0.9.956-Beta-x64), but whenever I try to open it, I see the logo for a few seconds, and then it closes. I disabled my antivirus, in case that was blocking it (although nothing in the AV logs indicated that it was), but that made no difference. I'm running Windows 11 Pro 23H2. Any suggestions?
Were you actually able to install it? Make sure you have MSIX package support installed.
Step 1: Launch Microsoft Store on your computer – type Microsoft Store into the search box and click the app to open.
Step 2: Search for App Installer in Store and then install it.
Step 3: Then, double-click on the .msixbundle file and you can see the following window. Just click Install to start installing MSIXBundle.
https://www.minitool.com/news/install-msixbundle-windows.html
-
1 minute ago, asyba said:
@jason managed to get error logs.
the ones with the issue are not rechargeable they are generics, LR03 1.5V (https://www.simplicity.com.ar/pilas-alcalinas-simplicity-aaa-troquelada/p)
what I did: put the "dead" batteries , then click 3 times any button and then it "shutdown", then I connected to the PC with the batteries, and check logs and found this.
(I reproduce it two times, so two logs sessions.)
Maybe it helps or maybe they are normal logs.
Note: I don't see a low battery message in the log that I looked that before when using a rechargeable batteries.
I can record a video if that still is needed after you analyze the logs, let me know.<2>task_start(41): Hypnos: v4.13.4<1>malloc_addblock(61): Heap Block: 0x200030E8 - 0x20007BFF (18k)<1>log_rcause(383): BOD33 BOD12 SYST WDT EXT POR<1>log_rcause(390): F F T F F F<2>crash_report(208): ***** Hardware Exception *****<2>crash_report(212): ------------------------------<2>crash_report(213): r0: 0x0000d88b<2>crash_report(214): r1: 0x000108dc<2>crash_report(215): r2: 0x20007f28<2>crash_report(216): r3: 0x20007f23<2>crash_report(217): r12: 0x2000314c<2>crash_report(218): lr: 0x00011ac0<2>crash_report(219): ra: 0x0000e10d<2>crash_report(220): xpsr: 0x0100e08d<2>crash_report(224): *******************************<1>init_remote(280): Initializing Past Profile: A<3>usb_hotplug(46): Connected<2>default_handler(163): Down pressed<2>default_handler(163): Down released<2>default_handler(163): Down pressed<2>default_handler(163): Down released<2>default_handler(163): Okay pressed<2>default_handler(163): Okay released<2>default_handler(163): Up pressed<2>default_handler(163): Up released<2>default_handler(163): Right pressed<2>default_handler(163): Right released<2>default_handler(163): Left pressed<2>default_handler(163): Left released—<2>task_start(41): Hypnos: v4.13.4<1>malloc_addblock(61): Heap Block: 0x200030E8 - 0x20007BFF (18k)<1>log_rcause(383): BOD33 BOD12 SYST WDT EXT POR<1>log_rcause(390): F F T F F F<2>crash_report(208): ***** Hardware Exception *****<2>crash_report(212): ------------------------------<2>crash_report(213): r0: 0x0000d88b<2>crash_report(214): r1: 0x000108dc<2>crash_report(215): r2: 0x20007f28<2>crash_report(216): r3: 0x20007f23<2>crash_report(217): r12: 0x2000314c<2>crash_report(218): lr: 0x00011ac0<2>crash_report(219): ra: 0x0000e10d<2>crash_report(220): xpsr: 0x0100e08d<2>crash_report(224): *******************************<1>init_remote(280): Initializing Past Profile: A<3>usb_hotplug(46): Connected<2>default_handler(163): Down pressed<2>default_handler(163): Down released<2>default_handler(163): Down pressed<2>default_handler(163): Down releasedThis is helpful. Can you post your configuration too?
-
I see the issue, and am working on some updates
-
2 hours ago, asyba said:
@jason are you talking about the app or the batteries comment?
I tried putting again the "dead" batteries and I can click three times an activity button, I can see the light turn on, but then is not doing anything after 2-3 click, low battery I guess ..?
Should I update to Alpha 4 or keep on 3 and report/help issues with another pair of batteries?These are rechargeable? The issue with rechargeable is the low voltage. These tend to hang around the 'dead' battery voltage of normal batteries despite having plenty of current. You can post a video and I can confirm. I can do a few things in firmware to detect and maybe prevent an under voltage lockout, just not on my list of things to do at the moment.
-
it wasn't dead. It looks like a crash. It takes a long time to reset. I'll reduce the timeout so I can see where it crashed.
-
Skip or the Flirc gui?
-
Can you try this and let me know if it works?
I wished ?????
in Skip 1s
Posted
I appreciate your feedback. I'll spare the details, but the delay in this was a massive technical marathon that I did not anticipate. All the way from the firmware to the app, it was a massive bitch. We have one more bug and the next update will likely be a release candidate. I'm really sorry for the frustration but appreciate all the feedback, support, and patience. I know it does not appear so, but we only have a few people at the company.