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

[P044] Parse P1 messages to make the values available in ESPEasy #4491

Open
tonhuisman opened this issue Jan 31, 2023 · 2 comments
Open

[P044] Parse P1 messages to make the values available in ESPEasy #4491

tonhuisman opened this issue Jan 31, 2023 · 2 comments
Labels
Category: Plugin Related to supported sensors Type: Feature Request Add a completely new feature (e.g. controller/plugin)

Comments

@tonhuisman
Copy link
Contributor

To make all values, available in the P1 datagram, available for regular use (like on displays) the datagram should be parsed to split out these values.

With pending PR #4283 the code for handling P1 messages will be merged into P020, so once that's completed, this can be implemented.

@JoostDkr
Copy link

Now that energy rates are going to become dynamic and the "Salderingsregeling" will soon be phased out, it would be nice if the individual data elements became available. So that you can control directly from the espeasy (without an intermediary from, for example, Domoticz).

@TD-er
Copy link
Member

TD-er commented Feb 13, 2024

@JoostDkr See today's news

About the dynamic tarifs, SolarEdge now has support for negative pricing in their latest firmware and I think others will follow soon.

However this doesn't mean it can be useful to have access to other elements in the parsed messages.

@TD-er TD-er added Category: Plugin Related to supported sensors Type: Feature Request Add a completely new feature (e.g. controller/plugin) labels Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category: Plugin Related to supported sensors Type: Feature Request Add a completely new feature (e.g. controller/plugin)
Projects
None yet
Development

No branches or pull requests

3 participants