Wireless Scene Switch 3-gang Zigbee TS0043 _TZ3000_w8jwkczz #5552
Comments
|
It's normal. |
|
ok, will test the code as soon as there is an update. |
|
I think the next update will be a DDF file and need more time for battery switch (the code is not ready yet) |
|
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. |
|
Keeping issue alive. @Smanar Any updates on this? |
|
Nope, for the moment all PR are blocked. |
|
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. |
|
Keeping issue alive. |
|
Hi @Smanar Is there any timeline about this and is there anywhere I can follow updates about support for battery switches? I am asking so I can get an idea about when this issue will be tackled. |
|
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. |
|
Keeping this alive.. |
|
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. |
|
keeping this alive |
|
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. |
|
keeping this alive |
|
Hello. I think it's possible using DDF. https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/DDF-cheat-sheet Just select "edit DDF", and remove useless light entry, or just add a ZHASwitch one. If it don't work can you copy paste your DDF ? |
|
Hi @Smanar, Been busy, will try later today and let you know. Thanks! |
|
Hi @Smanar, I tried editing the DDF and removing the useless light entries, however they still show in Phoscon Web. Then I tried removing the lights from Phoscon Web but it removed the switch too. Not sure how to proceed. |
|
Are you using the GUI or text editor ? The easier way is reincluding the device with a working DDF, don't forget to set the status to "Gold" And yes it s something normal, you can't remove a "part of a device", it s all or nothing. |
|
I was using the GUI and I set it to Silver (but allowed silver DDFs). I just tested with status Gold and I have the same result. I also tried removing the device and adding it back after saving this DDF. Here's the final DDF: {
"schema": "devcap1.schema.json",
"manufacturername": "_TZ3000_w8jwkczz",
"modelid": "TS0043",
"product": "TS0043",
"sleeper": false,
"status": "Gold",
"path": "/devices/ts0043.json",
"subdevices": [
{
"type": "$TYPE_SWITCH",
"restapi": "/sensors",
"uuid": [
"$address.ext",
"0x01",
"0x0006"
],
"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": "config/battery",
"description": "The current device battery level in 0–100 %.",
"default": 0
},
{
"name": "config/on"
},
{
"name": "config/reachable"
},
{
"name": "state/buttonevent",
"description": "The last received button event."
},
{
"name": "state/lastupdated"
}
]
}
],
"bindings": [
{
"bind": "unicast",
"src.ep": 1,
"dst.ep": 1,
"cl": "0x0001",
"report": [
{
"at": "0x0021",
"dt": "0x20",
"min": 300,
"max": 2700,
"change": "0x00000001"
}
]
},
{
"bind": "unicast",
"src.ep": 2,
"dst.ep": 1,
"cl": "0x0001",
"report": [
{
"at": "0x0021",
"dt": "0x20",
"min": 300,
"max": 2700,
"change": "0x00000001"
}
]
},
{
"bind": "unicast",
"src.ep": 3,
"dst.ep": 1,
"cl": "0x0001",
"report": [
{
"at": "0x0021",
"dt": "0x20",
"min": 300,
"max": 2700,
"change": "0x00000001"
}
]
}
]
} |
|
So all seem fine for me ... |
|
Correct, the web interface still shows 1 switch and 3 light entries. Current deCONZ version: 2.15.03 I am using this docker image: deconzcommunity/deconz:latest
|
|
I m asking to other devs, Not sure at 100% the legacy code is bypassed by DDF, but the result is still strange for me. |
|
I restarted the container and noticed that the logs show that it is loaded:
Also, when I click Edit DDF on the switch I get this:
Phoscon Web still shows:
and
I also tried reverting the docker container to a version where I have no switch setup and restarting this whole setup, but it still gives this result. |
|
Phoscon will never show the correct result as they have to add support on their own. Please use the rest api and websocket to determine if the behavior is correct. |
|
He have give the API extract on the first post, with all json. For me it's realy an issue on DDF core. For me the legacy code is not enought by-passed. |
|
I checked the API to make sure and the extra lights are still listed:
|
|
I have also noticed that I am unable to get the button events (buttonevent is null). Prior to DDF I had changed the button_maps.json file (see here) in order to make it work. How does it work now with DDF? {
"config": {
"battery": 0,
"on": true,
"reachable": true
},
"ep": 2,
"etag": "72e466e434e9860936a90f40f4328e37",
"lastannounced": "2022-05-08T08:52:49Z",
"lastseen": "2022-05-08T08:52Z",
"manufacturername": "_TZ3000_w8jwkczz",
"mode": 1,
"modelid": "TS0043",
"name": "Switch 7",
"state": {
"buttonevent": null,
"lastupdated": "none"
},
"type": "ZHASwitch",
"uniqueid": "80:4b:50:ff:fe:06:9a:e6-02-0006"
} |
|
I m seing this PR #6021 I readly don't see what do the code but seem usefull according to description
|
|
Is this PR going to be included in the upcoming release 2.15.04? If so I will wait and test when this is out. |
|
Yep, it's already merged. |
|
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. |
Device
Front:
Back:
Screenshots
Switch 01
Basic
Power Configuration
On/Off
OTAU (Grey)
Time (Grey)
Shows nothing.
On/Off (Grey)
Switch 02
Power Configuration
On/Off
On/Off (Grey)
Switch 03
Power Configuration
On/Off
On/Off (Grey)
Attempt
I have attempted to imitate other code changes, such as this PR here and compiled, tested and prepared a commit here. The device buttons work. I see the correct codes when a call to the REST API is made. However, I still see 3 On/Off entries under Lights in Phoscon. The resulting json and screenshots are below:
Correct switch addition:
Incorrect light additions:
Environment and Other
The software runs on a Rasperry Pi 4b inside a docker container. To compile the change, the following Dockerfile was produced:
and this Dockerfile was used to test the change after libde_rest_plugin.so was compiled:
The text was updated successfully, but these errors were encountered: