-
-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial documentation for Solis inverters #308
Conversation
Merge Main
Reformat to 180 line length (#304)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a couple of comments
docs/config-yml-settings.md
Outdated
@@ -186,13 +184,14 @@ Connect to your cars sensors for accurate data: | |||
Control how your battery behaves during car charging: | |||
|
|||
- **car_charging_from_battery** - When True the car can drain the home battery, Predbat will manage the correct level of battery accordingly. When False home battery discharge will be prevented when your car charges, all load from the car and home will be from the grid. This is achieved by setting the discharge rate to 0 during car charging and to the maximum otherwise, hence if you turn this switch Off you won't be able to change your discharge rate outside Predbat. The home battery can still charge from the grid/solar in either case. Only use this if Predbat knows your car charging plan, e.g. you are using Intelligent Octopus or you use the car slots in Predbat to control your car charging. | |||
- CAUTION: If you turn this switch back on during a car charging session you will need to set your battery discharge rate back to maximum manually. | |||
|
|||
- CAUTION: If you turn this switch back on during a car charging session you will need to set your battery discharge rate back to maximum manually. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The proper Markdown spec is to have 4 spaces (or a tab) for an indented list, I think you've changed this plus some others to 2.
I went through them all when I redid the docs and set them all to 4 (GitHub was fairly forgiving, and would work with 2).
And if it did with with mkdocs, that'll be because fairly late on I added the sane lists extension, as one of the original lists wasn't working with the strict implementation of Markdown spec.
@@ -19,6 +19,7 @@ nav: | |||
- creating-charts.md | |||
- predbat-plan-card.md | |||
- 'Predbat development': | |||
- other-inverters.md |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Personally I'd add this in another section, rather than in the section on developing on Predbat, as it's not really developer content.
docs/config-yml-settings.md
Outdated
@@ -230,21 +229,21 @@ The triggers count export energy until the next active charge slot only. | |||
|
|||
For each trigger give a name, the minutes of export needed and the energy required in that time | |||
Multiple triggers can be set at once so in total you could use too much energy if all run | |||
Each trigger create an entity called 'binary_sensor.predbat_export_trigger_<name>' which will be turned On when the condition is valid | |||
Each trigger create an entity called 'binary*sensor.predbat_export_trigger*<name>' which will be turned On when the condition is valid |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo, the star should be before binary?
docs/install.md
Outdated
@@ -45,7 +51,7 @@ | |||
|
|||
Predbat needs a solar forecast in order to predict battery levels. | |||
|
|||
If you don't have solar then comment out the Solar forecast part of the apps.yml: **pv_forecast_* ** | |||
If you don't have solar then comment out the Solar forecast part of the apps.yml: **pv*forecast*\* ** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why star's in place of underscore?
I don’t remember editing this at all. May have been som auto-formatting nonsense!
…On 11 Nov 2023 at 14:22 +0000, iainfogg ***@***.***>, wrote:
@iainfogg commented on this pull request.
Added a couple of comments
In docs/config-yml-settings.md:
> @@ -186,13 +184,14 @@ Connect to your cars sensors for accurate data:
Control how your battery behaves during car charging:
- **car_charging_from_battery** - When True the car can drain the home battery, Predbat will manage the correct level of battery accordingly. When False home battery discharge will be prevented when your car charges, all load from the car and home will be from the grid. This is achieved by setting the discharge rate to 0 during car charging and to the maximum otherwise, hence if you turn this switch Off you won't be able to change your discharge rate outside Predbat. The home battery can still charge from the grid/solar in either case. Only use this if Predbat knows your car charging plan, e.g. you are using Intelligent Octopus or you use the car slots in Predbat to control your car charging.
- - CAUTION: If you turn this switch back on during a car charging session you will need to set your battery discharge rate back to maximum manually.
+
+ - CAUTION: If you turn this switch back on during a car charging session you will need to set your battery discharge rate back to maximum manually.
The proper Markdown spec is to have 4 spaces (or a tab) for an indented list, I think you've changed this plus some others to 2.
I went through them all when I redid the docs and set them all to 4 (GitHub was fairly forgiving, and would work with 2).
And if it did with with mkdocs, that'll be because fairly late on I added the sane lists extension, as one of the original lists wasn't working with the strict implementation of Markdown spec.
In mkdocs.yml:
> @@ -19,6 +19,7 @@ nav:
- creating-charts.md
- predbat-plan-card.md
- 'Predbat development':
+ - other-inverters.md
Personally I'd add this in another section, rather than in the section on developing on Predbat, as it's not really developer content.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Hmm - something odd going on here. Again not a change I remember making…
…On 11 Nov 2023 at 14:30 +0000, Trefor Southwell ***@***.***>, wrote:
@springfall2008 commented on this pull request.
In docs/install.md:
> @@ -45,7 +51,7 @@
Predbat needs a solar forecast in order to predict battery levels.
-If you don't have solar then comment out the Solar forecast part of the apps.yml: **pv_forecast_* **
+If you don't have solar then comment out the Solar forecast part of the apps.yml: **pv*forecast*\* **
Why star's in place of underscore?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Could it be that you'd already written the code in the original README then you copied it in here after I reworked the documentation? The original README used 2 characters for indents, so that would explain it. |
I don’t think so. I think it may be VScode doing some autoformatting. I’ve noticed that it changes some markdown - sorting out tables and the like but maybe it’s not following the same standards?
Will have a look tomorrow once the rain has set in
…On 11 Nov 2023 at 19:53 +0000, iainfogg ***@***.***>, wrote:
Could it be that you'd already written the code in the original README then you copied it in here after I reworked the documentation?
The original README used 2 characters for indents, so that would explain it.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Ok, that's strange as I used VS Code to do the work in the first place. It griped about some indents but never auto changed them for me. I think it leans towards the GitHub more relaxed standards, rather than the strict standards. |
@fboundy were you going to fix the issues with the * before merging? |
Yes. Leave this for now
…On 14 Nov 2023 at 11:42 +0000, Trefor Southwell ***@***.***>, wrote:
@fboundy were you going to fix the issues with the * before merging?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@fboundy any updates on this one? |
No description provided.