Childtile in new app

doncaruana · January 9, 2020, 2:26am

My DTH has a childtile which, of course, shows perfectly in classic but causes a big odd “button” tile (that you can’t interact with) to show up in the new app. Is this a known thing? If the new app supports child tiles, how do they need to be done? The child DTH displays fine in the new app, but the child tile doesn’t. Is there some documentation on how to make that happen?

Automated_House · January 9, 2020, 3:17am

Do you have vid and OCF metadata assigned to it?

doncaruana · January 9, 2020, 7:32am

Actually I do, for both the parent and the child metadata. Thought I didn’t, but just double checked.

Automated_House · January 9, 2020, 8:02am

strange. Does your DTH child have a weird combination of capabilites? If you switch to a standard child DTH, does it work?

doncaruana · January 9, 2020, 8:37am

Well…I removed it, changed the child device that gets created to just the generic “child switch” and rejoined it and I no longer have an odd button. I actually have no additional button on the parent device in the new app, but still working perfect in classic.

doncaruana · January 9, 2020, 2:11pm

Is there an example somewhere of a child tile/composite device being properly displayed in the new app??

Automated_House · January 9, 2020, 2:58pm

the default Zooz double plug handlers work great for me. If you’re expecting all of the switches to have tiles in one device page, that won’t happen in the new app. Each switch should create its own device and only show the switch for that device

github.com

SmartThingsCommunity/SmartThingsPublic/blob/master/devicetypes/smartthings/zwave-multi-metering-switch.src/zwave-multi-metering-switch.groovy

/**
 *  Copyright 2018 SRPOL
 *
 *  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: "Z-Wave Multi Metering Switch", namespace: "smartthings", author: "SmartThings", mnmn: "SmartThings", vid: "generic-switch-power-energy", genericHandler: "Z-Wave") {
		capability "Switch"
		capability "Power Meter"
		capability "Energy Meter"
		capability "Refresh"
		capability "Configuration"

This file has been truncated. show original

doncaruana · January 9, 2020, 3:02pm

That’s actually exactly what I was trying to work out! Two switches on same device (one main, one endpoint). Wanted them as a “composite device” in the new app like they would appear in classic.

johnconstantelo · January 9, 2020, 3:16pm

As so many of us want as well. A good use for something like that would be the new Zooz Zen30 switch, right?

doncaruana · January 9, 2020, 3:59pm

Automated_House · January 9, 2020, 5:09pm

I haven’t seen any example of this with switch capabilities. I have seen it for multi buttons. They have some mcdsync metadata that may or may not enable this, but then you probably need a VID For switches to support it also.

If you’re on a deadline, I’d just release the DTH conforming to current new app limitations and update later if ST ever shed light on this being possible for switches.

doncaruana · January 10, 2020, 4:38am

@Automated_House - Not a deadline, per se, but did want to get it pushed out at least (which I just did).

@johnconstantelo - coincidentally enough…[OBSOLETE] Zooz Zen30

iquix · January 15, 2020, 8:03am

Child-tile works well in “Ikea dimmer” which have “ocfDeviceType” and “mcdSync: true” flag

github.com

SmartThingsCommunity/SmartThingsPublic/blob/master/devicetypes/smartthings/ikea-button.src/ikea-button.groovy

/**
 *  Ikea Button
 *
 *  Copyright 2018
 *
 *  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.
 *
 */

import groovy.json.JsonOutput
import physicalgraph.zigbee.zcl.DataType

metadata {

This file has been truncated. show original

But the problem is… writing “ocfDeviceType” and “mcdSync: true” is not just enough to make everything work properly in new app.

To test this,

If you just COPY the source code of “Ikea Button” dth above, and only change the name of the device handler, for example, to “Ikea Button2”.

change isIkeaRemoteControl() method to
private boolean isIkeaRemoteControl() { return true}
to mimic Ikea button,
NO OTHER CHANGE IS MADE.

and create a device using that device handler, (or use simulator), to make a virtual device with this DTH

–>

then these problem only occur in copied DTH.

(Problem 1)
child Buttons show, but, “supportedButtonValues” are being ignored when displaying buttons

(Problem 2)
New app automation is not working properly for child buttons

(Problem 3)
the name in “componentLabel” does not show up, as in original DTH.

There must be some hidden code in Ikea button DTH other than shown in github code to work for New app’s device controller page.

It would be best, if just adding “mcdSync: true” and “ocfdevicetype” would be enough to make multi-button DTH to work properly in new app.

Do you have any plan to fix this problem in smarttings team?

Why I need this fix is …
actually I’m re-writing a DTH for multi button zigbee device (actually it is Hue Dimmer Switch) by modifying Ikea Button DTH…
I expected it to work correctly in New app, but very same problem occurs as above.
(Of course, it works fine in classic app)

I’m sure it’s not the problem of virtual vs physical device. There must be something unknown behind Ikea DTH.

---- original Ikea button DTH (supposed to show like this)

---- copied Ikea button DTH (with error)

iquix · January 15, 2020, 8:44am

FYI, this is my Hue Dimmer Switch DTH, re-written by modifying Ikea Button DTH.

github.com

iquix/Smartthings/blob/master/devicetypes/iquix/hue-dimmer-switch.src/hue-dimmer-switch.groovy

/**
 *  Hue Dimmer Switch ver 0.1.4
 *
 *  Copyright 2020 Jaewon Park
 *
 *  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.
 *
 */
import groovy.json.JsonOutput
import physicalgraph.zigbee.zcl.DataType

metadata {
	definition (name: "Hue Dimmer Switch", namespace: "iquix", author: "iquix", ocfDeviceType: "x.com.st.d.remotecontroller", mcdSync: true) {

This file has been truncated. show original

suffering same problem in ST new app.
Works well in smartthings Classic.

doncaruana · January 15, 2020, 2:44pm

This is fascinating because when I use the original DTH, unmodified, with a virtual device I created, I get the custom behavior you see. I would expect it to look just like the original you posted, even though it’s a virtual device, but it doesn’t. So far, the only thing I’ve seen made a child in the new app is the minimote, and I can’t duplicate it, which may be related to what you see.

Automated_House · January 15, 2020, 3:15pm

Minimote, Zwave Button and zigbee multi button all use child devices and MCD I think. Things also get screwy without a VID defined. Which may be impossible for the Zooz double switch since I haven’t seen a combination dimmer and button VID.

doncaruana · January 15, 2020, 3:18pm

What is MCD? And is the vid responsible for all the button options that iquix posted? I’m not understanding why the actual device and the virtual device show different options. I should, in principle, be able to assign one of these types to a virtual device and have it display properly. But I can’t even get that far…

Automated_House · January 15, 2020, 3:43pm

MCD = multi component device

iquix · January 17, 2020, 2:24am

I think the problem is not about virtual vs real device thing.

Because my custom DTH for HUE dimmer switch(posted above), which has almost similar architecture with ikea switch dth, has problem in new app automation.

There must be hidden secret settings with mcd device, which only makes Ikea button work,

and I want to know about that hidden and secret setting.

iquix · January 31, 2020, 5:01pm

I found the solution by myself.

Adding

ocfDeviceType: “x.com.st.d.remotecontroller”, mcdSync: true, mnmn: “SmartThings”, vid: “generic-4-button”

made it work well in the new app with Phillips Hue Dimmer Switch

This is my Hue Dimmer Switch DTH which also works well in New App.

github.com

iquix/Smartthings/blob/master/devicetypes/iquix/hue-dimmer-switch.src/hue-dimmer-switch.groovy

/**
 *  Hue Dimmer Switch ver 0.1.5
 *
 *  Copyright 2020 Jaewon Park
 *
 *  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.
 *
 */
import groovy.json.JsonOutput
import physicalgraph.zigbee.zcl.DataType

metadata {
	definition (name: "Hue Dimmer Switch", namespace: "iquix", author: "iquix", ocfDeviceType: "x.com.st.d.remotecontroller", mcdSync: true, mnmn: "SmartThings", vid: "generic-4-button") {

This file has been truncated. show original

Topic		Replies	Views
Generic Multichannel Z-Wave devices stopped working with new SmartThings app Devices & Integrations migration2020	41	3673	August 7, 2023
Child devices in new app Writing Device Types	35	5716	March 2, 2020
Help needed with custom DTH for motorized zwave curtains Writing Device Types	8	599	December 23, 2019
Question about standardTile UI update in SmartThings app Writing Device Types	26	2907	April 8, 2022
ZWave Dual Relay Integration App Status Devices & Integrations	1	184	February 14, 2024

Childtile in new app

Related topics