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

Sensors for Power Consumption and Realtime COP not working #101

Open
nicx opened this issue Jun 4, 2024 · 9 comments
Open

Sensors for Power Consumption and Realtime COP not working #101

nicx opened this issue Jun 4, 2024 · 9 comments

Comments

@nicx
Copy link

nicx commented Jun 4, 2024

Maybe it's the same problem: My sensors for Power consumption (HC_Power) and Realtime COP (HC_COP) are always 0. Power Production Sensors are working, COP-Lifetime seems also correct. What could I check to find the reason for that? :)

@Arnold-n
Copy link
Owner

Arnold-n commented Jun 4, 2024

It's the same problem: power consumption and real-time COP calculation rely on an external electricity meter providing data via P1P2/P/meter/U/9/Electricity_Power. Daikin unfortunately does not provide any real-time consumption data via the P1/P2 interface. So without external input, these values remain 0.

HomeWizard meter users may use a local API and a separate ESP8266 to request data from the meter and copy it to MQTT.

@nicx
Copy link
Author

nicx commented Jun 4, 2024

@Arnold-n ah ok. understood. so could I populate thempower value from my espaltherma to this topic and then the COP is calculated automatically? should the value be the total power of the heatpump with or without the backup heater?

@Arnold-n
Copy link
Owner

Arnold-n commented Jun 4, 2024

Yes, but it may be less accurate than a real external electricity meter, as the current reported by ESPAltherma has low resolution (0.2-0.3A), and does not take blind power into account.
For COP the compressor power would be needed. The code for the backup heater power input is not complete yet (and less useful).

@buuhsmead
Copy link

I am updating topic 'P1P2/P/meter/U/9/Electricity_Active_Power' with current used Watts of the WP.
And the topic 'P1P2/P/P1P2MQTT/bridge0/C/9/COP_Realtime' is not updated.
Is there a time differences or other conditions that should be filled before?

@buuhsmead
Copy link

@Arnold-n The value in Watts is allowed to have a decimal point or should it be an int [0-32767].
Currently, I am sending 17.1 or 18 or 18.4.

@Arnold-n
Copy link
Owner

The entity provided by P1P2/P/meter/U/9/Electricity_Active_Power should be repeated at least once/minute. But COP_Realtime is currently only calculated for heating, and not for cooling, I will add that in the next version.

The value is rounded down (actually it just ignores any character other than [0-9]).

@adam-the
Copy link

Is there any potential harm in sending the value more frequently? i.e, every second or every 15 seconds?

@Arnold-n
Copy link
Owner

No harm at all, and it increases accuracy of the real-time COP reporting. The real-time COP calculation is done almost once/second and takes the most recent input values for active power and for heat production (flow * delta-T) unless power information is too old (>1 minute). Active power is not (planned to be) integrated over time; for this Electricity_Total will be used.

And as I just corrected above and in the documentation, by default it is P1P2/P/meter/U/9/Electricity_Power.

@hdaems
Copy link

hdaems commented Sep 29, 2024

Adjusting to P1P2/P/meter/U/9/Electricity_Power the COP is calculated, both realtime and lifetime.
For me this can be closed.

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

No branches or pull requests

5 participants