enebular Release Notes
Latest Release - 2.5.1 (October 12th, 2018)
New
- Forking an asset from Discover page now automatically opens the forked asset
- Candidates for InfoType keys and values are now shown on a drop-down list as you type when configuring it for PubNub or Firebase data sources
- InfoType name can be specified when uploading it
Fixed
- A preventive measure is taken to avoid multiple users from opening one flow on a flow editor.
- We have found whitespaces in two locations are missing from use case pages in the English documentation.
Changed
N/A
Known Issues
- Opening the flow editor from a web browser shows Japanese texts even if the browser is configured to show English
- The shared page with InfoMotion embedded, the filter function can not be used
Release History
- 2.5.1 (October 12th, 2018)
- 2.5.0 (September 25th, 2018)
- 2.4.4 (September 7th, 2018)
- 2.4.3 (August 20th, 2018)
- 2.4.2 (August 10th, 2018)
- 2.4.1 (August 3rd, 2018)
- 2.4.0 (July 19th, 2018)
- 2.3.1 (July 11th, 2018)
- 2.3.0 (July 6th, 2018)
- 2.2.1 (June 7th, 2018)
- 2.2.0 (May 23rd, 2018)
- 2.1.2 (April 16th, 2018)
- 2.1.1 (April 3rd, 2018)
- 2.1.0 (March 30th, 2018)
- 2.0.1 (March 1st, 2018)
- 2.0.0 (Jan 30th, 2018)
enebular agent Release Notes
2.2.0
New
- Added a one-step install script for quick and easy setup of enebular-agent
- Added a tool to support simple AWS IoT Thing creation and setup
- Added ability to do simple startup registration to have enebular-agent start at boot-time on Debian (systemd) based systems
- Added ability to list all supported configuration options
- Added support for command line options in order to allow use of the new configuration options and subcommands
Fixed
- Fixed an issue that caused enebular to report the connection status of AWS-IoT-connected enebular agent as "Connected" regardless of the actual connection status of the agent.
- Minor fix to enebular logging upload size handling
- mbed-cloud-connector
- Add missing files that prevented it from being built
- Removed invalid characters from readme
Changed
- Updated the Node-RED version to 0.18.x
- Updates to allow better connection status tracking on AWS IoT
- Improved daemon usage support (syslog logging and process termination support)
- Improved process management (startup and shutdown) of the Node-RED instance
- Added quick setup explanation and further manual setup details to the readme files
- Added integration tests
Known Issues
N/A
Recommended Hardware
The recommended hardware is as follows.
- Raspberry PI3 Model B
Operating Environment
The recommended operating environments are as follows.
Raspberry PI3 Model B
Raspbian Stretch base (9.0)
- nodejs 8.9.0
- npm 5.5.1
- node-red 0.17.5
Raspbian Jessie base (8.0)
- nodejs 8.9.0
- npm 5.5.1
- node-red 0.17.5
Linux (VirtualBox)
Debian Jessie (8.9)
- nodejs 9.2.0
- npm 5.5.1
- node-red 0.17.5
Debian Stretch (9.1)
- nodejs 9.2.1
- npm 5.6.0
- node-red 0.17.5
Release History
enebular edge agent Release Notes
Latest Release - 1.0.1 (June 7th, 2018)
In 1.0.1 release, Updated Mbed Cloud Client to 1.3.1.1 General Availability (GA).
New
N/A
Fixed
- Network disconnected when running an agent for an extended period of time. This was due to the Wi-Fi module taking full control of the communication processing. Issue solved by updating Wi-Fi module's library.
Changed
- Updated Mbed Cloud Client to 1.3.1.1 General Availability (GA)
Known Issues
- A BME280 node may not operate correctly if the flow size is too large.
- An inject node can set only a Timestamp for the Payload and Repetition of the Interval.
Operating Environment
Operating System
- Mbed OS 5.8.2 (ARM Ltd.)
Hardware
The following hardware is supported in enebular-edge-agent 1.0.1.
- FRDM-K64F (NXP Semiconductors N.V.) + Stag Beetle Board (Uhuru Corporation)
Communication
- IEEE 802.11 b/g/n (only 2.4GHz is supported for IEEE 802.11n)
- WPA/WPA2