Skip to content

Latest commit

 

History

History
62 lines (45 loc) · 2.16 KB

README.md

File metadata and controls

62 lines (45 loc) · 2.16 KB
Raw

windhager-biowint2-client-go

Windhager BioWinTouch 2 goes cloud native with Go.

Accessing the UI

The UI is served by the Windhager pellet appliance built-in MES inifinity controller. Behind the UI, a REST API serves all values that are avaialable through the ui or the touch panel. More information about the mes infinity controller can be found here: https://www.windhager.com/int_en/products/control/mes-infinity/

Usage

import "github.com/lukibahr/windhager-biowin2t-client-go" // with go modules enabled (GO111MODULE=on or outside GOPATH)

Construct a new NewWindhagerClient client, then use the various functions on the client to access different parts of the Windhager BioWin2T API. Make sure to pass the required Url, Username and Password to the client. For example:

client := github.NewWindhagerClient("url", "username", "password")

NOTE: Using the context package, one can easily pass cancelation signals and deadlines to various services of the client for handling a request. In case there is no context available, then context.Background() can be used as a starting point.

An example can be found in the examples/ folder.

Curling the API

The api endpoint is available under http://<your-host>/api/1.0/lookup/<OID>. To add the digest authentication, use the --digest parameter like the following: curl http://<your-host>/api/1.0/lookup/<OID> --digest -u "$USERNAME:$PASSWORD"

Sample response looks like the following:

{
    "OID": "/1/60/0/12/101/0",
    "groupNr": 12,
    "maxValue": "14.0",
    "memberNr": 101,
    "minValue": "6.0",
    "name": "12-101",
    "step": "0.1",
    "stepId": 0,
    "subtypeId": -1,
    "timestamp": "2021-09-07 11:23:03",
    "typeId": 15,
    "unit": "kg",
    "unitId": 45,
    "value": "6.0",
    "writeProt": false
}

More details and docs are coming soon. This is really in a early stage of development. The internal architecture of the webserver and how the api and the metrics are organized makes building a proper api client fuzzying.

ToDo's

  • Add more metrics
  • Write tests

stay tuned.