Sneak-peek version 2.3.0

[dannybloe]

Hiya folks,

We (me and jvandenbroek) are currently finalizing 2.3.0. As soon as it is ready for testing we probably give a link to a test branch or something like that.

Just to give you an idea of what's coming:

[2.3.0]

• Fixed a problem where if you have two scripts for a device and one script uses the name and the other uses the id as trigger, the id-based script wasn't executed.
• Added active to devices (more logical naming than bState). myDevice.active is true or false depending on a set of known state values (like On, Off, Open, Closed etc).
• Added simple urlEncode method on the Domoticz object so you can prepare a string before using it in openURL().
• Updating text from dzVents in a text-device now triggers the event system.
• Added adapter for the new Temperature+Barometer device.
• Added support for groups and scenes change events. Use "on = { scenes = { 'myScene1', 'myScene2' }, groups = {'myGroup1'} }"
• Added method backupDatabase(path) to the domoticz object. Now you can create your own (timer) scripts to create database backups.
• Added domoticz.startTime giving you the time at which the Domoticz service was started.
• Added the lua Lodash library (http://axmat.github.io/lodash.lua, MIT license).
• Fixed documentation about levelNames for selector switches and added the missing levelName.
• Added silent argument (boolean) to device.switchOn() and device.switchOff() commands. When set to true, no follow-up events are triggered switching the device. Using switchOn(true) will not allow you to set timing options!
• Moved dzVents runtime code away from the /path/to/domoticz/scripts/dzVents folder as this scripts folder contains user stuff.
• Added more trigger examples in the documentation.
• active setion is now optional. If you don't specify an active = true/false then true is assumed (script is active). Handy for when you use Domoticz' internal script editor as it has its own way of activating and deactivating scripts.

One interesting item is support for scene- and group-change events. Now you don't have to use dummy switches to have scripts triggered when switching scenes and groups. So you can now directly link an event script to a zwave scene actuator for instance. So let's say you have a zwave dimmer where the S2-switch triggers a scene in Domoticz. You can then write an event script for that scene. That way you can create much more complex scenes than just switching some lights. Or create an empty scene in Domoticz and do everything for that scene in a dzVents script.