Jump to content
Flirc Forums

Leaderboard

Popular Content

Showing content with the highest reputation on 05/26/2017 in all areas

  1. Okay guys, I think I figured it out. I pushed an update, GUI version v2.3.8 which has new firmware in it. So confident, I made it public, however, this may in fact just fix @Montas system. But I'm fairly confident. Seems to be a windows only thing, they send a set remote wake up feature request down to the device, in which case I would send a stall/nack. Windows said, 'oh yeah, fuck you' and then disconnected me. I'm now returning OK. This is not a required feature, apparently windows 10 says it is. Please don't leave me hanging if it works, please report back here and let me know. This was both brutal in finding, repeating, and solving.
    2 points
  2. I'm confident this was the issue. After seeing it, finding the problem, understanding it, I have extremely high confidence. This problem only exists for a small portion of users, and it follows windows as well. Blatant disregard to violate the USB spec. I owe you guys a second unit for your patience and help.
    1 point
  3. I owe you guys the thank you. And endless amount of gratitude for your patience and support.
    1 point
×
×
  • Create New...