Add entities for Input, Output and Value Clusters

[dmulcahey]

We already have entities OOTB for AnalogOutput (number entities). We should add implementations for the rest of the clusters in this section of ZCL. It may make sense to have these all start disabled by default.

• Analog Input Add support for entities derived from AnalogInput cluster #146 - sensor?

  The Analog Input (Basic) cluster provides an interface for reading the value of an analog measurement and accessing various characteristics of that measurement. The cluster is typically used to implement a sensor that measures an analog physical quantity.

• Analog Value - number?

  The Analog Value (Basic) cluster provides an interface for setting an analog value, typically used as a control system parameter, and accessing various characteristics of that value.

• Binary Input - binary sensor?

  The Binary Input (Basic) cluster provides an interface for reading the value of a binary measurement and accessing various characteristics of that measurement. The cluster is typically used to implement a sensor that measures a two-state physical quantity.

• Binary Output - switch?

  The Binary Output (Basic) cluster provides an interface for setting the value of a binary output, and accessing various characteristics of that value.

• Binary Value - switch?

  The Binary Value (Basic) cluster provides an interface for setting a binary value, typically used as a control system parameter, and accessing various characteristics of that value.

• Multistate Input - enum sensor?

  The Multistate Input (Basic) cluster provides an interface for reading the value of a multistate measurement and accessing various characteristics of that measurement. The cluster is typically used to implement a sensor that measures a physical quantity that can take on one of a number of discrete states.

• Multistate Output - enum select entity?

  The Multistate Output (Basic) cluster provides an interface for setting the value of an output that can take one of a number of discrete values, and accessing characteristics of that value.

• Multistate Value - enum select entity?

  The Multistate Value (Basic) cluster provides an interface for setting a multistate value, typically used as a control system parameter, and accessing characteristics of that value.

[dmulcahey]

This is created as a summary. When I start on this I will create individual Issues and PRs for each implementation.

[darrencocco]

Hey I've been working on writing an Arduino library(for public release) for the Espressif Zigbee chips to support Multistate and Analog values and I've come across a bit of a roadblock when trying to integrate them with ZHA.

Currently working on the Multistate Value implementation and noticed that the current ZHA SelectEntity mappings all rely on using an enum to provide the name of the selector and the options that is has.

As you probably already know the ZCL standard has the 0x0055(State Text) for providing the wording of the options and 0x001C(Description) for providing the description of what the cluster represents (limited to 16 chars)

I was hoping to use these fields so that people making their own Zigbee devices have less to write in their custom quirks and the Zigbee device itself could be more self describing.

Unfortunately I'm kind of a scrub when it comes to Python so I only know enough to have worked out that either in it's current state it won't do what I need (accept the options list and option name from the Zigbee Cluster Attributes) or I simply don't know enough Python to implement an appropriate quirk to achieve the same.

[prairiesnpr]

Currently working on the Multistate Value implementation and noticed that the current ZHA SelectEntity mappings all rely on using an enum to provide the name of the selector and the options that is has.

This is in work. See: #197 and zigpy/zigpy#1456

[darrencocco]

Thanks! Sorry I didn't notice that one sooner. You might want to also note the issue I opened on zigpy if you're doing work in that space: zigpy/zigpy#1526