The Custom Integrator Show Installment 018 is live.  In this Installment, Ian and I wrap up our series of Podcasts covering networking, Ethernet hardware, UPnP technologies, DLNA, Devices Profile for Web Services (DPWS), and Microsoft’s Rally platform.  There are so many related and inner twined components that it makes designing, configuring, and troubleshooting a really complex task for even the most savvy integrator.  Hopefully, with the background we have provided tied to the links we have posted over the last few blog entries, you are better positioned to understand the platform’s capabilities, how these various components and protocols communicate with each other, what you may or may not want commit to for your clients from an interoperability standpoint, and potentially what the future may hold in store for the next generation of the home ecosystem.  I encourage you to listen to the Podcast and review the blog from the last installment for understanding how the technical pieces fit together.



Direct Download – Subscribe via RSS – Subscribe via iTunes – Subscribe with Zune


This Installment’s blog takes a bit of a twist.  As you probably know by now, one aspect of our business here at Interactive Homes, Inc. ( is to provide consulting services to vendors and manufacturers on products they are designing and developing to fit into the home environment.  Following is a write up on a product we helped design in with our friends at Archronix (ArcX) in Toronto, Ontario, Canada (  To me, this product epitomizes the whole concept of DPWS, low resource-based intelligent devices in the home, and the concept of where these technologies are headed.  We developed a portable system that demonstrated the capabilities of DPWS-based devices in the home, which is what I describe here.  We even had the opportunity to take it up to show off to the Rally and DPWS product team at the Microsoft Rally Summit in Redmond, WA, a little while ago.

The product I am describing is Archronix’s ArcWay ZigBee to DPWS gateway wirelessly tied into a pair of the company’s prototype (at the time) ZigBee-based ArcLight light dimmers (which really are cool when you program the blue LED-based rear-lit clear paddles to fade up and down and sequence like a light show image) .  Since then, companies like Crestron and CentraLite (JetStream) have brought out their own ZigBee=based light dimmers, too.


ArcX’s ArcLight ZigBee-based Lighting Devices

The ArcLight dimmers are based on the ZigBee Lighting Device profiles.  ZigBee is one of the leading mesh networking wireless standards (based on IEEE 802.15.4) we discussed previously for connecting constrained and low power devices within the home.  The standard has different “profiles” defined for various device classes.  In this case, it they use a Lighting Device profile.

The concept is that the ArcLight dimmers are connected wirelessly to the ArcWay gateway using ZigBee.  On the “other end” of the ArcWay gateway is an Ethernet interface that connects to the same home network as a Windows Vista PC running Windows Media Center.  Using Microsoft’s Rally technologies built into Windows Vista (and now Windows 7), the gateway exposes the Lighting Devices (the dimmers) as discoverable DPWS-based objects and we will be able to control them from within the Windows Media Center experience without having to setup or configure anything.

As you can see in the following screen shot, the Lighting Devices (Dimmers) show up as resources in the Network Explorer within Windows Vista.


The ArcLight Dimmers dynamically show up in Windows Vista’s Network page

This means that applications running on Windows Vista now have access to them and they can interact with them using the standard Rally and Devices Profile for Web Services Application Programming Interfaces (APIs).

When we bring up the properties of the ArcLight by double clicking on it, we get the following information:


The properties of the ArcLight as seen through Windows Vista

These are the same types of properties we discussed when talking about the Device Control Protocol (DCP) XML schemas in our previous Podcasts.  Notice that the dimmer has a Unique Identifier, which is how the system sees it, in addition to exposing various other properties like its Serial Number, Manufacturer, and Model Number (XML “tags” in the DCP).

These particular properties are all that Windows Vista lets you see by default.  However, any application trying to control the Lighting Device expects to know a lot more about what capabilities the device has.  It turns out many more attributes are available; we just need a better tool for viewing them.  A great little utility we have talked about quite a bit on our show, which is included with the Windows Vista Software Development Kit, is called FDBrowser.exe (Function Discovery Browser).  It lets us drill down into all of the attributes a device exposes through the Devices Profile for Web Services interfaces (it lets us look at other type of properties, but the DPWS category is the only one of interest to us for this).  Unfortunately, the roots of Windows still uses the old moniker of Web Services for Devices or WSD, so the navigation tree on the left still exposes these devices as being WSD Providers.


The ArcLight’s attributes as seen through the FD Browser utility

Here you can see that there is a lot more to one of these devices than meets the eye (or is exposed via the Properties Page from the Windows Vista Network page).  This is the information that lets us dynamically interact with the ArcLight dimming device without having to configure it or enter its capabilities into some kind of program.  By “self-describing” its features, it is easy for a home control application to be able to interact with the device dynamically.  This is the heart of Devices Profile for Web Services as it relates to home control applications.

It does not stop there, though.  We still need to do something with the dimmer.  ArcX wrote a simple Windows Media Center application using MCML (Media Center Markup Language).  After the application is registered in Windows Media Center during a brief installation process, an icon shows up in the Start Menu.


A simple MCML Windows Media Center application for interacting with the ArcLights

Note that this is a demonstration application to show how easy it is for someone to interact with a dynamically discovered device using Devices Profile for Web Services.  Its intent is not to replace a full-blown automation package like Exceptional Innovation’s Life|ware, which actually recognizes the same DPWS WSDLs we are using here.  Since Life|ware does support DPWS technologies and the associated WSDLs I published as part of our previous Installment (, you hopefully can get an appreciation for why they use DPWS for their connectivity and devices integration platform and the potential versatility it provides moving forward.

Now for the best part – the road to home control Nirvana almost is complete.  When the application comes up, it discovers the two light dimmers and makes them available for us to control.  We can operate the lights as if we were standing at the dimmers and physically adjusting them.  Moreover, if you do adjust them from the physical dimmer itself, the user interface tracks the changes and displays the change of status in real time (remember the concept of event subscriptions?).


A simple Windows Media Center application interacting with the DPWS Lighting Devices

The first time I saw the entire process work, I had to smile and say, “This really is boss, man. It actually works.” We are able to plug in a dimmer, have the OS discover it automagically, and control it with a remote through the Windows Media Center experience – all without having to download drivers, set it up through some sort of application, or configure anything. Who says dreams can’t come true?

Some more technical DPWS/Rally resources

And a little plug for our friends at Archronix Corp. (ArcX)

Archronix Corporation ( is a technology design and product engineering firm specializing in hardware control systems and the associated enabling software.  Archronix has taken its expertise in embedded processor and Windows application work and extended it into connected devices in the home.  The company provides product development and integration services for several OEM clients in Canada and the US. Much of ArcX’s current work includes connectivity to and integration with Windows Media Center for both high-end audio and audio distribution systems.  Archronix also is responsible for creating the Media Center interface for Magnum Dynalab’s MD109 high-end radio tuner in addition to Ethernet control for the Matrix MiSeries audio distribution controller.  Keep an eye out in the not too distant future for some more innovative products we are helping them develop.


Leave a Reply