Welcome to this new OpenRemote community forum.
Today we released the first milestone of the OpenRemote version 3 series. The main project is or-controller, you can find the code on Github: https://github.com/openremote/or-controller
This is still very early code, only suitable for development and testing.
So for the second milestone we have a few priority items to work on:
Creating an iOS project and re-using as much code from the or-shared project as possible. This Java code has been written vor Java 1.7 and should be cross-compilable to iOS with j2objc. On top of this we have to build the UI layer with native iOS frameworks, for a great user experience. We are trying to share and cross-compile Java code between platforms, instead of a less sophisticated hybrid mobile application strategy (we use mobile WebViews internally to render the OpenRemote panel console).
Work on IoT core functionality: We need a Context Broker in OpenRemote v3. The old broker (called StatusCache) in v2 was really an internal element and we should expose the context/current state of the system as a proper service. We have been looking at the Fiware context broker Orion (http://fiware-orion.readthedocs.org/) and so far like the dynamic model and API.
We have only just started on Protocol Adapters and Flow Components in v3. Our new integration framework is Apache Camel, so protocol adapters are Camel components with some metadata to make them easier to manage in OpenRemote. Some protocols we want to have our own adapters for are KNX, BLE, Philips Hue, Nest, and Belkin Wemo. Flow event processors also touch the Camel API, and flow widgets have a Web Component (Shadow DOM, etc.) HTML5 user interface. One particular flow widget we want to work on soon is a flexible Map/GIS component based on OpenStreetMap.
This is an exciting time for OpenRemote and we invite you to join us in this effort.