1.1.1 is released.
It's a patch on 1.1.0, adding:
* Mongodb 2.0.1 (to fix an issue with 32-bit systems where the database wouldn't start)
If you are running fine with 1.1.0, there is little reason to upgrade to 1.1.1. We did provide a 1.1.0-1.1.1 upgrade path though, so users can all be on a common database version.
If you have already upgraded to 1.1.0, and are having trouble starting, you can manually install the updated mongod binary:
* download and unzip:
mongodb-win32-i386-2.0.1.zip* copy the mongod.exe to your <mFi>/bin/
* start mfi (after killing java process if needed)
If you are running your own mongod (such as in Linux), you need to have at least mongod 2.0.1 to run mFi 1.1.0 and higher
Downloads
mFi Controller for Mac [url]mFi Controller for Windows[/url]
Release Notes
Official mPower support.
Support for automation (Rule Tab).
Support for scheduling.
Support for action timer on outputs/outlets.
Support for condition sets. This provides nested and/or rules.
mPower outlets are shown on map now.
Cloud support: mfi.ubnt.com
Speed up device adoption process.
Real-time sensor state is pushed to UI.
Java 7 support.
More robust custom sensor support.
Limitations and known issues
32 bit systems are not recommended - they are limited to 2GB of data
To avoid issues with the gatekeeper function on Mac OSX Mountain Lion, either disable it, or ‘right click’ on the mFi application to launch.
The absolute value of an mPower outlet’s accumulation of energy does not get cleared when configuring a new outlet.
If you have plugged an appliance into an unconfigured outlet, the energy usage will accumulate. If you subsequently assign this outlet to a new appliance, this accumulated data will not be cleared. Power cycling the mPower is the only way to clear accumulated energy with 1.1.0. This should not affect operation, since normally users only care about changes in accumulated energy (energy meters count upward forever, and never reset)
mPower will not detect power under 3W.
mPort serial antenna selection is currently stored under the serial device configuration. In the future the antenna selection will be moved to the mPort serial configuration. Currently, if you reassign the serial sensor to another mPort, the antenna selection may be changed for the new mPort.
No static IP & SNMP support.
When using Mac OSX Lion or Mountain Lion to connect to the mPower Wi-Fi captive portal, the captive portal dialog popup window that automatically appears might temporarily disappear, and then reappear.
The default port numbers were changed from 9080 and 9443, to 6080 and 6443. (The port numbers can be changed in the <mFi>/data/system.properties file.)
Cloud:
No custom sensor support in the cloud yet.
To use mPort Serial in the cloud, holes must be punched in any firewalls for TCP port 2323 since the controller users that port for serial data. And public IP addresses, or port forwarding, must be used for the mPort Serial. (it is expected that most mPort Serial users will use local standalone controllers)
