Mydlink™ Home Door/Window Sensor DCH-Z110

jbtibor · May 26, 2016, 10:52am

I have created a device type for mydlink™ Home Door/Window Sensor DCH-Z110.
This is for the Z-Wave version not the WIFI version.

Can be downloaded from here:

It has support for SensorBinaryReport but it is only tested with default settings using NotificationReport.

Nick_S · August 31, 2016, 9:39am

Hi Tibor

Thanks for that, I have three of these sensors and just got smartthings yesterday. So I am very glad to see this posted.
One question however: The tile where I was expecting illuminance measures gives me an output of “10%” ?

jbtibor · August 31, 2016, 11:03am

Illuminance is reported as % by device not lux. I don’t do any transformation of the reported value. I couldn’t find the formula how the percentage is calculated.

Nick_S · August 31, 2016, 11:32am

Ah ok, I was not aware of that actcually. Thanks for clarifying, and even more so for the keeping an eye on this thread and replying so swiftly

jbtibor · August 31, 2016, 11:40am

You’re welcome. If you have any issues please contact me here.

Nick_S · September 11, 2016, 9:32am

Hi Tibor

I actually DO have another question:

Going through my logs I do have two types of message:

“Door Sensor is open” / "Door Sensor is closed"
and
“Door Sensor open/close state changed at …”

Whats the difference? Especially the 2nd one seems to show up at times where I am quite sure nobody actually did open or close the door that the sensor is attached to.

Thanks for clarifying.

N

jbtibor · September 11, 2016, 8:04pm

I’ll look at mine, thanks for letting me know.

Nick_S · September 16, 2016, 6:06pm

Im happy to take some screenshots in case thats of use…?

jbtibor · September 16, 2016, 10:39pm

I made a change, please check if it helps. It wasn’t happening often for me so I’m not sure if it didn’t yet happen or is fixed

github.com

jbtibor/SmartThings/blob/master/D-Link/DCH-Z110/DCH-Z110.DeviceType.groovy

/**
 *  Copyright (c) 2016 Tibor Jakab-Barthi
 *
 *  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.
 *
 *  mydlink™ Home Door/Window Sensor DCH-Z110
 *
 *  Author: Tibor Jakab-Barthi
 */

metadata {
	definition (name: "mydlink™ Home Door/Window Sensor", namespace: "jbt", author: "Tibor Jakab-Barthi") {
		capability "Battery"

This file has been truncated. show original

jbtibor · September 17, 2016, 12:12am

This message is supposed to be logged only when contact is opened or closed and the purpose is to display on UI when the last change was.

Nick_S · September 18, 2016, 9:17pm

Thx, ill see if its behavior changes. Do I need to reinclude the sensors after updating the device type?

jbtibor · September 18, 2016, 9:31pm

Just copy the new code to device handler, save and publish for self.
However the change didn’t fix the issue, I still get those entries. I think is related to illuminance report about every 6 hours, but I don’t get how that results in this event. I keep looking.

Nick_S · September 24, 2016, 3:45pm

Hey Tibor

What did you change? I dont seem to notice any differences, but then im not sure if I did things correctly.
Behavior of this sensor is still odd in my system.

I have a door sensor on a door that literally never gets opened…

I have the “open/close state changed” message appearing every 5 hours 50 minutes exactly:
15:14:41
09:24:15
03:34:11 etc

Also there are periods where I get a temperatur update from that sensor once every minute for like 10-15 minutes straight…whereas on other occasions i would get no temperature update for literally hours.

Illuminance updates then also arrive every 5:50hrs, but not at the same times as the “open/close state changed” messages.

I woud post a log, but not sure how and if thats possible

(Edit: There it is: http://pastebin.com/6xQb8fHZ )

jbtibor · September 25, 2016, 10:13pm

Unfortunately is not happening that regular for me so debugging is not easy.
The issue was that timestamp event was created even if there was no open/close event, I thought becuase testing for events was always true so I added size:

This didn’t work for me so now I moved the event creation to where open and close events are created.
Give it a try.

Nick_S · October 2, 2016, 8:58pm

No change to me it seems…I am wondering is anyone else using this sensor and confirm my observations?

jbtibor · October 2, 2016, 9:16pm

I have the same log entries, but not on a schedule so I couldn’t yet identify what triggers it. It shouldn’t happen so I asked a question but nobody answered yet:

Event created without apparent reason, should not happen Writing Device Types

Hello, I have this device type: This is the relevant code snippet: if (cmd.notificationType == 0x06) { def dateTime = new Date() def sensorStateChangedDate = dateTime.format("yyyy-MM-dd HH:mm:ss", location.timeZone) if (cmd.event == 0x16) { log.debug "open" events << createEvent(name: "contact", value: "open", descriptionText: "$device.displayName is open.", translatable: true) events << createEvent(name: "sensorStateChangedDate", value: sensorStateChangedDate, descriptionText: "$device.displayName open/close state changed at $sensorStateChangedDate.", translatable: true) } else if (cmd.event == 0x17) { log.debug "close" events << createEvent(name: "contact", value: "closed", descriptionText: "$device.displayName is closed.", translatable: true) events << …

If nothing changes for another week then I’ll remove the last state change date.

Nick_S · October 2, 2016, 9:19pm

So the open/close state change bit appears randomly for you? Because for me it appears periodically…

jbtibor · October 2, 2016, 9:37pm

Yes it is random, and it should be there only if there is also an open or a close.

jbtibor · October 11, 2016, 3:22pm

I updated the device type on Github. I didn’t have the false event for a day, could you try it too?

Nick_S · October 22, 2016, 9:53pm

Hi Tibor

Sorry, for some reason did not get notified of an update in here. I will update the device type and report back on its behaviour.

Topic		Replies	Views
Linkind Door/Window Sensor Model: ZS1 10050078 Devices & Integrations	20	3645	August 2, 2023
Z-Wave door sensor shows up as "Z-Wave sensor" and is Active or Inactive vs Open/Closed Devices & Integrations	8	3618	May 12, 2017
Hive Window/Door Sensors on ST Hub Devices & Integrations devicetype	3	1161	August 23, 2017
Monoprice Z-wave Plus Door/Window sensor Devices & Integrations monoprice	11	8570	January 5, 2017
Fibaro multi sensor fgms-001 Devices & Integrations	6	2548	April 22, 2017

Mydlink™ Home Door/Window Sensor DCH-Z110

Related topics