Problems with the Intel UPnP Tools

[bwelsh]

Hi UDI - I'd like to use these Intel Tools with the ISY26

 

http://www.intel.com/cd/ids/developer/a ... /index.htm

 

Does anyone else use these tools? I've looked over the License Agreement and it seems OK to use these tools for debugging purposes royalty free.

 

The ISY26 isn't recognized by the Device Spy (my favorite), Device Sniffer, or Device Validator. I can see the Device Spy ask for and receive the /0/d.xml device file, but it doesn't ask for the /WEB/UPNPSVC.XML SCPD file. My 1st guess is that the Intel tools don't understand these two elements:

 

<__CU>h

<__NU>/WEB/NODESCNF.XML

 

I checked the Flexible XML Processing Profile draft

http://www.upnp.org/download/draft-goland-fxpp-01.txt

 

Maybe these two unknown elements cause d.xml to fail schema checking because they're not in the upnp namespace xmlns="urn:schemas-upnp-org:device-1-0"

[Michel Kohanim]

bwelsh,

 

We have never had this request nor do we use the Intel tools ourselves.

 

We had to make some modifications to the original UPnP specifications becuase, at least in the Lighting world, they did not reflect the reality. It would've been quite impractical to create 100s of Embedded Devices in the UPnP device, update associates with them, and etc.

 

Instead, we do have two configuration files which you are referencing. They should've been prefixed with X_ to show manufacturer extension but we decided against it.

 

__CU is our configuration file; it has all the details of the device running on ISY

__NU is our nodes configuration file; it has all the devices and their relationships

 

May I humbly ask whether or not you have a specific application for ISY in mind?

 

With kind regards,

Michel

 

Hi UDI - I'd like to use these Intel Tools with the ISY26

 

http://www.intel.com/cd/ids/developer/a ... /index.htm

 

Does anyone else use these tools? I've looked over the License Agreement and it seems OK to use these tools for debugging purposes royalty free.

 

The ISY26 isn't recognized by the Device Spy (my favorite), Device Sniffer, or Device Validator. I can see the Device Spy ask for and receive the /0/d.xml device file, but it doesn't ask for the /WEB/UPNPSVC.XML SCPD file. My 1st guess is that the Intel tools don't understand these two elements:

 

<__cu>h

<__nu>/WEB/NODESCNF.XML

 

I checked the Flexible XML Processing Profile draft

http://www.upnp.org/download/draft-goland-fxpp-01.txt

 

Maybe these two unknown elements cause d.xml to fail schema checking because they're not in the upnp namespace xmlns="urn:schemas-upnp-org:device-1-0"

[bwelsh]

Hi Michel - Thanks for the quick reply. At this point I'm only trying to understand the capabilities of the ISY-26. Please understand that I'm not complaining about the way the ISY-26 works.

 

I initially thought that the ISY-26 was a UPnP device representing an INSTEON network. It looks like the ISY-26 is similar to a UPnP device, but there are substantial differences.

 

Is the ISY26 a UPnP device? Could I use any UPnP Control point Stack to control it?

[Michel Kohanim]

bwelsh,

 

My pleasure. Yes, you can use a controlpoint to control it. The only issue is that you cannot assume that ISY is a UPnP Light Device because it is not. Your controlpoint, however, can read the service description and send UPnP web service requests.

 

So, in short, ISY is UPnP enabled; it is not UPnP certified and it does not conform to UPnP Light Device since they do not apply.

 

With kind regards,

Michel

 

Hi Michel - Thanks for the quick reply. At this point I'm only trying to understand the capabilities of the ISY-26. Please understand that I'm not complaining about the way the ISY-26 works.

 

I initially thought that the ISY-26 was a UPnP device representing an INSTEON network. It looks like the ISY-26 is similar to a UPnP device, but there are substantial differences.

 

Is the ISY26 a UPnP device? Could I use any UPnP Control point Stack to control it?

[Michel Kohanim]

bwelsh,

 

Quick clarifications.

 

I forgot to mention that we use UPnP Security 1.0 for our communications. I haven't seen any UPnP Security 1.0 aware controlpoints. Furthermore, I believe that UPnP Security 1.0 has since been abandoned. If you really want to test ISY with a controlpoint, please do let us know: we'll be able to send you an insecure version which should work with most controlpoints out there.

 

From a strategic perspective, we shall move away from UPnP and more towards DPWS since it leaves the implementation details of device attributes to the manufacturers (unlike UPnP).

 

With kind regards,

Michel

[bwelsh]

Hi Michel - Thank you. I saw DecryptAndExecute and related methods in your service file but I wasn't sure that was my problem. If you have an insecure version for download, I will try it with my Control Point.

 

I look forward to hearing more about the ISY-26 and DPWS. - Burt

[Michel Kohanim]

Burt,

 

My pleasure ... it shall be sent to your email address profiled on the forum.

 

With kind regards,

Michel

Hi Michel - Thank you. I saw DecryptAndExecute and related methods in your service file but I wasn't sure that was my problem. If you have an insecure version for download, I will try it with my Control Point.

 

I look forward to hearing more about the ISY-26 and DPWS. - Burt

[bwelsh]

Hi Michel - Thanks for the unsecured version. The reason that my Control Point didn't recognize the ISY-26 device may be because the WEB/UPNPSVC.XML file is a Web Service interface instead of a UPnP Service Description file.

 

I think the two types of files must be similar, but the UPnP Service Description file also requires:

1) each of the action elements need a element and a corresponding element in the element

2) the Unsubscribe action have an element (actually the UPnP subscription URL is specified in the Device file)

 

Does that sound right to you?

 

In order to use my control point I'd need to know the API for each of the actions (type and allowed values for each argument). Has UDI published that? Not sure about the slightly different subscription technique yet.

[Michel Kohanim]

bwelsh,

 

You are 100% correct and apologies for the confusion/discrepancies. I had totally forgotten that about 5 months ago - in preparation for DPWS - we had removed all the UPnP specific service descriptions (such as , "event=yes/no", etc.).

 

If you have a special need, we can surely resurrect our old code and send you a firmware update from a while back.

 

Again, may I humbly ask about the application?

 

With kind regards,

Michel

 

Hi Michel - Thanks for the unsecured version. The reason that my Control Point didn't recognize the ISY-26 device may be because the WEB/UPNPSVC.XML file is a Web Service interface instead of a UPnP Service Description file.

 

I think the two types of files must be similar, but the UPnP Service Description file also requires:

1) each of the action elements need a element and a corresponding element in the element

2) the Unsubscribe action have an element (actually the UPnP subscription URL is specified in the Device file)

 

Does that sound right to you?

 

In order to use my control point I'd need to know the API for each of the actions (type and allowed values for each argument). Has UDI published that? Not sure about the slightly different subscription technique yet.

[bwelsh]

Hi Michel - I understand some of UPnPs limitations (specifically control via the internet), and DPWS is a good alternative.

 

What do you recommend?

1. Web Services via something like https://forge.soa4d.org/

2. UPnP via your older code

 

Either way, I'd need to know the ISY API. For each action, I'd need to know what each argument is for and what it's allowed values are. I might be able to figure out some of that from your older service file. Does UDI publish the ISY API? Or does UDI only support the JSDK?

 

No application yet. At this point I'm looking the best products to easily interface with Insteon and Zigbee networks.

[Michel Kohanim]

bwelsh, hello again:

 

I prefer not sending you a back-level code simply because it's back-leveled! You can use any program that can send SOAPMessages.

 

You can get the list of all of our WebServices, with descriptive comments, at http://isy.ip.address:port/WEB/UPNPSVC.XML . The most important service, to communicate with INSTEON or our other supported protocols (UPB, ZWave, NetStreams, NuVo, etc.), is

UDIService - takes a Control, Action, Node (all strings), a flag and turns on/off/dims/brightens/changes set point/heat cool/etc. The node can be either a scene (a group of devices) or a device

 

With UDIService, you can implement all operational aspects of any INSTEON/UPB/ZWave/etc. network. For configuration related aspects, obviously, you need to use our other services (such as RenameNode).

 

Here’s a summary:

1. Find ISY (UPnP or DPWS). Get the UPnP Description which defines the following two resources:

a. <__cu> element = Retrieve ISY's configuration (http://isy.ip.address:port/0/h) to figure out what are the Controls and permissible Actions thereto.

b. <__nu> element = Retrieve ISY's Nodes Configuration: http://isy.ip.address/WEB/NODESCNF. This file has the pertinent information about each Node which could either be a device or a scene. For devices/scenes, you'll have the type, name, address

4. Subscribe to either of or

5. Communicate using UDIService, addressed to , and using permissible values as deciphered in steps 1a. and 1b. above.

 

example:

 

1. Subscribe

SUBSCRIBE /0/e HTTP/1.1
Host: 192.168.0.203:64325
Content-Length: 732
Content-Type: text/xml; charset="utf-8"
CALLBACK:
NT:upnp:event
TIMEOUT:Second-infinite
SOAPACTION:"urn:udi-com:service:X_Insteon_Lighting_Service:1#Subscribe"

 

2. Turn on a device

POST /0/c HTTP/1.1
Host: 192.168.0.203:64325
Content-Length: 813
Content-Type: text/xml; charset="utf-8"
SOAPACTION:"urn:udi-com:service:X_Insteon_Lighting_Service:1#UDIService"


DON65531B 31 66 1

 

3. Turn off a scene

POST /0/c HTTP/1.1
Host: 192.168.0.203:64325
Content-Length: 806
Content-Type: text/xml; charset="utf-8"
SOAPACTION:"urn:udi-com:service:X_Insteon_Lighting_Service:1#UDIService"


DFOF417041

 

NOTE: flag == 4, therefore the request is for a scene OTHERWISE its for a node/device.

 

 

If you haven't yet, I certainly suggest reading the JSDK's documentation (ISY-JSDK-Manual.pdf which you can find here: http://forum.universal-devices.com/viewtopic.php?t=5). This document explains, in detail, the relationships between controls/actions/nodes which are essentially the same regardless of how you communicate with ISY.

 

With kind regards,

Michel

 

 

 

Hi Michel - I understand some of UPnPs limitations (specifically control via the internet), and DPWS is a good alternative.

 

What do you recommend?

1. Web Services via something like https://forge.soa4d.org/

2. UPnP via your older code

 

Either way, I'd need to know the ISY API. For each action, I'd need to know what each argument is for and what it's allowed values are. I might be able to figure out some of that from your older service file. Does UDI publish the ISY API? Or does UDI only support the JSDK?

 

No application yet. At this point I'm looking the best products to easily interface with Insteon and Zigbee networks.

[Mark Sanctuary]

Not to derail but why is the forum windows expanding way off the side of the screen all of a sudden?

[bwelsh]

Thanks, for those examples.