Devolo Home Control Motion Sensor MT02647

[brumster (Paul)]

Does anyone have a solution to get this sensor working? It’s a motion, Lux, Temp sensor. I picked it up for not a lot of cash on eBay but I’m having trouble getting it working. And yes I’ve wondered if there is something wrong with it which is why it ended up on eBay

I’ve tried a couple of device handlers. And have also tried the code supplied by @timecrash linked here:

Connecting Philio tech PST02-B

Try this one. It works with Devolo Motion Sensor MT02647. Perhaps somebody has the ability to clean the code. It`s from the AEON Multisensor 6. /** Copyright 2015 SmartThings 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. */ metadata { definition (name: “Devolo Motion Sensor MT02647”, namespace: “smartthin…

I’m not sure if I’ve copied and pasted the code correctly or if I’m missing something obvious. It’s detected by ST as a “Z-Wave Door/Window Sensor”. I’ve changed the device type to a number of alternatives but it just can’t get it to work.

It seems to announce itself and then do nothing more???

Here’s the log when I power it up:

df3ab7a4-bf4f-4de5-9492-2e2253495db3 09:45:45 BST: debug After zwaveEvent(cmd) >> Parsed 'zw device: 04, command: 8407, payload: ’ to [[‘descriptionText’:Z-Wave Door/Window Sensor woke up, ‘isStateChange’:false, ‘displayed’:false, ‘linkText’:‘Z-Wave Door/Window Sensor’], physicalgraph.device.HubMultiAction@198e42c1]
df3ab7a4-bf4f-4de5-9492-2e2253495db3 09:45:45 BST: debug Device has been configured sending >> wakeUpNoMoreInformation()
df3ab7a4-bf4f-4de5-9492-2e2253495db3 09:45:45 BST: debug parse() >> zwave.parse(description)
df3ab7a4-bf4f-4de5-9492-2e2253495db3 09:45:45 BST: debug parse() >> description: zw device: 04, command: 8407, payload:
df3ab7a4-bf4f-4de5-9492-2e2253495db3 09:45:38 BST: debug After zwaveEvent(cmd) >> Parsed 'zw device: 04, command: 8407, payload: ’ to [[‘descriptionText’:Z-Wave Door/Window Sensor woke up, ‘isStateChange’:false, ‘displayed’:false, ‘linkText’:‘Z-Wave Door/Window Sensor’], physicalgraph.device.HubMultiAction@3febf899]
df3ab7a4-bf4f-4de5-9492-2e2253495db3 09:45:38 BST: debug Device has been configured sending >> wakeUpNoMoreInformation()
df3ab7a4-bf4f-4de5-9492-2e2253495db3 09:45:38 BST: debug parse() >> zwave.parse(description)
df3ab7a4-bf4f-4de5-9492-2e2253495db3 09:45:38 BST: debug parse() >> description: zw device: 04, command: 8407, payload:
df3ab7a4-bf4f-4de5-9492-2e2253495db3 09:45:38 BST: debug After zwaveEvent(cmd) >> Parsed 'zw device: 04, command: 9881, payload: 00 8F 01 02 03 80 03 64 05 31 05 03 01 5D ’ to [‘descriptionText’:‘MultiCmdEncap(numberOfCommands: 2)’, ‘isStateChange’:false, ‘displayed’:false, ‘linkText’:‘Z-Wave Door/Window Sensor’]
df3ab7a4-bf4f-4de5-9492-2e2253495db3 09:45:38 BST: debug General zwaveEvent cmd: MultiCmdEncap(numberOfCommands: 2)
df3ab7a4-bf4f-4de5-9492-2e2253495db3 09:45:38 BST: debug encapsulated: MultiCmdEncap(numberOfCommands: 2)
df3ab7a4-bf4f-4de5-9492-2e2253495db3 09:45:38 BST: debug parse() >> zwave.parse(description)
df3ab7a4-bf4f-4de5-9492-2e2253495db3 09:45:38 BST: debug parse() >> description: zw device: 04, command: 9881, payload: 00 8F 01 02 03 80 03 64 05 31 05 03 01 5D

As always thanks in advance for any help.

Zwave info here:

http://products.z-wavealliance.org/MarketCertification/File?folder=&filename=MarketCertificationFiles/1131/Devolo%20home%20Control%20Motion.pdf

[jbtibor]

My guess is that the last two bytes in command 9881 are the temperature report, where 01 is the code for temperature sensor and 5D is the temperature value in degrees F or C.
06 or 0A is for open/close and 03 is illuminance.
You might get illuminance only when the sensor is opened or closed, but usually this can be changed in configuration.

You get 98* messages because of encrypted communication.

I’m doing a brute force parse in a similar case becausse multi commands are not yet supported so the only way is brute force for now:

How to parse MultiCmdEncap?

Hi Guys, Anyone have example how to parse this? def zwaveEvent(physicalgraph.zwave.commands.multicmdv1.MultiCmdEncap cmd) { log.debug "MultiCmdEncap ${cmd}" } and the output is “MultiCmdEncap [4]” which is contained 4 commands. How to parse those 4 commands so that i can send each command to zwaveEvent(cmd)?

[JDRoberts]

It’s identifying as a door/window sensor, which is the MT 02648. Not the 2647. A lot of people get confused on this because they only put out one user manual for both models, but they are two separate devices and they use different command clusters.

That’s this one:

http://products.z-wavealliance.org/MarketCertification/File?folder=&filename=MarketCertificationFiles/1130/Devolo%20home%20Control%20Door-Window.pdf

Note also that if it is the door/window sensor that you should have the separate little magnet piece. If not, it will never show is closed. But you can use any magnet for that, just find one about the right size.