jason
-
Posts
3,723 -
Joined
-
Last visited
-
Days Won
228
Posts posted by jason
-
-
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?
-
Edit, updated links, we had a strange bug where you could not sync the remote sometimes. It's been updated.
-
Interesting feedback, I'll take a look to see if I can reproduce this. Thanks for letting me know.
-
New release with some fixes: https://forum.flirc.tv/index.php?/topic/13858-skipapp-09955-with-ir-learning-alpha-4/
-
1
-
-
Critical - Learning requires both remotes to be facing each other and about 1 inch apart.
Further detail here along in previous releases:
Alpha 1
Alpha 2
Alpha 3Here is how it works:
You need to be using the included firmware in order to do any recording. The version embedded is v4.13.2
Changelog
Alpha4
- Fixed - Dragable Buttons getting stuck
- Fixed - Elements / Tabs should not be during in wizard
- Fixed - Sync button should not be clickable during wizard
- Improved - UX elements in record and hover states
- Improved - UX style and animations during record
Windows Download
Mac Download
Linux - We understand the issue, and have one more bug to solve. We're working on it.Firmware Update
If you are not presented with update dialog, please follow the directions outlined here.
What's Next
- Better Error Handling and user feedback during record process
- Better phone home for failures so I can quickly identify protocol trouble and issue quick fixes
- Smoother transition when we are done recording
- Automated handling for buttons that only send out one single signal
- Many Many bug fixes you probably don't see
-
Let me look into this
-
What device are you using channels on?
-
I'm sorry for my delay. TLDR, it's supported. For an explanation, see below.
The BuiltIn Profiles are custom Flirc Codes that will not conflict with anything else. Those codes are built in harmony's database, and the skipapp.Harmony died before we had a chance to get more profiles in their software. I have not created a profile for channels yet.
But all that means is that it's not pre-pared if you use a Skip1s or Harmony remote. You can use the GUI to dynamically map those keys to your remote just fine.
Let me know if that makes sense. -
22 hours ago, jason said:
We're able to reproduce this. Trying to get another update out tomorrow.
Have this fixed. I'd like a couple more things included. Release is coming.
-
39 minutes ago, peperico said:
Thanks again!
It's not really a macro I'm after, I just want to assign a keyboard key/key combination (e.g. Alt+f) to a remote button directly with the SkipApp.
I understand a workaround is to assign a whatever remote signal to a button in the SkipApp and then do the keyboard key assignment with the Flirc App, but a more straightforward solution would be nicer. Your last sentence suggests that is not possible yet?
Yes. You are correct. Just remap it in the Flirc App and no direct way to do it yet within SkipApp
-
1
-
-
6 minutes ago, peperico said:
Thanks a lot for the prompt response.
Got my skip remote only yesterday, it has been surprisingly fast and easy to get it working with my setup. That is the only thing that is bugging me a bit.
Oh awesome, I like to hear that.
Sorry, to clarify, you can do macros in the skip app with the skip remote. Any button can become a macro, and the remote can do all the sequencing and timing for you.
OR, you can do that directly in the Flirc App Gui with the FLIRC USB. Where the filrc usb will receive one signal, and do macros by itself.
Either can do it. But the SkipApp + Remote is much more intuitive and controlling.I just meant you can't do it with SkipApp and the Flirc USB since the SkipApp doesn't talk to the Flirc USB yet. Sorry, did that make sense?
SkipApp-0.9.955 with IR Learning - Alpha 4
in Beta Feedback
Posted
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.