feat: operator guide#950
Conversation
b0661
added
documentation
b0661
force-pushed
the
feat/operation_guide
branch
2 times, most recently
from
2640238 to
1d863bf
Compare
Signed-off-by: Bobby Noelte <b0661n0e17e@gmail.com>
b0661
force-pushed
the
feat/operation_guide
branch
from
1d863bf to
6ac2522
Compare
| * **Load** energy meter readings | ||
| * **Grid export** energy meter readings | ||
| * **Grid import** energy meter readings | ||
| * **PV production** energy meter readings |
There was a problem hiding this comment.
This is one of the parts where I was confused and couldn't find any documentation. What's the difference between load and import here? I guess load is the current (absolute) meter reading, but what do I configure as import? As an example, Tibber exposes two entities: sensor.tibber_pulse_xxx_last_meter_consumption (current meter reading) and sensor.tibber_pulse_zzz_accumulated_consumption (consumption today). There's also one for the current hour. I guess I would use last_meter_consumption as "load", but I'm unsure about the other one. Or is it the other way round? import/export are last meter reading and load is daily consumption? Or are there other smart meters that distinguish between what I consume in total vs. what I consumed from the grid? Wouldn't that just be consumption - production?
There was a problem hiding this comment.
- Load is the electric energy consumption within your system (aka. house, apartment). What your home appliances (e.g. oven, dish washer, fridge, wall box, ...) consume.
- Grid export is how much electric energy you export to the electric grid
- Grid import, how much electric energy you import from the electric grid
- PV production is the amount of electric energy that your solar panel provide to your system
Tibber only wants to and can only see grid import/ export. That is what your grid meter provides.
Load can be estimated by a load provider (prediction provider), same for pv production.
There was a problem hiding this comment.
Makes sense. Would be helpful if that were written down somewhere. 😉
| % SPDX-License-Identifier: Apache-2.0 | ||
| (operator-guide-page)= | ||
|
|
||
| # Akkudoktor-EOS Operator Guide |
There was a problem hiding this comment.
This guide is a good step forward, but it still doesn't quite align with my first experience with the software. Looking back I can now piece together a few things from this, but as a new user, I would still be at a loss why the dashboards behave like some deployment failed.
I prefer clear steps from start to finish like:
- Add repository
- Install app
- Set mode to OPTIMIZATION and configure the timeout
- Optional: set config option X to Y if you have ABC...
- Wait for first run
- Inspect dashboard, adjust filled-in dummy data like so: ...
- Click save config to file, otherwise changes are lost on restart.
Or something like that.
There was a problem hiding this comment.
You are welcome to improve.
| - Missing or misconfigured prediction providers. | ||
| - System description (battery, inverter) not defined. | ||
| - No measurement inputs (e.g., current PV power, load) available. |
There was a problem hiding this comment.
A missing first run due to a missing configuration seems to be the most common cause for new users at least.
|
This pull request has been marked as stale because it has been open (more than) 90 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 30 days. Note, that you can always re-open a closed pull request at any time. |
2 participants
Work in progress to create a comprehensive operator guide. Feel free to review and provide improvements.
The guide should help to get a quick setup for a user. More details may be referenced.