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

Madimack Elite V3 - Added Power Sensor and updated EEV sensor class and unit #1772

Merged
merged 1 commit into from
Mar 25, 2024

Conversation

jwGeorge
Copy link
Contributor

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

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.
@make-all make-all merged commit 43e9d0d into make-all:main Mar 25, 2024
4 checks passed
make-all added a commit that referenced this pull request Mar 25, 2024
@jwGeorge jwGeorge deleted the patch-1 branch April 2, 2024 23:18
timlaing pushed a commit to timlaing/tuya-local that referenced this pull request Aug 8, 2024
@doertli
Copy link

doertli commented Sep 1, 2024

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?

@jwGeorge
Copy link
Contributor Author

jwGeorge commented Sep 1, 2024

Odd, I'm not seeing that behaviour.

Getting very consistent readings in HA, even if I open smartlife app or query from tuya directly.

Below is what my power usage for last couple of hours looks like. How does that compare?

Screenshot_20240901_110928_Home Assistant

Running HA OS 10.5 with version 2024.4

@make-all
Copy link
Owner

make-all commented Sep 1, 2024

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?

@jwGeorge
Copy link
Contributor Author

jwGeorge commented Sep 2, 2024

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:

{ "result": { "properties": [ { "code": "switch1", "custom_name": "", "dp_id": 101, "time": 1725232764888, "type": "bool", "value": true }, { "code": "mode1", "custom_name": "", "dp_id": 102, "time": 1725069761500, "type": "enum", "value": "heating" }, { "code": "child_lock1", "custom_name": "", "dp_id": 103, "time": 1700473309495, "type": "bool", "value": false }, { "code": "temp_set1", "custom_name": "", "dp_id": 104, "time": 1725069761487, "type": "value", "value": 29 }, { "code": "work_mode", "custom_name": "", "dp_id": 105, "time": 1725069890810, "type": "enum", "value": "perfect" }, { "code": "temp_unit_convert1", "custom_name": "", "dp_id": 106, "time": 1725069761403, "type": "enum", "value": "c" }, { "code": "fault1", "custom_name": "", "dp_id": 107, "time": 1725069760887, "type": "bitmap", "value": 0 }, { "code": "temp_current1", "custom_name": "", "dp_id": 108, "time": 1700473309495, "type": "value", "value": -22 }, { "code": "compressor_strength", "custom_name": "", "dp_id": 109, "time": 1725233230532, "type": "value", "value": 100 }, { "code": "temp_top", "custom_name": "", "dp_id": 110, "time": 1725069761426, "type": "value", "value": 40 }, { "code": "temp_bottom", "custom_name": "", "dp_id": 111, "time": 1725069761484, "type": "value", "value": 18 }, { "code": "temp_coiler", "custom_name": "", "dp_id": 112, "time": 1725256835996, "type": "value", "value": 2 }, { "code": "temp_venting", "custom_name": "", "dp_id": 113, "time": 1725257636458, "type": "value", "value": 84 }, { "code": "temp_effluent", "custom_name": "", "dp_id": 114, "time": 1725256722582, "type": "value", "value": 26 }, { "code": "temp_around", "custom_name": "", "dp_id": 115, "time": 1725257833520, "type": "value", "value": 18 }, { "code": "fault2", "custom_name": "", "dp_id": 116, "time": 1725069760930, "type": "bitmap", "value": 0 }, { "code": "temp_inflow", "custom_name": "", "dp_id": 117, "time": 1725257524931, "type": "value", "value": 24 }, { "code": "temp_return", "custom_name": "", "dp_id": 118, "time": 1725257837002, "type": "value", "value": 2 }, { "code": "temp_coiler_inside", "custom_name": "", "dp_id": 119, "time": 1725245406687, "type": "value", "value": 25 }, { "code": "temp_radiator", "custom_name": "", "dp_id": 120, "time": 1725254818549, "type": "value", "value": 31 }, { "code": "expansion_valve", "custom_name": "", "dp_id": 121, "time": 1725257762357, "type": "value", "value": 212 }, { "code": "power_w", "custom_name": "", "dp_id": 122, "time": 1725069762555, "type": "bool", "value": true }, { "code": "cool_enable", "custom_name": "", "dp_id": 123, "time": 1725069762593, "type": "bool", "value": true }, { "code": "oc_mode", "custom_name": "", "dp_id": 124, "time": 1725069762610, "type": "enum", "value": "oc_1" }, { "code": "power", "custom_name": "", "dp_id": 125, "time": 1725257836502, "type": "value", "value": 2010 } ] }, "success": true, "t": 1725257840165, "tid": "0290c41e68f311ef88b02ac421ecbce6" }

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

Successfully merging this pull request may close these issues.

3 participants