How to get a device type published?

DrZWave · November 25, 2016, 1:45pm

I have been trying to get my EZMultipli Device Type published for two years.
I have “submitted” it for publication several times but at no time has the submission even progressed to the next state.
No review, nothing. Can someone help to get this published?
The device type is fully functional and 2 other developers have helped contribute to the effort and a number of people have downloaded the GitHub Groovy code. But it would be so much easier for users if ST could simply support the device directly!

https://graph.api.smartthings.com/ide/submission/show/1ed40f12-d5ef-496e-8033-636e83022778

github.com

drzwave/ExpressControls/blob/master/EZMultiPliDeviceType.gy

// Express Controls EZMultiPli Multi-sensor 
// Motion Sensor - Temperature - Light level - 8 Color Indicator LED - Z-Wave Range Extender - Wall Powered
// driver for SmartThings
// The EZMultiPli is also known as the HSM200 from HomeSeer.com
//
// 2017-04-10 - DrZwave (with help from Don Kirker) - changed fingerprint to the new format, lowered the OnTime 
//              and other parameters to be "more in line with ST user expectations", get the luminance in LUX so it reports in lux all the time.
// 2016-10-06 - erocm1231 - Added "updated" method to run when configuration options are changed. Depending on model of unit, luminance is being
//              reported as a relative percentace or as a lux value. Added the option to configure this in the handler.
// 2016-01-28 - erocm1231 - Changed the configuration method to use scaledConfiguration so that it properly formatted negative numbers.
//              Also, added configurationGet and a configurationReport method so that config values can be verified.
// 2015-12-04 - erocm1231 - added range value to preferences as suggested by @Dela-Rick.
// 2015-11-26 - erocm1231 - Fixed null condition error when adding as a new device. 
// 2015-11-24 - erocm1231 - Added refresh command. Made a few changes to how the handler maps colors to the LEDs. Fixed 
//              the device not having its on/off status updated when colors are changed.
// 2015-11-23 - erocm1231 - Changed the look to match SmartThings v2 devices. 
// 2015-11-21 - erocm1231 - Made code much more efficient. Also made it compatible when setColor is passed a hex value.
//              Mapping of special colors: Soft White - Default - Yellow, White - Concentrate - White, 
//              Daylight - Energize - Teal, Warm White - Relax - Yellow
// 2015-11-19 - erocm1231 - Fixed a couple incorrect colors, changed setColor to be more compatible with other apps

This file has been truncated. show original

@duncan @mager @slagle @Ben can someone in ST help out?

tgauchat · November 25, 2016, 7:06pm

Just ping @slagle or @Tyler; either can check in on the submission and see where it is stuck.

DrZWave · May 29, 2018, 5:14pm

So the device type has been published and generally is working well.
But for some reason some devices are reading the temperature as -98.3, -74.2 or other invalid values. I can see the Z-Wave traffic and I am returning the properly formatted report per the scale requested (F) so the temperature is in the low 70s.

How can I try to get this fixed?

I excluded and then re-included the devices thinking they are using an old version or something but that didn’t appear to help.

@slagle @Tyler can someone help out here?

tgauchat · May 29, 2018, 5:43pm

Slagle and Tyler are no longer with SmartThings.

Even though the Device Type is published for public use, you can still create a self-published instance with extra log debug commands to diagnose the problems you are encountering.

How to get a device type published?

Customers

Developers

Download the SmartThings App