Most should work, the only other modification is fan which has some features added and should work for old config too.
The one I took fork from recently had some fix for time concurrency which I didn’t merge as they also modified fan which now conflicts with mine and requires cherry picking to merge. I’ll merge it a bit later.
So, should work as is. However, this CID added is a shortcut and while it seems that non-gateway devices are ignoring it, you may find one which does not ignore and gets confused. So far no-one found such device.
I don’t think so. Look at other PRs there, many good ones and stuck and this is minor change in fact. I tried with fan with no luck. In fact this change came partially from rospogiorgio - there is gateway branch, I just added missing “set”. Knowing that gateway branch is abandoned there, I believe he lost interest in this.
ok. Am I right to say if rospogiorgio make an incremental release (IE 3.2.5), potentially his code there will overwrite your code here with the Holman, if I update the integration via HACs ?
Still no luck I’m afraid. I add my device using the YAML config shown on the Git Hub. The device shows up but unavailable. I get the following error in my log.
Logger: custom_components.localtuya.common
Source: custom_components/localtuya/pytuya/init.py:559
Integration: LocalTuya integration (documentation, issues)
First occurred: 07:46:09 (2 occurrences)
Last logged: 07:47:07
[015…015] Connect to 192.168.1.16 failed
Traceback (most recent call last): File “/config/custom_components/localtuya/common.py”, line 151, in _make_connection status = await self._interface.status() File “/config/custom_components/localtuya/pytuya/init.py”, line 472, in status status = await self.exchange(STATUS) File “/config/custom_components/localtuya/pytuya/init.py”, line 457, in exchange payload = self._decode_payload(msg.payload) File “/config/custom_components/localtuya/pytuya/init.py”, line 559, in _decode_payload return json.loads(payload) File “/usr/local/lib/python3.9/json/init.py”, line 346, in loads return _default_decoder.decode(s) File “/usr/local/lib/python3.9/json/decoder.py”, line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) File “/usr/local/lib/python3.9/json/decoder.py”, line 355, in raw_decode raise JSONDecodeError(“Expecting value”, s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
Hey All,
I went and got the WX2 (https://www.holmanindustries.com.au/product/wx2-dual-outlet-tap-timer-and-wi-fi-hub/) from Bunning with the Wifi Hub… I have managed to get the Hub/Switch linked up with LocalTuya… But i cannot for the lift of me get the CID values using tuya-cli for the WX2 as this has 2 tap switch’s on it which are obviously going to be different to the WX1…
Happy to get some guidance on getting the required values so it can be setup in HA
When i try the get command this is all that comes up…
root@ubuntu:~# 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?
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?
root@ubuntu:~# tuya-cli get --ip 10.50.3.168 --id bfa9161f8d01c389c2#### --key bd03bfe66449####
undefined
It bring up nothing…
Just a command prompt afterwards
root@ubuntu:~# tuya-cli get --id bfb829575319560f27#### --key bd03bfe66449#### --cid 851 --full
root@ubuntu:~#
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?