-
Notifications
You must be signed in to change notification settings - Fork 506
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New device support request: Linkind 1 key Remote Control / ZS23000178 #2321
Comments
I read somewhere, that if the search in Phoscon is active and the basic cluster gets read, some more Information are shown. I did that with this button and the output of the basic cluster changed: Can somebody point me in the right direction, what has to be done to get this Button in phoscon / iobroker? Maybe I can do that on my own, but I can't find any documentation how to add a new device. Thanks! |
It seems this issue is resolved or otherwise inactive. If it is not, please re-open! |
Hi @Mimiix, edit: I can't reopen this issue |
@madbrain- i can ;) @SwoopX Is there anything that is missing? |
Thanks :-) |
Power configuration cluster would be helpful as well. Later on, we'd require some additional debug output from deconz for finetuning... |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
What can I do to help with the integration? Can I find somewhere a developer documentation? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I would also be interested in seeing support for this. |
Can someone compile the rest plugin and test? |
I can try it on the weekend. Great to hear some news! Thank you very much! :-) |
I tried to compile the plugin. I did the following: I assume the plugin got loaded? How can I check that? But I can't see the device in the Phoscon App nor in the rest api. |
I assume your deconz is still working, that's the check since you've overwritten your previously installed version of the plugin.
Yes, because it is not supported. I just asked if you can do it, not to do it 😉 |
Yes, everything is working, as far as I can notice until now.
okay :-) |
Hey @madbrain- Haven't forgotten about you, but was busy to finish a new feature. So, I got some code prepared for you to test now, but it will require some doings on your end. Here are the steps to download and compile my version:
Then, start Phoscon sensor search and pair the button. Make sure to has been properly reset before. When the device has paired, do all button push variations the device should support. Note their order and ideally, what the button press should have done, if known. |
Thank you @SwoopX , |
Hi, @SwoopX |
Ah, crap. I blew it. Anyway, we can make it on point with that info. Thanks! So, it has single, double and long press...? |
has no double, just single and long press |
Hi thank you all for the work. My deconz is working again. The instruction manual of the button says it has on/off/dimming: |
@madbrain- @mralex07 This here implies that there's more commands the device can issue:
As per feedback provided here: #2321 (comment) , the debug output translates into the following: Off command - no button map for: ZBT-DIMSwitch-D0001 ep: 0x01 cl: 0x0006 cmd: 0x00 pl[0]: 000 -- first short click on button In that sense, I'd at least expect to see in addition: ep: 0x01 cl: 0x0008 cmd: 0x01 pl[0]: 001 -> Move down command Can you guys please double check the logs and try to force the move down? Maybe the manual gives hints on that. Please also take double press + hold into consideration. |
Hi, @SwoopX double press: double press + hold (on second click): |
Hi - I have this device, It is detected in phoscon, but I'm unable to assign any actions to it - it seems I can only get it's battery level. Pressing the button does generate activity in debug log: /usr/bin/deCONZ --dbg-info=2 >debug.log Is there some instructions I can look up to find out if I am doing something wrong? I'm on version 2.09. Graeme |
@mathieg2 phoscon needs to add support for it too. You can use it with the rest api |
@SwoopX, I don't understand: this is a one-button device, but deCONZ exposes two buttons for it?! |
What should it be then? Twice short, long and hold on button 1?
|
Hi,
thank you for this product, I really love it. Works great until now.
How can I add this device to Phoscon? It gets recognized in deconz:
Model ZS23000178
FCC ID 2ASHKZS23000178
https://www.amazon.de/dp/B07V53MLNT/ref=cm_sw_em_r_mt_dp_U_x3WhEbP0WFG06
bought it for about 10 € a few weeks ago
Here is a Log, that may be related to a push on the button:
22:38:59:921 APS-DATA.indication srcAddr: 0x04f8, srcEp: 0x01 dstAddrMode: 1, profile: 0x0104, cluster: 0x0006, lqi: 151, rssi: -72
But if I use the phoscon-app and search for new switches it doesn't get recognized. I assume, it has to be added to the API or soething like this?
Maybe I could help. I'm very interested in the Zigbee Bridge, maybe I could help to integrate the switch.
Let me know, if you need more information!
Thanks!
regards, Thomas
The text was updated successfully, but these errors were encountered: