Closed JackJackattack4 closed 2 months ago
The "product id" you have given appears to be the device id (unique per device), not the product id. Only the product id is of use to the integration, the device id is used to configure your specific device.
You are right.
Here is the device ID : 02ek8thasvo40fmd
It is the same for both identical devices.
Similar to fisher_water_heatpump, in that it mixes heating and cooling with hot water functions. Although perfect support is not really possible without some special enhancements to cater specifically for this type of device, we can implement support of the climate functions assuming hot water is always on, and providing an extra select for full mode control if that assumption is not valid.
In my case, hotwater is never on, but an extra select for full mode control is a good solution.
Log Message
Information about DPS mappings
Product ID
I have two exactly identical devices and they do not have the same product ID One has the following ID: eb313fb004c523375cxgzw The other has this other ID: eb9a44bd30916d3150ftup
Information about how the device functions
See the 3 tabs in the excel file attached, Deakon Heatpump.xlsx
Also, please find a manual of the device attached, Manual A2 Pro-2(2.1).pdf
There is an element of challenge in supporting these devices: they are configured in such a way that some parameters and their values are separated in two DPIDs, have a look into the script of the device I created attached below, I added comments.
I have created and used successfully within a local version of Tuya-Local the following script under the already existing component named "Poolex_Silverline_heatpump" (I used this name because this is the only one I could pick from the drop-down menu when adding the Tuya device in Tuya-local).
EVI DC Inverter Heat Pump script.txt