Change History
This document describes the main changes made for a certain release
Release 3.7 (December 2015)
- Support for ESP8266 based gateway
- Real-Time clock enabled in ESP8266 Gateway and supported in Arduino Gateway
- On every ESP8266 gateway you can log on to the local admin server at http://<ESP IP>:8080/config. It also allows setting the debug level and send simple LamPI messages to KlikAanklikUit devices
- The daemon support a config option as well to read status of ALL devices and sensors: Use http://<daemon-IP>:8080/config
Release 3.6.5 (November 2015)
- New version of ArduinoGateway supporting the Arduino Mega
- Realtime Clock support (DS3231)
- Support for Mega and RTC in LamPI-arduino.c on Raspberry
- Initial version of ArduinoPIR, infrared motion detection
Release 3.6 (October 2015)
- Solve critical bug in Action/Puls switch support for Arduino Gateway
- Solve bug to prevent error in LamPI-node.js when Z-Wave devices report values for a device not present in the config database
- Update Arduino Software LamPI-arduino.c to support several WT440 message types
- Update Arduino software, when BH1750 sensor not present the software will not output nonsense values
- Update LamPI-receiver.c to NOT support non-standard WT440 messages
- Update LamPI-node.js several bug fixes for sensors and reporting.
- Add support for DS3231 RTC (real time clock).
- Add support for the Quhwa / SelectPlus doorbell
- Added BH1750FVI sensor for Luminescense
- Changed the ~/scripts/PI-log script to work better without requiring restart of servers
- Documentation update for doorbell
Release 3.5 (August 2015)
- Make all I2C messages from sensors to the LamPI-nod.js daemon the same. The address contains the specific address for the sensor on the bus and the channel will contain the last byte of the IP address of the machine the sensor is on. Together they will make that sensors messages will always be unique.
- Add a configuration reporting function
- Make an init function for the LamPI-node daemon using either 'http://<Your IP>:8080/init' or start the daemon with '~/scripts/PI-node -i'
- Statistics of devices last seen, etc etc when using: 'http://<Your IP>:8080/config'
Release 3.4 (Juli 2015)
- All parameters that need configuring, including stuff like server IP adresses, MySQL server, Z-Wave, etc are in a configuration file (~/config/params.js) which is JSON encoded or so and be loaded quickly by the daemon. Parameters can be set as Enrironment variables as well in tfis file
- Made the tiles/metro interface (in beta)
- Added the touch-punch hack to make touch available on the standard LamPI jQueryUI interface on mobile devices.
- Added scene functionality to queue scenes in "~/LamPI-node.js"
- Added examples for rule sin the "~/config/database.cfg" file
- Improved ~/PI-install installer script, now also updating Wifi and MySQL settings
- Cleaned up (removed) old code pieces
- Shared Javascript code for LamPI-x.y.js, sensor.js, energy.js and rules.js is now in a "~/www/LamPIlib-3.4.js" library file.
- Updated printConfig() function in "~/LamPI-node.js" to show more devices and scene info
- Bug fixes:
- Corrected the Play scene function of the LamPI gui in "~/LamPI-node.js"
- Corrected small syntax error in rules engine "~/rules/rules.js"
Release 3.3 (July 2015)
- Added rules editor (Blockly) to start with "http://<your-IP>:8080/rules"
- Make LamPI start up even without Z-Wave gateway.
- Improved the Z-Wave gateway function to be more responsive
- Added functions "http://<your-IP>:8080/init" to re-read the "database.cfg" file and "http://<your-IP>:8080/config" to print out the configuration to the screen.
Release 3.2 (June 2015)
- Change the last sensors and energy webpages in "graphs" from PHP to node.js
- Make first steps in "rules" engine, with a blockly page on http://<server-IP/rules/index.html and support in LamPI-node.js
- Implement users. and login for external sites
- Changed all weather names and references to sensors
- Check compatibility of Raspberry 2.0 (OK)
- Implement new I2C sensors LM-75 and BMP180
Release 3.0 (May 2015)
- Change all PHP daemons and change to node.js
- Integration with Z-Wave so that manual operations on switches will be visible in the GUI and Z-Wave 100% managed same as Kaku devices
- Several bug fixes such as sorting Scenes
- Implement DeviceTree support
Release 2.8
- Add basic alarm function for sensors. Trigger in LamPI-gate.php and send to daemon who will do action as specified by LamPI-gate (Either display message on LamPI Gui or start a predefined scene in the system).
- Start rework for a LamPI-gate in node.js
- The /opt/z-way-server/automation/userModules directory now contanins first modules as intended by z-way. Given the rather high cpu-load, limited socket functions available etc. it remains to be seen whethe rthis is a better solution than building a separate gateway in either JS or PHP.
Release 2.7
- Added several pages including pictures to the documentation and worked on the structure
- Added .css support for the dialogs in askForm and myConfirm functions in LamPI
- Support for Cookies / localStorage to store username, password preferences on the local machine.
- Added localstorage support for skins. This means that skin setting will survive a page reload (because of the localStorage) without the skin being taken from the database upon reload. This allows users/sessions to have different skins.
- Define a scaling css template. These templates are in the styles directory and start with the "scale-" in front of their name
Release 2.6
- Added a health indicator in the header area. The color of this little bar indicates the health of the client-daemon communication
- Solved a bug in ALL OFF command for a room. Since the id (used in the GUI) and the unit number used in the daemon might differ we need to make sure that ALL OFF command works as expected (on unit number).
- Changed the CSS system significantly. Templates are now available in scss-styles directory that can be used together with tools like "koala" to build new Look and Feel in a matter of minutes.
- Display the current skin in the "skin settings" dialog, and make the current skin the default option in the drop-down menu
last updated: November 12, 2015