thekaptn Posted September 9, 2023 Report Share Posted September 9, 2023 Is there a way to permanently remove the ability for the Flirc usb from waking up the pc? Tried unchecking "Allow this device to wake the computer" and it still happens. Quote Link to comment Share on other sites More sharing options...
jason Posted September 9, 2023 Report Share Posted September 9, 2023 Yeah. Send me your config and I’ll do a trick to disable it Quote Link to comment Share on other sites More sharing options...
thekaptn Posted September 9, 2023 Author Report Share Posted September 9, 2023 (edited) Thanks Jason! Appreciate the quick assist! my_flirc_config.fcfg Edited September 9, 2023 by thekaptn Quote Link to comment Share on other sites More sharing options...
jason Posted September 11, 2023 Report Share Posted September 11, 2023 Here you go, I think you had a duplicate in there too. I didn't remove it because I wasn't sure. That might have been causing the problem. 'noise' is recorded as an extra 'up' keyboard stroke.. wake disabled.fcfg Quote Link to comment Share on other sites More sharing options...
thekaptn Posted September 11, 2023 Author Report Share Posted September 11, 2023 (edited) Thanks! Just did a quick check with flirc_util.exe settings And noticed what your talking about... 5 33733D53 045 02 next_track 6 CF881170 130 01 up 7 2C2DDF24 045 01 up 8 D1B6D3EB 045 01 left #6 does seem like the odd one out of the rest of the codes, I tried to delete it with flirc_util.exe delete_index 6 But it doesn't seem to take effect as running the settings command shows it. Is there another argument that I should be using or could you please remove it? *EDIT* Just noticed this one... 12 10A01061 045 01 0 Not sure if that was from you or not, but if not it could likely be removed as well. Edited September 11, 2023 by thekaptn Quote Link to comment Share on other sites More sharing options...
thekaptn Posted September 12, 2023 Author Report Share Posted September 12, 2023 Hey Jason, was able to kill that mapping using the UI. So far everything seems to be working great! Again, appreciate the assist! Quote Link to comment Share on other sites More sharing options...
jason Posted September 12, 2023 Report Share Posted September 12, 2023 19 minutes ago, thekaptn said: Hey Jason, was able to kill that mapping using the UI. So far everything seems to be working great! Again, appreciate the assist! My pleasure. Yeah, looks like I have a bug in the command, so sorry about that. On my list is a bit of a firmware re-write to bring it up with the remote as well as make the configs human readable JSON. 1 Quote Link to comment Share on other sites More sharing options...
thekaptn Posted September 18, 2023 Author Report Share Posted September 18, 2023 @jason, I noticed over the weekend that things weren't 100%. When applying the profile you gave it seemed to work because I had every device that was listed in... powercfg -devicequery wake_armed ...and then disabled it via... powercfg -devicedisablewake '$DeviceName' ...so when I applied your fix, the keyboard was disabled from waking, so it didn't wake the PC. However, after enabling it with... Enable-WakeForDevice -DeviceName $deviceName ...The remote is waking the PC again through the Flirc when it is sleeping. I confirmed the only device listed as wake_armed is my logitech keyboard that is connected via the unifying USB receiver. Any suggestions on how to only have my logitech keyboard wake the PC? Quote Link to comment Share on other sites More sharing options...
jason Posted September 19, 2023 Report Share Posted September 19, 2023 Send me your config again. Maybe my addition got deleted. Quote Link to comment Share on other sites More sharing options...
thekaptn Posted September 20, 2023 Author Report Share Posted September 20, 2023 Here is the current. I had tried going back to the one you sent, which also has the extra "up" that could be deleted. 2023-09-19.fcfg Quote Link to comment Share on other sites More sharing options...
jason Posted September 20, 2023 Report Share Posted September 20, 2023 Wait, it's not, hang on. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.