Request update "Heating Energy" sensors D2CND

Question

Request update "Heating Energy" sensors D2CND

eduardkirkosa opened this issue 2 years ago · 32 comments

Could you please update the "Heating Energy" sensors for D2CND ( via DRGATEWAYAA ) the device_class/state_class, so' I can add it to Energy Dashboard ( Gas Consumption ).
Thanks,
Edy

eduardkirkosa commented 2 years ago

HP

eduardkirkosa commented 2 years ago

Hi, yes

Answer 1 · 2022-12-09T09:08:37.000Z

Fixed in v1.3.7

Answer 2 · 2022-12-09T10:15:07.000Z

Thanks :) working

Answer 3 · 2022-12-09T10:33:25.000Z

12kWh electricity consumption. You must be paying a fortune for electricity 😄

Answer 4 · 2022-12-09T11:03:06.000Z

hope not ;) - i still wait for the bill on November ;)
75%+ it's the dmn HeatPump :( , and 0% Gas - "Keep it real" kamikaze level

Answer 5 · 2022-12-09T11:12:01.000Z

You must be heating football stadium if it takes 75% of the 12kWh. If I see 20kWh/day (only for heatpump) I am already freaking out. Overall my total consumption looks a bit higher (~800kWh) for Nov.

Answer 6 · 2022-12-09T11:21:11.000Z

Combo combination : Poor(I think) isolation from windows + doors + attic , radiators (not underfloor) , pets (1 door sometimes open for long time) , I bet in January the external part of the HP will take off like a helicopter :))))))))))

Answer 7 · 2022-12-13T07:35:01.000Z

Hi @tadasdanielius

I turn on the D2CND to check how it's working, and the values for "Heating Energy" stay at "0 kwh" - something it's weird :(

And from the App:

If more info/logs are needed just point me to the right location and i try get it :)

Thanks,
Edy

Answer 8 · 2022-12-13T08:02:57.000Z

How about electricity consumption? I only have electric heating, thus currently it's only picking electricity usage.

Answer 9 · 2022-12-13T09:07:10.000Z

for HP works

Answer 10 · 2022-12-13T09:24:16.000Z

And what the official app showing for electricity consumption (not gas)?

Answer 11 · 2022-12-15T06:35:35.000Z

Looks like the D2CND has both options for Energy "gas + electricity" - and your sensor pick up the "electricity"

for sure the energy "gas" has different source

Answer 12 · 2022-12-15T09:29:56.000Z

Yes, Gas has separate values but at the moment they are not being used as I don't have gas device therefore I don't see them.

Answer 13 · 2022-12-15T13:41:29.000Z

can I / it's possible - to get out some logs/events that you can use ?

Answer 14 · 2022-12-15T15:43:58.000Z

if you can drop a profiles of your devices then I might be able to implement, but can't promise anything 😄

Answer 15 · 2022-12-15T16:54:17.000Z

I think the best way is to log debug real info with original app to zip file. Run it for linger time to cillect more data.

Answer 16 · 2022-12-17T08:48:14.000Z

@tadasdanielius i did the steps for profiles and i get now:

Answer 17 · 2022-12-17T19:20:26.000Z

You probably changed something too much. You just need to remove # from those lines in __init__.py

It should look like this

Answer 18 · 2022-12-18T09:33:39.000Z

/config/daikin_altherma_0.json
{"SyncStatus": "reboot", "UnitStatus": ["ErrorState"], "DateTime": {"DateTimeAdjustable": false}}

/config/daikin_altherma_1.json
{"SyncStatus": "update", "Sensor": ["IndoorTemperature", "OutdoorTemperature", "LeavingWaterTemperatureCurrent"], "UnitStatus": ["ErrorState", "InstallerState", "WarningState", "EmergencyState", "TargetTemperatureOverruledState"], "Operation": {"Power": ["on", "standby"], "OperationMode": ["heating"], "TargetTemperature": {"heating": {"maxValue": 30.0, "minValue": 12.0, "stepValue": 0.5}}, "RoomTemperatureHeating": {"maxValue": 30.0, "minValue": 12.0, "stepValue": 0.5, "settable": true}, "LeavingWaterTemperatureOffsetHeating": {"maxValue": 10, "minValue": -10, "stepValue": 1, "settable": true}}, "Schedule": {"Base": "action", "defaultScheduleAvailable": "true", "NameAdjustable": "false", "List": {"heating": [{"StartTime": {"stepValue": 10.0, "unit": "minutes"}, "TargetTemperature": {"heating": {"maxValue": 30.0, "minValue": 12.0, "stepValue": 1}}, "Actions": ["StartTime", "TargetTemperature"], "maxActionsAllowed": 6}, ["monday", "tuesday", "wednesday", "thursday", "friday", "saturday", "sunday"], ["monday", "tuesday", "wednesday", "thursday", "friday", "saturday", "sunday"], ["monday", "tuesday", "wednesday", "thursday", "friday", "saturday", "sunday"], []]}}, "Consumption": {"Electrical": {"unit": "kWh", "Heating": {"Daily": {"contentCount": 24, "resolution": 2}, "Weekly": {"contentCount": 14, "resolution": 1}, "Monthly": {"contentCount": 24, "resolution": 1}}}}}

/config/daikin_altherma_2.json
{"SyncStatus": "update", "Sensor": ["TankTemperature"], "UnitStatus": ["ErrorState", "InstallerState", "WeatherDependentState", "WarningState", "EmergencyState"], "Operation": {"Power": ["on", "standby"], "OperationMode": ["heating"], "TargetTemperature": {"heating": {"maxValue": 60.0, "minValue": 30.0, "stepValue": 0.5}}, "DomesticHotWaterTemperatureHeating": {"maxValue": 60.0, "minValue": 30.0, "stepValue": 1.0, "settable": true}, "powerful": ["0", "1"]}, "Schedule": {}, "Consumption": {"Electrical": {"unit": "kWh", "Heating": {"Daily": {"contentCount": 24, "resolution": 2}, "Weekly": {"contentCount": 14, "resolution": 1}, "Monthly": {"contentCount": 24, "resolution": 1}}}}}

Answer 19 · 2022-12-18T09:34:22.000Z

The - error state it's due to stupid 60gr tank water clean/cycle blabla - that i stopped.

Answer 20 · 2022-12-18T20:19:33.000Z

Nothing related to gas usage to pick it up. Do you have two separate devices?

Answer 21 · 2022-12-19T19:46:16.000Z

I see. Can you temporary disable Daikin Altherma and leave only GazBoiler restart HA, copy files and then you can enable it again. The reason is that they both write to the same files and apparently Daikin Altherma overrides the GazBoiler

Answer 22 · 2022-12-20T07:24:56.000Z

daikin_altherma_0.json
{"SyncStatus": "registration", "UnitStatus": ["ErrorState"], "DateTime": {"DateTimeAdjustable": true}}

daikin_altherma_1.json
{"SyncStatus": "update", "Sensor": ["IndoorTemperature"], "UnitStatus": ["ErrorState", "WarningState", "TargetTemperatureOverruledState"], "Operation": {"Power": ["on", "standby"], "OperationMode": ["heating_day", "heating_night"], "SensorTemperature": {"stepValue": 0.5}, "TargetTemperatureDay": {"maxValue": 30.0, "minValue": 10.0, "stepValue": 0.5}, "TargetTemperatureNight": {"maxValue": 30.0, "minValue": 10.0, "stepValue": 0.5}, "TargetTemperature": {"heating_day": {"maxValue": 30.0, "minValue": 10.0, "stepValue": 0.5}, "heating_night": {"maxValue": 30.0, "minValue": 10.0, "stepValue": 0.5}}, "EcoMode": ["0", "1"]}, "Schedule": {"Base": "TimeSegment", "defaultScheduleAvailable": "false", "NameAdjustable": "false", "List": {"Heating": [{"StartTime": {"stepValue": 15, "unit": "minute"}, "EndTime": {"stepValue": 15, "unit": "minute"}, "OperationMode": ["heating_day", "heating_night"], "TargetTemperature": {"heating_day": {"maxValue": 21.0, "minValue": 21.0, "stepValue": 0.0}, "heating_night": {"maxValue": 21.0, "minValue": 21.0, "stepValue": 0.0}}, "TimeSegment": ["StartTime", "EndTime"], "MaxSegmentsAllowed": 3}, [], ["weekday", "weekend"], ["monday", "tuesday", "wednesday", "thursday", "friday", "saturday", "sunday"]]}}, "Consumption": {"Electrical": {"unit": "kWh", "Heating": {"Daily": {"contentCount": 24, "resolution": 2}, "Weekly": {"contentCount": 14, "resolution": 1}, "Monthly": {"contentCount": 24, "resolution": 1}}}, "Gas": {"unit": "kWh", "Heating": {"Daily": {"contentCount": 24, "resolution": 2}, "Weekly": {"contentCount": 14, "resolution": 1}, "Monthly": {"contentCount": 24, "resolution": 1}}}}}

daikin_altherma_2.json
{"SyncStatus": "update", "Sensor": ["TankTemperature"], "UnitStatus": ["ErrorState", "WarningState"], "Operation": {"Power": ["on", "standby"], "OperationMode": ["heating", "standby"], "SensorTemperature": {"stepValue": 1.0}, "TargetTemperature": {"heating": {"maxValue": 60.0, "minValue": 35.0, "stepValue": 1.0}, "standby": {"maxValue": 60.0, "minValue": 35.0, "stepValue": 1.0}}, "DomesticHotWaterTemperatureHeating": {"maxValue": 60.0, "minValue": 35.0, "stepValue": 1.0, "settable": true}}, "Schedule": {"Base": "TimeSegment", "defaultScheduleAvailable": "false", "NameAdjustable": "false", "List": {"Heating": [{"StartTime": {"unit": "minute"}, "EndTime": {"unit": "minute"}, "OperationMode": ["heating"], "TimeSegment": ["StartTime", "EndTime"], "MaxSegmentsAllowed": 3}, [], ["weekday", "weekend"], ["monday", "tuesday", "wednesday", "thursday", "friday", "saturday", "sunday"], ["weekday", "weekend"], ["monday", "tuesday", "wednesday", "thursday", "friday", "saturday", "sunday"]]}}, "Consumption": {"Electrical": {"unit": "kWh", "Heating": {"Daily": {"contentCount": 24, "resolution": 2}, "Weekly": {"contentCount": 14, "resolution": 1}, "Monthly": {"contentCount": 24, "resolution": 1}}}, "Gas": {"unit": "kWh", "Heating": {"Daily": {"contentCount": 24, "resolution": 2}, "Weekly": {"contentCount": 14, "resolution": 1}, "Monthly": {"contentCount": 24, "resolution": 1}}}}}

Answer 23 · 2022-12-20T18:42:24.000Z

Can you try to replace sensor.py file, located in your config folder custom_components/daiking_altherma with this one.

And of course after you replace restart HA

Answer 24 · 2022-12-21T06:06:48.000Z

Good morning, done

1st logs:

2nd sensors appear for D2CND(Gas):

Answer 25 · 2022-12-21T08:16:31.000Z

That's not bad. Now try to replace with this

Answer 26 · 2022-12-21T08:21:38.000Z

eduardkirkosa commented 2 years ago

Answer 27 · 2022-12-21T09:17:41.000Z

Ok that was a stupid mistake. Let's try again with this

Answer 28 · 2022-12-21T10:07:13.000Z

Sensor are back ;)

and no errors in HA logs regarding daikin :)

Thanks,

Answer 29 · 2022-12-21T11:41:04.000Z

what I can see a bit odd ;), maybe it's History logging slow, but the Value for the sensor show zero and attributes show data ( 2Hours and Day):

Month show value + attributes

Answer 30 · 2022-12-30T08:49:26.000Z

I see what is happening here. Normally, on my device, the data arrives with values and then is set to null for the rest of the day. This means I can simply pick the last non-null value and set it as the sensor value. However, in your case, the values are being set to 0, which is causing confusion with the integration. It might be best for you to create a template sensor that checks the time of day and picks the correct value from the attribute values. I will think about it.