torpid hedge
Greetings, entered the server looking for information on how to get a Wooting One working. I had received a hand-down from a friend that was in rough but working shape, and liking it wanted to get another one. Problem was that this new (to me) one wasn't showing up.
The fact that Wootility only really goes "Doesn't show up? You're plugging it wrong. Still doesn't show up? Go to Support." is really not all that useful, and none of my Google-fu was giving me any results. My problem in the end is (I am guessing) old firmware, as it showed up as 03eb:ff01 Atmel Corp. WootingOne while my detected KB was 31e3:1102 Wooting Wooting One. I had mostly used Windows for all of my testing, I had since moved to Linux for lsusb which coincidentally meant looking at the /etc/udev/rules.d/70-wooting.rules file I had to make and have some relief as to the fact that the device I was seeing was there. Looking up that device ID here didn't really give me anything, but "wooting one wootility" gave me https://discord.com/channels/167181566978555904/1090597633392902175 which made me go "wait, there's a restore mode?". Followed the article, and a minute later I'm up and running.
So, restore works and the article is clear (enough) about it. My feedback is more about the fact that I had to join the server here and look at old threads to luck into this information. Wootility doesn't make this clear in probably the most important screen there is: the screen where your keyboard is not being detected. It just throws you to support asking you for an order number. The lack of self-help info that is seemingly there but not accessible at all makes it a bit hard to expect one to really go help themselves out. idk if this would be of use to anyone for future changes, at least I hope this post saves someone from https://xkcd.com/979/
echo canyon
vital marlin