v1.2.0: New Features - Drying action, high-res zone temperatures

New Features:

• Drying (aka Dehumidify) can now be reported as the current action when the system appears to be in that mode. This defaults to previous behavior since it could confuse clients not expecting to see it; add -drying to the command line to enable it. Currently, heuristics are used to guess when this mode is active, since we have not found a way to determine it precisely. Refer to README.md for details.
• High-resolution raw temperature readings (to 1/16 degree) reported by the thermostat are now published as infinitive/zone/X/temp16 in MQTT, and per-zone bonus sensors named <zoneName> Raw Temperature will be created via Home Assistant MQTT Discovery if using. These sensors do not affect the Home Assistant MQTT Climate integration but you will find them as stand-alone sensors in case you would like to use them. They will differ from the smoothed, rounded values shown on the thermostat but are undoubtedly used internally.

Minor Fixes:

• The fix to the Infinity clock skew in v1.1.0 was found to over-compensate a bit; this release contains a small adjustment to keep the Infinity clock within 1 minute of the infinitive host's clock whenever the affected register is written.

Full Changelog: v1.1.0...v1.2.0

What's Changed

Features

• You may now pass duct capacity parameters on the command line rather than needing to be hardcoded. Duct capacities are used in the calculation of relative airflow between zones, so this is only important if you have a multi-zone system and you use the airflow weights published in MQTT. The default has been changed, and now equally weights all zones rather than reflecting the author's own system. See README for notes on usage.
• Add experimental MQTT sensors for current displayed zone, current system day of week, current system time skew
• Add experimental MQTT action for setting current displayed zone on thermostat
• Add Home Assistant MQTT discovery for the above new sensors/settings as well as previously-added MQTT sensors for outside air and coil temperatures. Remember that experimental topics and sensors may be changed or removed in a future version.

Fixes

• When setting parameters in register 3b02, such as Mode, we observed the Infinity system time would slip backward by up to one minute; this could accumulate over time and amount to a significant clock skew. Whenever setting values in this register, infinitive now also sets the Infinity system time to host time, to correct for this. This makes it more important to keep your host clock set correctly.

Potential "Breaking" Changes

There really are no breaking changes, but there are two changes in behavior from older versions:

• If you were using zone airflow weights published in MQTT but you did not change the source code to provide the duct airflow percentages for your own system, the values being reported by this version will be different from prior - however both will probably be objectively wrong for your system. You should follow the instructions in README to provide your duct assessment data on the command line, or continue to ignore all this bit.
• See above about setting the Infinity system clock whenever changing certain settings via infinitive. This was always impacting the Infinity system clock but this new fix could make things worse for you if you don't keep your host system clock set correctly.

Full Changelog: v1.0.0...v1.1.0

What's Changed

• The -instance command line arg is now more useful when you have multiple systems, especially non-zoned ones
  • The instance name is used to differentiate multiple instances of entities that are not associated with a zone
  • The instance name is used to differentiate multiple Climate entities when using non-zoned systems

Note about breaking changes

NOTE: This release changes the names of several entities which are automatically created in Home Assistant via MQTT Discovery. If you use that feature and those entities, you will need to take some steps to accommodate this change:

• after you have stopped using older versions of Infinitive, you will need to flush retained MQTT Discovery topics from your broker
  • there is some advice about this in README.md
  • this will delete all the automatically-created entities from the older version of Infinitive, and any references to these sensors will show as undefined or unavailable
• new entities will be created next time this new version is run and they will in many cases have different names
• you will then need to update any references to those entities to use the new names

The particular entity names that will change, and what they will change to, depends on your system(s) and how you set the -instance option. Refer to README.md for details.

ALSO NOTE: MQTT topics themselves (the MQTT API) have not changed so you only need to worry about updating references to entities created by DIscovery.

Full Changelog: v0.5.0...v1.0.0

What's Changed

• README document updates and cleanup - things got really tangled for a while
• Add State Class to sensors in MQTT Discovery to satisfy current Home Assistant requirements
• Add Instance Name option to allow multiple instances of Infinitive to coexist on an MQTT bus and Home Assistant without direct conflicts. See README for details.

New Contributors

• @themrwookiee made their first contribution in #2 - thanks!

NOTE: this release tag is being created retroactively based on work done through 4/13/2025

Full Changelog: v0.4.0...v0.5.0

This release completes the MQTT Discovery support for Home Assistant. With this version, an MQTT Climate entity is created for each zone in the system. Additionally, button entities are created for adjusting Vacation mode settings.

Refer to README.md for details.

NOTE: this release tag is being created retroactively for work done in June, 2024

Full Changelog: v0.3.0...v0.4.0

The focus of this release is a stable MQTT API. This includes async connect/reconnect, solid publication of values only when they change, and MQTT Discovery topics for Home Assistant, for the auxiliary sensors (i.e. those not part of the Climate entities). MQTT Climate entities still need to be configured manually; see the README. With this release you can and should delete the statically configured sensors that are now being created by Discovery.

This also includes experimental work relating to airflow metrics, and a peek at additional interpretation and research into data from the controller.

NOTE: this release tag is being generated way retroactively

Full Changelog: v0.2.0...v0.3.0

This release adds an initial cut at MQTT support. We are going this route rather than trying to update or create a custom Climate integration for Home Assistant. Instead, we are creating an MQTT API and will add discovery support to create Climate and other entities dynamically based on the system's configuration. All the old APIs and UI are still being maintained but new development will focus on MQTT.

Refer to the README.md file for details on what is currently in place.

NOTE: this release tag is being created way retroactively

Full Changelog: v0.1.0...v0.2.0

Initial apparently stable release from this fork.

• Supports zones via extension of the existing REST API
• UI has been reworked to show multiple zones when present
• Fixed old buffer handling bug in upstream which caused intermittent misreads from the controller

Documentation updated with what's been done so far and ambitions for what is to come

NOTE: Adding this release tag way retroactively