Edge Xpert 2.0
Edge Xpert 2.0 is based on the open source EdgeX Foundry version 2.0 release, codenamed "Ireland".
EdgeX Ireland Features
- Brand new “V2” APIs with all new REST endpoints using improved model objects (for request and responses) and improved API URIs
- Internal message bus communication between Device Services and Application Services (Core Data can also subscribe to sensor readings or be removed if persistence is not necessary)
- Improved security to include enabling the Consul API through the API Gateway
- Simplified device profiles
See the EdgeX Ireland release page for more details.
Additional Edge Xpert Features and Enhancements
- Brand new Edge Xpert Manager UI with many key advantages from previous versions. Features include a dashboard view, device onboarding menus for all support device services and capability to start, stop and restart application services from the UI
- S7 Device Service performance enhancements including multi-block read and write capability
Release Changelog
2.0.6
Edge Xpert CLI
New Features
- Added GPS Device Service
device-gps
Edge Xpert Device Services
GPS Device Service
New Features
- GPS Device Service added to Edge Xpert
S7 Device Service
New Features
- Enabled data source timestamp feature
Edge Xpert Microservices
New Features
- Added security settings for GPS Device Service
2.0.5
Edge Xpert Device Services
BACnet Device Service
Bug Fixes
- Fixed duplicated data transformation and upgraded the XRT version
Modbus Device Service
Bug Fixes
- Fixed duplicated data transformation and upgraded the XRT version
OPC-UA Device Service
Bug Fixes
- Fixed duplicated data transformation and upgraded the XRT version
REST Device Service
Enhancements
- Predefined device configuration updates
S7 Device Service
Bug Fixes
- Fixed duplicated data transformation and upgraded the XRT version
2.0.4
Edge Xpert CLI
New Features
device-s7
entry added to docker-compose files
Edge Xpert Manager
New Features
- Manufacturer and Model information now shown on Device Profile details panel
Enhancements
- Added a Virtual protocol option when adding a device
- All links on the menu are now accessible on any page
- Improved field names during password change
Bug Fixes
- Fixed issue where DateTimePicker showed the wrong value when editing an interval
- Fixed a bug in creating subscriptions when qos was passed as string
Save
button disabled on Upload Device Profile page when no profile added
Edge Xpert Device Services
BACnet Device Service
Enhancements
- Updated underpinning service to improve service stability
Modbus Device Service
Enhancements
- Updated underpinning service to improve service stability
OPC-UA Device Service
Enhancements
- Updated underpinning service to improve service stability
S7 Device Service
New Features
- Added to Edge Xpert v2
Virtual Device Service
Enhancements
- Updated pre-defined device configuration to include Virtual Protocol
Edge Xpert Microservices
Enhancements
secretstore-setup
andsecurity-bootstrapper
have been updated ton includedevice-s7
2.0.3
Edge Xpert Application Service
Bug Fixes
- Fixed potential nil reference panic when store and forward mechanism is enabled with MQTT-related export functions
Edge Xpert CLI
Bug Fixes
- Added new volumes for
influxdb
to prevent generating dangling volumes and allow reusing the volumes
Edge Xpert Device Services
OPC-UA Device Service
Enhancements
- Added new volume on
device-opc-ua
for client secure connections
Edge Xpert Manager
Enhancements
- Added validation on Name, Label, and Category fields. Only
a-z
,A-Z
,-
,_
and~
characters are allowed - Adjusted the displayed value of get command with Binary data type to "[binary value]"
- Updated visibility condition of Private Key Filename for OPC-UA. Private Key Filename field now visible when Security Policy is
Basic256Rsa256
Bug Fixes
- Adjust the error message from the Port attribute in BACnet-IP
- Fixed the "Cannot update label widget" bug on CreateSubscription page
2.0.2
Edge Xpert Application Service
Enhancements
- Updated Application Service sample configuration in
configuration-insecure-shadow.toml
.TransformToAWSDeviceShadow
pipeline function name has been changed toConvertToAWSDeviceShadow
. This is due to pipeline function names that start withTransform
will be treated in v2 as the Transform function due to the new feature Multiple Instance of Function - Added new parameter
UseRawDataType
for Batch Function to allow users to decide whether to use raw data type for batched data. If set tofalse
, the data to be batched will be converted to a []byte. The default value istrue
Bug Fixes
- Fixed the panic error when using golang gzip function for high frequency data
Edge Xpert CLI
New Features
- Added port-mapping to
core-command
in docker-compose-security.yml
Enhancements
- Improved
pull
command behaviour. Users are encouraged to run theedgexpert pull --all
command to pull the valid and required images for their installed licenses. If necessary, third-party services (such asnodered
) listed in the docker-compose.yml can be updated usingedgexpert pull <SERVICE>
instead
Bug Fixes
- Updated restart policy for
kong
andproxy
Edge Xpert Manager
Enhancements
- Improved
ResourceName
field in Auto Events of devices to allow users to find required resource names faster
Bug Fixes
- Fixed "app-service already exists" error when trying to update ASC via UI
- Added warning text to Control Device page when there are no available commands (or when
is Hidden
property is set totrue
) - Fixed the blank page bug on Control Device page when the Get Command has failed
- Renamed
compression
tocompress
for the payload of creating/editing App Services - Fixed bug where checkboxes on the App Services creation page did not enable the save button
2.0.0
Edge Xpert Microservices
Enhancements
- Renamed the security service
Vault Worker
toSecretStore Setup
Edge Xpert Device Services
Virtual Device Service
Enhancements
- Upgraded to v2.0. From the user's perspective, the only thing to be aware of is the breaking changes in device profile
Migration changes
2.0
When upgrading from Edge Xpert v1.x to Edge Xpert v2.x, some migration changes may be required, depending on your use case. See the v2 Migration Guide for an high level overview.Edge Xpert CLI
Edge Xpert Services
- The
Logging
service has been deprecated in Edge Xpert v2
Edge Xpert Microservices
Core Data
Data Model
- As of Edge Xpert 2.0, Core Data is completely optional. Device Services can send data via message bus directly to Application Service. If local persistence is not needed, then the service can be removed.
If persistence is needed, sensor data can be sent via message bus to Core Data (the new default means to communicate with Core Data) or sent via REST to Core Data (the legacy way to send data to Core Data). See Core Data for more information. - In Edge Xpert 2.0, Value Descriptors have been removed. The ResourceNAme in a reading provides an indication of the data read. The other properties that were in Value Descriptor (min, max, default value, unit of measure etc) can all be obtained from the Resource (in Core Metadata's resource properties associated to each Resource which are associated to a device profile) by ResourceName. ValueType property is also provided in the Reading so that the data type of the value is immediately available without having to do a lookup in Core Metadata.
- For Edge Xpert 2.0 the
Logging
andStartup
sections have been removed.Startup
has been replaced with theEDGEX_STARTUP_DURATION
(default is 60s) andEDGEX_STARTUP_INTERVAL
(default is 1 sec)environment variables. - Writeable:. For Edge Xpert 2.9 the
Writable.InsecureSecrets
configuration section is new. - Service: For Edge Xpert 2.0
Protocol
andBootTimeout
have been removed.CheckInterval
andTimeout
have been renamed toHealthCheckInterval
andRequestTimeout
respectively.MaxRequestSize
was added for all services. - Clients.[service-key]: For Edge Xpert 2.0 the map keys have changed to be the service's service-key, i.e.
Metadata
changed tocore-metadata.
- SecretStore: For Edge Xpert 2.0 the
Protocol
default has changed toHTTP
which no longer requiresRootCaCertPath
andServerName
to be set. Path has been reduce to the sub-path for the service since the based path is fixed.TokenFile
default value has changed and requires theservice-key
be used in the path.