Tuya Double Switch TS0012 turns itself off again. #3693
Comments
|
Hello, can you make a try with the api disabled ? Plugin / rest API plugin. |
|
I'm not sure how to do this? 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. |
|
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") |
|
@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. |
|
@megawubs https://nl.aliexpress.com/item/4000298926256.html?cv=47843 @Smanar |
Ha ? are you sure of that ? "rest API plugin" then uncheck the case on the popup. |
|
Got it unchecked, going to test it now. /edit: |
|
You can pair it, and disable the switch after, or just let it already paired. |
|
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. 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. |
|
This is no documentation with the device ? even in chinese ? |
|
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)
|
|
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. |
|
I think I spoke too soon, after some time they started automatically turning off again ... |
|
I have perhaps an idea for tuya, but not sure It's that, because I have the ame bug on different brands. |
|
I'm not sure what log types need to be activated and what version (I'm running 2.5.88), but my switch is identified as What I noticed is that after pairing it works fine for a few hours and then randomly switches to the auto-off behaviour. |
|
You haven't the GUI ? You have not line starting with "Tuya debug X" when using a button ? |
|
As most of the people out there I'm using a Conbee 2 via the Home Assistant addon. More specifically HASS.io on a PI 4. I do have access to the deCONZ app via VNC but can't copy paste from there and finding something in there is a pain. I can use docker logs from the host, but I need to enable the logs in the addon's config. I have enabled |
|
I have just installed two new switches: https://www.aliexpress.com/item/4000298926256.html |
|
I did some further investigation... 01:30:39:194 DeviceAnnce of LightNode: 0xbc33acfffeedfc0f Permit Join: 0 |
|
Workaround: |
|
I noticed the same behaviour with the latest firmware, I left the switch unpaired for a week, yesterday I paired it again, after that I rebooted my PI and it was gone, so did a re-pair (altho the switch lights showed that it was paired) and it showed up again in Phoscon and HA with the names that I previously set and it's been working fine since. Usually it takes up to 2h for the auto-off behaviour to kick in, but now it seems to be fine for the past 20h. |
|
Ha yesssss, thx a lot, It help so much, I was totaly lost, no idea at all.
But BTW what is this feature .... |
|
Hello, I have TS0011 and TS0012 switches and They turned off after 2 minutes no matter if I use home assistant or the button to turn the light on. After this procedure everything works ok: It seems like there’s two versions of this switch coming from AliExpress. The TS0011 appears to turn off by itself after two minutes after being paired for the first time with ZHA. To get it to function correctly after pairing the first time, press and hold the switch for 10s to enter pairing mode and then press ‘Add Devices Via This Device’ in your Zigbee Coordinator in Home Assistant. After that, it should function correctly. Original source: https://zigbee.blakadder.com/Lonsonho_X711A.html |
|
Same here. |
|
And have you done the procedure ? |
|
Yes, but if i disable api i cant use Tradfri 5 button remote, so it's not a solution for me. |
|
Disable the API ? If you disable the api, you will loose all your devices, not only the tradfri remote. |
|
I tried to pair it again, after pairing. Next i tried this on ZHA, stil same problem. I just moved to z2mqtt and its gone. |
I've got both models: 1- and 2- gang. No issue with paring any of them on compiled version. |
|
1,2,3 gang work for me |
|
As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs. |
|
As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again. |
|
The compiled version from an above repo seems working fine. Thank you @Smanar for your efforts! It took about 1h to compile the ARM version on my RPI. So if anyone is interested to reuse the compiled library — just unzip the attached file into Hope the changes will be merged to master soon. |
Can this also be done in HassIO? |
I never used HassIO because my HA setup is too heavy for RPI. Technically there should be no problems with this if your deCONZ instance is running under ARM CPU (directly on RPI or in docker). You only have to locate the file to be replaced, replace it and make sure no official updates will be overwriting it for now. |
|
I have updated the code some days ago, because there was ugly code. Hoping for a validation for next version |
|
@Smanar, |
|
hee ... seriously I realy don't know what to say. You can make a try, just edit the DDF for the device, and use a basic one with absolutely nothing in the tab "binding", then make a "hot reload". https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/DDF-cheat-sheet |
|
@Smanar I tried doing what you mention. I did a DDF where I removed the one binding, hot reloaded and I still get the incorrect behavior of turning off after 2 minutes. IDK perhaps what I'm doing is incorrect, or perhaps it's not loading the DDF.
Anyways, why is this change being held up even if it can be done with DDF? I mean, it sounds like it's a fix that everyone would be benefit from and not custom behavior. |
|
Right, and for me the DDF is good. You have tried with "strict" mode too ? (the DDF mode in "control") |
|
@Smanar thanks for answering. I put it into "strict" mode too and still I haven't had positive results. Again, perhaps I'm doing something wrong and perhaps it's worth if you can check it too. Moving forward with the patch is also a good option :) |
|
I don't have device with this issue, and DDF is relay obscure for me (and it move too much for the moment) |
|
Hi @mpeterson, did you get luck with DDF ? I'll have a go myself as soon as I have a bit of time, but would appreciate any hint ;) |
|
I'm having the same problem. How can I rectify? |
|
It seem it can be solved with creating a DDF, but no comfirmation cf #5118 |
|
3a-zigbee-switch.groovy |
|
Have answered here #5118 (comment) |
|
I managed to create a working DDF for the 2 gang switch, you can find it below. To overcome this problem, I would modify the DDF and save it as a new file containing the device name (here I hope this helps you all. {
"schema": "devcap1.schema.json",
"manufacturername": "_TZ3000_fvh3pjaz",
"modelid": "TS0012",
"product": "TS0012",
"sleeper": false,
"status": "Gold",
"path": "/devices/tuya/ts0012.json",
"subdevices": [
{
"type": "$TYPE_ON_OFF_LIGHT",
"restapi": "/lights",
"uuid": [
"$address.ext",
"0x01"
],
"fingerprint": {
"profile": "0x0104",
"device": "0x0000",
"endpoint": "0x01",
"in": [
"0x0000",
"0x0001"
],
"out": [
"0x0006"
]
},
"items": [
{
"name": "attr/id"
},
{
"name": "attr/lastannounced"
},
{
"name": "attr/lastseen"
},
{
"name": "attr/manufacturername"
},
{
"name": "attr/modelid"
},
{
"name": "attr/name"
},
{
"name": "attr/swversion"
},
{
"name": "attr/type"
},
{
"name": "attr/uniqueid"
},
{
"name": "state/alert",
"description": "The currently active alert effect.",
"default": "none"
},
{
"name": "state/on",
"description": "True when device is on; false when off.",
"refresh.interval": 5
},
{
"name": "state/reachable"
}
]
},
{
"type": "$TYPE_ON_OFF_LIGHT",
"restapi": "/lights",
"uuid": [
"$address.ext",
"0x02"
],
"items": [
{
"name": "attr/id"
},
{
"name": "attr/lastannounced"
},
{
"name": "attr/lastseen"
},
{
"name": "attr/manufacturername"
},
{
"name": "attr/modelid"
},
{
"name": "attr/name"
},
{
"name": "attr/swversion"
},
{
"name": "attr/type"
},
{
"name": "attr/uniqueid"
},
{
"name": "state/alert",
"description": "The currently active alert effect.",
"default": "none"
},
{
"name": "state/on",
"refresh.interval": 5
},
{
"name": "state/reachable"
}
]
}
]
} |
New DDF for Tuya 2 gang wall switch TS0012. Proof tested. Has been working in my home for a month now. Fix to dresden-elektronik#3693.
New DDF for Tuya 3 gang wall switch TS0013. Based on TS0012 2 gang Fix to dresden-elektronik#3693.
New DDF for Tuya 1 gang wall switch TS0012. Based on TS0012 2 gang switch. Fix to dresden-elektronik#3693.
|
Nice, thx for the information ^^.
If I m right it happen when a device have no DDF at all, mean deconz was not able to create a basic one with defaut value. But I can't explain why it happen. |
|
Hi all, I've done the procedure through ssh on port 22222, installed nano, new DDF file in /usr/share/deconz/devices/tuya/ after reboot addon and ha it shows the default DDF and now when i am trying to load the custom one it fails to load it. |
|
Just to note that on windows I did as smanar recommended. |
|
Ha ? |
and others
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
The text was updated successfully, but these errors were encountered: