iCasa Pulse 8S Zigbee wall controller

[ebaauw]

Is there already an existing issue for this?

• I have searched the existing issues and there is none for my device

icasa.io kindly provided me with a new version of these switches. The hardware seems unchanged, except for the printed label. The firmware has changed, however.

The old version of the switch is currently supported by legacy code. This seems to work for the new switch as well, except for the battery (see Power Configuration cluster below) and the Off button (see Endpoints and clusters below). This seems like a good opportunity to create a DDF and lose come legacy code.

Product name

iCasa Pulse 8S Zigbee wall controller

Manufacturer

icasa

Model identifier

ICZB-KPD18S

Device type to add

Switch

Node info

Endpoints and clusters

The client Color Control cluster is new, but doesn't seem relevant. The switch still sends commands from the client On/Off, Level Control and Scenes clusters.

The Off button now sends Move to Level and Stop when held/released, instead of Move to Level (with On/Off) and Stop (with On/Off). That's easily added to button_maps.json.

Basic

Note the new ZCL Version (3 instead of 2) and, of course, SW Build ID.

Further relevant clusters

Power Configuration

Note that Battery Percentage Remaining now follows the standard and reports the value in 0.5%. The old firmware reports full percentages. I think we can probably use ZCL Version in the eval, so we would be able to support both firmware versions from the same DDF.

The new firmware supports attribute reporting on Battery Percentage Remaining, unlike the old firmware. I suppose if we specify it in the DDF, the REST API plugin will give up on configuring it for the old firmware on UNSUP_GENERAL_COMMAND?

OTAU

Manufacturer Id: 0x1224 (as in Node Info)
Image Id: 0x03F0 (old firmware used 0x2FAA)
Version: 0x0000001A

[ebaauw]

The new iCasa Pulse 4S Zigbee Wall Controller is exactly the same from a Zigbee perspective, except, of course, for the Model Identifier, ICZB-KPB14S. Also the same firmware. Since the difference in buttons is in button_map.json, I suppose we would support both switches from the same DDF. However, this will break once we will be able to specify the buttons in the DDF, so I expect @manup will want me to create separate DDFs.

I'm still expecting the new version of the Pulse 2, but I suspect it will be the same changes with respect to the old version, as for the 4S and 8S. Very similar DDF, except no binding for the Scenes cluster.