-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Varta: add battery control #21841
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
Varta: add battery control #21841
Conversation
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.
|
Vorschlag: |
Parameter dischargepower in positiven Wert geändert, Umwandlung erfolgt im Template
|
den Parameter dischargepower bräuchte es innerhalb von evvc eigentlich nicht, da er für nichts genutzt wird. Gibt es eine Möglichkeit den Ist-Wert aus Register 1074 zu irgendwo zu speichern, wenn hold aktiviert wird und beim Wechsel auf normal diesen Wert wieder zurück zu schreiben? |
|
Nein, gibts nicht :/ |
Case 3 ergänzt, Parameter umbenannt
maxdischargepower ergänzt
|
Wäre toll wenn nochmal jemand drüber gucken könnte. Ich weiß leider nicht warum die defaults.yaml einen Konflikt hat und freue mich über einen Tipp. |
watchdog ergänzt
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.
Hey @zoomy01 - I've reviewed your changes - here's some feedback:
- The
batterymodeblock’s indentation looks off compared to the surrounding YAML—please align it with the other fields to avoid rendering issues. - You’re hardcoding
timeout: 120sin thebatterymodesection instead of using the{{ .watchdog }}parameter—consider switching to the template variable for flexibility. - The
maxdischargepowerparam is defined both invarta.yamland indefaults.yaml—please consolidate it to a single definition to avoid duplication.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- The `batterymode` block’s indentation looks off compared to the surrounding YAML—please align it with the other fields to avoid rendering issues.
- You’re hardcoding `timeout: 120s` in the `batterymode` section instead of using the `{{ .watchdog }}` parameter—consider switching to the template variable for flexibility.
- The `maxdischargepower` param is defined both in `varta.yaml` and in `defaults.yaml`—please consolidate it to a single definition to avoid duplication.
## Individual Comments
### Comment 1
<location> `templates/definition/meter/varta.yaml:27` </location>
<code_context>
- name: host
- name: port
default: 502
+ - name: watchdog
+ type: duration
+ default: 120s
</code_context>
<issue_to_address>
Add description/help for 'watchdog' parameter
Adding a localized description or help text for 'watchdog' will enhance documentation and make the parameter easier to understand for users.
</issue_to_address>
<suggested_fix>
<<<<<<< SEARCH
- name: watchdog
type: duration
default: 120s
usages: ["battery"]
advanced: true
=======
- name: watchdog
type: duration
default: 120s
help:
de: Zeit in Sekunden, nach der der Watchdog auslöst, wenn keine Kommunikation erfolgt
en: Time in seconds after which the watchdog triggers if no communication occurs
usages: ["battery"]
advanced: true
>>>>>>> REPLACE
</suggested_fix>Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
sourcery-ai comments
|
Was fehlt hier noch? |
small correction
unit: W for maxdischargepower
von meiner Seite nicht. ;) |
#19631