I Andreas, thanks for continuously looking into this. At least for me, the recent update (6.129) did not solve the issue. I appreciate any hints on what I could try.
Unfortunately, the problem is not fixed for me either. I did notice one change since being on 6.127+ though: previously the “Logitech Mouse Configuration” node would need to be deleted to stop causing screen wakes, now it just needs to be disabled.
that is actually very helpful info as it confirms the code path that causes the issue. Could you try once more with 6.133?
This might have done it. I’ll test it more tomorrow, but for now the device is soundly asleep with Logitech Mouse Configuration enabled.
Thank you for your hard work, Andreas.
EDIT: After testing it for 2 days, the wake issue is fixed for me, thank you.
I’m on a Mac mini, so I don’t have a battery or battery apps ![]()
But I can confirm that on 6.137 the issue seems to be solved for me, the system goes to sleep and stays asleep with the mouse turned on ![]()
What is maybe odd, is that now the BTT app quits and restarts after the system wakes (sometimes, but not always triggering the “this app quit unexpectedly“ notification) - I will continue to test and report back
@Laszlo_Vass that restart is a crash, I think it should already be resolved in 6.138 - if not it would be great if you could send the crashlog from the macOS console app's crash report section
Unfortunately it’s still happening for me on 6.138. I attached the most recent crash log:
I no longer observe the waking issue (thank you!) but now seem to have the problem that after waking, the Logi-specific commands are not recognised for some time. The usual BTT triggers work just fine, but the Logi special keyboard keys are not triggering. I have not quite figured what specifically reverts the issue (wait for a minute, restart BTT, click something...) and I am not sure whether it is related to this original issue. Apologies for being so unspecific, please take it more as a feedback on the updated BTT version than as a bug submission.
@BerndBread I know, I'm currently working on that! A new release that should fix this while maintaining the wake sleep issue fix should be available later today!
6.152 should solve the wake issue!