Skip to content

Releases: sitewhere/sitewhere-admin-ui

SiteWhere Admin UI 3.0.3

23 Mar 22:41
4f9f9b8
Compare
Choose a tag to compare

Maintenance Release

This is a maintenance release and is compatible with instances created with swctl v0.9.2.

New Features

  • Introduce event pipeline debugging features.

SiteWhere Admin UI 3.0.2

12 Feb 20:58
Compare
Choose a tag to compare

Maintenance Release

Bugs Addressed

  • Use distinct background colors for assignments to indicate status (#44)
  • When listing assignments for an asset, list entries are blank (#43)
  • Unable to list zones from area detail page (#42)
  • Unable to create boundaries for new area when using administrative UI (#41)

SiteWhere Admin UI 3.0.1

26 Jan 21:13
Compare
Choose a tag to compare

Maintenance Release

Bugs Addressed

  • MQTT outbound connectors not properly interacting with the underlying configuration.

SiteWhere Admin UI 3.0.0

16 Jan 17:04
Compare
Choose a tag to compare

Administrative user interface for interacting with SiteWhere 3.0 instances.

Installation

After installing SiteWhere (using swctl), start the UI and point it to the IP address exposed for the Istio ingress controller. You can find the correct address by issuing the following command.

kubectl -n istio-system get services

Look for the External-IP for the istio-ingressgateway service:

NAME                   TYPE           CLUSTER-IP      EXTERNAL-IP     PORT(S)                                                                      AGE
istio-ingressgateway   LoadBalancer   10.103.29.184   192.168.0.103   15021:30725/TCP,80:30308/TCP,443:32512/TCP,15012:30661/TCP,15443:31451/TCP   3d1h

For the above example, if you created an instance using swctl create instance sitewhere, you would enter http://192.168.0.103/sitewhere as the instance API path in the admin user interface.

SiteWhere 3.0.0 Beta 1

11 Aug 17:56
Compare
Choose a tag to compare
Pre-release

Beta Notice

This is the first beta release of the SiteWhere administrative application for SiteWhere 3.0. It is considered beta-quality software, so there will be bugs. Report any problems via GitHub issues. Note that this UI depends on updated APIs and is not backward compatible with SiteWhere 2.x.

Installation

After installing SiteWhere (preferably with swctl), start the UI and point it to the host:port exposed for the SiteWhere REST HTTP service. You can find the correct address by issuing the following command (depending on the namespace for your instance).

kubectl -n sitewhere get services

Look for the External-IP for the sitewhere-rest-http service:

sitewhere-rest-http                 LoadBalancer   10.103.195.82    192.168.1.106   8080:32077/TCP               24h

For the above example, you would enter 192.168.1.106 for the hostname and 8080 as the port in the admin UI.

SiteWhere Admin Application v2.1.0

09 Aug 23:18
6e2363e
Compare
Choose a tag to compare

The SiteWhere Admin v2.1.0 release adds UI support for the new features introduced in SiteWhere 2.1.0. Note that there may be issues when using this application with versions of SiteWhere prior to 2.1.0 due to API updates. The administrative application is based on Electron. Install the version for your platform (Windows/Mac/Linux) then open the application and point it to a running SiteWhere instance.

The v2.1.0 release has been entirely rewritten using a new TypeScript-based component model and the latest SiteWhere REST APIs which include a complete TypeScript object model. Much of the core IDE functionality has been broken out into component libraries for a more consistent approach in the user interface which will be used across all SiteWhere IDE products.

2.0.0

15 Dec 02:09
Compare
Choose a tag to compare
v2.0.0

Reconnect to MQTT broker if MQTT setting are updated.

SiteWhere Administration Application v2.0.0-RC2

14 Sep 21:39
Compare
Choose a tag to compare

This is the first release of the SiteWhere Administration Application to be based on Electron. Install the version for your platform (Windows/Mac/Linux) then open the application and point it to a running SiteWhere instance.

Note: Deploy a SiteWhere instance first using the Deployment Guide.