v2.0.0 Release

This update contains breaking changes. Upgrade carefully.

What's new?:

• more unit settings (e.g. change the unit of leaf temperatures and soil temperatures separately)
• stable interfaces (interfaces shouldn't get killed on disconnect, they should wait for the weather station to reconnect)
• helper method waitForNewSerialConnection: this method waits for a change in the usb devices list - on change it returns the new device's path
• sunset / sunrise as dates instead of strings
• better naming (some classes had misleading names, this has been fixed)
• updated documentation

v1.0.7

This update contains no breaking changes. Upgrading is recommended.

What's new?:

• Fix LOOP1, LOOP2 and RichRealtimeData typescript type definitions (the etDay property was missing)

v1.0.6 Release

This update contains no breaking changes. Upgrading is recommended.

What's new?:

• Fix critical v1.0.4 bug
• Code clean-up

v1.0.4 Release

This update contains no breaking changes. Upgrading is recommended.

What's new?:

• Dependency upgrades (minimatch)

v1.0.3 Release

This update contains no breaking changes. Upgrading is recommended.

What's new?:

• Fixes this issue.
• Introduces the new interface methods getWeatherstationType and getWeatherstationTypeID (read more here)

v1.0.2 Release

This update contains no breaking changes. Upgrading is recommended.

What's new?:

• The new method interface.setBackgroundLight(boolean) allows you to turn the console's background light on / off
• Reduced dependencies
• Improved documentation for realtime data containers

v1.0.1 Release

This update contains no breaking changes. Upgrading is recommended.

What's new?:

• Internally a new binary parser is used to parse binary data received from the console
  • The new parser ensures type safety making the maintainence of this project much easier
  • As the new parser is only used internally this doesn't affect developers developing with vantjs
• Minor bug fix:
  • There was an error in the HighsAndLows class/type definition, the uv property's type was defined as ElementHighsAndLows even though it actually is ElementHighs

v1.0.0 Release

What's new?:

• unit settings: select the units vantjs should use, the weather data is converted automatically
• bug fixes / stability: v1.0.0 will be the first stable release of vantjs, many bug fixes have been made
• better types / structures: more subtypes were created, leading to a more readable documentation
• better imports: imports are now structured in seperate modules
• starter-guide/documentation: a helpful starter guide introducing you into vantjs step by step and a full documentation

v0.4.0 Release

What's new?:

• Refractored code base: Internally a lot of code got refractored. Now it's much more readable and easier to maintain!
• Switch to a fully promise based code style: All functions related to the connection to / communication with the weather station now return promises, allowing clean code to be written using async/await. Therefore the VantInterface.ready function and the "error" event got removed.
• Progress on weather data containers: The first weather data container (the RichRealtimeDataContainer) is now available offering a more abstract layer to interact with your weather station.
• Typed-checked events: Event listeners are now type-checked!

v0.3.0 Release

What's new?:

• Integration of error handling into the event system: Instead of passing an error handler callback function to the device.ready function you can handle errors by listening to the error event.

device.on("error", (err: Error) => {
   console.error(err);
});

• The auto close option is now easily configurable: Instead of overwriting the "finally" callback function, you can (optionally) pass a boolean disabling/enabling the auto close feature. By default it's enabled.

device.ready(async () => {
 ...
}, false);

• First (unstable) draft of weather data containers: Weather data containers are self-updating objects representing the weather station's current state (including all sensors). It's a new level of abstraction. Accessing the current outside temperature is as easy as possible. You simply write container.temperature.in.