Releases: scottyphillips/echonetlite_homeassistant
Bug fixe for non-climate sensors
This should resolve a few issues with using non climate sensors.
Support for ECHONETlite Manufacturers
Thanks everyone for all the help.
Support for HVAC energy readings
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.
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
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
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.
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...
Bugfix for outdoor sensors
This fixes a breaking change to the outdoor sensor that was introduced with the rolling changes to mitsubishi_echonet v5.0.
The library is now version 0.5.1 so the custom component is now version 2.1.2.
Updated to support 'mitsubishi_echonet' v0.5
This is a release to hopefully address potentially issues related to the non-availability of 'Outdoor Temperature' ECHONET values for some systems.
This was a feature/bug that was introduced in v0.4.1 of the 'mitsubishi_echonet' library which I think is adversely impacting the 'update' routine in the Home Assistant component for some users. This feature/bug was not present in v0.3 of the library which is why it was probably working for most users on prior release 2.0.1 of the custom component.
The underlying bug has been addressed in v0.5 of the 'mitsubishi_echonet' library.
If users are still having issues, please add the following debug logging to your 'configuration.yaml' file:
logger:
default: warning
logs:
custom_components.mitsubishi: debug
Look for the following details in the logs:
2021-06-12 08:46:08 DEBUG (MainThread) [custom_components.mitsubishi.climate] ECHONET lite HVAC X.X.X.X component added to HA
2021-06-12 08:46:08 DEBUG (MainThread) [custom_components.mitsubishi.climate] HVAC has the following get properties:
2021-06-12 08:46:08 DEBUG (MainThread) [custom_components.mitsubishi.climate] {'Operation status': 128, 'Air flow rate setting': 160, 'Operation mode setting': 176, 'Installation location': 129, 'Standard version information': 130, 'Identification number': 131, 'Set temperature value': 179, 'Manufacturers fault code': 134, 'Fault status': 136, 'Fault description': 137, 'Manufacturer code': 138, 'Measured value of room temperature': 187, 'Status change announcement property map': 157, 'Set property map': 158, 'Measured outdoor air temperature': 190, 'Operation power-saving': 143, 'Get property map': 159}
2021-06-12 08:46:08 DEBUG (MainThread) [custom_components.mitsubishi.climate] HVAC has the following set properties:
2021-06-12 08:46:08 DEBUG (MainThread) [custom_components.mitsubishi.climate] {'Operation status': 128, 'Installation location': 129, 'Operation power-saving': 143, 'Air flow rate setting': 160, 'Operation mode setting': 176, 'Set temperature value': 179}
That will give me a hint as to what any potential issues are when compared to my own setup.
Minor fixes
The Experimental branch containing all the async code updates for performance improvements has been merged into the master branch