keyNotFound(code: "CHWA")

[Tackoil]

After updating the macOS 15.0 beta 5, bclm is not working well. Running read or write will get an error (maybe) following.

keyNotFound(code: "CHWA")

I know that using the beta version of macOS is my own risk. Creating this issue is just for a notice about this change.

[ftpd]

I experience the same issue - just for the record.

[Zw96042]

I'm also experiencing this issue

[IShinji]

same

[CalebMtuwetaM]

I have the same issue

[zackelia]

Ouch, not sure what we can do without it. Unless this was accidental, we'll just have to wait and see what replacement key (if there will be one) can do the same trick. Before, we learned about CHWA from the Asahi SMC driver so we'll see what findings they have soon I assume: https://github.com/AsahiLinux/linux/blob/asahi/drivers/power/supply/macsmc_power.c

[yanzhem02]

I updated my system to 15.1 beta 2 and encounter the same issue.

[TrainerBlade]

same error message. using MacOS 15.0 beta (24A5320a)

[samzong]

same with me. Version 15.1 Beta (24B5024e)

[TimNN]

Asahi now seems to have changes for the latest firmware: https://github.com/AsahiLinux/linux/commit/c6ccbdd693e7d0944642064aa5df1010fe29c35d

[zackelia]

@TimNN Good eye! I'll install Sequoia on another volume and test that out.

[GimmiGoose]

Got this too on 15.1 I am using AlDente until it gets fixed, but will definitely switch back once it is fixed, because I prefer a more "native" solution.

[TimNN]

When trying to manually write to (or read from) CHLS (via smc), I'm getting kIOReturnNotPrivileged:

$ sudo smc -k CHLS -w 0150
Error: SMCWriteKey() = e00002c1

Disabling SIP didn't seem to help either...

[zackelia]

Getting the same error even just reading CHLS. From Console:

kernel    SMCC::smcYPCEventCheck ERROR: not entitled for key CHLS

Not really sure what entitlement I need to sign with to get access to this key. com.apple.private.applesmc.user-access stood out to me but I can't sign with that one.

[TimNN]

Ugh, this is very sad. I guess the only options are:

• Do something like Al Dente does (have the App monitor the charge level and toggle charging).
• Hope that Apple changes their mind and provides a way to write arbitrary SMC values.
• Hope that Apple provides a built-in way to always limit the charge level (as they do for some iPhones, IIRC).
• Reimplement SMC writes in a custom kext (though that obviously has its own problems, especially since kexts are very deprecated).
• Figure out if there's a way to hijack whatever process is in charge of implementing Apple's own "optimize battery charging" feature (and trick it into always limiting the charge level).

[sibilus]

CHWA is also gone on macOS Sonoma 14.7. I seem to be able to read and write CHLS though, but I'm not sure how it's supposed to function as nothing seems to happen when I change it.

[thaff786]

https://github.com/lslqtz/bclm_loop/tree/main

Fork of BCLM called BCLM_Loop which I can confirm does work on Sequoia 15.0 release. It installs and can be enabled pretty much in the same fashion as the original BCLM.

Under the hood it may not be as clean or elegant as the original BCLM as it runs in a loop as a background service (as opposed to writing to the SMC), but it still does the job 100% as far as I can tell so far with no impact on battery life when unplugged.

Still hoping the original BCLM can be fixed though.

[TimNN]

@sibilus: Which value did you try to write? Based on the Asahi code, setting CHLS to 0150 (hexadecimal) should have a similar behavior to setting CHWA to 1.

(The 01 apparently means "discharge down to target percentage" and 50 is the target percentage, in this case 80%).

[anqut]

I'm getting the same error, after updating to macOS 15.0

[zackelia]

This is great news if people are able to read/write CHLS! Something must've changed since the last beta if the entitlement isn't necessary anymore? I'll be able to test it out again in a few days.

[TimNN]

@zackelia: The success report was for "macOS Sonoma 14.7", so I have very little hope that this is going to work on 15.0.

I assume that 14.7 got the firmware update with CHLS, but the entitlement protections were only implemented in 15.0.

On the 15.0 release (24A335)) I still cannot write CHLS. I'll be testing this on all future releases as well, of course, but have relatively little hope.

[sibilus]

@TimNN: I've tried 0150 on 14.7, but it doesn't seem to work, unfortunately.

[wpiekutowski]

I tried CHLS with 0150 and 0100 (which seems to be supposed to cause discharge) on 14.7, but both values unfortunately do nothing.

I'm turning on builtin "Optmized battery charging" and I'll see if they maybe improved it.

[yuukiyuuna]

in macos 15.0 not work

[ryudexter]

My OCD is going nuts seeing the battery icon go to %81 😅 Really hope this can be a fix for this awesome application 🙏🏻

[emmaus-zam]

My OCD is going nuts seeing the battery icon go to %81 😅 Really hope this can be a fix for this awesome application 🙏🏻

agreed! for anyone struggling with this I found the free version of AlDente to be an adequate replacement. It's inferior since not a native solution, so hopefully it's only temporarily needed.

[myTerminal]

agreed! for anyone struggling with this I found the free version of AlDente to be an adequate replacement. It's inferior since not a native solution, so hopefully it's only temporarily needed.

I tried it, and it does seem to work even without a reboot. Now we just have to wait for a fix, but have something to use till then.

[Immortalin]

I am pretty sure they have the same issue

https://github.com/AppHouseKitchen/AlDente-Charge-Limiter/issues/1326

[sozercan]

I changed to use https://github.com/mhaeuser/Battery-Toolkit now which works with any limits.

[chriswep]

I am pretty sure they have the same issue

https://github.com/AppHouseKitchen/AlDente-Charge-Limiter/issues/1326

They use a background process to monitor the battery. This is different from just setting an SMC value and letting the MacBook firmware do the rest which this tool does. The AlDente method still works with sequoia, I have it currently running.

[linkc0de]

macOS Ventura 13.7 (22H123) : same issue

[ninadpchaudhari]

This is so backwards! Seems they added a feature to limit charge on new iPhone 16 models [1] while removing the ability to write to SMC to achieve the exact same thing on Macs with Sequoia

[PiterrsPl]

i hope it will renew for this system during zackelia

[eproxus]

I could swear the charge limit set by bclm was synced to my Apple Watch as well which never charged over 80% when I had it enabled on my M2 MacBook Pro (but obviously not on my iPhone 14 Pro), but now with Sequoia it charges back to 100% again.

[ssh352]

upgraded from 14.6.1 -> 14.7 got the same issue.

[IshanFernandoCutAndDry]

macOS 15.0 same issue

[pgardiner]

Same issue on macOS 15.0. Using Al Dente for now, but would like to go back to bclm, which has been perfect since I started using it, and has definitely extended my battery life.

[PiterrsPl]

https://github.com/lslqtz/bclm_loop/tree/main > > Fork BCLM o nazwie BCLM_Loop, który mogę potwierdzić, działa na wydaniu Sequoia 15.0. Instaluje się i można go włączyć w taki sam sposób jak oryginalny BCLM. > > Pod maską może nie być tak czysty lub elegancki jak oryginalny BCLM, ponieważ działa w pętli jako usługa w tle (w przeciwieństwie do pisania do SMC), ale nadal wykonuje pracę w 100%, o ile mogę powiedzieć do tej pory, bez wpływu na żywotność baterii po odłączeniu zasilania. > > Nadal jednak mam nadzieję, że oryginalny BCLM może zostać naprawiony.

https://github.com/lslqtz/bclm_loop/tree/main

Fork of BCLM called BCLM_Loop which I can confirm does work on Sequoia 15.0 release. It installs and can be enabled pretty much in the same fashion as the original BCLM.

Under the hood it may not be as clean or elegant as the original BCLM as it runs in a loop as a background service (as opposed to writing to the SMC), but it still does the job 100% as far as I can tell so far with no impact on battery life when unplugged.

Still hoping the original BCLM can be fixed though.

hi i have one question how to install this fork ? because its not so easy like using brew. please help me because I have spend few hours to install this fork and I have no idea how to do this .. my Mac is with m1 procesor

[lslqtz]

hi i have one question how to install this fork ? because its not so easy like using brew. please help me because I have spend few hours to install this fork and I have no idea how to do this .. my Mac is with m1 procesor

brew support has been added, but versions obtained through it may occasionally be out of date.

BTW: It only supports Apple Silicon based Mac computers. (I don't have an Intel Mac to test)

$ brew tap lslqtz/formulae
$ brew install bclm_loop

And, macOS 15.1 beta 5 still does not provide the required permissions to write to CHLS.

$ sudo smc -k CHWA -r
  CHWA  [    ]  no data
$ sudo smc -k CHLS -r
Error: SMCReadKey() = e00002c1

[ssh352]

I changed to use https://github.com/mhaeuser/Battery-Toolkit now which works with any limits.

@lslqtz I was deciding on bclm_loop and Battery-Toolkit, could you advise on the benefits of bclm_loop over Battery-Toolkit?

for reference: I've asked the Battery-toolkit author https://github.com/mhaeuser/Battery-Toolkit/discussions/38

ideally the micro charging is as infrequent as possible when the laptop runs on power adapter.

[variia]

@ssh352 i switched to Battery-Toolkit yesterday temporarily. it is GUI but i like the more fine-grained control over my charging and the option to drain (condition) my battery while in clam-shell mode.

[lslqtz]

I changed to use https://github.com/mhaeuser/Battery-Toolkit now which works with any limits.

@lslqtz I was deciding on bclm_loop and Battery-Toolkit, could you advise on the benefits of bclm_loop over Battery-Toolkit?

for reference: I've asked the Battery-toolkit author mhaeuser/Battery-Toolkit#38

ideally the micro charging is as infrequent as possible when the laptop runs on power adapter.

bclm_loop is an improvement on bclm [1]. It has no GUI and runs silently in the background. This means it does not occupy the menu bar, but is less flexible. In terms of energy consumption, although the two projects use different methods, there is almost no difference in actual use. In addition, since the code of bclm_loop is simpler, it is easier to make user-defined code modifications.

In addition, bclm_loop, like bclm, (used to) support firmware-based charging control, and the current version of bclm_loop will still try to use firmware-based charging control on supported firmware.

[1] The original purpose of bclm_loop was to provide MagSafe LED control capabilities based on bclm. (PR https://github.com/zackelia/bclm/pull/39)

If you need a GUI and the greater user flexibility it provides, there are other options, including this one or something like AIDente.

[ssh352]

In addition, bclm_loop, like bclm, (used to) support firmware-based charging control, and the current version of bclm_loop will still try to use firmware-based charging control on supported firmware.

thanks very helpful info.

"Battery Toolkit uses the OS APIs to be notified of changes to the charging level and is idling most of the time. "

Battery-toolkit appears not firmware based though.

[PiterrsPl]

thx

[PiterrsPl]

hi i have one question how to install this fork ? because its not so easy like using brew. please help me because I have spend few hours to install this fork and I have no idea how to do this .. my Mac is with m1 procesor

brew support has been added, but versions obtained through it may occasionally be out of date.

BTW: It only supports Apple Silicon based Mac computers. (I don't have an Intel Mac to test)

$ brew tap lslqtz/formulae

$ brew install bclm_loop

And, macOS 15.1 beta 5 still does not provide the required permissions to write to CHLS.

$ sudo smc -k CHWA -r

  CHWA  [    ]  no data

$ sudo smc -k CHLS -r

Error: SMCReadKey() = e00002c1

Thx very much for help

[Nolenius]

I'm also hoping the original BCLM can be fixed, very helpful! Does anyone use batt [https://github.com/charlie0129/batt] ?

[reedgrass777]

Does anyone use batt [https://github.com/charlie0129/batt] ?

Why should I prefer BCLM over batt? It seems batt gets the job done, isn't it?

[sozercan]

Why should I prefer BCLM over batt? It seems batt gets the job done, isn't it?

Main difference is that bclm doesn't run in the background, but it's at the firmware level. Anything else runs in the background.

[majal]

Why should I prefer BCLM over batt? It seems batt gets the job done, isn't it?

Main difference is that bclm doesn't run in the background, but it's at the firmware level. Anything else runs in the background.

Which further means that batt and others will not be able to monitor charging if the system is suspended. (That's why batt by default will disable charging before suspend, which means no charging of a closed laptop.)

I'm actually thinking of having both batt and bclm together. batt has more features while the computer is on, and bclm limits charging even when the system is suspended.

[ivankovnatsky]

Forgive me, but this does not seem like a suitable place to discuss other battery tools.

[yuukiyuuna]

Is there any update plan for this project ?