JoBo Posted April 6 Report Share Posted April 6 (edited) Hi, I was able to set up the 1s a couple of months to half a year ago. Now that I wanted to add something to the configuration the app does not recognize the remote. When I plug the remote in I can hear the windows connected sound and a device being added to the device manager, but the status in Skip app remains "ManCave is not connected": Yes, the name of the remote is ManCave. I can see the lowermost grayed out button changing to "connecting" when I insert the cable but that is as far as it gets. I've tried two different cables and two different PC,s using both the lates beta x.965 and latest nightly x.965.7441. I'm at a loss here, please assist Edited April 6 by JoBo Link to comment Share on other sites More sharing options...
JoBo Posted April 6 Author Report Share Posted April 6 (edited) Small update: I noticed there is an offline firmware updater and a beta version (4.12.12-beta) of the firmware available here so I tried that. The 1s connects to the updater and I was able to update the firmware of the device it seems. At least the progress bar finished and it says "success". But still it is not connected in the app :/ Edited April 6 by JoBo Link to comment Share on other sites More sharing options...
JoBo Posted April 6 Author Report Share Posted April 6 (edited) Another small update after reading more on the forums: Yes, I get the SkipDeviceBroker-popup and yes I grant it. Yes, Steam is installed on both Windows PC's. Running fully updated windows 11 Edited April 6 by JoBo Link to comment Share on other sites More sharing options...
JoBo Posted April 6 Author Report Share Posted April 6 So I seem to be suffering from the Steam issue as described here: I can workaround the issue by installing the skip app on a PC that has never seen Steam. Seeing that this has been an issue for some nine months now - is there any progress? I'm an open source developer so I can appreciate how difficult things can be, I have actually run into another issue with Steam with their implementation of Steam input, which caused some issues for me (still unresolved even after contacting Valve to try and work something out). But I'd really like to see some developments regarding this issue as it kind of makes the user experience awful. I wouldn't even had known what the issue was unless I researched the issue. Link to comment Share on other sites More sharing options...
jason Posted April 17 Report Share Posted April 17 Long overdue, but I have a temporary solution there that will become more elegant and invisible overtime. Continue the discussion over there. Link to comment Share on other sites More sharing options...
Recommended Posts