Enerwave Motor Controller (Model: ZWN-MCM-AC) recognized as Basic Relay Switch instead of Curtain Motor Controller/Shutter Relay by SmartThings Hub/App

[Chun (Chun Liew [SmartHomeDB Evangelist])]

So I changed the device type to a “centralite dimmer” and unfortunately the result is that the actions ON/OFF in the SmartThings App do not result in the engine turning right OR left physically.

So I believe the hardware Enerwave Motor Controller (Model: ZWN_MCM-AC) is not compatible with the CentraLite Dimmer Device Type.

Just to make sure I followed the right process:

On https://graph.api.smartthings.com/ide/devices I clicked on [+ New SmartDevice]

I selected tab [From Template]

I selected [CentraLite Dimmer]

I clicked on [Create]

I clicked on [Set Location]

I selected for ‘Choose a device to test with’ [Enerwave Shutter Relay]

I clicked on [Install]

I clicked on [Publish] > [For Me]

I clicked on [Save]

I tested whether the hardware and updated software configuration would pair by unplugging and replugging the power to the SmartThings Hub and the Enerwave Motor Controller.

It unfortunately did not.

I created a New SmartDevice and followed the same above steps but now for Dimmer Switch (the original auto-selected Device Type initially).

After unplugging and replugging the power to the SmartThings Hub and the Enerwave Motor Controller I was able to control the Enerwave Motor Controller as per original configuration:

On = Turn Right
Off = Turn Left

As a side-remark, I believe I read user Aracaneshark experience the same problem as me, but with the Fibaro FGRM 222 - Roller Shutter:

@Arcaneshark

So I would like to say thanks @duncan for getting the latest firmware. It certainly resolved my issue with getting the Fibaro FGRM 222 joined. I now have a basic Device Type which allows control to raise blinds, drop blinds, and set to a percentage opened. Unfortunately I haven’t found a command to “stop” movement where it is. So I for now will write a “Stop” based on getting current position when button pressed and then “Set” to that value, which depending on the lag may slightly reverse direction for a fraction. I’m also working on an option to open/close lamella’s.

I’m also trying to explore all of the other Command Classes it offers, to see what else is available, just from a knowledge perspective.

Unfortunately, when I try to read the Parameters 1 and 2, which are the “local button protection” and “Z-wave protection”. I get no response from these Configuration requests.

Anyways, progress is being made.

Fibaro FGRM 222 - Roller Shutter

Yeah. It needs all message sent as secured: I had to do the same thing for the recessed door sensor. Basically I added the following method: private secure(physicalgraph.zwave.Command cmd) { response(zwave.securityV1.securityMessageEncapsulation().encapsulate(cmd).format()) } and replaced result << response(NON TEXT BLAH) with result << secure(NON TEXT BLAH) I also changed the fingerprint to make it auto-detect.