-
Notifications
You must be signed in to change notification settings - Fork 526
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
Madimack Elite V3 - Added Power Sensor and updated EEV sensor class and unit #1772
Conversation
File was missing the power entity on dps id 125. EEV sensor updated to treat the integer as a measurement. Changed name to include 11-40kW versions.
Looks like the 'power' sensor is actually a power counter keeps resetting itself when it's polled (probably by Tuya cloud), so HA keeps getting errant readings. Similar issue with the Madimack pool pump. Any other (non counter) sensor for current power draw? |
Power is an instantaneous value, not a cumulative value. A cumulative reading would be energy, and it is common for tuya devices to reset that after reporting to the cloud. Are you sure you are both talking about the same sensor here? Are there different versions of the firmware that report different things on the same dp? |
I'm definitely talking about Power - mine doesn't return energy at all. Yes, maybe @doertli has a different dp set. I just checked mine again and dp 125 is definitely for "power" but there is another dp 122 called "power_w" that's a boolean. Maybe this has got something to do with what is returned in "power". Below is the response from Query Properties on mine:
|
Configuration was missing the power entity on dps id 125.
EEV sensor updated to treat the integer as a measurement.
Changed name to include 11-40kW versions.
Tested with Madimack Elite V3 14kW