All Activity

Hi, I've just started using the Skip app on macOS. After importing my Windows config into the Mac app, every button now seems to have a small glitch next to its name. I've attached a screenshot with an example of one such glitch. I'm using the Skip App v0.9.992-beta on macOS 15.1.1, and the glitches don't seem to affect functionality in any way, but just look out of place. Thanks, Paul.

I'm glad and I'm sorry for my poor instructions. Thanks for letting me know and thank you so much for sharing that the recording worked. I'm so very sorry for the initial headache, grateful for the patience.

User error (oops) when attempting firmware upgrade. I was re-installing the batteries after step 3 for some reason. Close the software Unplug the USB-C cable Remove the batteries. Press and hold the return and center key while you insert the USB-C cable (image attached) Start the software All isues resolved now after firmware upgrade

Record issue resolved after upgrading firmware

Record ("IR Learning") feature worked perfectly first time after firmware upgrade to 4.13.11-0 (from 4.12.6-0) using the above upgrade method

Hoping that this is OK to ask here. I've been researching a problem that we've been having, and some other websites have pointed me here as a potential option. Here's my setup: Two LG UR9000, one LG C4 - all one one wall together. The dream was for me and my two sons to be able to play minecraft (via xboxes) or other games (via playstations/nintendos) together on the TVs. I also have an Nvidia Shield Pro connected to each - in the event that I'd like to game and watch two things on the other TVs. I read in advance of buying the TVs that you could disconnect the LG remotes and then reconnect them to separate the signals - but I've tried pretty much everything I've read, and it's not working as intended. Here's what I'd love to do. Option 1 - control each tv with it's own remote (LG or Flirc) - without having to use apps on phone/tablet to power them on. Option 2 - control each tv with one remote - with profiles set up to power on and control each TV (not sure if possible). The key is I also need my wife and sons to be able to easily turn them on/off/switch inputs. Would some combination of the Flirc USBs/Remotes help solve this? I'm willing to spend money to solve the problem if it means buying new remotes or a new piece of hardware.

The above instructions for updating the firmware have worked for me. I have been upgraded to 4.13.11-0 (from 4.12.6-0) Note: for some reason I assumed I should replace the batteries after having taken them out for a few seconds, then proceeding with the keypress+connect step. This was preventing my device from entering DFU/bootstrapper mode. Things went much better when I remembered how to read :) "To safely enter bootloader mode. Take out the batteries. press the middle cursor button, and the back button. while plugging it into the computer. See attached. If successful, pressing any button will blink the LED 3 times. If so, start the app, it should force an update."

So the earliest version of hardware had a bug. It would deny an update without the ability to check USB state, without this piece of hardware working perfectly, the remote can get stuck indefinitely. To safely enter bootloader mode. Take out the batteries. press the middle cursor button, and the back button. while plugging it into the computer. See attached. If successful, pressing any button will blink the LED 3 times. If so, start the app, it should force an update. If not, message me.

Hello all I also have this Issue on Windows 11 whereupon Double Clicking the .msix File I get a Blank White Window for a few Seconds after which it Closes. I finally managed to Install the App using the Powershell in Windows 11 using the following Command: Add-AppxPackage -Path C:\Path\AppPackage.msix This Installed the App fine. Could the Issue be with Windows 11 rather than the File? I Hope this Helps. Kevin

Hello I currently have the Harmony Elite and Hub which is unfortunately not going to last much longer. I have not Purchased yet as I wanted to make sure everything was compatible first. I Downloaded the Skip Software, which would not Install by Double Clicking on the File, however, I managed to Install the Software using the Command Line. All of My Devices seem to be supported so that is Good. One thing I am not able to figure out is how to Assign Long Presses on Keys. Any suggestions? Thanks in advance Kevin

ok thx i would appreciate it

Saw your other message. I’m sorry. I’ve had a really really shitty week. It’s just me that does support. (I’m the owner) I’ll help on your other thread shortly. Really sorry.

because my firmware wont update, i have 3 remotes and 2 flircs and want to buy more but there is NO SUPPORT FROM THIS TERRIBLE COMPANY!!!!

I've continued discussion of above Record issues on the following thread (in relation to what firmware is needed and how to get it)

I have a brand new Skip 1s and need the Record feature as my new Panasonic Smart TV is not listed (model: TB-50W60AEY) Firmware Version 4.12.6-0-g60dd93b Remote Model SKIP.1S.RELEASE.A05 Registration Date 12/05/2024 22:22:23 I am on MacOS Sonoma 14.4 + I have attempted Record, with no success, using the following SkipApp versions SkipApp 0.9.993.9156 (Nightly) SkipApp 0.9.993.9152 (RC) SkipApp-0.9.992.9056 (Beta) From reading earlier series of posts culminating in SkipApp-0.9.955 with IR Learning - Alpha 6, it is mentioned several times that the firmware version is key and that it can be updated following these instructions, copied below: Close the software Unplug the USB-C cable Remove the batteries. Press and hold the return and center key while you insert the USB-C cable (image attached) Start the software I have had no success with this method of firmware update. Is it critical to update from 4.12.6-0 to have any chance of Record working with the above SkipApp builds? Is it expected that a SkipApp update itself can update the firmware (when using MacOS)? Has anyone using MacOS successfully done the firmware update method listed above? I have posted this problem originally on Beta Feedback section. Thanks in advance for any help!

Yes. Hang on.

It's been a while since I have need help, which says a lot about how rock solid this thing is. I have recently made some changes to my setup, but still needed to have my original activity on the remote. I created the new setup conditions under activity B, however, the new setup will be the main usage with the old setup being secondary. I was wondering if there is a way to swap activity designations for the programmed activity so that what is currently on A is now on B and what is currently on B is moved to A? While the app and the remote are easy to program, it does take time to make sure it is programmed correctly (ie order/macros) and so it would be fantastic if we could just do a swap migration from on activity letter to another. This would also be great if we could migrate programming to an unused activity letter (if there are unused letters) as well.

The remote is a Spectrum SR-002. The remote has two modes to work with two types of cable boxes. Mode 1 works perfectly with FLIRC, but won't long-press (I need it to). Mode 2 will long-press, but has the issues described above. This happens with fresh batteries and no matter what distance you record.

Recreated Record issue using RC build 0.0.003.9152 Log sample: 23:42:14 <1> #USBController #ReadChunks index.js:73 * parsed the following packet metadata: {"reportId":1,"declaredSizeOrSequence":2,"isLast":false,"dataChunk":{"type":"Buffer","data":[110,102,52,46,49,50,46,54,101,100,105,114,116,121,107,45,48,45,103,54,48,100,100,57,51,98,100,85,85,73,68,120,32,70,56,49,69,54,69,52,55,53,48,53,53,51,52,52,65,51,53,50,69,51,49,50,48,70,70,49,54,49,55]}} 23:42:14 <1> #USBController #ReadChunks index.js:46 Reading a usb packet... 23:42:14 <1> #USBController #ReadChunks index.js:52 * ReadHidPacket response: {"dataHexDump":"01033038ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff","bytesRead":65,"responseCode":0} 23:42:14 <1> #USBController #ReadChunks index.js:64 * ReadHidPacket response data: "01033038ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff" 23:42:14 <1> #USBController #ReadChunks index.js:73 * parsed the following packet metadata: {"reportId":1,"declaredSizeOrSequence":3,"isLast":true,"dataChunk":{"type":"Buffer","data":[48,56,255]}} 23:42:14 <1> #ReadChunks index.js:81 * this was the last usb packet 23:42:14 <1> #USBController #ReadChunks index.js:90 cborBuffer: {"type":"Buffer","data":[159,0,170,100,102,117,108,108,115,83,75,73,80,46,49,83,46,82,69,76,69,65,83,69,46,65,48,53,104,112,108,97,116,102,111,114,109,103,83,75,73,80,46,49,83,102,99,111,110,102,105,103,103,82,69,76,69,65,83,69,99,115,107,117,97,65,99,114,101,118,98,48,53,101,98,117,105,108,100,120,24,50,48,50,50,45,49,50,45,49,51,84,49,54,58,50,57,58,50,52,45,48,56,48,48,102,98,114,97,110,99,104,102,114,101,109,111,116,101,103,118,101,114,115,105,111,110,102,52,46,49,50,46,54,101,100,105,114,116,121,107,45,48,45,103,54,48,100,100,57,51,98,100,85,85,73,68,120,32,70,56,49,69,54,69,52,55,53,48,53,53,51,52,52,65,51,53,50,69,51,49,50,48,70,70,49,54,49,55,48,56,255]} 23:42:14 <1> #USBController #ReadChunks index.js:94 offset: 0 192 23:42:14 <1> #USBController #ReadChunks index.js:106 read usbChunks cbor result: {}. 23:42:14 <1> #USBController #WritePacket index.js:188 Final usb response: [0,{"full":"SKIP.1S.RELEASE.A05","platform":"SKIP.1S","config":"RELEASE","sku":"A","rev":"05","build":"2022-12-13T16:29:24-0800","branch":"remote","version":"4.12.6","dirty":"-0-g60dd93b","UUID":"F81E6E475055344A352E3120FF161708"}] 23:42:14 <1> #CommandProcessor #handleResponse CommandProcessor.js:49 Command: {"version":{}}. Response: {"full":"SKIP.1S.RELEASE.A05","platform":"SKIP.1S","config":"RELEASE","sku":"A","rev":"05","build":"2022-12-13T16:29:24-0800","branch":"remote","version":"4.12.6","dirty":"-0-g60dd93b","UUID":"F81E6E475055344A352E3120FF161708"}. 23:42:15 <1> #SkipApi #Learning learning.js:50 Reset learning. 23:42:15 <1> #SkipApi #Learning index.js:726 Recording for button "POWER TOGGLE". 23:42:15 <1> #CommandProcessor #Process CommandProcessor.js:64 Sending command: {"learn":{"enable":true}}. 23:42:15 <1> #USBController #Send index.js:242 Sending command. 23:42:15 <1> #USBController #CreateUsbChunk index.js:122 Creating usb send promises... 23:42:15 <1> #USBController #CreateUsbChunk index.js:136 WriteHidPacket response: {"bytesWritten":65}. 23:42:15 <1> #USBController #WritePacket index.js:178 Posted all chunks via NativeHidApi, these are the sequential USB write results: [{"bytesWritten":65}] 23:42:15 <1> #USBController #ReadChunks index.js:46 Reading a usb packet... 23:42:15 <1> #USBController #ReadChunks index.js:52 * ReadHidPacket response: {"dataHexDump":"01039f30ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff","bytesRead":65,"responseCode":0} 23:42:15 <1> #USBController #ReadChunks index.js:64 * ReadHidPacket response data: "01039f30ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff" 23:42:15 <1> #USBController #ReadChunks index.js:73 * parsed the following packet metadata: {"reportId":1,"declaredSizeOrSequence":3,"isLast":true,"dataChunk":{"type":"Buffer","data":[159,48,255]}} 23:42:15 <1> #ReadChunks index.js:81 * this was the last usb packet 23:42:15 <1> #USBController #ReadChunks index.js:90 cborBuffer: {"type":"Buffer","data":[159,48,255]} 23:42:15 <1> #USBController #ReadChunks index.js:94 offset: 0 3 23:42:15 <1> #USBController #ReadChunks index.js:106 read usbChunks cbor result: {}. 23:42:15 <1> #USBController #WritePacket index.js:188 Final usb response: [-17] 23:42:15 <4> #CommandProcessor #Process CommandProcessor.js:70 600 23:42:15 <4> #CommandProcessor #handleResponse CommandProcessor.js:46 Command: {"learn":{"enable":true}}. Response: 500. 23:42:15 <4> #Learning index.js:233 Error at record signal. Code: 500. 23:42:15 <4> #RemoteConnection useRemoteConnection.js:289 Check connection error code: 504. 23:42:16 <4> #RemoteConnection useRemoteConnection.js:289 Check connection error code: 504. 23:42:17 <4> #RemoteConnection useRemoteConnection.js:289 Check connection error code: 504.`

At the Record step of Record Device (i.e. My Device -> Design -> Record) I get "We have had an unexpected error". See attached screenshot + screenshot for firmware version. And last few seconds of logs. Using MacOS Nightly build (because Record button is greyed out in 0.9.992-beta, screenshot below) Branch: master Pull Request: #false CI Build: 9155 Commit: 8943d5a react 17.0.2 react-native 0.67.4 react-native-macos 0.66.48 redux 4.2.1 react-redux 7.2.6 hidapi 0.13.1 Last few entries in log file at that point were: 22:11:05 <1> #USBController #ReadChunks index.js:73 * parsed the following packet metadata: {"reportId":1,"declaredSizeOrSequence":3,"isLast":true,"dataChunk":{"type":"Buffer","data":[48,56,255]}} 22:11:05 <1> #ReadChunks index.js:81 * this was the last usb packet 22:11:05 <1> #USBController #ReadChunks index.js:90 cborBuffer: {"type":"Buffer","data":[159,0,170,100,102,117,108,108,115,83,75,73,80,46,49,83,46,82,69,76,69,65,83,69,46,65,48,53,104,112,108,97,116,102,111,114,109,103,83,75,73,80,46,49,83,102,99,111,110,102,105,103,103,82,69,76,69,65,83,69,99,115,107,117,97,65,99,114,101,118,98,48,53,101,98,117,105,108,100,120,24,50,48,50,50,45,49,50,45,49,51,84,49,54,58,50,57,58,50,52,45,48,56,48,48,102,98,114,97,110,99,104,102,114,101,109,111,116,101,103,118,101,114,115,105,111,110,102,52,46,49,50,46,54,101,100,105,114,116,121,107,45,48,45,103,54,48,100,100,57,51,98,100,85,85,73,68,120,32,70,56,49,69,54,69,52,55,53,48,53,53,51,52,52,65,51,53,50,69,51,49,50,48,70,70,49,54,49,55,48,56,255]} 22:11:05 <1> #USBController #ReadChunks index.js:94 offset: 0 192 22:11:05 <1> #USBController #ReadChunks index.js:106 read usbChunks cbor result: {}. 22:11:05 <1> #USBController #WritePacket index.js:188 Final usb response: [0,{"full":"SKIP.1S.RELEASE.A05","platform":"SKIP.1S","config":"RELEASE","sku":"A","rev":"05","build":"2022-12-13T16:29:24-0800","branch":"remote","version":"4.12.6","dirty":"-0-g60dd93b","UUID":"F81E6E475055344A352E3120FF161708"}] 22:11:05 <1> #CommandProcessor #handleResponse CommandProcessor.js:49 Command: {"version":{}}. Response: {"full":"SKIP.1S.RELEASE.A05","platform":"SKIP.1S","config":"RELEASE","sku":"A","rev":"05","build":"2022-12-13T16:29:24-0800","branch":"remote","version":"4.12.6","dirty":"-0-g60dd93b","UUID":"F81E6E475055344A352E3120FF161708"}. 22:11:05 <1> #SkipApi #Learning learning.js:50 Reset learning. 22:11:05 <1> #SkipApi #Learning index.js:726 Recording for button "POWER TOGGLE". 22:11:05 <1> #CommandProcessor #Process CommandProcessor.js:64 Sending command: {"learn":{"enable":true}}. 22:11:05 <1> #USBController #Send index.js:242 Sending command. 22:11:05 <1> #USBController #CreateUsbChunk index.js:122 Creating usb send promises... 22:11:05 <1> #USBController #CreateUsbChunk index.js:136 WriteHidPacket response: {"bytesWritten":65}. 22:11:05 <1> #USBController #WritePacket index.js:178 Posted all chunks via NativeHidApi, these are the sequential USB write results: [{"bytesWritten":65}] 22:11:05 <1> #USBController #ReadChunks index.js:46 Reading a usb packet... 22:11:05 <1> #USBController #ReadChunks index.js:52 * ReadHidPacket response: {"dataHexDump":"01039f30ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff","bytesRead":65,"responseCode":0} 22:11:05 <1> #USBController #ReadChunks index.js:64 * ReadHidPacket response data: "01039f30ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff" 22:11:05 <1> #USBController #ReadChunks index.js:73 * parsed the following packet metadata: {"reportId":1,"declaredSizeOrSequence":3,"isLast":true,"dataChunk":{"type":"Buffer","data":[159,48,255]}} 22:11:05 <1> #ReadChunks index.js:81 * this was the last usb packet 22:11:05 <1> #USBController #ReadChunks index.js:90 cborBuffer: {"type":"Buffer","data":[159,48,255]} 22:11:05 <1> #USBController #ReadChunks index.js:94 offset: 0 3 22:11:05 <1> #USBController #ReadChunks index.js:106 read usbChunks cbor result: {}. 22:11:05 <1> #USBController #WritePacket index.js:188 Final usb response: [-17] 22:11:05 <4> #CommandProcessor #Process CommandProcessor.js:70 600 22:11:05 <4> #CommandProcessor #handleResponse CommandProcessor.js:46 Command: {"learn":{"enable":true}}. Response: 500. 22:11:05 <4> #Learning index.js:233 Error at record signal. Code: 500. 22:11:06 <4> #RemoteConnection useRemoteConnection.js:289 Check connection error code: 504. 22:11:07 <4> #RemoteConnection useRemoteConnection.js:289 Check connection error code: 504. Device+Firmware details We have had an unexpected error: flirc20241204.logflirc20241204.log Record button is greyed out in 0.9.992-beta:

im trying to do IR leaning which needs 4.13.7 minimum according to the video but my device is on 4.12.18. No matter what i try the app doesnt show me any newer firmware? If i try to do IR learning on this version the learn button is greyed out. Why? How do i update the firmware?

Yes, that's correct. But you can also use a harmony and a flirc-usb as well, I have built in support for that.

The android box doesn’t support IR. So I get a skip and the usb dongle. I put the dongle in the usb box, and the skip will work with it, right? Then I program the skip to control my other devices that are now controlled with the Harmony via IR. I can then control all of them from the skip, correct?

Yes, what remote is this? I'm seeing completely invalid stuff come in, make sure you are not too close, you should be 2 feet away, point it at the ceiling, make sure you have good batteries.