Skip to content

Releases: scottyphillips/echonetlite_homeassistant

Bug fixes.

17 Feb 06:01
Compare
Choose a tag to compare

This is a minor uplift to include the recent bug fix contributions. Thanks everyone who has supported this project.

Bug fixes

14 Jan 23:16
Compare
Choose a tag to compare

This release contains the following bug fixes:

  • Improves behaviour when reloading Home Assistant and ECHONETlite device is offline or not reachable from the network at reboot. Device will be loaded but in state 'unavailable'. Device will continue to be polled and not throw errors in the logs
  • Minor bugfix for when climate state is auto.

Add light class and correctly handle config flow for unavailable devices

15 Sep 01:24
Compare
Choose a tag to compare

This release introduces support for the light class.
Tested against MoekadenRoom simulator.

Also this address an issue where ghost ECHONET devices would be appear to be added to HomeAssistant. Config flow will now identify if no ECHONET device actually exists and cancel.

Bug fixe for non-climate sensors

15 Sep 00:04
Compare
Choose a tag to compare

This should resolve a few issues with using non climate sensors.

Support for ECHONETlite Manufacturers

12 Sep 23:26
Compare
Choose a tag to compare

Thanks everyone for all the help.

Support for HVAC energy readings

09 Sep 01:28
bf2667e
Compare
Choose a tag to compare

If your HVAC system supports energy readings via ECHONET you can now add this information to your energy page in Home Assistant.

Thanks @khcnz for your work on this

Changed to pychonet-2.0 and remove 'mitsubishi' branding.

02 Sep 22:21
8c72ea4
Compare
Choose a tag to compare

This is the long awaited release to resolve many annoying issues people are encountering.
At the moment, you will need to copy across 'echonetlite' into your 'custom_components' and delete any mention of 'Mitsubishi' as the two codebases will clash. You can then add the integration using the GUI as per the instructions.

Updated for target temperature precision as per ECHONET spec

15 Jun 06:20
Compare
Choose a tag to compare

Many of you have probably been annoyed that you cant set temperature in half degree increments as per the Mitsubishi app, or as per the physical panel.

Well you can continue to be annoyed, but at least you cant 'accidently' set the temperature to 19.5 in HA.
'climate' now only accepts whole numbers for setting temperature as per the current ECHONET spec.

Support for Unique IDs

15 Jun 05:56
Compare
Choose a tag to compare

This release brings support for the Home Assistant 'Unique ID' attribute which means it should be easier to configure the HVAC in the GUI.

Another Bugfix for outdoor sensors.

15 Jun 04:33
Compare
Choose a tag to compare

2.1.2 fixed the climate component. 2.1.3 fixes the sensor component.
If your outdoor unit to your HVAC does not support temperature sensing this should hopefully fix the issue...