# AT&T Digital Life Devices

**URL:** <https://community.smartthings.com/t/at-t-digital-life-devices/4304>\
**Category:** Devices & Integrations\
**Created:** [August 19, 2014, 12:28pm UTC](https://community.smartthings.com/t/at-t-digital-life-devices/4304 "2014-08-19T12:28:59Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![swanny](https://avatars.discourse-cdn.com/v4/letter/s/ecccb3/32.png) [@swanny](https://community.smartthings.com/u/swanny)\
**Post date:** [August 19, 2014, 2:26pm UTC](https://community.smartthings.com/t/at-t-digital-life-devices/4304/3 "2014-08-19T14:26:06Z")

</div>

@Keo was looking at an indirect way to integrate them in this thread but that is definitely some work. The suggestions from @Tyler is probably the best way to start.

> [@Integration with AT&T digital life](http://community.smartthings.com/t/integration-with-at-t-digital-life/4082/22):
>
> I think I am beginning to understand what you are showing me now. This actually appears pretty simple to do. Once I parse out the data from the email on my raspberri pi I can pass the necessary data to the url and as long as my smartApp know what to expect, It should work. I’ve been reading the docs and I think I may start working on this tomorrow. I still don’t get the whole child device thing. How is a child device different than a regular device? I understand parent/child relationships, I just don’t understand how a child device is different. If I am making a child device, what is it’s parent?

---

_[View the full topic](https://community.smartthings.com/t/at-t-digital-life-devices/4304)._