Charge limit no longer changing with policies
See original GitHub issueRecently I’ve noticed my car charging during scheduled time when SoC is above 50%. My configuration in /etc/twcmanager/config.json is as follows:
"chargeNowLimit": -1,
"greenEnergyLimit": 90,
"scheduledLimit": 50,
#"nonScheduledLimit": -1,
This was working fine with no updates or config changes taking place, so I assume this must be TeslaAPI related. I am able to start/stop charging OK so I think the API connection is OK. TWCManager is v1.2.6.
If I manually adjust the charge limit from the app, TWC Manager doesn’t change it back to 50% or 90% in either scheduled or green energy policy times.
If logs are helpful, I’ll just need a but of a noob guide on how I go about providing them.
Issue Analytics
- State:
- Created a year ago
- Comments:12 (1 by maintainers)
Top Results From Across the Web
About Optimized Battery Charging on your Apple Watch
Optimized Charge Limit changes dynamically depending on how you use your Apple Watch Ultra. Based on your usage patterns, your watch might ...
Read more >How to Extend Your Windows Laptop's Battery Lifespan With a ...
This setting maximizes the battery health by lowering the maximum battery charge level to 80%. Next, press the F10 key to save the...
Read more >Can my credit card issuer reduce my credit limit?
If a card issuer decreases your credit limit, the card issuer cannot charge you over-the-limit fees or a penalty rate for exceeding your...
Read more >What Is Regulation D – Forbes Advisor
The Federal Reserve's Regulation D no longer limits the number of transactions and withdrawals you can make in your savings or money market ......
Read more >Fact Sheet: Calendar Year (CY) 2023 Medicare Physician Fee ...
On November 01, 2022, the Centers for Medicare & Medicaid Services (CMS) issued a final rule that includes updates and policy changes for ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yup that was it. The issues I do believe started when I changed the 50 to 40 a couple weeks ago. Just didn’t see the note about 50-100 being the valid range (probably saw it initially years ago). Anyway thanks @alexeiw123 for helping troubleshoot that!
@ngardiner is correct – anything less than 50 or greater than 100 is equivalent to
-1
– return to the original limit.