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!
A quick update also from me, now running 6.183. The wake from sleep issue has been completely solved for the last two updates (thank you, Andreas!)
I still observe BTT crashing and restarting after waking up, but it does not happen every time and so far I have not been able to correlate it with anything, other than perhaps the longer the preceding sleep, the higher its likelihood is.
I attached the latest crash log again, maybe it contains something useful: https://pastebin.com/VHdXWHgJ
@Laszlo_Vass your pastebin seems to be set to private, would be great if you could make it public or share via andreas@folivora.ai!
I haven't seen crashes anymore on my system, thus the crashlog would be helpful.
Sorry, I set it to public now.
I think I might have found something in that log. Would be great if you could retry with 6.186!
I updated straight to 6.194, I didn’t have time to test before, but I’m happy to say everything is working perfectly.
Not only is there no BTT crash on wake, but the wake itself seems faster. Earlier the window redrawing (if that’s the word) was slow and blocky, not its buttery smooth. Not sure that’s related to this issue, but good news nevertheless. 
I have not noticed any unintended wakes or crashes in the past days (running 6.194), thank you!! However (let me know if I should post this as a new issue instead), the Logi keyboard mappings seemingly do not work for some time after waking up. That is, after waking from sleep (and only then), keys I mapped via BTT do not do anything. I cannot say whether this affects ALL actions, at least I experienced it with the special (function) keys. I also do not know whether it is only a matter of time until the actions startet to trigger (I would say about 30 seconds after wake) or whether it is some intervention from my side.
Maybe the logs attached can show this: for the first 5 seconds, the issue was still present (key pressed: nothing); afterwards the actions worked as expected.
Let me knof if I should try/report anything or if this should go into a separate thread. Thanks for you continued help!
Logi log new.txt (82.3 KB)
I'll check your logs later!
It can however indeed take a bit until a keyboard is initialized especially if it is connected via receiver (it's faster via Bluetooth). However 30s is still too much, it can take about 10s until all keys are initialized.
If you don't need to change all of the special keys, selecting the ones you need to remap will speed things up significantly:
