Hello,Our company is currently developing a Zigbee device, and would like to be able to offer customers the Echo Plus as one option for a simple voice-activated solution. We have done some testing and discovered several issues that would prevent us from moving forward with that idea. I'll try not to make these questions too technical for now. Is there someone I can contact outside of these forums to discuss this with? I have tried contacting email@example.com a few times over the last 6 weeks or so, but I have never received a response.
- The Echo Plus seems to base functionality on the Zigbee Device ID, instead of the actual Clusters that are supported by the device. Our device will support On/Off/Level Clusters, but these controls are not available when connected to the Echo Plus due to our Device ID.
- Our product will have an optionally connected second motor that appears as a second endpoint on the device. Is support for additional endpoints something that the Echo Plus can eventually support? If not, is there some workaround we can implement that the Echo Plus can support? (such as MFG-specific attributes/commands, see 4 below)
- Will there be some way to utilize the generic Zigbee OTA Cluster for pushing updates to the device through the Zigbee network on the Echo Plus?
- Will there be anything in the Echo Plus API to allow sending/receiving either MFG-specific reads/writes/commands or other HA1.2 read/write/commands that are not currently being supported by the Echo Plus? This would allow a much more robust integration platform since we would not be constrained by the limited command set implemented by the Echo Plus (and would allow us to implement a second endpoint ourselves).