Disable certain functionality that the driver supports but HA not?

[marcelveldt]

Add some way to flag the driver that the consumer (HA) doesn't support a certain feature/CC.

Usecase is for example the Thermostat Setback feature that we do not support in HA while its being tested in certification if we say we support it in the driver. We need to inform the driver that we do not support this particular feature(s) so the driver doesn't report them as supported to the certification tests.

Find out what flags we need, known so far:

• Thermostat Setback CC
• Energy Production
• Schedule Entry Lock (Z-Wave JS UI has a dedicated UI for this)

Probably (I don't think those are supported):

• Climate Control Schedule
• Door Lock Logging
• Humidity Control Mode
• Humidity Control Operating State
• Humidity Control Setpoint
• Irrigation
• Language
• Scene Actuator Configuration
• Scene Controller Configuration

[AlCalzone]

Task:

For each of the above CCs, either

• Implement the minimum required functionality in the expert UI, see https://github.com/zwave-js/specs/blob/master/Z-Wave%20Specification%20AWG%20V5.0.pdf, chapter 6.2 Application Command Class Control Definitions
  or
• Declare that we won't support it in HA, so the support can be removed in the driver using a feature flag.

The latter requires followup work on both sides.

[MartinHjelmare]

I think we should decide before the Hackaton what to do so we can spend time on the Hackaton on implementing things instead of discussing things. If we can't do that I suggest we put this in hold until after the Hackaton.

[AlCalzone]

My suggestions:

The CCs marked (optional) have no control specification, therefore everything is just recommended.

Climate Control Schedule:
Seems complex UI wise and is deprecated --> disable

Door Lock Logging: (optional)

• Put in expert UI
• Textbox + Button to get X logging records, X = 0...(max supported)
• Show retrieved logging records, see definition

The following three may make sense to tie into the climate entity, but for certification the following should be enough:

Humidity Control Mode: (optional)

• Add a select entity to change the mode. Seems easy enough to do:
  

Humidity Operating State: (optional)

• Add a sensor to show the current state:
  

Humidity Control Setpoint: (optional)

• Probably expert UI?
• For each supported mode (this is a 1:1 match with Humidity Control Mode CC), add a way to change the target humidity.
• Each setpoint must be between the supported min/max value for that setpoint.
• The scale/unit must be one of the supported scales for that setpoint, these exist:
  

Irrigation: (optional)
Pretty complex, not many devices exist, I'd skip this.

Language: (optional)

• Probably expert UI
• A select that contains language (ISO 639-2:1998 alpha-3) / country codes (ISO 3166-1 alpha-2) in the format eng or eng-US

Scene Actuator Configuration: (optional)

• Definitely expert UI
• 4 fields:
  • Scene ID (1-255)
  • Dimming duration (instant, 1-127s, 1-127 minutes, default)
  • Checkbox for "override current settings"
  • Level (0-99; 255 [on])
• Buttons to retrieve and/or set the configuration for a scene ID

Scene Controller Configuration: (optional)

• Definitely expert UI
• 3 fields:
  • Group ID (between 2 and max. association group no. of the device)
  • Scene ID (0 = disable; 1-255)
  • Dimming duration (instant, 1-127s, 1-127 minutes, default)
• Buttons to retrieve and/or set the configuration for a scene ID

Schedule Entry Lock: (optional)
Versions 1-3 are deprecated (but useful), v4 will never be certified, replacement pending.
I'd skip this, unless we are looking for something to do.

Thermostat Setback CC:
If we report support for this, it is required. @marcelveldt what's the status of your investigation into Matter / Zigbee?
If expert UI, we need a few fields:

• select for the setback type:
  
• Setback state - switch between:
  • number input from -12.8 °C to +12.0 °C
  • select for the special modes
    

Energy production: (optional)
Apparently never certified.
Implementing would be easy enough though:

• 4 different values to display definition here
• parameter is one of
  
• unit is included in the value metadata