|
|
5 tahun lalu | |
|---|---|---|
| .github | 5 tahun lalu | |
| custom_components | 5 tahun lalu | |
| .gitignore | 6 tahun lalu | |
| LICENSE.md | 6 tahun lalu | |
| README.md | 5 tahun lalu | |
| custom_updater.json | 6 tahun lalu | |
| hacs.json | 6 tahun lalu |
The goldair_climate component integrates
Goldair WiFi-enabled heaters, WiFi-enabled dehumidifiers, and WiFi-enabled fans into Home Assistant, enabling control of setting the following parameters via the UI and the following services:
GPPH Heaters
5-35 in Comfort mode, 5-21 in Eco mode, in °C)Auto, 1-5, Stop)Current temperature is also displayed.
GPCV Heaters
15-35 in °C)Current temperature is also displayed.
Dehumidifiers
30-80%)Current temperature is displayed, and current humidity is available as a property. The "tank full" state is available via the error attribute, and if you want to you can easily surface this to a top-level entity using a template sensor.
Fans
1-12)Light
Lock (heaters and dehumidifiers)
There was previously a sensor option, however this is easily achieved using a template sensor and therefore is no longer supported.
Please note, this component has currently only been tested with the Goldair GPPH (inverter), GPDH420 (dehumidifier), and GCPF315 fan, however theoretically it should also work with GEPH and GPCV heater devices, may work with the GPDH440 dehumidifier and any other Goldair heaters, dehumidifiers or fans based on the Tuya platform.
The preferred installation method is via HACS. 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.
You can also use Custom Updater. Once Custom Updater is set up, go to the Developer Tools > Service page and call the custom_updater.install service with this service data:
{ "element": "goldair_climate" }
Alternatively you can copy the contents of this repository's custom_components directory to your <config>/custom_components directory, however you will not get automatic updates this way.
You can easily configure your devices using the Integrations UI at Home Assistant > Configuration > Integrations > +. This is the preferred method as things will be unlikely to break as this integration is upgraded. 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.
If you would rather configure using yaml, add the following lines to your configuration.yaml file (but bear in mind that if the configuration options change your configuration may break until you update it to match the changes):
# Example configuration.yaml entry
goldair_climate:
- name: My heater
host: 1.2.3.4
device_id: <your device id>
local_key: <your local key>
(string) (Required) Any unique for the device; required because the Tuya API doesn't provide
the one you set in the app.
(string) (Required) IP or hostname of the device.
(string) (Required) Device ID retrieved
[as per the instructions below](#finding-your-device-id-and-local-key).
(string) (Required) Local key retrieved
[as per the instructions below](#finding-your-device-id-and-local-key).
(string) (Optional) The type of Goldair device. auto to automatically detect the device type, or if that doesn't work, select from the available options heater, gpcv_heater, dehumidifier or fan.
Default value: auto
(boolean) (Optional) Whether to surface this appliance as a climate device.
Default value: true
(boolean) (Optional) Whether to surface this appliance's LED display control as a light. (not supported for GPCV heaters)
Default value: false
(boolean) (Optional) Whether to surface this appliances's child lock as a lock device (not supported for fans).
Default value: false
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.
In my experience, fans don't like to receive a lot of commands in a short period of time. They will emit two fast beeps when accepting a command, and two slow beeps when rejecting one. If you are writing automations for your fan and need to set multiple properties, you may need to put a delay of around 5 seconds or more between each.
You can find these keys the same way as you would for any Tuya local integration. You'll need the Tuya Smart app rather than the Goldair app (the Goldair app is just a re-branded clone of Tuya Smart).
You're looking for uuid (this is the device ID) and the localKey values.
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.
None of this would have been possible without some foundational discovery work to get me started: