Holman WiFi Tap timers intergration?

Im only new to tuya-cli so im not even sure i am doing it correctly… But

When i use the Wizard Option i get the list…

[
{
name: ‘Wi-Fi Hub’,
id: ‘bfb829575319560f27####’,
key: ‘bd03bfe66449####’,
subDevices: [
{
name: ‘WX2 Tap Timer’,
id: ‘bfa9161f8d01c389c2####’,
cid: ‘851’
},
{
name: ‘Wi-Fi Socket’,
id: ‘bf6199a0d63171ce4c####’,
cid: ‘85B’
}

When i try the get command this is all that comes up…
[email protected]:~# tuya-cli get --ip 10.50.3.168 --id bfa9161f8d01c389c2#### --key bd03bfe66449####
undefined

I would guess that the WX2 will list as one device but have a different array of dps values then. You have one CID there, can you try treating it like WX1 and following what others have done?

Ok, So i’ve added the the WX2 with the CID and using the DPS map from https://raw.githubusercontent.com/darek-margas/localtuya/87041d7c00a9558e82912e853bae0cf37c30a222/Holman%20WX1%20WiFi%20Irrigation%20Tap.md and it all seems to be perfectly fine for “Zone1” which is Tap1…

But i need to get all the DPS values for “Zone2” which is Tap2…
I would imagine that the temp/moisture etc are all the same as thats fed from a sensor connected…
But all the other values are different for zone2

Can somebody explain how i can use tuya-cli to get the “missing” DPS values? As i have no clue how to map them out?

have you got the dps results from tuya-cli that it produces for your WX2? We can compare to the dps that we see for the WX1 and probably work back from there. Could it be possible that there is only one more dps (another dps like 106 on the WX1) that then uses the same values for both taps perhaps?

@nat8 this is what i have been asking…
HELP with how to GET the DPS results using tuya-cli?
I have no idea how to do this… As the commands i am trying don’t seem to work??

When i try the get command with tuya-cli all i get is “Undefined” as a result?

[email protected]:~# tuya-cli get --ip 10.50.3.168 --id bfa9161f8d01c389c2#### --key bd03bfe66449####
undefined

tuya-cli get --id ID_OF_GATEWAY --key KEY_OF_GATEWAY --cid WX2_CID --full

where the gateway is the ‘parent’ device that you can get from running the tuya-cli wizard command. This should generate something like this for you:

[ { name: 'Wi-Fi Hub', id: 'ID_OF_GATEWAY', key: 'KEY_OF_GATEWAY', subDevices: [ { name: 'WX1 Tap Timer', id: 'WX1_ID', cid: 'WX_CID' }, { name: 'Wi-Fi Socket', id: 'Socket_ID', cid: 'Socket_CID' } ] }

From which you should be able to get all the details you need for the command.

It bring up nothing…
Just a command prompt afterwards
[email protected]:~# tuya-cli get --id bfb829575319560f27#### --key bd03bfe66449#### --cid 851 --full
[email protected]:~#

Actually i kept trying it and after the 5th time it brought something up yay!
{
dps: {
‘101’: 0,
‘102’: 0,
‘103’: 144,
‘105’: ‘2’,
‘106’: ‘0’,
‘107’: 10,
‘108’: true,
‘113’: ‘0’,
‘114’: ‘12’,
‘115’: false,
‘117’: false,
‘120’: 0,
‘125’: false,
‘127’: ‘HOL9H005-061-000-000’,
‘150’: 0,
‘151’: 0,
‘152’: 5,
‘153’: ‘0’,
‘154’: 25,
‘155’: true,
‘160’: ‘0’,
‘161’: false,
‘162’: false,
‘166’: false
},
cid: ‘851’
}

fantastic, congratulations. It looks roughly like all dps up to 127 match between WX1 and WX2. Are you able to change some values in the app and re-run the command to see which dps change to help map out what each dps represents?

Can confirm that the WX2 works nicely with this custom component.

Have mapped the dps for the second tap/outlet as follows:
{ dps:

{ ‘101’: 0,
‘102’: 0,
‘103’: 10,
‘105’: ‘2’,
‘106’: ‘0’,
‘107’: 8,
‘108’: true,
‘113’: ‘0’,
‘115’: false,
‘117’: false,
‘120’: 0,
‘125’: false,
‘127’: ‘HOL9H005-061-000-000’,
‘150’: 0,
‘151’: 0,
‘152’: 7, // amount of water used last time
‘153’: ‘1’, // 1 when runs water, 0 when stopped, 3 when stopped and time/rain delay active
‘154’: 5, // minutes set for manual run,
‘155’: false, // starts manual countdown when false
‘160’: ‘0’,
‘161’: false,
‘162’: false,
‘166’: false },
cid: ‘B41’ }

Note: for me I had to remove the ‘Beta’ tag from the manifest.json of [darek-margas] custom_component to have the component pass some (new in 2022.3) validity check for it to load.

1 Like

I merged fan compatibility changes for 2022.4

I have managed to connect my WX8 to home assistant using Tuya Local. It works great and using local means its very responsive.

See may post Holman WX8 Watering System

Seems this all does not work with NON YAML based config. as the Web Config does not support the CID for Subdevices?

Would there be anybody around that could shed some light on why the Web Config doesn’t support Subdevices?

Hi Darek,

Thanks for your great effort for making the Holman Tap Timer working on LocalTuya. I have bought the WX2 which has 2 outlet, and set this up successfully based on the dps meaning shared by other user in this thread. After that I bought another WX1 and want to connect to the same WiFi hub, then the problem comes.

Most of the dps of WX1 is actually same as dps of the outlet 1 of WX2, looks like LocalTuya of your fork doesn’t route the message to the correct CID but just rely on the DPS. Below is the scenario

DPS 106 - tap open/closed status
DPS 108 - tap manual countdown on/off (i.e. tap on/off)

both DPS number are same between WX1 and WX2’s 1st outlet.

When I switch on DPS 108 of WX1, both WX1 and WX2 DPS 106 show the tap is opened, and vice versa. However, only the WX1 tap is actually switched on but not WX2, although status of WX2 DPS106 shows this is running. Looks like the status going back to HA UI has not distinguish the CID.

Would you mind looking into this and see if this is possible to have a fix?

I have this exact issue also. WX1 + WX2, taps behave as expected but UI shows incorrect states.

yes, able to control but cannot get the status correctly. When implementing the automation, need to take this into consideration.

Hi everyone… similar issues… I know this thread is a bit old now but…

status of one tap seem to be reflected onto my other two, and vice versa - if I turn one tap on the other two show as on. Did anyone find a fix for this?

I have not… The system still works fine. Visually its just annoying. I only every have one tap on at a time anyway.

Pls circle back here if you find a solution

Has anyone had an issue where HA won’t turn on/off the taps until you activate them using the Tuya app first? Its like it thinks the devices are unavailable until then.