Developer Documentation and getting up to speed

I’ve just started getting into Vera again after looking a number of years ago. Things some much better and more organized now and I hope that I will quickly get past the static friciton of getting started. So will risk what, I hope, are teething questions. My goal is to move quickly from SmartThings to local control

I?ve been looking at the micasaverde wiki and forum and while there is a lot of discussion and examples there isn?t any reference documentation that I can find. I can figure things out once I have effective documentation.

I want to do the simplest of simplest and turn on a light yet when I say
http://192.55.226.189:3480/data_request?id=action&DeviceNum=1&serviceId=urn:upnp-org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=1

I get
ERROR: ERROR: The requested service cannot be performed, because it is not a recognizable Z-Wave command.

How do I just turn on a light for device 1?

Question I may find the answer to when experimenting – is there support for cross-domain scripting so I can issue the http requests from a browser app?

Also I want to be able to get notifications of changes. If I have a simple sample of LUA code that can send a message over TCP or, better, use Websockets, I can work to generalize it.

It would be nice to have support of mDNS so I can find the server by name rather than the MAC address on the LAN.

[BTW, in the verification question having to cite Newton as using the Apple to prove gravity is painful in that it’s a story for children - the right answer is his calculus]

I highly doubt that your device number is 1 as it is reserved to the zwave chip. You might want to check what the device number of your device really is.

It took me a bit to figure out where to get my device number. Click on your device then click Advanced. It’s listed in the header, “device #48” and it’s listed under “id”.

I took your query string and put my office light’s id in there and it turned off my light.

I keep the URL below open in a separate tab, I refer to it so much. It lists all of your scenes and devices in short form:

[tt]http://your-vera-local-ip:3480/data_request?id=sdata&output_format=xml[/tt]

The resulting XML format is very readable in Chrome and Firefox. I can’t speak to the results with other browsers.

For your devices, the “id” is the Vera device number (which is almost always the number you want), and the “altid” is a special identifier that is type-specific (e.g. for Z-Wave devices it’s the Z-Wave node number in the network).

[quote=“rigpapa, post:4, topic:197858”]I keep the URL below open in a separate tab, I refer to it so much. It lists all of your scenes and devices in short form:

[tt]http://your-vera-local-ip:3480/data_request?id=sdata&output_format=xml[/tt]

The resulting XML format is very readable in Chrome and Firefox. I can’t speak to the results with other browsers.

For your devices, the “id” is the Vera device number (which is almost always the number you want), and the “altid” is a special identifier that is type-specific (e.g. for Z-Wave devices it’s the Z-Wave node number in the network).[/quote]

That url is very helpful indeed. Do you what other query strings are supported?

There’s some documentation from Vera on that, link here:

http://wiki.micasaverde.com/index.php/Luup_Requests