Daikin Onecta (Cloud) Binding [4.0.0.0;5.0.0.0)

Add-on Marketplace Bundles
468

Great,

Then I will delete the Target temperature channel

thanks a lot.

1 Like
469

Can confirm that Target Temperatur (and Target Temperatur Min Value, Target Temperatur Max Value, and Target Temperature Value Step) as UNDEF. I use the SetPoint without any issues.

1 Like
470

Hello everyone I need some input.

In the pull request, where my code for the binding is being reviewed by other developers, the question arose whether the number of channels regarding energy consumption is actually useful. Onecta provides this data in a strange way: per day, per hour, and per month. I simply send this data through the binding. But I think this is pointless and, above all, inaccurate.

I also created a yearly total in the binding, in which I calculate the consumption myself based on all the separate data per month. Every year, this channel also correctly resets to 0.

From this data, you can also calculate the consumption on a specific date.

My idea is to remove this strange consumption data from the binding and only pass on the calculated annual totals.

Am I missing something in this reasoning?

Greetings Alexander

1 Like
471

I think it’s worth knowing the monthly totals.

472

Would agree that the monthly totals are useful.

473

Hi Alexander,

Is there a technical reason to remove channels? Users can choose to use or ignore channels according to their personal needs. If there is a valid reason, then yes, channels can be removed. For power consumption, the current year is sufficient. If you keep the raw data, everyone can add whatever they want. But if there is no real reason to remove channels, then leave them as they are, since they map 100% to the Onecta GUI.

474

Hi @HenMus
The RawData had to be removed due to pullrequest comments.

My approach was also, “I’ll put everything in there so everyone can choose for themselves.”
But:
The problem with the energy items is that I can’t get the naming to conform to the desired standard.

The labels can consist of a maximum of 3 words and a maximum of 23 characters.
This doesn’t work with the following labels:

  • Energy Heating Last Year, January
  • Energy Heating Current Year, January
  • Energy Cooling Last Year, January
  • Energy Cooling Current Year, January

These are 4 different channels. And I really don’t know how to shorten this while keeping it unique and meaningful.
Mayby naming :

  • Energy Heating Last Year, January → Energy Heating Jan-1
  • Energy Heating Current Year, January –> Energy Heating Jan
  • Energy Cooling Last Year, January –> Energy Cooling Jan-1
  • Energy Cooling Current Year, January –> Energy Cooling Jan

I can ask to the reviewer if this is ok ?

On the otherhand if the yearly power is stored the data can be selected with an simple sql

This gives me a headache :frowning: