All Activity

Using the latest version of software/firmware (3.27.15), I am having a problem with long press - the paired key is always executed at least twice (even with keyboard repeat delay set to longest & repeat rate set to slowest in OS to prevent accidental repeats). I tried reverting back to my previous version of software/firmware (3.27.3), but I get an error (disconnected, unsupported fw v:4.10). How can I at least get back to the old version?

@jason thanks for coming back with a response on this and sharing a detailed response it's much appreciated. I'll drop a Pm over in a bit on just some thoughts in case they help. Again thanks for everything you and the team are doing, it's not easy when there are so many moving parts.

I need to find a good self hosted app to share progress and road map. Internally we use Jira and Github (not for bugs), and there are too many confidential tasks to make everything public. I'm looking, if you have recommendations, I'll take a look. Once we finished learning, we had a few different tasks: - Rebase react native desktop to latest - Figma Integration investigation - Sentry Investigation - Work on smarter activity switching - GUI related updates - Update Wizard - Allow easier testing of different protocols - Easier management of creating custom remotes Rebasing react native was an absolute failure. Everything broke, especially on windows. In the end, we got everything working. However, when it was all said and done, react native SVG was broken and we couldn't figure out why. Of course, only on windows. The performance was unacceptable. It was a complete step back and we found no other improvements after all that work. So we left it in another branch and gave up. Figma integration was shit. We have a lot of problems with the current UX, it doesn't match figma. It would have been amazing to be able to export different aspects of the design for direct use. It would save us so much time from having to pixel push. But it didn't work. Sentry, which we use for investigating crashes announced two new features, real time playback of crashes and a way to measure performance to see how and what we can improve. Both didn't work. So then we were planning to quickly move on and improve our build and release tools, because it's always a mess and needed to be done. But then got interrupted with Windows bullish, that was about 2-3 weeks. We are just about done with the build and release tools. What's on the short list right now: - Fix Play/Pause button so we can toggle between distinct play and pause - Fix Mute button so we can toggle between distinct mute on and mute off - Implement smart activity switching. - Finish qualification of learning firmware so we can release it - Fix Wizard and Test modes We have a lot on the long list as well as the products that we are working on in development. Feel free to pm me with suggestions.

Hi @jason. DId you get a chance to look at this?

I ordered and received 2 of these devices. First one works on the fire stick no issues at all. Second one does not work at all. Here is what I have tried. OTG Cable connected to Flirc -> Flirc conntected to Fire stick. USB Keyboard connected to OTG cable and power. (this is to verify kepresses). Does not work. OTG Cable connected to Fire stick with the Flirc on the power side the USB keyboard works as expected. The Flirc device isnt passing the commands to the firestick from itself or the usb keyboard. now if I plug the flirc device in the PC with the power side of the device it controls the pc. So I am curious if this one is just faulty or needs the new firmware. (note this one will not update in the software).

I had the same issue - turns out the function was there, just erroneously assigned cursor enter. Change thesecond "cursor enter" to "cursor right" and be done with it, make sure you sync afterwards. I will try to attach a snip of what it should look like, don't be jealous of my paint skills. To be clear, all I did was edit the name of the second instance of cursor enter to cursor right. After syncing it showed right up and was auto assigned. or just replace the SECOND instance of cursor enter with this: "label": "CURSOR RIGHT", "protocol": "PRONTO", "code": "0000,006D,000D,0000,005C,0015,002D,0015,002D,0015,0016,0015,0017,0014,002D,0015,002E,0014,0016,0015,002D,0015,0016,0015,0016,0015,0016,0015,0016,03C1"

I note the test version we had lost the update channel, so had to go back to a earlier release and update and have 0.9.966 beta now installed. With the service re-enabled. Fire it up first time, it didn't work was a bit odd (may have been me). Did create the remote, skipped passed the add device stuff so I could just do a restore (an option for this at the start might be good, especially as it seems you can detect if the remote is new or has been updated). So tried a second time, this time it did bring up the pop up after the remote was detected and sync was tried. Get the previous windows permissions error then your new pop up with the download link, used that installed the "fix". Checked the services it does disable it correctly - some of the messages are kinda worrying, (I think deleting usb devices .. was a fun one to see). When complete return to the app. Remote is picked up, and could sync. Swapped remotes, picked up the second one ok, (as a fresh install) tried to skip past the setup which locked the app up, needed a restart to clear that. Came back to the blank second remote, imported the config ok. Remote connects (doesn't offer a sync this time). Swap them over again the app swaps to the other remote correctly. So looks like this is all working to fix the usb/logitech/steam issue. Thanks for getting it included and working. Can I dare ask if there will be an update or a roadmap for the remote and things we can expect (no dates, or order) just so we can see what's hopefully coming at some point. Just my remotes are still in their boxes waiting for some key changes and would be at least nice to know these are still planned and will appear at some point (time etc permitting). Happy to post or message you a list of what I'm hoping for and you can confirm yes/maybe/no if easier.

We released an update that will try and detect this and if so, send you to a link to download a utility to try and turn this off, hotplug the device, as well as remove the restricted interface and filter driver that steam installed. This was a horrible amount of fucking work and is the best we can do for now. We will try and work on the alternative USB method, but honestly, I really don't want to. I would say that we spent the last 2 months working on windows issues and failed to progress towards any of our goals. All sales were halted again, no one is going to give a shit if steam or logitech caused the problem, they say it's our fault and return the remote. The amount of development I've done in the past two weeks was a marathon. I've stayed up until 1:30 in the morning every night working on this 7 fucking days a week. Windows is absolutely the worst fucking platform. Everything is an afterthought, there are a million different languages, C#, C# dot net, dot net desktop, dot net web, WPF, react, UWP, FUCK! And all language have different versions, different laws and rules. What the fuck is even the registry. Dumb fucking idiots at that company. I hate them. I fucking hate them.

Been in the middle of a move so everything's been boxed up. I was able to test this morning and so far working after following these steps. Will continue to test later on this weekend. Thanks!

Hi All, I'm trying to update the firmware but nothing seems to be happening. I am doing the following; Remove the batteries. Press and hold the centre button and the back button (the one below and left and has a circular arrow on it) Plug in the USB cable Light blink red (Light blink red if I press any other button) Start the app After around 10-12 seconds the remote contacts but not firmware update has taken place. Model is SKIP.1s.RELEASE.A05 and has a FW version of 4.12.6-0-g60dd93b Has anyone got any ideas or can the firmware not be updated on this model? Thanks Graham

Hi All, I'm trying to update the firmware but nothing seems to be happening. I am doing the following; Remove the batteries. Press and hold the centre button and the back button (the one below and left and has a circular arrow on it) Plug in the USB cable Light blink red (Light blink red if I press any other button) Start the app After around 10-12 seconds the remote contacts but not firmware update has taken place. Model is SKIP.1s.RELEASE.A05 and has a FW version of 4.12.6-0-g60dd93b Has anyone got any ideas or can the firmware not be updated on this model? Thanks Graham

Anyone got a code for cursor right? I tried with the flirc app to capture it, to no luck.

Anyone?

Hello, My Skip 1s remote suddenly stopped responding completely as if the batteries were dead after about 2 months of light use. Ultimately I'd like a replacement but after submitting this issue in January of this year, I've gotten no response. There was no damage and no sign of issue the day before. Changing the batteries to a few different newly bought pairs didn't work. It is not recognized by the computer any more. Nothing lights up on it. Not sure why it crapped out but would appreciate suggestions on things to try or would like a replacement seeing this seems like a manufacturing error.

No problem, just good timing on when you posted. I guess you expected the new app, to block the skip software from connecting, in a similar way that the logitech service does. And I guess that proves you can grab sole control over the remote when they are plugged in without asking for extra permissions. Very happy to test any versions as you need (timezones permitting of course will depend on the speed of the answer). PS those commands I mentioned are one of the worst case options, next to doing it manually in the service panel, they just need sticking in a batch file (or run from a command prompt) as long as it has admin privileges - it will just stop and then block the service.

Now it just depends on Windows Universal App will allow me to run an escalated process that uses hidapi to communicate with the remote. It'll be a ton of work. So fucking stupid. Thank you so much for the quick feedback. I'm going to deploy a external windows app that users can run that auto-fixes all this bullshit for now until I can implement my entire USB stack outside the app and hope it works.

So quick test for you. Enabled the service checked the Skip app, fails. As expected. Run this app, get a small window, with disconnected, (percent bar 0% and load file). Plug in the remote Disconnected changes to Connected. Tried this with the service on Auto and Manual, - but running both times the same. The service state does not change and is running all the time. Just to confirm load up the Skip App on its own, and that can't connect. Out of insanity. with the service disabled. this app running, then start the skip app, that throws the warning message again and never connects... until I close this app and then Skip app connects to the remote without needing to be reloaded. So looks like you are onto something. Hope the feedback helps.

I bought a mouse but can don't know why my windows 10 machine is not auto lauching that logitech service. I've also tried installing every damn version of logitech hub I can find... I need help, can someone with the issue please help. Can you start the logitech service that causes the problem. Unplug/plug the remote. Launch the SkipApp to see if the problem exists. Can you tell me if the following app is able to connect to the remote? Download here: Skip Sync If so, I will try one more method. Please, I'm at the mercy of your support since I can't reproduce this, and I can't progress with any features until this is solved and we've been working on it for 3 weeks.

Ohhh it’s not that simple. That’s what I’m trying to do is put this in the app. I need a machine to test this on. The app has limited permissions and I’ve tried stoping other services on my computer and I get permission denied errors. So I’m hoping the app has permission for this service. But would need help. That’s why you get the dialog asking for permissions. I had to run a process with elevated permissions but so far that hasn’t worked for me.

Sorry timezones and such make answering slow at times.. Happy to test anything you have, but to be honest we have a solution, just add that to the faq. Or give them a batch file that if run as admin stops the service and then disables it. A quick test these are the lines people would need to run in a admin command prompt. net stop logi_lamparray_service sc config logi_lamparray_service start= disabled And sc query logi_lamparray_service checks if its running. Still waking up, but could be thrown into a batch file, or I assume you can call this within an app. As said I think you have spent too much of your precious time fixing windows issues, to do much more than have a faq somewhere. But if you have something happy to test and feedback.

Thanks, confirmed I downloaded using the main link above and it includes the learning firmware.

I may be able to detect the service and stop it manually... I'm trying to create an app for test. If anyone has some time today, I would love some help testing this approach. I can't reproduce this locally so am dependent on everyone's kindness and generosity with this.

@jason Thanks for looking at this, and thanks to @Wesley for providing the platform to get to this stage. Can confirm the craziness I had all fixed by stopping the service. No pop up asking for permissions each time which I guess is the big red flag for the future if people have problems. Why these remotes are being picked up as a possible logitech device is strange for sure, I just hope this confirmation and thanks, helps in some small degree. And I do hope you can take a moment to relax and know people are thankful for your support.

Thanks to Wesley, I spent about 7 hours on his machine, and once again, it's Microsoft's fault. Short answer Windows Shipped Broken Software in their Last Update Explanation They now support something called dynamic lighting through human interface devices. Unfortunately, they auto load logitech software that runs when you plug in something that 'may' be in the same category. Logitech software runs and checks to see if it's their device. When they check, they open it, and they never fucking close it. So now no matter what I do, no matter what I try, I can not open my own device because of logitech. Solution Kill the processes Step 1 hit Start and type Services and hit enter. Step 2 Scroll down and find "logitech lamparray service" and double click it. Step 3 Click Stop to stop the service Change the Startup Type to: Disabled Step 4 Unplug the remote and Plug it back in. --- I understand your frustration. But believe me, as someone who has spent 4 years on this product only to keep getting fucked by windows, I assure you, I'm more frustrated. I constantly hault sales because of their bullshit. They force me into a sandboxed envirornment and keep doing stuff like this. I spent almost all night trying to come up with a work around. There is none. I don't have permissions to kill the service within the app. I don't have permission to open the device in shared mode. I tried running an outside program that talks to the USB device but creates a sock connection between the app and the external app but I don't have permission. I'm so fucking angry with them I can't put into words how much of a waist of time this has been. I'm on week 3 of windows only debugging. The only thing I can do now is detect the issue ,and bring up a page to the user and walk them through these instructions.

Wondering the same...rather disappointed by the relatively slow pace of updates even in the Beta channel. Unfortunately so far unable to put my two Skips to productive use due to the cumbersome input switching and the apparent need to go through a TV Power cycle when changing input devices (Kodi on HDMI1 and AppleTV on HDMI2)