UseeLink ZigBee power strip

bertabcd1234 · April 17, 2020, 3:50am

For you or anyone curious about this: I ordered one and it arrived today. Surprisingly, I couldn't even get it to work with generic drivers (I was expecting on() and off() to maybe at least control everything; obviously control of individual endpoints would not be there unless the driver provided them). With some playing around, I was able to make something work. Here are my results:

github.com

RMoRobert/Hubitat/blob/master/drivers/useelink-sm-so301-uz-zigbee-power-strip.groovy

/*
 * ==================  UseeLink SM-SO301-UZ Zigbee Power Strip Driver ====================
 *
 *  Copyright 2020 Robert Morris
 * 
 *  Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 *  in compliance with the License. You may obtain a copy of the License at:
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
 *  for the specific language governing permissions and limitations under the License.
 *
 * =======================================================================================
 *
 *  Last modified: 2020-04-16
 * 
 *  Changelog:
 *  v1.0    - Initial Release

This file has been truncated. show original

By default, this driver creates a "parent" device for the strip with five child devices, one for each of the four outlets and one for the USB plugs (which, unlike many others, are indeed controllable). No other drivers are necessary (the child devices are created using Hubitat's built-in component switch drivers; also, you can disable their creation, but I can't imagine why you'd want to, though I created custom commands you can use with endpoint IDs on the parent if you do). I'd welcome feedback from anyone familiar with Zigbee, because this device appears to have some oddities for me:

it is my understanding that endpoint 01 is often the entire device itself (i.e., all outlets), but that is not the case here; that is outlet 1
outlets 1-4 are endpoints 1-4, the USB ports are outlet 7, and I did not see reports from or successful commands send to any other endpoint ID
because of the above, I'm not sure that there is any one particular ID for the strip itself (device.endpointId is null ... assuming this couldn't have been something going wrong during pairing?), so the parent on(), off(), and refresh() commands just send multiple commands, one to each known endpoint

Hopefully this works for anyone who has this! I'll move it from my dev hub to my "real" Zigbee hub later tonight or tomorrow and see if I notice any other issues.