short question, is there a list of the aviable commands and the possible responses avaiable somehow ?
i would like to get startet with some external stuff
I am not sure this is what you are looking for …
http://wiki.micasaverde.com/index.php/Luup_Requests
There is a lot of information on the Wiki … not always easy to find … Search is your friend!
yeah that was it prety much, but i doubt it holds all parameters and options.
but its a good way to get startet.
a white-paper or somethings like that would be great.
but this will get me startet for sure.
Thanks
Another vote for this - I’m currently writing a library to abstract out the communication over HTTP (It’s a PHP library if anybody is interested, I’ll shout the code repository later when it’s more stable) and it’d be great to have a more definitive list of just what’s possible over the interface.
nullx8, don’t expect any more than that wiki page. It looks complete to me.
Perhaps if you were more specific about what you wanted to do, we could be more specific about how you could achieve it.
Things like where it says “Not all requests support all [tt]output_format[/tt] options” it would be nice to have information on which outputs are actually supported by which requests. It’d also be really nice to have examples of the output - I’d happily add some myself, but can’t edit anything (doesn’t that kinda defeat the purpose of a wiki?).
Similarly, in running an ‘action’ (as in [tt]?id=action[/tt]) is there a predefined list of available actions (as in [tt]?action=[/tt]) and their subsequent extra query parameters (as in [tt]?newLoadLevelTarget=[/tt], [tt]?&newTargetValue=[/tt] and [tt]?SceneNum=[/tt])?
You need to look around on the wiki. Yes, it is not the most organized, but the answers you are looking for are there:
http://wiki.micasaverde.com/index.php/Luup_Devices
- Garrett
Similarly, in running an 'action' (as in ?id=action) is there a predefined list of available actions (as in ?action=) and their subsequent extra query parameters (as in ?newLoadLevelTarget=, ?&newTargetValue= and ?SceneNum=)
The Actions are defined by a particular device type … as the creator of a plugin I can create my own actions … and the arguments associated with them.
This is a growing list … There are plenty of examples for the basic device types.
If you want to get a feel for what actions are available … create a scene … go to the advanced tab and add some device type … it will show you the actions that device supports.
[hr]
For a general understanding of development concepts I would recommend the following Wiki Page:
http://wiki.micasaverde.com/index.php/Category:Development
I would browse the contents of various referenced pages from there.
well i dont really know what exactly i want to do yet 
generally i want to use my own php driven controls, since the Vera wont be the center of my little universe.
in matters of taking actions … my internal Websites would do this in a very basic way so even peoples without any knowledge can use it.
like my appletv xbmc asterisk PBX even my car plays a role
in matters of displaying informations … my internal website, public website and a xbmc plugin i am about to develop.
as example i want to combine the Vehicle Tracking in my car doing things “on arrivial” and doing things “if away” … that sort of things …
okay the most actions will have vera-defined triggers “scenes” and they are quite straight forward as far i can see.
my mark was more on “actions” and “lu_actions”
there seems to be a wide range of sub-commands aviabale (hopefully there are)
some of them explaining themselfs, but it would be alot more easy to get to know the commands and subcommands avaiable.
A noble cause. Essentially you will be creating a remote control device in the vein of AutHomation or HomeWave, only it will run in PHP under your web server rather than on a mobile device.
I recommend this page, which explains how you make your own remote: http://wiki.micasaverde.com/index.php/UI_Simple
As Richard said, the actions are not enumerated on the wiki because they depend entirely on the device in question.