Nav apraksta

Jason Rumney d43f2fb122 Split andersson generic climate test into a device specific file. 4 gadi atpakaļ
.github 326bc6bb95 Latest isort requires a path argument. 4 gadi atpakaļ
.vscode 4980c8883a Completed tests for all light and lock components 5 gadi atpakaļ
custom_components d43f2fb122 Split andersson generic climate test into a device specific file. 4 gadi atpakaļ
tests d43f2fb122 Split andersson generic climate test into a device specific file. 4 gadi atpakaļ
.coveragerc 25efc866a6 Initial pytest setup (#34) 5 gadi atpakaļ
.gitignore 9c7da0e833 Add tests for Kogan Heater 5 gadi atpakaļ
LICENSE.md f35065d59d Move to a more generic tuya_local namespace. 5 gadi atpakaļ
README.md 0b2f0af7a7 Update version and clean up README.md 4 gadi atpakaļ
hacs.json 8bf3ad30d4 Remove country filter from HACS config. 4 gadi atpakaļ
requirements-dev.txt 5d54b1aef1 Get the legacy_class from the config files for lock devices. 4 gadi atpakaļ
requirements-first.txt b7afcb8c93 Add pycryptodome as a dependency 5 gadi atpakaļ
requirements.txt 0a5b600a98 Switch out the underlying library to tinytuya. 4 gadi atpakaļ
sonar-project.properties 8a6214b59d Fix sonar org. 5 gadi atpakaļ

README.md

Home Assistant Tuya Local component

Reliability Rating Security Rating Maintainability Rating Lines of Code Coverage

This is a Home Assistant add-on to support Wi-fi devices running Tuya firmware without going via the Tuya cloud. Using this integration does not stop your devices from sending status to the Tuya cloud, so this should not be seen as a security measure, rather it improves speed and reliability by using local connections, and may unlock some features of your device, or even unlock whole devices, that are not supported by the Tuya cloud API. Currently the focus is mainly on climate devices, which are not well supported by other similar integrations. Simpler devices like switches and lights can be covered by rospogrigio/localtuya.


Device support

Please note, this component is actively tested with the Goldair GPPH (inverter), GPDH420 (dehumidifier), Kogan SmarterHome 1500W Smart Panel Heater and Kogan SmarterHome Energy Monitoring SmartPlug. Other devices have been added at user request, and may or may not still be actively in use by others.

Note that devices sometimes get firmware upgrades, or incompatible versions are sold under the same model name, so it is possible that the device will not work despite being listed below.

Heaters

  • Goldair heater models beginning with the code GPPH, GCPV, GECO.
  • Kogan Wi-Fi Convection Panel heaters.
  • Andersson GSH heaters.
  • Eurom heaters.
  • Purline Hoti M100 heaters.

Pool heaters

  • Garden PAC pool heatpumps.
  • Remora pool heatpumps (possibly also BWT FI 45 models that appear to be similar)

Fans

  • Goldair GPCF315 fans

Dehumidifiers

  • Goldair GPDH420 dehumidifiers

SmartPlugs

  • Kogan Single Smartplug with Energy Monitoring Kogan ---

Installation

hacs_badge

Installation is via the Home Assistant Community Store (HACS), which is the best place to get third-party integrations for Home Assistant. Once you have HACS set up, simply follow the instructions for adding a custom repository and then the integration will be available to install like any other.

Configuration

You can easily configure your devices using the Integrations UI at Home Assistant > Configuration > Integrations > +. This is the preferred method as the configuration can be migrated as this integration evovles. You will need to provide your device's IP address, device ID and local key; the last two can be found using the instructions below.

Configuration variables

name

    (string) (Required) Any unique name for the device; required because the Tuya API doesn't provide the one you set in the app.

host

    (string) (Required) IP or hostname of the device.

device_id

    (string) (Required) Device ID retrieved as per the instructions below.

local_key

    (string) (Required) Local key retrieved as per the instructions below.

type

    (string) (Optional) The type of Tuya device. auto to automatically detect the device type, or if that doesn't work, select from the available options heater, geco_heater gpcv_heater, dehumidifier, fan, kogan_heater, gsh_heater, eurom_heater, gardenpac_heatpump, purline_m100_heater or kogan_switch. Note that the type is likely to change in future to be a configuration file name or product id, as the hardcoded list is a maintenance burden.

climate

    (boolean) (Optional) Whether to surface this appliance as a climate device. (not supported for switches)

    Default value: true

display_light

    (boolean) (Optional) Whether to surface this appliance's LED display control as a light (not supported for Kogan, Andersson, Eurom, GECO or GPCV Heaters, or switches). This is likely to change in future to light, to make way for lights which are not secondary lighting on another device.

    Default value: false

child_lock

    (boolean) (Optional) Whether to surface this appliances's child lock as a lock device (not supported for fans, switches, or Andersson ,Eurom, Purline heaters or Garden PAC heatpumps). This is likely to change in future to lock, to make way for locks which are not secondary child locks on another device.

    Default value: false

switch

    (boolean) (Optional) Whether to surface this device as a switch device (supported only for switches and Purline heaters for the Open Window Detection)

Heater gotchas

Goldair GPPH heaters have individual target temperatures for their Comfort and Eco modes, whereas Home Assistant only supports a single target temperature. Therefore, when you're in Comfort mode you will set the Comfort temperature (5-35), and when you're in Eco mode you will set the Eco temperature (5-21), just like you were using the heater's own control panel. Bear this in mind when writing automations that change the operation mode and set a temperature at the same time: you must change the operation mode before setting the new target temperature, otherwise you will set the current thermostat rather than the new one.

When switching to Anti-freeze mode, the heater will set the current power level to 1 as if you had manually chosen it. When you switch back to other modes, you will no longer be in Auto and will have to set it again if this is what you wanted. This could be worked around in code however it would require storing state that may be cleared if HA is restarted and due to this unreliability it's probably best that you just factor it into your automations.

When child lock is enabled, the heater's display will flash with the child lock symbol ([]) whenever you change something in HA. This can be confusing because it's the same behaviour as when you try to change something via the heater's own control panel and the change is rejected due to being locked, however rest assured that the changes are taking effect.

When setting the target temperature, different heaters have different behaviour, which you may need to compensate for. From observation, GPPH heaters allow the temperature to reach 3 degrees higher than the set temperature before turning off, and 1 degree lower before turning on again. Kogan Heaters on the other hand turn off when the temperature reaches 1 degree over the targetin LOW mode, and turn on again 3 degrees below the target. To make these heaters act the same in LOW power mode, you need to set the Kogan thermostat 2 degrees higher than the GPPH thermostat. In HIGH power mode however, they seem to act the same as the GPPH heaters.

Fan gotchas

In my experience, fans can be a bit flaky. If they become unresponsive, give them about 60 seconds to wake up again.

Kogan Switch gotchas

While setting this up, I observed after a while that the current and power readings from the switch were returning 0 when there was clearly a load on the switch. After unplugging and replugging, the switch started returning only dps 1 and 2 (switch status and timer). If HomeAssistant is restarted in that state, the switch detection would fail, however as Home Assistant was left running, it continued to work with no readings for the current, power and voltage. I unplugged the switch overnight, and in the morning it was working correctly.

Finding your device ID and local key

You can find these keys the same way as you would for any Tuya local integration. You'll need the Goldair app or the Tuya Tuya Smart app (the Goldair app is just a rebranded Tuya app), then follow these instructions.

Next steps

  1. Fallback support for a simple switch device using only a boolean dps 1. As well as covering the failure mode of the Kogan Switch described in Kogan switch gotchas above, it can also cover basic operation of many other devices that use dps 1 for an on/off switch.
  2. Config flow improvement to offer only the options available to the detected device, and an indication of which device was detected.
  3. The devices need to be generalized so a new subdirectory with source code is not needed to add a new device. Instead, device descriptors should be in a yaml file, which is referenced by the config.
  4. Further config flow improvements to filter the available types to possibilities based on the known dps. When many device configurations are supported, this will be required, as not all devices will be distinguishable automatically.
  5. This component needs specs! Once they're written I'm considering submitting it to the HA team for inclusion in standard installations. Please report any issues and feel free to raise pull requests.
  6. This component is partially unit-tested thanks to the upstream project, but there are a few more to complete. Feel free to use existing specs as inspiration and the Sonar Cloud analysis to see where the gaps are.
  7. Once unit tests are complete, the next task is to complete the Home Assistant quality checklist before considering submission to the HA team for inclusion in standard installations.

Please report any issues and feel free to raise pull requests.

Acknowledgements

None of this would have been possible without some foundational discovery work to get me started:

BuyMeCoffee