Skip to content

Releases: oznetmaster/WiserHeatAPIv2

v1.1.3

Choose a tag to compare

@github-actions github-actions released this 20 Sep 13:56

WiserHeatAPIv2 v1.1.3

This patch fixes cancellation of HTTP response-body reads. Previously, a hub could return its response headers and then stop sending data, leaving a request waiting beyond the caller's cancellation deadline. Error responses had the same gap.

The .NET Framework build now reads the response stream with cancellation, including on Mono. Modern .NET retains its native cancellable content read. The response is released when cancelled, and the client remains available for subsequent requests. Public API signatures, target frameworks and runtime dependencies are unchanged.

Validation covers stalled headers, partially transmitted success and error bodies, caller cancellation and client reuse. The complete offline suite passes on .NET Framework 4.7.2, .NET 10 and the tested Mono runtime, including real loopback HTTP connections. These tests do not operate household devices.

See CHANGELOG.md for release history.

v1.1.2

Choose a tag to compare

@github-actions github-actions released this 18 Sep 14:01

WiserHeatAPIv2 v1.1.2

This patch corrects Fahrenheit readings and writes when WiserAPI.Units is Imperial. Room, thermostat, valve, underfloor, heating-actuator, system, converted schedule and OpenTherm values now follow the selected units. For example, a 20 C room returns 68 F, and a requested 68 F target sends 20 C to the hub.

Conversion occurs before applying the existing Celsius limits. Boost differences use the appropriate scale without an absolute-temperature offset. Off and hot-water control values remain control values, and raw hub dictionaries and raw schedule JSON remain unchanged. Setting a manual temperature from Off sends the requested target without briefly restoring the old scheduled target first.

Public API signatures, target frameworks and runtime dependencies are unchanged. Existing standalone OpenTherm constructors retain Celsius behavior. Applications displaying Fahrenheit must use corresponding Fahrenheit ranges and must not convert values a second time.

The offline suite passes on .NET Framework 4.7.2 and .NET 10, including synthetic command-payload, dynamic-unit, schedule round-trip and Off-state regressions. The net472 test build retains its existing RuntimeHelpers compiler warning. These checks do not claim live equipment validation. See temperature units, CHANGELOG.md and development history.

v1.1.1

Choose a tag to compare

@github-actions github-actions released this 18 Sep 07:39

WiserHeatAPIv2 v1.1.1

This patch fixes false success reports from schedule JSON import and editor updates after a rejected request or connection failure. Schedule forwarding methods now preserve their underlying command results consistently.

Public API signatures, target frameworks and runtime dependencies are unchanged. Callers should check the returned Boolean and refresh hub state when they need confirmation that a requested change has actually taken effect.

The offline suite passed on both .NET Framework 4.7.2 and .NET 10, including regression cases for accepted, rejected and disconnected schedule commands. See development and validation history for verification details, CHANGELOG.md for shipped fixes, and the README for usage.

v1.1.0.6

Choose a tag to compare

@github-actions github-actions released this 12 Sep 05:33

WiserHeatAPIv2 v1.1.0.6

This patch updates the library's runtime dependencies to log4net 3.4.0 and YamlDotNet 18.1.0. Public library API signatures are unchanged.

The repository now includes seven opt-in read-only hub tests and two explicitly selected room control tests. Control tests capture the starting state, restore it even after a failed command or assertion, and verify the result by reading the hub. They use a privately configured room, skip temperature changes when an existing override prevents reliable restoration, and require explicit selection.

Private settings and credentials remain outside the published package. Only an empty settings example is included in source. CI and release publishing run the offline suite and exclude all live tests.

Validation on both net472 and net10.0:

  • 138 offline tests passed per framework.
  • Six read-only live tests passed; the optional OpenTherm check skipped because the hub returned no data.
  • Both room control tests passed, with the original scheduled setpoint, Auto mode, window-detection setting, and absence of an override confirmed afterward.

Only the library is published to NuGet. The test suites are available in the repository and are not NuGet packages.

See CHANGELOG.md and the README for details and test setup instructions.

v1.1.0.5

Choose a tag to compare

@github-actions github-actions released this 12 Sep 04:58

WiserHeatAPIv2 v1.1.0.5

This patch fixes HTTP failures found while adding the library's offline NUnit suite.

  • Retry requests retain their original payload after a transient response; intermediate responses are disposed before retrying.
  • REST reads and commands preserve authentication and endpoint exception types.
  • Caller cancellation remains cancellation rather than being reported as a timeout; actual transport timeouts still report connection errors.
  • Updated connection secrets take effect on subsequent requests.
  • UTF-8 room and device names preserve accented and non-Latin characters.
  • Redirected schedule requests retain HTTP/1.0 and their content headers.

The new NUnit suite is included in the existing Visual Studio solution and covers requests, error handling, models, commands, schedules, refreshes, and disposal. CI and package publishing run it on both supported frameworks.

Validation: 112 tests passed on .NET Framework 4.7.2 and 112 passed on .NET 10. The complete Release solution build passed with zero warnings or errors. Tests use simulated responses and do not require or operate a physical hub.

Public API signatures are unchanged. Callers of the REST controller can now catch its documented authentication and endpoint exceptions directly; code relying on every failure being wrapped as a connection error should account for these more specific exceptions.

Only the library is published to NuGet. The test project is not packable.

See CHANGELOG.md for the detailed changelog.

v1.1.0.4

Choose a tag to compare

@github-actions github-actions released this 31 Jul 04:49

Full Changelog: v1.1.0.3...v1.1.0.4

v1.1.0.3

Choose a tag to compare

@github-actions github-actions released this 09 Jun 15:29

Full Changelog: v1.1.0.2...v1.1.0.3

v1.1.0.2

Choose a tag to compare

@github-actions github-actions released this 08 Jun 10:55

Full Changelog: v1.1.0.1...v1.1.0.2

v1.1.0.1

Choose a tag to compare

@github-actions github-actions released this 07 Jun 04:38

Full Changelog: v1.1.0.0...v1.1.0.1

v1.1.0.0

Choose a tag to compare

@github-actions github-actions released this 07 Jun 04:30

Full Changelog: v1.0.0.0...v1.1.0.0