Z-Wave Multi Channel (PE653)

šŸ›Žļø Get Help Devices
122

@keithriley As you tipped me off with your prior remarks about the HE hub not receiving a response here is the log when I press the 'On' switch from the device.

From a practical point the on switch operates the pool light which, in the ST world, was EP1.

[dev:257](http://192.168.7.201/logs#dev257)2018-05-17 07:33:01.488:debug<<<<< dly:1500/1500 <<<<< Event: [name:switch, value:on]

[dev:257](http://192.168.7.201/logs#dev257)2018-05-17 07:33:01.473:debug>>>>> BasicReport(value:255) - description:zw device: 38, command: 2003, payload: FF

[dev:257](http://192.168.7.201/logs#dev257)2018-05-17 07:32:59.822:debug<<<<< dly:1500/1500 <<<<< Dev cmd: BasicSet(value:255) --> 2001FF, delay 1500 <<<<< Dev cmd: BasicGet() --> 2002

[dev:257](http://192.168.7.201/logs#dev257)2018-05-17 07:32:59.820:trace## HubAction: BasicGet(), format()=2002

[dev:257](http://192.168.7.201/logs#dev257)2018-05-17 07:32:59.818:tracel -> BasicGet()

[dev:257](http://192.168.7.201/logs#dev257)2018-05-17 07:32:59.817:trace## HubAction: BasicSet(value:255), format()=2001FF

[dev:257](http://192.168.7.201/logs#dev257)2018-05-17 07:32:59.814:tracel -> BasicSet(value:255)

[dev:257](http://192.168.7.201/logs#dev257)2018-05-17 07:32:59.793:debug+++++ on()
123

I will tell you that I have made a modicum of success with the multi-channel app;

I installed the app and chose as my template (Device with 9 switches), BUTI did not select any switches... instead I completed the installation.

This caused no child devices to install.

I then went back into the Multichannel App and this was the first time I was able to select 9 switches. I've selected 9 switches (excluding on/off) which gives me a total of 10 switches just like I am supposed to have.

I will see whether they are responsive later today when I get home.

1 Like
124

As more of an update, I turned on the child device Switch2 (this should turn on #2 on the PE653), but did nothing. Here is the log:

[dev:257](http://192.168.7.201/logs#dev257)2018-05-18 15:40:13.617:debug<<<<< dly:1500/1500 <<<<< Dev cmd: MultiInstanceCmdEncap(command:1, commandClass:37, instance:2, parameter:[255]) --> 6006, delay 1500 <<<<< Dev cmd: MultiInstanceCmdEncap(command:2, commandClass:37, instance:2, parameter:null) --> 6006

[dev:257](http://192.168.7.201/logs#dev257)2018-05-18 15:40:13.615:trace## HubAction: MultiInstanceCmdEncap(command:2, commandClass:37, instance:2, parameter:null), format()=6006

[dev:257](http://192.168.7.201/logs#dev257)2018-05-18 15:40:13.613:tracel -> MultiInstanceCmdEncap(command:2, commandClass:37, instance:2, parameter:null)

[dev:257](http://192.168.7.201/logs#dev257)2018-05-18 15:40:13.612:trace## HubAction: MultiInstanceCmdEncap(command:1, commandClass:37, instance:2, parameter:[255]), format()=6006

[dev:257](http://192.168.7.201/logs#dev257)2018-05-18 15:40:13.611:tracel -> MultiInstanceCmdEncap(command:1, commandClass:37, instance:2, parameter:[255])

[dev:257](http://192.168.7.201/logs#dev257)2018-05-18 15:40:13.606:debug+++++ onMulti(2)
125

Anyone???

126

So @keithriley is correct and the most recent firmware update did not fix the issue (it may not even be a firmware issue).

[dev:257](http://192.168.7.201/logs#dev257)2018-05-23 14:11:27.163:debug<<<<< dly:1500/1500 <<<<< Event: [name:switch, value:on]

[dev:257](http://192.168.7.201/logs#dev257)2018-05-23 14:11:27.127:debug>>>>> BasicReport(value:255) - description:zw device: 38, command: 2003, payload: FF

[dev:257](http://192.168.7.201/logs#dev257)2018-05-23 14:11:25.120:debug<<<<< dly:1500/1500 <<<<< Dev cmd: BasicSet(value:255) --> 2001FF, delay 1500 <<<<< Dev cmd: BasicGet() --> 2002

[dev:257](http://192.168.7.201/logs#dev257)2018-05-23 14:11:25.115:trace## HubAction: BasicGet(), format()=2002

[dev:257](http://192.168.7.201/logs#dev257)2018-05-23 14:11:25.111:tracel -> BasicGet()

[dev:257](http://192.168.7.201/logs#dev257)2018-05-23 14:11:25.107:trace## HubAction: BasicSet(value:255), format()=2001FF

[dev:257](http://192.168.7.201/logs#dev257)2018-05-23 14:11:25.102:tracel -> BasicSet(value:255)

[dev:257](http://192.168.7.201/logs#dev257)2018-05-23 14:11:25.068:debug+++++ on()

[dev:257](http://192.168.7.201/logs#dev257)2018-05-23 14:11:04.256:debug<<<<< dly:1500/1500 <<<<< Dev cmd: MultiInstanceCmdEncap(command:1, commandClass:37, instance:2, parameter:[255]) --> 6006, delay 1500 <<<<< Dev cmd: MultiInstanceCmdEncap(command:2, commandClass:37, instance:2, parameter:null) --> 6006

[dev:257](http://192.168.7.201/logs#dev257)2018-05-23 14:11:04.236:trace## HubAction: MultiInstanceCmdEncap(command:2, commandClass:37, instance:2, parameter:null), format()=6006

[dev:257](http://192.168.7.201/logs#dev257)2018-05-23 14:11:04.216:tracel -> MultiInstanceCmdEncap(command:2, commandClass:37, instance:2, parameter:null)

[dev:257](http://192.168.7.201/logs#dev257)2018-05-23 14:11:04.209:trace## HubAction: MultiInstanceCmdEncap(command:1, commandClass:37, instance:2, parameter:[255]), format()=6006

[dev:257](http://192.168.7.201/logs#dev257)2018-05-23 14:11:04.190:tracel -> MultiInstanceCmdEncap(command:1, commandClass:37, instance:2, parameter:[255])

[dev:257](http://192.168.7.201/logs#dev257)2018-05-23 14:11:04.016:debug+++++ onMulti(2)

The first log shows what happens when the user turns 'On2' directly from the device.  The second shows what happens when the user turns 'On' directly from the device.

You can see the extra line of code appearing on the command that works (On)

2018-05-23 14:11:27.127:debug>>>>> BasicReport(value:255) - description:zw device: 38, command: 2003, payload: FF

Which, according to @keithriley, means the hub is not talking back to the device with regards to anything other than On/Off.

@mike.maxwell you've been instrumental in making lots of strides with this one... is this firmware related or a device issue?

1 Like
127

Ok @JDogg016, I think I see the issue, and I suspect it may be a firmware issue. On ST when I turn on channel 3 the DTH sends the following (note highlighted raw command):

Dev cmd: MultiInstanceCmdEncap(command: 1, commandClass: 37, instance: 3, parameter: [255])
--> 6006032501FF, delay 1000
Dev cmd: MultiInstanceCmdEncap(command: 2, commandClass: 37, instance: 3, parameter: [])
--> 6006032502

Response from Device:
MultiInstanceCmdEncap(command: 3, commandClass: 37, instance: 3, parameter: [255]) - description:zw device: 16, command: 6006, payload: 03 25 03 FF

but in your logs when Hubitat encodes the same commands, the raw data is truncated:

Dev cmd: MultiInstanceCmdEncap(command:1, commandClass:37, instance:2, parameter:[255])
--> 6006, delay 1500
Dev cmd: MultiInstanceCmdEncap(command:2, commandClass:37, instance:2, parameter:null)
--> 6006

The 6006 is the MultiInstance command prefix that must be followed by the specific encapsulated command details. The first command should be also sending the 032501FF, which translates to:

03 length of encapsulated command
25 the command class, hex for 37 decimal
01 the command: "set device channel state"
FF the value to set the channel state to. In this case "on"

Hopefully this will be enough to let @mike.maxwell know where to look.

2 Likes
128

Yes it is, thanks!

2 Likes
129

ok, this should be fixed in the next release.

side note:

this byte is actually instance id, not the length

3 Likes
130

Right you are of course @mike.maxwell. Thanks for the fix, canā€™t wait to hear how it checks out...

131

Any time table?

1 Like
132

@keithriley Just saw the above from a couple of weeks ago on the ST forum. Can you say what your intentions are for your updated Device Handler (a/k/a DTH) on Hubitat? As far as I know, you haven't yet taken the HE plunge, so we are depending on your "kindness to strangers" to help us out. Just wondering what your thoughts are - probably too much to expect, but I'm hopeful. :slight_smile:

133
  1. Convert to ā€œCompositeā€ DTH which will re-enable Multi-Channel (multiple ā€œthingsā€)
  2. Improves VSP integration. No longer uses funky schedules to control VSP and can read current speed even if set manually or by remote control.
  3. Ability to set the Controllers clock.
  4. Display air temperature.
  5. IncorpĆ³rate adjustments for Hubitat compatibility. My goal is to do this in a way it is compatible with all platforms. Hoping to get results from latest HE firmware testing soon.

Most of this work is complete. Should be ready in another week or two.

134

Me, too. AFAIK, we're waiting on a Hubitat release that has the fix. I guess nothing else is broken in Hubitat :blush: so no releases lately.

Thanks for keeping this alive. And @JDogg016 too.

135

First let me say hi @JDRoberts.
Nice to be on the other side of the fans for a change. I have ordered my Hubitat this weekend.

Can you tell me how I can connect both of my Vision Z-wave Single and Dual Relay switches?

136

Sorry, I don't know. @mike.maxwell may.

137

Did it make it into 1.1.0.120 ?

138

Yes

1 Like
139

First of all, I'd like to thank everyone for their hard work on this! I'm finally able to control the individual switches on my Multiwave from Hubitat. What I would like to do is to be able to create a dashboard where I can see the current status of the switches, the current water temp, as well toggle each switch individually. I have a tile that shows the temp but I can't seem to get modes working at all, which would be an alternate solution although not as desired.

I should say that I am coming from a Vera Edge and never used the Smartthings hub so any help would be greatly appreciated!

1 Like
140

So I managed to get much further after looking back through this thread. I added the multi switch app as well as the vTile device driver and that got me almost all of the way. Now Iā€™m running into issues with my switch3 being triggered repeatedly and my logs being spammed with errors ā€œCME: CANTā€™T FIND INSTANCE: 3ā€

Everything else seems to be functioning well enough at this point. Iā€™m going to keep looking into it but if anyone has any pointers, that would be great!

141

After a week's worth of effort in implementing this, it might not be welcome news, but @keithriley has a new version:

https://community.smartthings.com/t/intermatic-pe653-pool-control-system/936/619?u=cal7

He teased it a couple of weeks ago and I've been anxious to upgrade.

1 Like