Sitewhere Versions Save

This is an enhancement & bug fix release. See the latest documentation for more details.

Enhancements

• Groovy outbound connector filter: Add device and other context info for event (#696)
• Send events to device upon creation and deletion in the system (#701)

Bug Fixes

• Device registration microservice API channel / Consul errors (#697)
• Service discovery causing connections to drop between microservices (#700)

This is a bug fix release. See the latest documentation for more details.

Bug Fixes

• XML parsing error when adding filters to outbound connectors (#692)
• Default values for MQTT outbound connector cause error (#693)
• Version of QRCode library is no longer available on Maven Central (#694)

This is a maintenance release. See the latest documentation for more details.

New Features

• Add outbound connector for sending customized HTTP requests based on events (#686)

Bug Fixes

• Device status not persisted when using MongoDB device management (#688)

This is a maintenance release.

Enhancements

• Update Spring injection for instance variables to only load from environment (#677)
• Change Zookeeper behavior to wait indefinitely for instance to be available (#678)
• Change MongoDB client behavior to wait indefinitely for instance to become available (#679)
• Change Kafka producer behavior to wait indefinitely for instance to become available (#680)
• Update token naming from "hardwareId" to "deviceToken" in JSON batch decoder (#683)

This is a bug fix release to address data caching issues in 2.0.0.

New Features

• Allow caching on API channels to be changed/disabled (#675)

Bugs

• Updates to devices and other objects are hidden by caching (#674)

This is the GA release of SiteWhere 2.0 which includes a completely redesigned microservices architecture and Kubernetes deployment model. For an overview of the updates to the platform see the documentation.

Note: The deployment model now requires a Kubernetes infrastructure and the use of Helm charts to configure the instance. See the deployment guide for more details.

Updates

• Allow threading to be controlled for each MQTT event source (#604)

Bugs

• Loading invocation by unique id in InfluxDB can overload RAM (#655)
• Assignment state not being captured when events with 'updateState' are processed (#647)
• Event state not properly persisted for MongoDB/InfluxDB hybrid installations (#653)
• Solr: Indexing fields with null values in sharded Solr Cloud cluster fails (#645)
• Concurrent tenant updates via API may generate an exception (#605)
• Users with usernames that end in ".au" can not be accessed via REST (#601)
• Deleting a user also deletes metadata from user tenants (#591)

This is an early (beta quality) release candidate for the upcoming SiteWhere 2.0 architecture. It is not complete and is not intended for production use. As of this release, SiteWhere runs on a Docker infrastructure and must be launched via Docker Compose or an orchestration platform such as Docker Swarm.

The following new features and enhancements have been added since RC1:

New Features

• Support deletion of scripts along with version history via REST API (#640)
• Add concept of script templates to provide code examples for scripting (#641)
• Allow scripts to be registered as part of tenant template (#648)

Enhancements

• Simplify CoAP event source configuration and update API support (#635)
• Add reasonable defaults for subcomponents to prevent configuration errors (#637)
• Update Polling REST Event Source to use new Groovy constructs (#639)
• Refactor scripts to be scoped at the microservice level (#643)

Bugs

• Presence manager operations fail with remote access exception (#634)

For more information on the new architecture, see the beta documentation here.

This is an early (beta quality) release candidate for the upcoming SiteWhere 2.0 architecture. It is not complete and is not intended for production use. As of this release, SiteWhere runs on a Docker infrastructure and must be launched via Docker Compose or an orchestration platform such as Docker Swarm.

The following new features and enhancements have been added since EA5:

New Features

• Add concept of alarm to device management model (#627)

Enhancements

• Capture component tree state as part of tenant engine status updates (#622)
• Add device assignment index for device type (#623)
• Rework command delivery components to better fit microservice structure (#624)
• Add gRPC/REST support for device state APIs (#625)
• Update registration to support new model concepts (#628)
• Support sending multiple events per API call in event management APIs (#629)
• Update user management search APIs to be consistent with others (#631)

Tasks

• Remove 'force' flag on deletes as it complicates APIs (#630)
• Remove constraint that requires tenant auth tokens to be unique (#632)

For more information on the new architecture, see the beta documentation here.

This is an early access (alpha quality) release of the upcoming SiteWhere 2.0 architecture. It is not complete and is not intended for production use. As of this release, SiteWhere runs on a Docker infrastructure and must be launched via Docker Compose or an orchestration platform such as Docker Swarm.

The following bug fixes and enhancements have been added since EA4:

New Features

• Add concept of customer type and customer to data model (#599)
• Add device state microservice for tracking most recent events (#608)
• Support instance-level metrics gathering (#613)
• Create separate template for data model initialization in addition to tenant template (#619)

Enhancements

• Allow Java debugging to be enabled for microservices (#549)
• Remove area map metadata and replace with bounding coordinates (#598)
• Event management has inconsistent approach for searching by indexes (#606)
• MQTT event source does not support configurable thread pool (#614)
• Refactor zone APIs to be consistent with other device management APIs (#616)
• Update device command and status APIs to be consistent (#617)
• Microservices need obvious logging to indicate when they have started (#621)

Bug Fixes

• User interface no longer displays permissions tree when creating a user (#600)

For more information on the new architecture, see the beta documentation here.