Outdoor unit power incorrect

[Finale0171]

A recent update to this integration seems to have inflated the Outdoor unit power usage entity.

Previously, in my case, my power usage was recorded as between 18-23 watts (it’s winter and my outdoor A/C compressor is idle)

Since a recent update (I’m not sure which), the wattage is inflated to 180-230 watts. It looks like the value is being incorrectly multiplied or a trailing zero was added.

[apetrycki]

@wirecuttr, I'm guessing this should be set to zero when the unit is not on? What is your experience with the outdoor unit values?

[wirecuttr]

What is your outdoor unit?
I have DZ17VSA heat pumps
My system is set up with CT clamps in the panel so I can compare the two and the power tracks decently well.
Below are two images. The first one is when the heat pump is heating.
And the other is when I switch the unit to emergency heat (i.e., gas furnace)

Perhaps the value needs to be handled differently for different types of outdoor units...?

[apetrycki]

@Finale0171 @dualtronic, please share your model numbers. We need to keep track of what units are having issues to figure out how to handle them.

[Finale0171]

I have a DX17VSS (air conditioner only). So right now while my system is in heat only mode, my outdoor unit power should be near zero (a few W might be expected as the mainboard is still on for the communication system)

[dualtronic]

@apetrycki

@Finale0171 @dualtronic, please share your model numbers. We need to keep track of what units are having issues to figure out how to handle them.

My furnace is DM97MC0804CNAA and air conditioner (outside unit) is DX17VSS361AA. This is gas heating, so outdoor power should be zero since the compressor is off (or a couple watts for keeping the micro awake), but not nearly as much as being reported.

[dualtronic]

Bump. Is there an update on this? Setting outdoorpower to zero whenever the thermostat changes to state = 5 should solve this problem. Currently, the power doesn't return to zero after being set to a large value. Therefore, it is nearly always incorrect. Is there a concern about making this change?

[apetrycki]

Sorry, I haven't had a chance to work on this integration lately. I've been working to move my home server to a Proxmox cluster hosting kubernetes. It'll probably be a couple weeks at least before I can get back to it. Right now I don't have a dev environment or the time.

[dualtronic]

Bump. Here is a trace of my A/C while off. Shows 0W, 180W or 200W. Is data coming directly from the Daikin API? It seems like offset error noise with a high gain.