My utility put in two different peak periods just to be a-holes as the app only lets me guarantee one period is respected as peak...Including the link would help, eh? Powerwall2 update – Time-of-Use enabled – MikesGear
You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
My utility put in two different peak periods just to be a-holes as the app only lets me guarantee one period is respected as peak...Including the link would help, eh? Powerwall2 update – Time-of-Use enabled – MikesGear
I'm trying to work out exactly what is going on with the way my PW2 is charging from Off-Peak overnight. I've got it set in TBC cost-saving mode. Originally (over the winter) it would charge to 100% and then start discharging at the start of the expensive rate. With the increase in solar generation now the days are starting to extend in the UK, I had already started to do what John suggested by shortening the off-peak period to reduce the amount stored in the battery. However in the last week or so I've noticed that even though I set the off-peak period back to the full time, the battery is not charging to 100%. It's typically only going to around 70% +/- 5% and then sits at that level until the start of the normal rate. It's as if it's decided how much generation I will get and so is not charging fully. Which would be fine except 2 days ago the weather was rubbish (and I knew it would be from the forecast) but there was no way to actually get the PW to fully charge from off-peak electricity so I ran out of stored energy about 4 hours before off-peak started again. I would expect that behaviour in balanced mode maybe but not in cost-saving mode. Does anyone have a good idea of the actual logic being used behind the scenes? The app is reporting Version 1.45.0 - not sure if that is the Powerwall vesion or the app version!I've figured out a work-around for the lack of user control in Cost Saving mode over the maximum off-peak charging from the grid: Shorten the off-peak period in the Tesla app. It's not an ideal fix as the PW will using battery power during the remainder of the true off-peak period but the financial loss due to round-tripping that power is a lot less than the loss which occurs if the battery can't use the day's excess solar power so it goes to the grid. Some snow has also revealed the need for user control over the minimum off-peak charge but I haven't yet figured out a fix for that (I don't have a backup gateway). There had been a sunny day two days before the snow arrived so the PW only charged itself to 60% the night the snow arrived.
I'm trying to work out exactly what is going on with the way my PW2 is charging from Off-Peak overnight. I've got it set in TBC cost-saving mode. Originally (over the winter) it would charge to 100% and then start discharging at the start of the expensive rate. With the increase in solar generation now the days are starting to extend in the UK, I had already started to do what John suggested by shortening the off-peak period to reduce the amount stored in the battery. However in the last week or so I've noticed that even though I set the off-peak period back to the full time, the battery is not charging to 100%. It's typically only going to around 70% +/- 5% and then sits at that level until the start of the normal rate. It's as if it's decided how much generation I will get and so is not charging fully. Which would be fine except 2 days ago the weather was rubbish (and I knew it would be from the forecast) but there was no way to actually get the PW to fully charge from off-peak electricity so I ran out of stored energy about 4 hours before off-peak started again. I would expect that behaviour in balanced mode maybe but not in cost-saving mode. Does anyone have a good idea of the actual logic being used behind the scenes? The app is reporting Version 1.45.0 - not sure if that is the Powerwall vesion or the app version!
Thanks for your confirmation. I've since written a small utility that runs on my Raspberry Pi that allows me to set the backup percentage automatically during off-peak electricity period so that I can essentially set a minimum charge level when off-peak period ends. I implemented that following two nights ago where the Powerwall decided to only charge up to 26% overnight which left me out of power with 6 hours left to off-peak electricity. The weather forecast was pretty accurate in suggesting there would be minimal generation but obviosuly the powerwall does not take any notice of that, simply the fact that the previous two days had good generation...There are a lot of UK users that have the same complaint - the system is basing its operation on history, not forecast. So, in the highly variable weather in the UK, the results are not nearly as good as one would hope.
Sorry I don't have any more useful information, other than the fact that you're not alone.
I'd love to have a way to set that "minimum charge level at end of off-peak" without having to buy a backup gateway (not available here when I bought my PW). I've previously asked Tesla support to add this feature (sensibly a min + max level) and I'll have to ask again as this time of year seems to be particularly traumatic for Tesla's algorithm which also appears to consider the solar generation of several days ago but ignores yesterday's generation.Thanks for your confirmation. I've since written a small utility that runs on my Raspberry Pi that allows me to set the backup percentage automatically during off-peak electricity period so that I can essentially set a minimum charge level when off-peak period ends. I implemented that following two nights ago where the Powerwall decided to only charge up to 26% overnight which left me out of power with 6 hours left to off-peak electricity. The weather forecast was pretty accurate in suggesting there would be minimal generation but obviosuly the powerwall does not take any notice of that, simply the fact that the previous two days had good generation...
Had a Powerwall 2 and gateway installed in April. It's purpose is to cover power outages (rural location puts us at risk), make better use the solar power from our PV (rather than export to the UK grid), and to shift load by charging the battery at cheap overnight rate from the grid. The later will be the main mode of use over October to March.
We are getting heartily sick of the lack of local control of the gateway. Who really cares that we can (maybe) see what our Powerwall is doing from anywhere in the world with an internet connection, when we can't immediately control it locally and maybe not even at all if there are internet connectivity or server problems. The increasingly flaky firmware Tesla release (without explanation), not to mention the UI downgrade of the v4 app (did people really get paid to develop that!!) is also a frustration.
The best approach for us would be to be able to change the power reserve percentage locally on the gateway via API - no need for internet connectivity, no need for Tesla mothership servers, no delay while things maybe communicate or not. Is there a way to do that via API? Has anyone got something like that working directly on the gateway? We have tech skills (see more below) just need pointing in the right direction.
We have tried to use time-based control, but clearly the algorithm is not designed to allow for the varied nature of UK weather (today I may generate 19kWh, and tomorrow only 3kWh) nor how our domestic power consumption varies from day to day. Doesn't matter how much data Tesla have, it repeatedly does not charge overnight on the cheap electricity. What would work perfectly is to simply be able to tell the gateway daily what percentage we want the Powerwall to be charged to using cheap off peak power. As humans we can look at the local weather prediction, consider our activities (things Tesla mothership can not know) and set that percentage before bedtime.
Currently we run in self-powered mode and adjust the power reserve percentage accordingly, but it is inconvenient to have to be awake at 00:30 and 4:30 to set power reserve percentage using the app. Thankfully we have tech skills, so we wrote a Python app that runs on RPi and sends setting changes via API to Tesla mothership at chosen times. Mimicking the official app in this way was working well until a few weeks ago when we noticed that the settings changes were no longer being applied immediately, and sometimes not at all. Random delays of up to hours happened for changes made from both our Python app and the official app. The settings reported from Tesla mothership (via API or official app) would change but be out of sync with the true gateway status (as viewed via wifi) despite reporting it was connected OK. What a useless mess Tesla.
Just to add, in a similar time frame we have had problems getting it to monitor our solar. This uses a 2nd neuriometer and suddenly was not being seen by the gateway. Reporting this to support has resulted in several firmware updates (on 21.35.0 today), and days with it working and then being dropped again. Support have tried to blame "atmospherics and wifi", but it is in direct line of sight 4m from the gateway and worked perfectly for months through all possible conditions! At the moment it can see it so maybe 21.35.0 was the cure (or are they just throwing firmware at it?).
Thank you for the interest @jjrandorin but I'm a bit surprized you have tacked my post onto a zombie thread from over a year ago. Tesla changed the security for API access in March 2021 making any older answers unlikely to work now.Note that I am not endorsing anything specific, just pointing you at some threads to check. I moved your post into one thread on this discussion, and am providing a couple of links for discussions on this topic that I am aware of that have occured here.
Thank you for the interest @jjrandorin but I'm a bit surprized you have tacked my post onto a zombie thread from over a year ago. Tesla changed the security for API access in March 2021 making any older answers unlikely to work now.
I have had a good search of the forum including the threads you mention already an unable to find any discussion of setting Powerwall parameters directly at the gateway via API. It seems mad to me if this is not possible, but Tesla seem to think mothership must always be in command. Oh well hope someone notices this query.
Thank you for the interest @jjrandorin but I'm a bit surprized you have tacked my post onto a zombie thread from over a year ago. Tesla changed the security for API access in March 2021 making any older answers unlikely to work now.
I have had a good search of the forum including the threads you mention already an unable to find any discussion of setting Powerwall parameters directly at the gateway via API. It seems mad to me if this is not possible, but Tesla seem to think mothership must always be in command. Oh well hope someone notices this query.
Sure, I'm in. As a customer I have a very poor view of Tesla products, particularly their software, already given their app a 1 star review for the UI downgrade of v4.I think it is time to act as a group and make our voices heard.
@zTesla you get data from the gateway, have you also tried setting values locally using the API? Also is that via wifi or have you managed to locate the gateway on your network?The local API has generally been stable for me. I've had two main glitches since beginning automation last year related to when authentication methods were changed. Even the data I had gone out to the cloud API for, I can now get locally. [knocks on wood]
Have not tried setting values (yet); that's next. TEG is connected via ethernet to router with a fixed IP (tied to TEG MAC address)@zTesla you get data from the gateway, have you also tried setting values locally using the API? Also is that via wifi or have you managed to locate the gateway on your network?
Until a month ago Powerwall has done its off-peak charging at about 3.45kW so the 4 hours of Octopus Go is just about enough to get it full charged so I'm surprised if you are seeing 1.7kW charge rate unless Tesla has sabotaged something in a recent firmware update. However, I completely agree about the need for more convenient user control as today's gloomy weather has coincided with higher than usual domestic electricity consumption so the battery, which saw no need for off-peak charging after yesterday's sunshine is approaching empty. As I don't have the backup Gateway I can't force it to charge. It will, I expect, charge itself tonight ready for tomorrow's sunnier day but I'm going to be paying for some full-price electricity prior to 00.30.Primary use is to load shift - charge the Powerwall in the 4 hours of off-peak cheap overnight electricity. To achieve this we use self-powered mode and adjust the power reserve percentage, however that means a charge rate of 1.7Kw, and so we can only get a max of 6.8kWh into our battery (practically a bit less because of losses, server delays in applying commands etc.). We can not rely on time-based control mode because the algorithms Tesla uses is not fit for purpose (in can not accommodate variable weather and variable domestic demand).
Yes, on Octopus tariff too @JohnRatsey and what you describe is exactly the weather/use situation that Tesla does not handle. Algorithm (and limited gateway control options) designed by people living in the constant Californian sunshine I guess.Until a month ago Powerwall has done its off-peak charging at about 3.45kW so the 4 hours of Octopus Go is just about enough to get it full charged so I'm surprised if you are seeing 1.7kW charge rate unless Tesla has sabotaged something in a recent firmware update. However, I completely agree about the need for more convenient user control as today's gloomy weather has coincided with higher than usual domestic electricity consumption so the battery, which saw no need for off-peak charging after yesterday's sunshine is approaching empty. As I don't have the backup Gateway I can't force it to charge. It will, I expect, charge itself tonight ready for tomorrow's sunnier day but I'm going to be paying for some full-price electricity prior to 00.30.
Even in California, it rains and gets overcast...despite what the song says.Yes, on Octopus tariff too @JohnRatsey and what you describe is exactly the weather/use situation that Tesla does not handle. Algorithm (and limited gateway control options) designed by people living in the constant Californian sunshine I guess.
I think 3.45kW charge rate from grid only happens when in time-based control mode and the algorithm decides to charge from grid by some amount at that rate. It also did the same higher rate in the now removed backup only mode. But when in self-powered mode it is only a pathetic 1.7kW. Why?