Tuya Double Switch TS0012 turns itself off again.

[schumi2004]

Describe the bug

Connected the wired double Tuya switch (no-neutral) switch as described and paired it with Deconz (Home Assistant).
When turned on manually or via Deconz the switch tunrs itself off again after approximatly 2 min.
Looks like some timer got activated but can't find any documentation about it.

And sometimes, after it happened for a few times, it becomes unresponsive and only manual activation makes it work again.

Steps to reproduce the behavior

Connect the switch as instructed, pair it with Deconz and just turn it on, manually or using Deconz/Home Assistant.

Expected behavior

Just stay on.

Screenshots

n/a

Environment

• Host system: Raspberry Pi 3B+

• Running method: Home Assistent deCONZ Add-on

• Firmware version: 26660700

• deCONZ version: 2.05.88 / 15-10-2020

• Device: ConBee II

• Do you use an USB extension cable: yes

• Is there any other USB or serial devices connected to the host system? If so: Which? SSD

• switch used: 2 gang switch TS0012

deCONZ Logs

Need to figure out how to save the logs to a file in HassIO.

Additional context

n/a

[Smanar]

Hello, can you make a try with the api disabled ? Plugin / rest API plugin.

[schumi2004]

I'm not sure how to do this?
I checked the Home Assistant Add-on: deCONZ in my HassIO setup but can't find anything to disable api?

I removed the port in HA deCONZ addon configuration that disables API backend, is that what you mean?

For now, I unpaired the switch and it functions normal again as a regular switch.
Will pair it again later this evening when I have more time.
Is it also possible I caused this behavior using a combination of button presses?
At first, I thought it did not pair so I tried it again to find out they were added underneath the lights section. Maybe a reset of the switch (if possible?) will help also?

[Smanar]

Ha, sorry it s only possible using the GUI.

It s possible too with removing the lib file from the folder, but I don't want to broke your setting. Was to make the same test than you, the device in the network but without the API, to check if it s from zigbee or api side.

For the rest, idk, never see a timer feature in this kind of switches. Perhaps something visible in log (you have it in phosocn too now, in "help")

[megawubs]

@schumi2004 Not really related to the topic, but where did you got this switch? I've been searching for something like this for a while now. But can't really find any shop selling this when I search for it on the web.

[schumi2004]

@megawubs https://nl.aliexpress.com/item/4000298926256.html?cv=47843

@Smanar
The HassIO deCONZ addon does have a GUI.
I can choose from Phoscon or Deconz, i'll check again when i have some more time inbetween work.

[Smanar]

The HassIO deCONZ addon does have a GUI.
I can choose from Phoscon or Deconz, i'll check again when i have some more time inbetween work.

Ha ? are you sure of that ?
But if you have the deconz GUI

"rest API plugin" then uncheck the case on the popup.

[schumi2004]

Got it unchecked, going to test it now.

/edit:
Okay, this is frustrating.
I needed to enable REST API again otherwise I couldn’t pair the switch again, after it got paired, I left REST API enabled to see what will happen and guess what, it works normal as expected.
Only difference is that I only paired it once.
Will test next few days if i can replicate the issue.

[Smanar]

You can pair it, and disable the switch after, or just let it already paired.
It s just to check if you have the same issue with the api disabled, only with the zigbee network alone. The important part is not pairing, but to check if you still have the "timer" bug.

[schumi2004]

Switch still functions as expected since yesterday. The only difference is that I only did the pairing procedure once and not twice as the first time.
I think that the very first time I paired the switch and thought it did not work I activated some feature during second attempt that caused this auto off. I took 2 minutes every time it turned itself off (used a timer to measure) and because of that I think something got activated during pairing when it already was.

Yesterday when I wanted to test I already had deleted the device and I needed to enable REST API again for it to get paired and since then it works flawless.

Maybe we should close this issue for now and reopen when I have new devices with similar behavior.

[Smanar]

This is no documentation with the device ? even in chinese ?

[schumi2004]

Documentation is shipped with it but doesn't describe "advances" features like auto off or something like that (if any). It only describes how to wire and pair it for different versions (neutral, no neutral, wifi, zigbee, rf433)

[kind3r]

Had the exact same issue, obviously because of the 'double pairing'. I thought that you have to pair each gang individually.

Deleted the switch from Phoscon app (removing one light removes the other also) and then repaired and now it's ok. I'm thinking I should do this with some of the other sensors that sometimes missbehave.

[kind3r]

I think I spoke too soon, after some time they started automatically turning off again ...