Certification device for Thermostat Setpoint CC has a broken entity in HA about certification-backlog

[AlCalzone]

You can now reproduce like this:

1. check out the current master of https://github.com/zwave-js/node-zwave-js
2. run yarn && yarn build to get everything up to date
3. save the following file in the repository as server_config_thermostat_sp.js
4. run yarn mock-server -c server_config_thermostat_sp.js
5. execute zwave-js-server with tcp://localhost:5555 as the path
6. hook up Home Assistant to the external zwave-js-server

// @ts-check
const {
	CommandClasses,
} = require("@zwave-js/core");
const {
	ccCaps,
} = require("@zwave-js/testing");
const {
	ThermostatMode,
	ThermostatSetpointType,
} = require("zwave-js");

/** @type {import("zwave-js/Testing").MockServerOptions["config"]} */
module.exports.default = {
	nodes: [
		{
			id: 2,
			capabilities: {
				basicDeviceClass: 4, // Routing Slave
				genericDeviceClass: 8, // Thermostat
				specificDeviceClass: 6, // General Thermostat V2

				commandClasses: [
					{
						ccId: CommandClasses.Version,
						version: 3,
					},
					{
						ccId: CommandClasses["Manufacturer Specific"],
						version: 1,
					},
					ccCaps({
						ccId: CommandClasses["Thermostat Mode"],
						isSupported: true,
						isControlled: false,
						secure: true,
						version: 3,
						supportedModes: [
							ThermostatMode.Off,
							ThermostatMode.Heat,
							ThermostatMode["Auto"],
							ThermostatMode["Resume (on)"],
							ThermostatMode["Auto changeover"],
						],
					}),
					ccCaps({
						ccId: CommandClasses["Thermostat Setpoint"],
						isSupported: true,
						isControlled: false,
						secure: true,
						version: 3,
						setpoints: {
							[ThermostatSetpointType.Cooling]: {
								minValue: 10,
								maxValue: 36,
								scale: "°C",
							},
							[ThermostatSetpointType["Dry Air"]]: {
								minValue: -9.87,
								maxValue: 56.78,
								scale: "°C",
							},
							[ThermostatSetpointType["Full Power"]]: {
								minValue: 20,
								maxValue: 32.767,
								scale: "°C",
							},
						},
					}),
					CommandClasses["Z-Wave Plus Info"],
				],
			},
		},
	],
};

[marcelveldt]

Reproduce as soon as we have the mock controller, it seems that we can't map a few properties for this test device.

[marcelveldt]

If the device has heating mode but not heating setpoint, it means the device setpoint for heating can not be controlled.
We should just hide the temperature control in that case.

[marcelveldt]

We can end up in the situation where a device has some setpoint that needs to be set but not (Z-Wave) mode exists for that. Worst case scenario we just make up a new mode to satisfy HA user interface but we don't set it in Z-Wave.

[AlCalzone]

Update: The test no longer throws errors in the UI. I still can't change setpoints though.