Hi @csader,
Yes, i saw that one and used some of it as a starting point. It was well documented and easy to understand, but I wanted to do more.
That project uses the ‘on/off (example)’ device type and doesn’t report back the status of the door. It only shows the correct status of the door if the app is used to open and close the door(which is unlikely).
I created my own device type that shows two garage door icons that also indicate the current status of the door. If someone opens the door, the device on the smartthings app will immediately show that the door is open. This works with both garage doors. Using this as an example, it would not be hard to expand upon and keep track of other things. The example you mention does not provide any insight on how to build a new device type.
There was another example that shows the door status, but uses another smartthings device to do it. Although this is neat, it’s also quite expensive. My project uses an arduino($30), smartthings shield($?), a two channel relay($5), and two window sensors($2).
@jlboygenius Very cool! Thanks for the clarification. I would be VERY interested in the details about your hardware setup, your device type code, etc. Please share, even if it’s in a work-in-progress state…the project pages are fairly decent at allowing you to progressively post updates and make it clear that it’s a work-in-progress.
We don’t have an answer on @twack 's original question…
Can you have the ThingShield represent multiple devices with multiple tiles?
Understand that you can have ThingShield control multiple devices (as a unit, or separately), but currently only sounds like that is possible within a single tile (with multiple sub-tiles), rather than multiple top-level tiles representing multiple devices on the same ThingShield. I’m interested in the same. @urman can you provide insight?
tgauchat
(ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)
24
I made this a “feature request” eons ago. (Along with a few related variations; such as allowing multiple tiles of the SAME Thing, so that it could be represented under multiple groups… i.e., like soft-links or shortcuts in Windows).
Thanks for continuing to put pressure on this issue. There are dozens of appropriate scenarios to represent one ZigBee or Z-Wave endpoint as multiple main tiles.
The context I mostly have mentioned this in, is for building “bridge” devices (e.g., a ZigBee to X-10 bridge … One ZigBee/shield could message up to 256 X10 devices, and each should be allowed a Main Tile).
We don’t have an answer on @twack ‘s original question…
Can you have the ThingShield represent multiple devices with multiple tiles?
Understand that you can have ThingShield control multiple devices (as a unit, or separately), but currently only sounds like that is possible within a single tile (with multiple sub-tiles), rather than multiple top-level tiles representing multiple devices on the same ThingShield. I’m interested in the same. @urman can you provide insight?
@baloodevil not currently. We’re building something in for devices to act like “parents” so there is a main “parent” device with “child” devices. An example of its current implementation is the Philips Hue. There is the main device and multiple bulbs. So while its not possible with the shield now, its definitely getting very close.
@urman@hagins I add my vote for an enhancement to allow multiple tiles per ThingShield. I agree with @tgauchat that the primary use for this is for bridge devices. It would be a good strategic move for SmartThings. Allowing makers to build bridge devices to other home automation technologies will solidify SmartThings as the go to home automation platform. An existing X10 network that can be properly hooked up to SmartThings with multiple top level tiles or devices will encourage migration. Analogous to Mac’s running Windows applications. That opened the door for long-time Windows users to switch. It applies to X10, HomeEasy, Sonos, NinjaBlocks, etc. Or really, any home automation device that does not speak directly to a SmartThings hub.
Another vote. This functionality is absolutely critical, especially when compared to more open systems coming down the line.
Two things have kept me from committing fully to SmartThings: the lack of multiple tile/item support for bridging X10/Insteon/Other systems and the lack of multiple Modes.
Oh, and of course the horrible state of the Android app, even after all the promises made to catch up and take the lead over the walled-garden iPhone version.
To be honest, I’m looking more and more at the Ninja Sphere project - mainly because it’s an open system.
tgauchat
(ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)
28
Ditto on the desirability of a more (or fully…) “open system”; I’ve been following Ninja quite closely.
Have you looked at / considered “Webee” (currently on Indiegogo)? I am a little worried about their viability due to such a low funding goal ($50,000 – not enough money to get a SmartThings competitor off the ground, right?), but I am intrigued that their SMART HUB or “Boss” (?) is completely Android based, and, they imply, will be open software. I’m not sure of their commitment in this regard.
What I really wish for is for Apple to open AppleTV to third-party developers. This would immediately put brakes on all this proprietary hardware proliferation and allow people to focus of what’s really important, that is writing quality software. Don’t you agree that AppleTV would make a perfect home automation hub?
LOL, @Col. Hack! That made my day. The walled garden company is the antithesis of open systems. (That was a joke, right? It’s so hard to tell on the Internet)
Well… I don’t think that Android’s garden is less walled than iOS, however that’s not my point. What’s important is that all developers get behind a common hardware/software platform (or two) which is sufficiently open (and I don’t necessarily mean open-source) and conductive to application development and stop spinning their wheels on all these mushrooming half-baked, haphazardly designed, overpriced junk boxes like Vera, Iris, ST, Ninja, Revolv and a dozen of others trying to get crowd-funded now and then. If success of the iPhone and iTunes is not convincing enough then I don’t know what is. For that matter, I don’t care whether it’s Google or Apple who takes the lead. Hopefully they both will. Now that Google made its move with Nest, I’m waining for Apple’s response.
I would totally agree that having multiple devices represented by a single shield is of the utmost importance. The whole reason I bought SmartThings was the Arduino shield. I am looking to integrated it with an existing 10 thermostat RS485 network, all of which should show up as individual devices, not under one master device. I will also be trying to integrate with an existing Lutron HomeWorks system which has tens of dimmers on it.
I would strongly encourage SmartThings to move in this direction as this will help migrate many existing installed systems (Lutron, AMX, Aprilaire HVAC, etc.) to SmartThings.
Most of these are controlled via simple ASCII serial commands (RS232 or RS485) and address many devices. All that’s needed is a single shield and Arduino to/send receive ASCII data to control various devices on these networks. Let’s simplify the process and represent a true physical device (dimmer, thermostat, switch) as a single device, regardless of what network it is on.
tgauchat
(ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)
33
Hear hear!
Thank-you!!!
All that’s needed is a single shield and Arduino to/send receive ASCII data to control various devices on these networks. Let’s simplify the process and represent a true physical device (dimmer, thermostat, switch) as a single device, regardless of what network it is on
@urman Any idea on timing for the parent-child device tiles? Hopefully we could eventually have a way to represent one physical radio (ZigBee or Z-Wave), such as the one on the SmartShield, with multiple devices.
I’m working on integrating both a Lutron Homeworks system (tens of dimmers and switches) and an Aprilaire HVAC system (10 thermostats) with SmartThings and would really love to be able to represent the Lutron/Aprilaire devices as its own device rather than under a parent.
This will be done by passing ASCII messages from SmartThings to the Arduino (with SmartShield) which also utilizes an RS-232 to TTL serial adapter (https://www.sparkfun.com/products/449) to talk via RS-232 to Lutron and Aprilaire.
I am planning on sharing all the source code once finished and think that if we can move this route we’d really solidify SmartThings as integrator-friendly!
@gradinko I don’t have a solid timeline, but the parent-child relationship is necessary for a high priority device we’re working on. As soon as its done (or hopefully slightly before) we can load the code up into the examples list for all to see!
INTEGRATE OR PERISH!
Project looks bad ass btw, we had someone working on that recently I think @dlieberman was toying with it.
@Keymaster, can I assume high priority means ~ revenue stream?
The pooch was screwed when not originally organically conceived … as I have previously stated.
I can concede that due to … not enough thinking was put into these … variants of things.
I am hopeful at some point we have more transparency of happenings at SmartThings. Meaning when we are stuck or SOL.
In the meantime you are correct with your statement “INTEGRATE OR PERISH!” but how about something more modern -
‘Integrate or Disintegrate’ or 'Interoperability is … not a solid timeline …". ?Do you need a product manager?
Any update on this? Anyone building with Arduino will potentially greatly benefit from this. At the moment I have to expose things as custom capabilities, which means I cannot leverage any of the default SmartApps.
Cheers, Jonathan
tgauchat
(ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)
38
Thanks for keeping this topic alive… I’m still (not) holding my breath.
Curious if you would like to share some examples of what / how you implemented using “custom capabilities”, though. I know it’s not ideal, but maybe the community will informally agree on a typical standard workaround (?).
I used custom capabilities of Relay1 thru Relay8 but have not managed to get my SmartApp to see the device yet. This is what led me to this post - why am I messing around with custom capabilities when all I really need are 8 switches. Using my own capabilities also means that I can only use my own apps, and for most of what I want to do the off-the-shelf apps will suffice. I don’t want to re-write all the basics.
I’m running out of enthusiasm - I’ve spent hours fighting the platform and trying to find documentation and I’m beginning to feel it is hindering me, not helping me. At this point I’m tempted to put everything on hold and see if anything happens with directly supporting multiple devices on on Arduino shield. If not, this will probably be easier to code directly - I have a server which is always on which could easily control the arduino directly via USB and a very simple web app would give me the necessary control. A lot less cool though - I really want this to work out with the ST hub and app.
Sorry I’ve off-line for a few days. House projects and such.
Anyway, I’m currently working an 8 sub-device/arduino project too. I’ve figured out how to logically have the 1 parent and 8 children, but I’m stuck on the children appearing as detail tiles underneath the parent. I have some dialog going with ST guys so hopefully we can figure something out. I’ll share when I can.