Skip to content

Releases: IgnacioHR/diematic_server

Version 3.6 - project migrated to new python tools

24 Nov 20:32

Choose a tag to compare

Version 3.6 is functionally equivalent to 3.5 but some file content has been consolidated into a new pyproject.toml and version number is now declared in init.py file.

Maintenance release, requirements updated

17 Nov 13:00

Choose a tag to compare

On this version there are some updates related with the mqtt integration and the device discovery process from Home Assistant.

Full Changelog: v3.1...v3.5

Added boiler pumps to MQTT discovery

23 Nov 09:54

Choose a tag to compare

On this new version I've added boiler pumps to MQTT discovery process

Full Changelog: v3.0...v3.1

New version 3.0 with MQTT Broker backend

16 Nov 18:40

Choose a tag to compare

In this new release I added support to write all values from the boiler to an MQTT broker.

I've also added support to Home assistant MQTT Discovery so in case you are using that integration the device and some entities will appear just there.

Note, you can configure what you want to see modifying the diematic.yaml file and restarting the service.

Full Changelog: v2.2...v3.0

Stable final version 2.2

11 Apr 13:26

Choose a tag to compare

Updated gen.py and diematic.yaml example. This version is production ready. The web site has been updated and allows to read and update registers individually

Bug fix release

02 Apr 16:22

Choose a tag to compare

Bug fixed. Write operation did not start

Improved web service handler

02 Apr 15:56

Choose a tag to compare

The new web service is based on aiohttp and supports HTTP 1.1. The previous one had issues with some clients. This one supports also keep-alive

replace dash for underscore

31 Mar 14:07

Choose a tag to compare

v1.2

renamed package to replace dash for underscore

Fix pip install issue

31 Mar 12:43

Choose a tag to compare

Fix error raised by pip install regarding pkg-resources=0.0.0

Initial version

30 Mar 12:59

Choose a tag to compare

Although I have had the software in production for months, it is now when I am going to publish it in pipy, that is why I call it version 1.0