Aeon micro motor controller DSC14104 and SmartTiles?


I am using 3 Aeon micro motor controller DSC14104 , with the following device type;

And it works great in the smartthings app; up, down and stop.
But i have troubles making it work on SmartTiles dashboard. It only is possible to add it as a switch, but that doesn’t show the real state of the motor controller (doesn’t change when i make it go up/down/stop at the smartthings app), and offcourse i cannot use the 3rd option; stop.

Anyone knows a solution ? :slight_smile:

Tagging @tgauchat


Howdy, Dennis.

Unfortunately, SmartTiles (& ActionTiles) can’t directly support custom Device Types (i.e., those that use something other than the standard Capabilities… like Switch has on/off, not stop).

I actually wrote my own DTH for my projector screen, and yes, in SmartThings App it can have custom Tile for Stop, etc…

###The idea I have for this…

Add Capability “Momentary” and alias its “push()” Command to your “stop()” Command.

Then SmartTiles will let you add another “Thing Tile” for Momentary which you can place alongside the on/off (up/down).

BTW: ActionTiles has support for Capability Door, but even that official Capability only has open,close … no stop().

1 Like

Hi @tgauchat and @JDRoberts,

Thanks for clearing it up, i was assuming Tiles had problems with custom device handlers, now i know for sure.

I will try the solution you mentioned, and i was also thinking about using CoRe as a backup plan by adding a extra tile for stop. I will spend more time on the solution tomorrow, i’ll post the outcome.

once again, thanks :slight_smile:

1 Like

Well… i got this far:

Made virtual switches, added them to smarttiles and used Rule Machine for controlling the device handler of the roller shutter when i turn the virtual switch on/off. With CoRe the same rule doesn’t work (ehh…?)

Only thing is that when i use the smartapp and use the roller shutter device handler in the app (down up stop), the virtual switch isn’t updated to the new status of the roller shutter. Thing is… i think most of the times the roller shutters are controlled by automatic up/down and if i wanna change them myself i will use the tablet in the living room… But i preffered if i could just use CoRe with roller shutters and had access to all status :slight_smile:

You need to write a SmartApp that tracks the status of the Roller Shutter and updates the Virtual Switch accordingly!

It’s something that should have been built into the platform, but, alas, it isn’t there. I don’t know what CoRE can or cannot do in this regard.

I just handle this problem with my custom SmartApp(s): Almost the exact same situation: A Projector Screen that has up/down/stop. But I didn’t bother with a Virtual Switch for Stop.

You may find the code below helpful… or not. Dunno.

 *  Copyright 2015 Terry Gauchat
 *  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:
 *  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.
	name: "Screen Down Up Virtual Switch App",
	namespace: "CosmicPuppy",
	author: "Terry Gauchat",
	description: "Turns on (down) and off (up) movie screen linking it to Virtual Switch and ThingShield Projector Device",
	category: "My Apps",
	iconUrl: "",
	iconX2Url: "",
    iconX3Url: ""

preferences {
	section("When this Virtual Screen Switch is turned on / off :") {
		input "virtualSwitch", "device.projectorVirtualScreen", title: "VirtualSwitch", multiple: false, required: true
	section("Turn on (down) / off (up) Projector Screen:") {
		input "projector", "device.projectorScreenShield", multiple: false, required: true

def installed()
	subscribeToCommand(virtualSwitch, "switch.on", onHandler)
	subscribeToCommand(virtualSwitch, "", offHandler)
	subscribe(projector, "screen.on", screenPhysicalOnHandler)
	subscribe(projector, "", screenPhysicalOffHandler)

def updated()
	subscribeToCommand(virtualSwitch, "on", onHandler)
	subscribeToCommand(virtualSwitch, "off", offHandler)
  	subscribe(projector, "screen.on", screenPhysicalOnHandler)
	subscribe(projector, "", screenPhysicalOffHandler)

def logHandler(evt) {
	log.debug evt.value

def onHandler(evt) {
    log.debug "Handler caught On request from virtualSwitch."

def offHandler(evt) {
    log.debug "Handler caught On request from virtualSwitch."

def screenPhysicalOnHandler(evt) {
    log.debug "Handler Caught screen Physical On. Should not move screen."

def screenPhysicalOffHandler(evt) {
    log.debug "Handler Caught screen Physical Off. Should not move screen."

/* =========== */
/* End of File */
/* =========== */
1 Like

i’ve found a working solution (for me).

We barely use the stop function, so i didn’t add that to smarttiles.

I added virtual switches to the smart tile, one for each roller shutter, with an up/down icon depending on the status. When “Good Morning” is activated in the morning and “Good evening” is activated at night, it will also set the virtual switches to the right status. When the virtual switches are changed, it will also change the roller shutter itself, with the help of CoRe, so they are synced as long as we change the roller shutters from the virtual switch/ smarttiles :slight_smile:

1 Like