Add support for devices 013-000 (oven)

[oyvindwe]

Superseeds PR #135

Still about 40% properties left to map, creating this as a draft PR for transparency.

[Achronite]

I've just installed to try to set-up the same oven. What do you recommend I should do to progress this?

[oyvindwe]

It would be great if you could download the mapping file from this PR and test it out: https://github.com/oyvindwe/connectlife-ha/blob/devices/013-000/custom_components/connectlife/data_dictionaries/013-000.yaml

Store it in custom_components/connectlife/data_dictionaries/

It is a massive number of properties, and required some new features as well, so it has taken me much longer time than I anticipated.

I have not started on the translation strings yet.

[Achronite]

Here is an example of the entities whilst running, they are ordered by last update time.
During pre-heat:

and a bit later... during cooking:

I have a question, how do i change the yaml so that the entities are not hidden?

[oyvindwe]

I have a question, how do i change the yaml so that the entities are not hidden?

The hidden status in the yaml file is just default. There are so many properties for this device, so I set most of them to hidden. Once you have set visibility to true for a property, Home Assistant will remember that for you.

[hros]

@oyvindwe , thanks for the great work on the integration

I started working on annotating the oven yaml file from a blank dump of the properties (013-xxxx.yaml).
I see that you have made significant progress, so I'd like to use or build upon your version.

I'm still struggling to start a cooking cycle, that is, turning the oven "on." Have you managed to do it?
I can set timers, temperatures, and cooking modes for the various steps, but I haven't found the property that starts/stops the oven. I have a "status" property, but while it tracks the oven's state, changing it from Home Assistant doesn't change the oven's cooking status.

I had the status property configured as

- property: Status
  hide: false
  switch:
    "off": 1
    "on": 2
    command: 
      name: Oven Status
      adjust: 1

I changed it to your configuration

- property: Status
  sensor:
    device_class: enum
    options:
      0: not_avaliable
      1: idle
      2: running
      3: pause
      4: production
      5: delay_time_waiting
      6: error  

Which is defined as a sensor, so, naturally, it is not "actionable". Does this mean it is impossible to start cooking from the integration? After all, the ConnectLife app can do it, and it is using the same interface

Another question: how do you reload/reconfigure a device without restarting Home Assistant?

[oyvindwe]

I'm still struggling to start a cooking cycle, that is, turning the oven "on." Have you managed to do it?

I don't have this oven, I am working off a JSON dump of its properties provided by another user.

I'm still struggling to start a cooking cycle, that is, turning the oven "on." Have you managed to do it?

For most appliances, you have to first enable remote control physically on the appliance. Is this the case for this oven as well?

When the command is a separate write only property, these are usually suffixed _cmd.

Could you try to add this property:

  - property: Actions
    select:
      options:
        0: start
        1: pause
        2: stop

Another question: how do you reload/reconfigure a device without restarting Home Assistant?

It should work to reload the integration if you only change mapping files. If you change Python code, you always need to restart Home Assistant.

[hros]

Thanks @oyvindwe ,

For most appliances, you have to first enable remote control physically on the appliance. Is this the case for this oven as well?

Yes. The remote control is enabled, and the oven can be controlled using the ConnectLife app. I want to do the same (and more complex action sequences) from the home assistant integration.

My yaml file has the following properties related to "remote control":

- property: Remote_control_monitoring
  # Sample value: 1
- property: Remote_control_monitoring_set_commands
  # Sample value: 1
- property: Remote_control_monitoring_set_commands_actions
  # Sample value: 0

When the command is a separate write only property, these are usually suffixed _cmd.

I don't see any properties with the _cmd suffix, neither are there any such properties in the 023.yaml data dictionary for an oven (what is the difference between 013 and 023 ovens?).

Could you try to add this property:

  - property: Actions
    select:
      options:
        0: start
        1: pause
        2: stop

I added it to the data dictionary, but it does not show up in the device's controls. Even after adding "hide: false".

One more thing regarding your suggestion for adding the Actions property: Is it possible for a property, specifically an actionable property, to not be listed as the result of the connectlife.dump command?

[hros]

Based on your mapping for 013-000.yaml, I merged the shared properties into my properties dump file:
013-oven-bio21-fulltouch.yaml

My main question is how to use the integration to start and stop a baking step. The remote connection is active, which is evident by the fact that I can control the oven using Hisense's ConnectLife app.

On a side note, a home assistant question: currently, all the visible oven entities are showing in Home Assistant's dashboard as part of a list of entities in the "kitchen" area. Do you know how I can group them into a separate oven UI element? Can it be accomplished in the default dashboard, or must I create another dashboard?

[hros]

Hi @oyvindwe , is there any news regarding the support of ovens in general, or at least how to specify the controls to start and stop a program?