SilverCrest Smart Button (LIDL) _TZ3000_rco1yzb1 TS004F #6107
Comments
|
I also got this today. Could it possibly be the same as this one, just in a different case? Anyway, I paired it in with Phoscon and it creates a switch and a light. When I press the button, all the lights that exist in Phoscon are turned on without me even linking a light. |
|
Same Problem here. All devices turning on or off on button press. |
|
I have the same problem. I connected the silvercrest smart button via phoscon, then the button switches ALL the lights on and off. |
|
jep i have the same problem with two of these switches |
|
It does not only switch lights on all at once. |
|
Hello can you try this DDF And add the device in the list in the button_maps.json file (you will found it in the "devices" folder too) It will not solve the groupcast issue yet, but will make the state/buttonevent working. |
|
Just a little feedback while I was playing around with these switches (it's my first time I got into adding own DDFs): I am using the docker container deconzcommunity/deconz on armv7. Afterwards I restarted the deCONZ container and added the first switch (out of 3) via the Phoscon WebUI. It seemed to work and surprisingly the switch didn't turn on/off all devices. I could also connect the switch to OpenHAB and see the I added the second switch and it behaved like others mentioned before, turning all devices on/off. The I always get 2 devices/sensors per switch in the REST API (from "32": {
"config": {
"battery": null,
"group": "65520",
"on": true,
"reachable": true
},
"ep": 1,
"etag": "32c5f268b3f58453a3b9297e4a33bf83",
"lastannounced": null,
"lastseen": "2022-06-23T20:31Z",
"manufacturername": "_TZ3000_rco1yzb1",
"mode": 1,
"modelid": "TS004F",
"name": "TS004F",
"state": {
"buttonevent": null,
"lastupdated": "none"
},
"type": "ZHASwitch",
"uniqueid": "2c:11:65:ff:fe:c7:22:3c-01-1000"
},
"33": {
"config": {
"on": true,
"reachable": true
},
"etag": "63eead54a5881bba7838b0f0157c286f",
"lastannounced": null,
"lastseen": "2022-06-23T20:31Z",
"manufacturername": "_TZ3000_rco1yzb1",
"mode": 1,
"modelid": "TS004F",
"name": "Switch 33",
"state": {
"buttonevent": null,
"lastupdated": "none"
},
"type": "ZHASwitch",
"uniqueid": "2c:11:65:ff:fe:c7:22:3c-01-0006"
}Hope this helps in some way. If something needs to be tested, I'm glad to help. |
|
You have a "core mix" ....
This one is created with the legacy code, and it use the group feature
This one is created by the DDF code and don't use the group feature. I can't explain what happen :
|
|
I had some more time to tinker around with the switch. I'll try to answer your questions first:
I deliberately checked the Github Issues before I've done anything with the switch. I found this issue and added your DDF and button mappings before adding the device to my network. Today I double checked if the files are in the correct locations and also checked their filesystem permissions. Seems fine on my side.
As I have no deep insights in the internal functionality of deCONZ, I cannot answer this.
Same as above. I could never replicate this state. The only state I get now is the switch turning on all devices on single press and turning them off again on double press. There are still two switch devices present und
Today I started a "fresh" run. I made sure all switches are removed and only worked with one switch for now. I indeed discoved an odd looking entry in the Phoscon light section called Dimmer switch 11.
The REST API returns this: "11": {
"etag": "2d46612476b0191fd423f93a6aa82932",
"hascolor": false,
"lastannounced": null,
"lastseen": "2022-06-26T18:39Z",
"manufacturername": "_TZ3000_rco1yzb1",
"modelid": "TS004F",
"name": "Dimmer switch 11",
"state": {
"alert": "none",
"on": false,
"reachable": true
},
"swversion": null,
"type": "Dimmer switch",
"uniqueid": "2c:11:65:ff:fe:c7:22:3c-01"
}In the PhosconUI section for switches there is one entry called TS004F.
The REST API on the other hand still returns two entries und the "22": {
"config": {
"battery": null,
"on": true,
"reachable": true
},
"ep": 1,
"etag": "57102ed75a55a901072f4f4850ecead1",
"lastannounced": null,
"lastseen": "2022-06-26T18:39Z",
"manufacturername": "_TZ3000_rco1yzb1",
"mode": 1,
"modelid": "TS004F",
"name": "TS004F",
"state": {
"buttonevent": null,
"lastupdated": "none"
},
"type": "ZHASwitch",
"uniqueid": "2c:11:65:ff:fe:c7:22:3c-01-1000"
},
"23": {
"config": {
"on": true,
"reachable": true
},
"etag": "e122d2f722548697213bfe23dba502aa",
"lastannounced": null,
"lastseen": "2022-06-26T18:39Z",
"manufacturername": "_TZ3000_rco1yzb1",
"mode": 1,
"modelid": "TS004F",
"name": "Switch 23",
"state": {
"buttonevent": null,
"lastupdated": "none"
},
"type": "ZHASwitch",
"uniqueid": "2c:11:65:ff:fe:c7:22:3c-01-0006"
}I don't know if it helps, but here is a log from the deCONZ Container instance while adding the switch and some general device info:
|
|
Maybe it's a bit off topic but I've switched to Zigbee2MQTT, which supports this button quite well as well as all my other devices that gave me a lot of trouble when using deCONZ. |
|
Reopened as development is still in progress. |
|
I will give this link at Manup, he already have some idea for this issue. And we have
And ofc only the first one is needed. |
|
The problem with switching ALL devices on/off is a known problem and already discussed here: This solution worked for me. |
|
But he have another issue. |
|
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. |
|
@Smanar Are there any updates on the ddf/legacy code issue? I tried repairing the device with the latest update, but unfortunately it hasn't worked and still produced 3 items. |
|
Yep #6196 With using 0x1000 instead of 0x0006, but better to wait for next version, I think it can solve so much issue. |
|
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. |
|
Just wanted to leave a qick update: One thing I noticed upon setup is, that initially the button still somehow triggers the state of all devices (ON/OFF), but not actually turning them ON (single-press) or OFF (double-press). This means Phoscon reports that all lights were turned on in browser UI, but in fact the real light is still off (or on). In this state the button does not report any |
|
So the triple press enable/disable the broadcast mode ? |
|
I think you can compare it with the Moes smart knob _TZ3000_4fjiwweb. See manual page 2 and 12. |
|
I searched up the manual online. Unfortunately it seems only to be available in German: Manual (German). It mentions the following (Page 13): Functions:
Additionally it mentions the following about the 3x press: (Page 14)
|
|
ha ok, it s the scene mode. So we are using only the onoff cluster, I think in the other mode it use the Scene cluster 0x0005, it s for that deconz is not detecting buttonevent. |
|
BTW except the long press, the DDF is working ? (to know if I can make a PR with it) with deconz version > 2.18 ? |
|
Yes, it's working for single and double press as long as I don't switch accidentally to the scene mode (3x press). Long press is the only issue. I've been using it for the last couple weeks with no further issues on single and double press. |
|
Thx , have made a PR (some others users ask for this device) |
|
BTW, I have added the missing battery support, if you can test it ? |
|
Battery seems to work after re-pairing the switch: "48": {
"config": {
"battery": 90,
"on": true,
"reachable": true
},
"etag": "1dd0a1451df6241cbf838bb31dcf9691",
"lastannounced": null,
"lastseen": "2022-09-08T16:50Z",
"manufacturername": "_TZ3000_rco1yzb1",
"mode": 1,
"modelid": "TS004F",
"name": "Switch Livingroom",
"state": {
"buttonevent": null,
"lastupdated": "none"
},
"type": "ZHASwitch",
"uniqueid": "2c:11:65:ff:fe:c7:22:3c-01-0006"
}Some comments above you mentioned that |
|
Yep, right, I will correct it, better to use the good value. |
|
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. |
|
I have only Battery entry after connecting it with phoscon Web App, anyone else has this Problem? |
|
IDK how work HA, but take a look direclty in the API, phoscon / help / API Information / sensors / Device_ID |
There is no entity for the button, please read https://www.home-assistant.io/integrations/deconz/#remote-control-devices. |
|
I am new to github, i assume if the PR is merged it will be release someday? |
|
@thealkly I guess it will be released with one of the next HA releases. Until then, you can still use the button with the deconz_event trigger as explained in the link I posted above. |
|
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. |
|
Hello. I have no file caled "buton_maps.json" so i create one and add the text to it. So i edit the group entry on cluster info from 0x0000 to 0x0002 an hit exec. I use FHEM for home automation and here this button will not work if i edit the group. On/off will work, dimmer will not work. |
|
Hello, what is your deconz version ? And I m not sure to understand what you are doing, the issue is about a switch, so you are puting light in the device group ? You are using phoscon or FHEM to do that ? Switch group are special, and can't be deleted, you can add a light in a switch group, but the reverse will not work. There is no dimmer feature on plugs ? |
|
Hello. I think my Version is to old. I can not update because my system is old too (Stretch I think?) I was thinking the group numbers are only numbers. Good to hear that the new version will work. |
|
On thing, please look on the title: The right Name is |
Smanar
changed the title
|
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. |
|
Unfortunately, the "problem" with the different modes has not yet been fixed, or it has not been merged?! I noticed that when I change the mode, a single press "turns on" all the lamps, a double press turns all the lamps "off" again. The lamps themselves do not react, the status only changes in Phoscon / deConz. I'm not sure about this comment: #6107 (comment) And what's about this comment: #6107 (comment) |
|
Hello, If I m right the device work only in one mode, and not the scene one. About the first comment yep the code is here https://github.com/dresden-elektronik/deconz-rest-plugin/blob/master/button_maps.json#L1293 "modelids": ["_TZ3000_ee8nrt2l", "_TZ3000_ygvf9xzp", "_TZ3000_t8hzpgnd", "_TZ3000_wkai4ga5", "_TZ3000_bi6lpsew", "_TZ3400_keyjhapk", "_TYZB02_key8kk7r", "_TZ3400_keyjqthh", "_TZ3400_key8kk7r", "_TZ3000_vp6clf9d", "_TYZB02_keyjqthh", "_TZ3000_peszejy7", "_TZ3000_qzjcsmar", "_TZ3000_owgcnkrh", "_TZ3000_adkvzooy", "_TZ3000_arfwfgoa", "_TZ3000_a7ouggvs", "_TZ3000_rrjr1q0u", "_TZ3000_abci1hiu", "_TZ3000_dfgbtub0", "_TZ3000_rco1yzb1", "_TZ3000_gbm10jnj", "_TZ3000_5e235jpa", "_TZ3000_sj7jbgks", "_TZ3000_w8jwkczz", "_TZ3000_dziaict4", "_TZ3000_famkxci2", "_TZ3000_itb0omhv", "_TZ3000_tzvbimpq", "_TZ3000_mh9px7cq"], About the second comment, was because on older deconz version, the core create more than entry for this device. If I m right long time it was solved. |
Device
https://www.lidl.de/p/silvercrest-smart-button-mit-magnetischer-wandhalterung-zigbee-smart-home/p100339621
Screenshots
The device shows up as a connected switch but is not available in the device editor.
The text was updated successfully, but these errors were encountered: