drafts:dynamic_ess
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
drafts:dynamic_ess [2024-02-19 14:35] – dfaber | drafts:dynamic_ess [2024-11-09 15:16] (current) – [Q: My providers changes price at the half hour instead of the full hour] aleximb | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== Dynamic ESS - manual |
- | Dynamic ESS is an algorithm that aims to minimise the costs made on the grid and battery: | + | ===== Smarter energy, bigger savings with Dynamic ESS ===== |
- | * By scheduling charge/ | + | |
- | * While taking grid limitations, | + | |
- | * When it can, it also considers the consumption and solar yield forecasts when scheduling. | + | |
- | __NOTE: **Right now Dynamic ESS is still in beta and only available via the beta VRM.**__ | + | With Dynamic ESS, your Victron system becomes even smarter. It optimizes your battery' |
- | Also check these community posts for remarks and further troubleshooting: | + | Whether you're managing a home or a larger installation, |
- | - [[https:// | + | |
- | - [[https:// | + | |
- | - [[https:// | + | |
- | - [[https:// | + | |
- | ==== Can I use it? | Eligibility Criteria ==== | + | If you have dynamic energy rates or off-peak energy prices, start configuring now to take full advantage of your setup! |
- | Dynamic ESS is only eligible for the installations which fits the following criteria: | + | {{:drafts: |
- | * Be an ESS; | + | ==== Two modes: green or trade ==== |
- | * Not use Generator connection outside of power outages; | + | |
- | * Have a variable | + | |
- | * Have all loads behind the Victron system | + | |
- | Note: | + | We offer two operating modes to cater to different preferences for managing |
- | * //Only the dynamic | + | |
- | * If you have fixed prices (which may differ weekends/ | + | |
- | * **In case your system setup has heavy loads (EV charger, heat pumps) in front of the Victron system, there is a chance that the total load of the system exceeds what your main fuse can handle, causing it to break. See [[drafts:dynamic_ess# | + | |
- | ====== How can I get started? | Configuration ====== | + | |
- | {{: | + | === Green Mode === |
- | To get started, you need to provide VRM with the necessary configuration Dynamic ESS requires. To do this, you can navigate to //Settings -> Dynamic ESS// and follow | + | Sell surplus solar power back to the grid after covering your consumption |
+ | Reserve battery energy for your own use. | ||
+ | Charge your battery when prices are low to save more. | ||
- | From the page, you can configure | + | === Trade Mode === |
+ | Always sell surplus solar power back to the grid. | ||
+ | Use the battery energy to take advantage of trading opportunities. | ||
+ | Charge your battery when it’s most beneficial for trading. | ||
- | Also make sure that you have set the location of your device (so we can do the correct solar forecast) and have " | + | Green Mode is ideal for those who prefer a safer, more predictable approach, while Trade Mode is perfect for those looking |
- | ==== Step 1: System ==== | + | |
- | First thing we need to know is whether or not you can sell back to the grid or not. If you can, you get additional questions on the power limits when selling back. This is the lowest one of either your grid connection or what your system is capable of. So if your grid connection can do 4 kWh and your system 2.5 kWh, fill out 2.5 kWh. | ||
- | Note that this is part is setting the capabilities, | + | ====== Let’s get started ====== |
- | ==== Step 2: Battery | + | |
- | Then we need to know information on your battery: | + | Setting up Dynamic ESS happens in 5 steps. All of these settings can be adjusted later, so no worries if you make a mistake. Head over to settings → Dynamic ESS in VRM to get started! |
- | * //Battery Energy Capacity// - In order to calculate how much 1% of SOC of the battery is, we need to know how much capacity the battery has. | + | |
- | * //Maximum charge and discharge power// - This is used for determining the maximum amount we can (dis)charge the battery | + | |
- | * //Battery costs// - Battery costs indicate how expensive it is to use it for charging and discharging, | + | |
- | costs for buying the battery in € / (charging cycles * battery capacity in kWh) | + | ==== Step 1: System ==== |
- | One battery charge cycle equals full battery charged to 100% and fully used to 0%. If you only use half of the battery power, then recharge it and repeat it the following day — it will also count as one charge cycle instead of two. The number of charging cycles is a number that differs per brand. The battery costs is usually somewhere between € 0.02 and € 0.06 /kWh. | + | |
- | Some feedback of users is that they don’t care about the battery costs, as they already paid for it, so technically there’s no additional costs to charge it. In that case we still advise to put a small amount in as battery costs. E.g. 0.01 €/kWh. | + | |
- | In order to make the calculation for you, you can also fill out the invoiced battery cost and the estimated amount of cycles the battery can do. Together with the filled out battery capacity this will calculate the price for you. | + | First, confirm whether |
- | * //Configure Dynamic ESS SoC// - The Minimum Dynamic ESS SOC determines when Dynamic ESS will stop selling to the grid to leave enough energy for self-consumption. By not setting the Minimum Dynamic ESS SOC separately, Dynamic ESS will use the Minimum SOC instead. | + | |
- | If you set the min soc using the slider, then save the form, it will not have been logged to lastLogData yet. Thus the old value will be used in the schedule. Installation will handle this, and the next hour the correct value will be used. | + | Note: This step defines |
- | ==== Step 3 and 4: Buy and sell prices ==== | + | {{:drafts: |
- | For buying and selling you can either have dynamic (day ahead) prices or fixed prices (which can differ at different times / weekend vs weekdays). So first you need to fill out if you have fixed or dynamic pricing. | + | ==== Step 2: Battery information ==== |
- | === Dynamic prices === | + | Next, provide key details about your battery: |
+ | * Battery Capacity – To calculate what 1% of the battery' | ||
+ | * Maximum Charge and Discharge Power – This determines how much energy the battery can handle for charging or discharging in an hour. | ||
+ | * Battery Costs – These reflect the cost of charging and discharging the battery, usually expressed in €/kWh. | ||
- | Each country and provider uses their own formula for pricing. As the system grows, we will have more and more pre-filled out formula' | + | To calculate battery costs, you can input the purchase cost of the battery, the estimated number of charge cycles, and the battery’s capacity. Use the formula: |
- | The buy price formula and sell price formula | + | Battery cost (€) / (Number of charge cycles * Battery capacity in kWh) |
- | * p - the dynamic price / kWh | + | For example, if your battery cost €2,000, has a capacity of 10 kWh, and supports 6,000 charge cycles, |
- | * € 0.02 - energy provider profit share | + | |
- | * € 0.13 - DSO working price + contributions/ | + | |
- | * 21% - tax | + | |
- | The sell price formula looks often identical and in common cases looks something like (//p-0.02+0.13)*1.21//. So the energy provider profit share works the other way around. | + | 2000 / (6000 * 10) = € 0.03/kWh |
- | With different providers, the formula will likely be different. So this does require some research on how your pricing is build up. You can also get some ideas from [[https:// | + | * Charge/ |
- | === Fixed prices === | + | {{: |
- | If you have a fixed prices contract, you can still have different prices at different moments of the day. In some cases you can have different prices between weekdays | + | ==== Steps 3 & 4: Buying |
- | Then, you can fill out the price per hour (more granularity is currently not possible). | + | For energy transactions, you can use either **dynamic** |
- | ==== Step 5: Confirmation ==== | + | |
- | In the final step you see the filled out values summarised. If you need adjustments, you can do so. Otherwise you can //submit// the form and Dynamic ESS. | + | For the UK, Spain and France, |
- | You can now go to the Installation’s Dashboard and click the button shown below to open the Controls menu. Under the ESS section, you will find Dynamic | + | === Your Dynamic |
- | {{:drafts: | + | Getting your dynamic pricing formula is important, but it might not be easy to find in your energy contract. Let’s break it down with an example: |
- | ==== What's next? | After configuration ==== | + | When you sell energy back to the grid, you get the base rate from your energy provider. But when you buy energy, you also pay VAT and an extra charge of 11 cents per kWh. |
- | As the configuration flow points out, you need to go to the // | + | |
- | {{ :drafts:dynamic-ess-controls.png? | + | **Selling Energy**: Your selling formula is just: P |
- | The //Auto// mode is the usual mode in which Dynamic ESS should operate. The //Buy// and //Sell// modes are there you want to overrule the decision of the algorithm and fully charge or discharge the battery. | + | **Buying Energy**: Your buying formula |
- | If you want to disable Dynamic ESS, set the mode to //Off//. | + | |
- | Note that there will be shown an extra mode called // | + | If you’re not sure about your rates, start with a simple P for the price. You can compare the numbers in VRM with those in your energy provider' |
- | ====== Operational ====== | + | |
- | ==== Data Visualisations ==== | + | |
- | Note that there are still some issues with having the graphs show the data correctly. | + | {{: |
- | Once operational, | + | ==== Step 5: Confirmation ==== |
- | {{ : | + | In the final step, review a summary of all the settings you’ve entered. Make any necessary adjustments, |
- | On the left side of the vertical line, you see the recorded values. On the right side of the line it shows the solar forecast, the consumption forecast and also the target SOC that will be followed (as scheduled during the last calculation for the site). | + | ===== Tracking your daily energy schedule ===== |
- | By clicking | + | Once you've configured Dynamic ESS, a new section will appear at the bottom of your VRM dashboard. This section displays a graph showing today' |
- | Below you first find a summary on the totals for the day and then there are three tabs which visualise: | ||
- | * Earnings made as a result of Dynamic ESS usage; | ||
- | * Schedule of battery and grid usage; | ||
- | * All factors which are taken into account when scheduling (coming soon) | ||
- | === Costs and earnings | + | ===== Want to know more? ===== |
- | This tab begins with a summary that compares the system using Dynamic ESS with the system using regular ESS. | + | For more information on Dynamic ESS, check out our frequently asked questions. For some countries, Dynamic ESS provides an out of the box connection |
- | === Schedule | + | ===== For Victron installers ===== |
- | {{ : | + | |
- | The prices graph is available on both this tab and the //Energy// tab. It shows the buy and sell prices | + | As a Victron device installer, Dynamic ESS allows you to offer enhanced value to your clients while unlocking new sales opportunities. By intelligently optimizing battery charging |
- | {{ :drafts:energy-usage.png? | + | These savings can be further amplified with larger battery capacities. As customers see the financial benefits of increased battery storage, they are more likely to invest in expanding their energy |
- | The usage graph shows the energy usage of the grid and of the battery in kWh. | ||
- | === Energy === | ||
- | The prices and graph is the same one as on the // | ||
- | |||
- | {{ : | ||
- | |||
- | Then there is the energy graph, which summaries everything the system has done and is planning for. | ||
- | |||
- | ==== Warm-up period ==== | ||
- | Dynamic ESS uses consumption and solar yield forecasts to schedule ahead, when the forecasts are available. Depending on the historical data available prior, the accuracy of these forecasts can vary. As it stands now, optimal consumption forecasts need 28 days of past consumption data and optimal solar yield forecasts need 28 days of past solar data. Thus, if there is not enough data the forecasts might be suboptimal which makes the performance of Dynamic ESS suboptimal. However, despite lower accuracy in forecasts, turning Dynamic ESS on in this period is still more cost-efficient and it gets better every day until it reaches its optimal state after 28 days of warm-up period. | ||
- | |||
- | ==== Unexpected behaviour? ==== | ||
- | It is possible that you deem the behavior of Dynamic ESS to be unexpected or suboptimal. Depending on when it happens, there are two possible causes: | ||
- | * If the suboptimal scheduling is in the future plan, it is probably due to the configurations set by the user. For instance, battery costs being high leads to limited usage of the battery. | ||
- | * If the suboptimal scheduling is in the past, then it is mostly due to the inaccuracies that come from consumption or solar yield forecasts. It is important to note forecasting will always come with its inaccuracies and even with these inaccuracies at distinct hours, Dynamic ESS minimizes costs compared to Default ESS mode in the longer run. | ||
- | |||
- | You might also want to read the chapter on [[# | ||
- | |||
- | If you feel like the behavior that you are observing is not explained by above points and you cannot find the answer in the [[# | ||
- | |||
- | ====== Implementation ====== | ||
- | |||
- | This part of the documentation is about how the system works on a technical level, as it might help troubleshooting for the more advanced users. The system works by taking all of the available data (day ahead pricing/ | ||
- | |||
- | The planning is being converted into a target state of charge for the batteries per hour and whether or not the system can feed in to the grid during that hour. If the target SOC is lower than the current SOC, the batteries discharge (either to consumption or the grid; if feed-in is allowed), if the target SOC is higher than the current SOC the batteries get charged (either from solar or from grid). The upcoming four hours schedules are put into the GX device via the two-way VRM communication channel. On the dbus these schedules can be found under `com.victronenergy.settings`, | ||
- | |||
- | Every few seconds the GX device will compare the target SOC with the current SOC and determine the power to use to reach that target before reaching the timestamp + duration. So it takes the full hour to reach the target SOC. | ||
- | |||
- | In all cases, when the target SOC changes, it will calculate the charge current required to get there, and then distribute that over all the chargers, with the solar chargers getting priority. | ||
- | If it needs more current to get there than solar provides, it will charge from the grid for the rest. | ||
- | ===== Determining the target SOC ===== | ||
- | |||
- | Several people want to know how the algorithm determines the target SOC. This is done by taking 4 steps for each site running Dynamic ESS on each re-calculation of the schedule. This is typically done each hour. | ||
- | |||
- | - Obtain data; | ||
- | - Set boundary conditions (battery, grid and the consumption/ | ||
- | - Find the most optimal charging cycle according to the data at hand and the battery/ | ||
- | - Attempt to reach the target SOC for the current hour by the end of this hour | ||
- | |||
- | We've ran a lot of simulations to check if we needed to increase the frequency of re-calculation, | ||
- | |||
- | We keep the battery stable and not the grid: in our internal testing keeping the battery usage stable (basically the same as the plan) has been a lot more cost-effective than otherwise, because of the battery costs that pile up. | ||
- | |||
- | Also keep in mind that, when doing a consumption forecast, the system does not known when during the hour that consumption will be done. If the forecast does not match the reality, Dynamic ESS does keep the planned battery usage stable while punishing the forecast inaccuracies on the grid (selling the excess to grid, buy the additional need from the grid). This can be less ideal, but it is an issue of the forecasts being inaccurate, nothing that the Dynamic ESS decided. | ||
- | ===== The Node-RED implementation ===== | ||
- | |||
- | There exists also a [[https:// | ||
- | |||
- | The Node-RED flow uses the VRM API to get the calculation for the site and inserts the hourly schedules into the GX device. If you have specific needs, the Node-RED implementation gives you a lot more options than the current VRM implementation. | ||
- | |||
- | You should only be running one implementation at the same time. If you want to run the VRM version, disable the Node-RED flow. You can read on how to do that [[https:// | ||
- | ====== Country / provider specific ====== | ||
- | |||
- | It turns out that some countries have specific pricing rules and regulations. Most of these quirks that affect dynamic ESS have been added below. | ||
- | |||
- | ==== Czech Republic ==== | ||
- | |||
- | In the Czech Republic there are dynamic transport charges work the same as Denmark, working with peak-tariff and off-peak tariff transport fees. | ||
- | |||
- | ==== Denmark ==== | ||
- | |||
- | In Denmark there are dynamic transport charges, depending on the time of day. At the moment there is no support for this in our system, but we will plan to add it later on. | ||
- | |||
- | ==== Germany ==== | ||
- | |||
- | German regulation does not allow feeding in from the battery into the grid (even if the power came from solar). From Venus OS version 3.20~17 it is possible to set certain [[https:// | ||
- | |||
- | ==== Portugal ==== | ||
- | |||
- | At least one provider in Portugal only allows feeding in solar to the grid during daytime. This looks a lot like the German regulation. For the near future, won't link the battery to grid feed-in to specific times, but disabling battery-to-grid completely will be the first alternative (which is the function that will be implemented soon). | ||
- | |||
- | ==== UK ==== | ||
- | |||
- | We are aware that the provider Octopus offers day ahead pricing, but as these are not offered via the ENTSO-E API, we are unable to process those. Eventually we will probably support these prices, but will take some time. | ||
- | |||
- | Also in the UK, (fixed) prices are known to change at the half hour instead of the whole hour (where our system works with). The work-a-round is to add the average price of in the overlapping hour. So if the price changes from 40 cents to 20 cents at 16.30, fill out a price of 30 cents from 16.00 - 17.00. | ||
- | |||
- | Adding better support for this will eventually be done, but as this also affects graphs and the scheduling, it might take a while. | ||
====== FAQ ====== | ====== FAQ ====== | ||
- | Missing a question? Please ask them in [[https://community.victronenergy.com/articles/232720/dynamic-ess-on-beta-vrm.html|the community forum]] with a remark that it should be added to the documentation and/or FAQ. | + | Missing a question? Please ask them in [[https://victron.discourse.group/c/products/dess/21|the community forum]] with a remark that it should be added to the documentation and/or FAQ. |
==== Q: Why can't I find dynamic ESS on VRM? ==== | ==== Q: Why can't I find dynamic ESS on VRM? ==== | ||
- | Right now (early December) | + | There are some pre-conditions a site must fulfill in order to get the “Dynamic ESS” menu option. Make sure that the site's system type is set to ESS or Hub-4. If it is not set to this, you need a different ESS assistant, which can be configured |
- | + | ||
- | For those of you who aren’t familiar with beta VRM, you can log in through | + | |
- | + | ||
- | ==== Q: Why can't I find dynamic ESS on Beta VRM? ==== | + | |
- | There are some pre-conditions a site must fulfill in order to get the " | ||
==== Q: Which energy meters are supported? ==== | ==== Q: Which energy meters are supported? ==== | ||
Line 226: | Line 115: | ||
[[https:// | [[https:// | ||
- | Things like the Dutch P1 meter are not sampling fast enough and not supported right now. | + | ==== Q: What is the default behaviour if the VRM connection is lost longer |
- | + | ||
- | ==== Q: What is the default behaviour if the VRM connection is lost longer | + | |
The system will run out of its schedule after 12 hours and revert to standard ESS operation. Once the connection is reestablished, | The system will run out of its schedule after 12 hours and revert to standard ESS operation. Once the connection is reestablished, | ||
As the system is partly depending on third-party services (e.g. for retrieving the day ahead price information). If we are somehow unable to fetch new pricing information, | As the system is partly depending on third-party services (e.g. for retrieving the day ahead price information). If we are somehow unable to fetch new pricing information, | ||
+ | |||
==== Q: Can the system handle charging my EV or other heavy loads? ==== | ==== Q: Can the system handle charging my EV or other heavy loads? ==== | ||
- | The short answer is no. The longer answer is that we are working on this, but as it is not that straight forward to come up with a solution that is user friendly and works for everyone, it can take a while before support for this will appear. | + | It will be able to in the future. |
See [[drafts: | See [[drafts: | ||
+ | |||
==== Q: Is there an API available? ==== | ==== Q: Is there an API available? ==== | ||
Line 249: | Line 138: | ||
limits of the system. These capacities are used by the system to make its calculations, | limits of the system. These capacities are used by the system to make its calculations, | ||
- | If you want to limit the feed-in | + | If you need to limit the import configured |
- | {{ :drafts:limit-feed-in.png?nolink&400 |}} | + | {{:ess:system-ac-limits.png?400|}} |
- | On the other side of limiting power (what gets pulled from the grid) is more tricky. If you have all of your loads behind the Victron system, you can use the //AC input current limit//. If you don't have all of your loads behind the Victron system, there is currently no configurable option to limit the total input of all of your loads. Especially when you have high loads (EV charger, heat pumps) before your Victron system, **there is a chance of blowing your main fuse**. We are working on a way to account for the loads that will limit the power the system can take. But at the moment that is not available yet. | + | How does it work? |
+ | As you’d expect, it monitors the current and when needed engages to keep that within the configured limits: | ||
+ | * to prevent overcurrent during export, system limits solar production and battery discharge. | ||
+ | * to prevent overcurrent during import, system limits battery charging. | ||
+ | * to prevent overcurrent during import because of loads, system will assist using battery power. (As long as battery permits of course). | ||
+ | * In case SOC is dropped more than 5% below configured ESS minimum SOC, the battery will be recharged from the grid as soon as loads drop. | ||
+ | |||
+ | Requirements and other details: | ||
+ | - The feature is part of ESS; and applies to MultiPlus, Quattro, MultiPlus-II and so forth. The Multi RS will come with the same feature when we release Energy Meter and ESS support for that, but thats a different project and implementation. | ||
+ | - NOTE: The function properly, the inverter/ | ||
+ | - About the existing "Limit system feed-in" | ||
+ | - The GX does not limit PV-inverters in relation to the new export current limit. To illustrate: in case of major solar production, plus high tariff on selling energy to the utility, the new mechanism will limit feed in of power from the battery to 0. So, as long as the installed PV Inverter system is done such that it can’t by itself blow the fuse then its fine. | ||
+ | - Works with all ESS supported energy meters. | ||
==== Q: Does it also take into account changing provider fees during the day? ==== | ==== Q: Does it also take into account changing provider fees during the day? ==== | ||
Line 272: | Line 173: | ||
==== Q: My country is not using the Euro, how do I switch currency? ==== | ==== Q: My country is not using the Euro, how do I switch currency? ==== | ||
- | At the moment that is not possible yet, but we are working on adding it to the general settings per site. | + | Under the //Settings -> General// part of your site, you can set your currency. |
- | + | ||
- | ==== Q: My providers changes price at the half hour instead of the full hour ==== | + | |
- | + | ||
- | Some (UK) providers offer fixed prices that change on the half hour instead of at the full hour. | + | |
- | Unfortunately the 30 minute interval has some more implications than just allowing it to be entered into the fields. | + | |
- | + | ||
- | The calculations and forecasts are currently done on the whole hour, so that needs to be accounted for as well. And the same goes for the graphs. All not impossible to solve, but not trivial either and needs a fair bit of testing. | + | |
- | + | ||
- | So the 30 minute interval will be added eventually, but it will take some more time. | + | |
==== Q: Why does (dis)charging slow down or speed up towards the end of the hour? ==== | ==== Q: Why does (dis)charging slow down or speed up towards the end of the hour? ==== | ||
Line 297: | Line 189: | ||
At the moment this is not possible. If we decide to add it, it will first be added to the [[https:// | At the moment this is not possible. If we decide to add it, it will first be added to the [[https:// | ||
- | ==== Q: Can you give an example with calculations? | ||
- | {{: | ||
- | Given a system at 15% SOC that has set the battery costs to 0.06 €/kWh, energy prices right now (11.00) set at € 0.29 and becoming € 0.40 this evening. Why would it feed into the grid already and not wait until the prices are higher? | ||
- | The battery cost is € 0.06 per kWh. This means that for a cycle of battery usage to be useful (financially beneficial) | + | ==== Q: I am getting the alarm " |
+ | The cases this alarm can be triggered are: | ||
+ | * the system | ||
+ | * the system clock is off | ||
- | ==== Q: I am getting the alarm " | ||
In most cases your systems clock has drifted such that it cannot find a matching schedule. Usually the GX device will synchronize the time with a NTP server, but your network setup might refrain the GX device from reaching a time server. Please check your time setting / manually set it to the correct time. | In most cases your systems clock has drifted such that it cannot find a matching schedule. Usually the GX device will synchronize the time with a NTP server, but your network setup might refrain the GX device from reaching a time server. Please check your time setting / manually set it to the correct time. | ||
+ | Users running Dynamic ESS on a Raspberry Pi will see this error more frequently because the Raspberry Pi does not have a realtime clock. Which means that it usually takes a while for these to get back on track with the correct time after a boot. The alarm should disappear once the time is correct again. | ||
This alarm can also occur when DESS automatically switches to ESS because the SOC is below the min SOC level. | This alarm can also occur when DESS automatically switches to ESS because the SOC is below the min SOC level. | ||
- | |||
==== Q: I am getting the alarm " | ==== Q: I am getting the alarm " | ||
This probably means that you once activated Dynamic ESS and are no longer using it. In order to fully disable it, you need to set the `com.victronenergy.settings`, | This probably means that you once activated Dynamic ESS and are no longer using it. In order to fully disable it, you need to set the `com.victronenergy.settings`, | ||
Line 325: | Line 216: | ||
Decreasing the minimum SOC does not affect the performance of DESS negatively. However, when the minimum SOC is increased (above the current SOC), it might require the battery to be charged manually since Dynamic ESS is not designed to operate when current SOC is below the minimum. | Decreasing the minimum SOC does not affect the performance of DESS negatively. However, when the minimum SOC is increased (above the current SOC), it might require the battery to be charged manually since Dynamic ESS is not designed to operate when current SOC is below the minimum. | ||
+ | |||
+ | ==== Q: The energy graph is showing incorrect data ==== | ||
+ | |||
+ | Sometimes the graph shows that energy was taken from the grid. When looking at the installation data graphs, it shows that the energy actually came from PV yield. This is caused by a known misleading assumption with the Energy graph: It assumes if there is more production than consumption, | ||
+ | |||
+ | This is quite an assumption but this is how DESS considers it internally, so that’s why the visuals reflect it that way. If we do not have that assumption, the energy graph would be even more complicated. If you want to know the exact source of the energy, you should look at the installation data graphs (grid, solar and consumption). | ||
+ | |||
+ | ==== Q: I can't find the controls button on the dashboard ==== | ||
+ | |||
+ | You probably have //Realtime updates// switched off. You can switch it on via //Settings -> General -> Realtime updates//. | ||
+ | |||
+ | Note that the dashboard should show: //Last updated:// **Realtime** | ||
+ | |||
+ | ==== Q: I get the error message " | ||
+ | |||
+ | This error can happen when the Dynamic ESS system starts before we were able to communicate the battery capacity from VRM to the GX device. It will go away as soon as you restart Dynamic ESS or the GX device. |
drafts/dynamic_ess.1708349753.txt.gz · Last modified: 2024-02-19 14:35 by dfaber