Brad
unread,Feb 22, 2011, 11:21:54 PM2/22/11Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to domuslink-...@googlegroups.com
I have uploaded domus.Link2.0beta7 which includes the following:
* Issue 52 enhancement - Added a REST API for domus.Link to have applications be able to create other
applications that can talk directly to the domus.Link core. This will allow
creation of other types of UI's (native mobile, AJAX) or allow external
applications to use the domus.Link core to control heyu. This currently
only encompasses return of the floorplan and aliases and then providing
control to the aliases of on/off/dim/bright. Please refer to the document
DomusRestAPI.doc in the /doc directory.
* Issue 46 fixed - When creating an alias with spaces in the name, domus.Link
did not create a sanitized name with lowercase and underscores.
* Issue 51 fixed - CN17A commands for on/off were not being properly handled.
* Changed the way dimming is handled to correctly set based on request. There
is a new method to handle dimming in 0-100 percent terms with the corrected
calculation of if the device is on or off. This is now called by the legacy
method dim_bright.
* Issue 35 enhancement - Support for RCS TXB16. This is basic control of the RCS
thermostat. This also assumes default decode table of P.
* Issue 21 fixed - Objectified Triggers
* Issue 22 fixed - Objectified Macros
* Issue 8 fixed - domus.Link now removes the password and security level from the
frontend configuration and now allows the use of users or PINs to have multiple
logins with different access.
username/password || PIN is always required, currently there is a "no security"
setting and we will have to do away with that.
These are tied to a security level -
0 = admin level - all access
1 = macro/timer/trigger, start/stop and upload access
2 = allow starting of heyu but not stop and control of any aliases
3 - n = assignable to aliases and then limits control based on login.
The setting levels can be exact matches or greater than matches to further limit
control.
On first start of this version, the system will create a default admin user and
pin with pass '1234'. Please change the passwords to something better.
* Issue 1 fixed - stabilized iPhone theme. Removed references to any setup functions.
Also, updated iPhone theme to be compatible with new security and groupings
behavior. Changed iui library to be the base 0.31 native without modifications.
This will allow the path for domus.Link to be anything and will be found.
This fix also implements the auto detection properly for iPhone, iPad, iTouch, Android
for the theme. Since this noew works properly, I have taken the selection for the
whole fronend gui for iPhone and put into it's own config as Mobile Theme. This
will prevent using the iPhone theme as your normal browser theme but the iPhone
theme does not have any domus.Link configuration ability now due to the new
complex configuration items that have been added.
* Issue 17 fixed - Added a module of type status that does not have control and only
reflects the state of the module as on or off.
* Issue 36 and Issue 32 fixed - Added the ability to configure custom groups for the main
menu title bar. Also allow the switching from the domus.Link default menu by types to the
new groups and back. The menu is now dynamic and only displays menu groups that are visible
and have accessible modules in them. If there are no modules in a group, the menu item is not
displayed. If the menu group does not contain any accessible modules for the login access
level, that menu group will not be displayed. Groups can also set their visibility explicitly.
This should allow a multitude of display configurations by group/user/pin.
* Issue 50 added - A native Android application is created to use the new RESTAPI.
This is about as much as I believe should be included and is a pretty major upgrade. The default UI is now much more flexible and with the addition of security much more configurable.
Let's test it and see if we can get this released.
Oh, I took a lot of liberties with the iPhone theme and it it pretty stable. We will need to abandon IUI as it is not maintained much and Frank was looking in the direction of webkit. Which is a better idea.
Have fun!
Brad