[Shoop_NL]

Shoop,
I suggested this before but maybe I was not clear on the method and use cases.

For systems that use HTTP, if you expose the http command mapping to the end-user, then users can create configs on their own and share them with others - lessening your load and allowing for end-user customizations for specific setups.

Suggested Method:

• Separate mapping file (links specific http commands to script objects/commands) for each system
  
• Script's config file defines which mapping file it reads in - this is a similar concept that the Addons have with addon.xml file (being that it tell XBMC what to do).
  
• Upon launch, your script loads the selected mapping file
  

Example file set:

• config.xml = holds core script config, points to mapping file
  
• map_homeseer = http mapping
  
• map_tellstick = http mapping
  
• ...etc
  

I also suggest the same basic method for the Event definitions, this way there is the potential for users to create/share custom events.

This is pretty intresting stuff, I will try to find some time to figure this out.
It makes the system way more flexible and save's me a lot of time programming the core for all these different systems.