Skip to content
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

Change emergency power setting #199

Closed
Taffmailer opened this issue Nov 13, 2023 · 4 comments
Closed

Change emergency power setting #199

Taffmailer opened this issue Nov 13, 2023 · 4 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@Taffmailer
Copy link

Under certain circumstances, it makes sense to release part of the stored emergency power reserve for in-house consumption.

Currently, the tag EP_PARAM_EP_RESERVE_W
can already be changed. However, this is not accepted by the system. After a short time, the initial value is displayed again.

If changes are made directly via the system, EP_PARAM_EP_RESERVE_W is always changed in addition to the EP_PARAM_EP_RESERVE. This tag cannot currently be changed, it is read only.

It may be possible to solve the problem if EP_PARAM_EP_RESERVE is defined as read/write.

Please check and consider as a feature request.

regards
Franc

@git-kick
Copy link
Owner

git-kick commented Nov 13, 2023

@Taffmailer, thank you for your contribution, I will try to make EP_PARAM_EP_RESERVE read/write.

However please note that currently, all objects under EP.PARAM_0 are read-only - meaning, you can change the values in ioBroker, but the adater has no means to write them. This is reflected by the roles value and indicator. Writable pendants are level and switch.

@git-kick git-kick self-assigned this Nov 13, 2023
@git-kick git-kick added the enhancement New feature or request label Nov 13, 2023
@git-kick git-kick added this to the v1.2.5 milestone Nov 13, 2023
@git-kick
Copy link
Owner

I did a first implementation of read/write for PARAM_EP_RESERVE. Works on my S10. Note that PARAM_EP_RESERVE_W changes accordingly. Because it is an energy [Wh] value (not a power [W] value), I am thinking about renaming it to PARAM_EP_RESERVE_WH. The tag is not listed in the official tag list, so I assume it was named using best guess.

Available for testing in branch Issue#199

I will do some more trial & error and implement read/write for other PARAM_* tags, if appropriate. This may take some time...

@git-kick
Copy link
Owner

Implementation is done. Two objects are writable

  • PARAM_EP_RESERVE
  • PARAM_EP_RESERVE_ENERGY (fka PARAM_EP_RESERVE_W)

The four other PARAM_... objects are all read-only, as they reflect E3/DC status.

Available for testing in branch Issue#199; will be released with v1.2.5

@Taffmailer
Copy link
Author

Great!
Thanks a lot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants