News and announcements

Description

For news and announcements to the HAH community at large.

Fixed errors in xaplib2 and the iServer components.

xaplib2

Modifications to be fully compliant with xap wildcard filter addressing. There was an error in handling the > symbol.  For example: dbzoo.livebox.>:relay.* would erroneous be treated as the broader filter  dbzoo.livebox.> and would match the subaddress component.

As this is a xaplib2 modification every application on the HAH was affected by this bug.

Fully compare target and wildcard addresses.

Class wildcard based filtering to support iServer clients that use this.

iServer

  • This is an internal protocol modification.  Handling of filter delete  <flt-> and <cflt-> tokens was added.  The tokens </flt-> </cflt-> </flt+> </cflt+> are now handled although not present in the xAPFlash protocol its best they are handled for orthagonality.
  • Malformed packets could crash the iServer this was most notible using the netiom.
  • no xap-hbeat or xap-header and a disconnecting client will SEGV iserver
  • quickly cycling a client up/down can crash the iserver

Are you keeping up with all these updates?  These are a few more improvements to the iServer.

  • status display for each client registered with the iServer is shown on the web iServer tab
  • iServer listens on port 78 for HTTP requests so you can point you web browser at this port and directly get the status results too.  Might be useful if you want to include this in another  web page you have elsewhere.

http://www.dbzoo.com/livebox/iserver

A few more iServer tweaks

  1. Handling of messages over multiple TCP fragments
  2. Pacing (I'd coded microseconds instead of millseconds)
  3. Internal statistics held for web server page (work in progress)

Anybody else noticed their pachube feed frozen?  Mine had.  Investigating I found an issue in the xaplib2 filter calls which since release 253-255 had been working.  Weird.  I don't think I changed anything in 256 that would affect it.  Anyway I've fixed it.

This release includes an iServer allowing the xapFlash application that runs on the Joggler to use the HAH as a TCP/xAP gateway.  So no need to keep a Windows machine running just as a gateway anymore!

The gateway has had reasonable testing but there is nothing like getting it out there to iron out the wrinkles.

Minors fixes:

  • xap-serial memory leak
  • xap-googlecal - segv when using a password from the command line
  • displaytext= tag malformed for xap-livebox 1wire events
  • xAP Parser improvement

Fix SEGV when xAP messages have > 50 key/value pairs.  Limit increased to 150, when limit is reach it will reset to index 0 and start overwritting the header (with a debug notice if this happens).  80 keys is about 1300 bytes so you'd be pushed to get to 150 within 1500 bytes anyway.

This is a hotfix release to fix a couple of issues.

r139    
 
r138    
r137
r136  
r135

Due to a broadcast compatibility problem with iServer, Joggler integration was broken.  This release fixes that issue until the iServer uses a SUBNET based broadcast.

 This release has been >2 months in the making since release 252. There are some major new capabilities that will support additional hardware add-ons.

Upgrading:

 

Make a backup of your /etc/xap-livebox.ini file, preferably not on the HAH itself.

Run /etc/init.d/update 

 The HAH platform has historically relied upon existing code that parsed xAP messages. Some of this wasn’t optimal. Release 253 has replaced almost ALL of this legacy code. The new infrastructure is known as ‘xaplib2’.

This new xaplib2 library, although invisible to users, greatly enhances the stability and maintenance of the HAH system.  Applications that use this library have a faster xAP parser and a smaller memory footprint than those using the original xaplib. They also take up less flash space due to higher shared library reuse.  Debug capability has also been greatly improved.
 
These programs were all rewritten to use xaplib2, in addition to the noted enhancements:

  • xap-snoop - Added message filtering support and new command line options.
  • xap-serial  (NEW) - Allows easy integration with any serial device.
  • xap-currentcost - Full xAPBSC support, Current Cost generation 1 support, external sensor support; IAM’s and standalone development boards.  Endpoint UID stabilisation.  Command line option for setting the model when ran manually.
  • xap-googlecal - Added “where=” to the schema to allow events to be scheduled that trigger other events.  Errors emitted as xAP messages. Sanity check the system clock on authentication error for SSL problem.   INI file password frob (note: this is not ‘encryption’).
  • xap-pachube - Support for logging non xAPBSC events.
  • xap-hub - Faster, smaller, a heartbeat,  host IP encoded into its endpoint name making the HAH easier to find.
  • xap-sms - Errors emitted as xAP messages.
  • xap-twitter - Now supports the new OAuth authentication model  
  • xap-livebox - Endpoint UID stabilisation.

Programs still using the old xaplib:

  • xap-plugboard - Modified to honour single HAH instance setting
  • xap-bridge - Modified to honour single HAH instance setting

These will be uplifted in the next release.

Web changes

  • new Automation>Assists tab to start xap-sms, xap-serial and xap-plugboard
  • new Admin>Instance tab to make multiple HAH systems easier to setup.
  • Option to disable the login page for networks that don’t require it.
  • Pachube GUI page changes to support non xAPBSC events.
  • Title change to Home Automation Hub


Numerous bug fixes and stability improvements.

Due to a change in the way in which the Ethernet bridge is setup, after flashing, your HAH will acquire a new IP address so don’t be alarmed if you can’t find it.  Use xFxViewer to see its IP is emitted by the xap-hub component.

To upgrade your .INI file to handle the new Pachube format perform the following.

/etc/init.d/xap stop

/etc_ro_fs/upgrade

/etc/init.d/xap start

Just to keep things lively I've added Gravatar / User Image support.

If you already have a gravatar associated with the email address you used to register here then your image will automatically appear on posting.  If not either

  1. Get yourself a gravatar account.
  2. OR upload an image to your profile.

Brett