*WSO2 IoT Server 1.0.0 Alpha Released*
We are pleased to announce WSO2 IoT Server 1.0.0 alpha release. It can be
downloaded from
https://github.com/wso2/product-iots/releases/tag/v1.0.0-alpha
WSO2 IoT Server is an extensible, open-source, multi tenant, Internet of
Things Platform for implementing server-side of IoT Reference Architecture.
It comes with a reference implementations for the device layer.
WSO2 IoT Server supports:
-
Device Management
-
Extensions for registering device types
-
Self-service enrolment and management of connected devices
-
Group, manage and monitor connected devices
-
Share device operations / data with other users
-
Distribution and management of applications and firmware to devices
-
OOTB support for some known device types such as Raspberry Pi,
Arduino Uno, Android
-
IoT Protocol Support
-
Leverage MQTT, HTTP, Websockets and XMPP protocols for device
communications with IoT Server
-
Framework extension for adding more protocols and data formats
-
Analytics
-
Support for batch, interactive, real-time and predictive analytics
through WSO2 DAS
-
Pre-built visualisation support for sensor readings
-
View instant, visualised statistics of individual or multiple devices
-
Traverse through, analyse and zoom in/out of filtered data
-
Stats-API to write your own visualisation
-
Pre-built graphs for common sensor reading types like temperature,
velocity
-
API Management for App Development
-
Devices are represented as REST APIs
-
Develop applications using Device APIs
-
Identity and Access Management
-
Identity Management for devices
-
Token based access control for devices & operations (protect back end
services via exposing device type APIs)
- Support for SCEP protocol (encryption and authenticity)
List of known issues
- https://wso2.org/jira/issues/?filter=13055
Bug Fixes
- [IOTS-17 <https://wso2.org/jira/browse/IOTS-17>] - MQTT endpoints are
not secured for agent communication
- [IOTS-19 <https://wso2.org/jira/browse/IOTS-19>] - XMPP sessions not
closed before server shutdown
- [IOTS-21 <https://wso2.org/jira/browse/IOTS-21>] - Jaggery API calls
are not secured
- [IOTS-34 <https://wso2.org/jira/browse/IOTS-34>] - Backend Service
Invoker Fails Intermittently with Unexpected token: <
- [IOTS-37 <https://wso2.org/jira/browse/IOTS-37>] - Could not generate
a new access token (using refresh token) by using the current token endpoint
- [IOTS-47 <https://wso2.org/jira/browse/IOTS-47>] - Update the release
note in the release packs as it is about EMM
- [IOTS-50 <https://wso2.org/jira/browse/IOTS-50>] - users whos
iot-admin role is removed is shown all options for enrol devices as users
with iot-admin role
- [IOTS-55 <https://wso2.org/jira/browse/IOTS-55>] - Considerable delay
in server startup
- [IOTS-57 <https://wso2.org/jira/browse/IOTS-57>] - Error when starting
the IOT pack after pointing to the mysql database
- [IOTS-64 <https://wso2.org/jira/browse/IOTS-64>] - The wso2carbon log
file is growing rapidly
- [IOTS-68 <https://wso2.org/jira/browse/IOTS-68>] - when a tenant is
created with the same user name as super tenant seems the super tenant data
are shown
- [IOTS-69 <https://wso2.org/jira/browse/IOTS-69>] - until device admin
was disabled the camera policy was in effect preventing the use of camera
on android device
- [IOTS-75 <https://wso2.org/jira/browse/IOTS-75>] - view API throws a
Caused by: java.lang.NullPointerException: Tenant domain has not been set
in CarbonContext
- [IOTS-81 <https://wso2.org/jira/browse/IOTS-81>] - IOT devices are
allways in active status
- [IOTS-92 <https://wso2.org/jira/browse/IOTS-92>] - Error in executing
task: Table Not Found: X1234_DeviceBatterySummaryData
java.lang.RuntimeException: Table Not Found: X1234_DeviceBatterySummaryData
is thown when pointing to mysql
- [IOTS-93 <https://wso2.org/jira/browse/IOTS-93>] - XMPP server details
are hardcoded in virtual fire alarm and devicemgt-config.xml file
- [IOTS-94 <https://wso2.org/jira/browse/IOTS-94>] - Virtual firealarms
that were downloaded before xmpp was enabled can not connect to xmpp
protocol after enabling.
- [IOTS-100 <https://wso2.org/jira/browse/IOTS-100>] - When integrating
ActiveMQ as an external message broker IOTS fails to start
- [IOTS-102 <https://wso2.org/jira/browse/IOTS-102>] - Device analytic
line graph does not get generated when the device type has a capital letter
- [IOTS-104 <https://wso2.org/jira/browse/IOTS-104>] - Remove the device
type configs that is used for UI from conf directory
- [IOTS-105 <https://wso2.org/jira/browse/IOTS-105>] - clean unnecessary
jaggery apis
- [IOTS-106 <https://wso2.org/jira/browse/IOTS-106>] - A emm console url
is shown in carbon log at server startup
- [IOTS-110 <https://wso2.org/jira/browse/IOTS-110>] - No email
confirmation is sent to user when administrator creates a user
- [IOTS-112 <https://wso2.org/jira/browse/IOTS-112>] - A prefix as "
Device " is set to the devices that is been created
- [IOTS-114 <https://wso2.org/jira/browse/IOTS-114>] - Change Role
permissions: the user is unable to deselect a child node
- [IOTS-117 <https://wso2.org/jira/browse/IOTS-117>] - Edit/ create
Role: Domain needs to be marked as a mandatory field
- [IOTS-122 <https://wso2.org/jira/browse/IOTS-122>] - Tenant - admin
cannot enroll to virtual fire alarm, raspberry pi & arduino
- [IOTS-124 <https://wso2.org/jira/browse/IOTS-124>] - Group: View
analytics loads an error
- [IOTS-127 <https://wso2.org/jira/browse/IOTS-127>] - Admin cannot
reset user passwords
- [IOTS-129 <https://wso2.org/jira/browse/IOTS-129>] - If devicemgt-user
role is deleted users cannot register
- [IOTS-130 <https://wso2.org/jira/browse/IOTS-130>] - The line graph is
not generated correctly for virtual firealarm
- [IOTS-131 <https://wso2.org/jira/browse/IOTS-131>] - Publishing stats
via MQTT protocol to iot server fails
- [IOTS-134 <https://wso2.org/jira/browse/IOTS-134>] - Server startup
fails when configured to use MySQL
- [IOTS-136 <https://wso2.org/jira/browse/IOTS-136>] - User signup for
tenant is not supported
- [IOTS-150 <https://wso2.org/jira/browse/IOTS-150>] - Arduino sample is
not getting proper responses
- [IOTS-151 <https://wso2.org/jira/browse/IOTS-151>] - Server startup
fails when configured to use Oracle
- [IOTS-152 <https://wso2.org/jira/browse/IOTS-152>] - Platform
Configuration display android, iOS and windows Configuration
- [IOTS-153 <https://wso2.org/jira/browse/IOTS-153>] - Error is thrown
when accessing device API details page
- [IOTS-154 <https://wso2.org/jira/browse/IOTS-154>] - Typo
/enrollmentdevicesg/download for raspberypi (g)
- [IOTS-155 <https://wso2.org/jira/browse/IOTS-155>] - When browsing
analytics error 500 shown to user from a group which has no devices assigned
- [IOTS-156 <https://wso2.org/jira/browse/IOTS-156>] - 404 page when
cancel clicked in "Add New Group" page
- [IOTS-157 <https://wso2.org/jira/browse/IOTS-157>] - Signed up users
shown an error page when navigated to policy page
- [IOTS-158 <https://wso2.org/jira/browse/IOTS-158>] - Signed up users
cannot create policies
- [IOTS-159 <https://wso2.org/jira/browse/IOTS-159>] - Meaningful
message to be shown when On / Off issued to virtual fire alarm
- [IOTS-161 <https://wso2.org/jira/browse/IOTS-161>] - Remove the phrase
"Below QR code can also be used to enroll a device"
- [IOTS-163 <https://wso2.org/jira/browse/IOTS-163>] - Android sensor:
only admin can login to the app
- [IOTS-164 <https://wso2.org/jira/browse/IOTS-164>] - When an existing
user name is used by admin no proper validation message shown
- [IOTS-165 <https://wso2.org/jira/browse/IOTS-165>] - Server startup
throws "The following exception occurred when fetching
http://www.google-analytics.com/urchin";
- [IOTS-166 <https://wso2.org/jira/browse/IOTS-166>] - Connected cup
device analytics is failing to load
- [IOTS-167 <https://wso2.org/jira/browse/IOTS-167>] - Considerable
delay is taken to initialize transports for device types
*How To Contribute*
You can find more instructions on how to contribute on our documentation
site <https://docs.wso2.com/display/IoTS100/WSO2+IoT+Server>.
If you have any suggestions or are interested in discussions, you can join
the [email protected] or [email protected] lists.
*Reporting Problems*
We encourage you to report issues, improvements and feature requests
regarding WSO2IOT through the public WSO2 IoT JIRA
<https://wso2.org/jira/browse/IOTS>
*Contact us*
WSO2 developers can be contacted via the mailing list: Carbon developer
mailing list
For details on subscriptions see http://wso2.org/mail
Thanks and Regards,
*~ EMM / IoTS Team ~*
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
