CUBETOUCH 1s (3yqdo5yt) not supported about ha_tuya_ble

[PlusPlus-ua]

Could you please provide "Device debugging" from Tuya IOT Platform?

You have to login to https://iot.tuya.com/ then select Cloud on the left, select your project, Devices tab, click "Debug device" in CUBETOUCH device row, Device Debugging tab, copy text below Standard Instruction Set.

I suppose datapoints of CUBETOUCH 1 must be identical to CUBETOUCH II, so only adding product_id will be needed.

[damiano75]

Code	Type	Values
switch	Boolean	"{true,false}"
mode	Enum	{ "range": [ "click" ] }
click_sustain_time	Integer	{ "unit": "s", "min": 0, "max": 10, "scale": 0, "step": 1 }
arm_up_percent	Integer	{ "unit": "%", "min": 0, "max": 100, "scale": 0, "step": 1 }
arm_down_percent	Integer	{ "unit": "%", "min": 0, "max": 100, "scale": 0, "step": 1 }
power_saving	Boolean	"{true,false}"
tap_enable	Boolean	"{true,false}"

[PlusPlus-ua]

CUBETOUCH II doesn't have power_saving and tap_enable.

Has your device any buttons for manual control? In mobile application is there something corresponding to "power_saving"?

I think it's better to recheck id's of all datapoints. Here is described how to do it:

https://www.zigbee2mqtt.io/advanced/support-new-devices/03_find_tuya_data_points.html#_9-find-your-data-point

[damiano75]

CUBETOUCH II doesn't have power_saving and tap_enable.

Has your device any buttons for manual control?

Only an on/off switch

In mobile application is there something corresponding to "power_saving"?

No

I think it's better to recheck id's of all datapoints. Here is described how to do it:

https://www.zigbee2mqtt.io/advanced/support-new-devices/03_find_tuya_data_points.html#_9-find-your-data-point

If I understood the instructions:

Data Point	Code
switch	1
mode	2
click_sustain_time	3
control_back	4
arm_up_percent	5
arm_down_percent	6
charge_status	7
battery_percentage	8
power_saving	9
tap_enable	10
program	11

[PlusPlus-ua]

Yes, that's what I've expected, thank you.

I'll add the device with power_saving and tap_enable as switch entities. So, you will be able to check what these switches do on real device. Then you have to decide is it worth to expose it in HA or not.

[PlusPlus-ua]

I've added new version 0.1.3 with draft of CUBETOUCH 1s support. Can you update to it with HACS?

[damiano75]

I've added new version 0.1.3 with draft of CUBETOUCH 1s support. Can you update to it with HACS?

It works!
I have these two switches:

They should be power saving and tap enable, but they have the same generic name.
Probably they are useless, I will check and let you know.

Thanks a lot for your work

[christophernewton]

I have the same model number as damiano but cant seem to get mine running.

It gets discovered but hangs at the setup process

Logs say its timing out

What Ive tried

• unbinding and connecting to cubetouch
• rebinding and connecting to cubetouch
• adding the gateway (expect this to not work, just trying things 😓 )
• uninstalling and reinstalling from hacs
• unlinking in tuya app and re linking

Thanks for setting up the code you have so far do you know of anything else I could try to make this work?

(also running it on a Rpi4 with home assistant docker, not sure if thats relevant)

[PlusPlus-ua]

do you know of anything else I could try to make this work?

I think the problem is in connection quality, the integration itself has nothing to do with it. Try to move your device closer to your Bluetooth adapter to check.

[PlusPlus-ua]

@damiano75 have you decided about these two additional switches?

[damiano75]

@damiano75 have you decided about these two additional switches?

It seems they are useless, if I switch on them they come back to off after a while.
I have disabled them

[PlusPlus-ua]

I close the issue, feel free to reopen it if you decide to reactivate these switches.

[cyrano1966]

I have been testing this Integration for the last full day and it is working fine on my side. Only noticed that if the Bluetooth Proxy goes down or is disconnected, the Cubetouch does not connect back