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
Full support of the Xiaomi Aqara Opple switch 3 bands? (ZbBridge) #9823
Comments
Please report |
Button 1 single click:
Button 1 double click:
Button 6 single click:
Button 6 double click:
(button 1: upper left, button 6: lower right) |
@s-hadinger The opple switches have 2 working modes. One is light steering with On/Off, Dimm Upp/Down and scenes control. The other mode is one HA mode with click click click. . . . |
It would be nice to catch all button actions (single, double, long click), then you can use them for whatever you like. For completeness I also have the logging of button 1 and 2 (top row), single and long click: Button 1 single click:
Button 1 long click:
Button 2 single click:
Button 2 long click:
|
This issue has been automatically marked as stale because it hasn't any activity in last few weeks. It will be closed if no further activity occurs. Thank you for your contributions. |
Hold on, it's still on my todo list. |
As MattWestb mentioned it, the switch has 2 operations mode. The default is the one you have and makes no difference between single/double/long presses. left click: turn off To read of change the operation mode, you need to use the following commands: Read:
Write:
Can you please confirm? If it works, I can add the |
In the coming changes, it will be: Read:
Write:
|
NICE Stephan !! I think I can investing in some OPPLE switches now then deCONZ was making them HA only and not possible shushing / changing operating modes of them so it was a braking deal for my :-)))) The Santa Claus is bringing good things this year in both soft (ware) and hard (ware) packages ! |
Zigbee support for Opple operation mode #9823
Yes clearing the backlog for Christmas |
Guten Rutsch :-)) |
Running dev version 9.1.0.2 of today: Initially I checked the mode with then tried to change to mode 1 with this gives:
Reading the mode with If you need any further info please ask. |
|
I already did that. Next result: Two button presses and then a ZbSend Write
|
I have no idea why the coordinator can't find a route. Can you copy the Zigbee map diagram (needs the latest dev version) |
Here is some web log level 3 information when sending the write instruction for the OppleMode.
|
12:45:10.190 RSL: tele/tasmota_21D76C/SENSOR = {"ZbReceived":{"0x9C27":{"Device":"0x9C27","OppleMode":0,"Endpoint":1,"LinkQuality":119}}} setting OppleMode error |
You need to press a button on the device to wake it up right before sending Also please try to read again the attribute at the end: Variant: |
Immediately after the pairing process I can send an OppleMode write command without errors. Log:
|
Me too, can write successfully, but cannot read successfully |
Thanks but I need |
Weblog 3, no problem
|
Aha, thanks. I had the ZCL type wrong. It was Please try with #10246 (wait for a few hours until the binaries are avaialble) |
successfully |
This looks really nice! Setting the OppleMode succeeds and a confirmation is sent:
Button clicks:
A triple click is presented as "click":3 - should this be "click":"triple" to be more consistent with the single and double clicks?
The "hold" and "release" actions have the "action" key. For further handling of the messages and creating rules it would be nice if they also have the "click" key. So "click":"hold" and "click":"release" Mr. Hadinger, thank you for your work. I'm very happy with the result. |
How can I make a rule like: on ZbReceived#0x5E59#click=single#Endpoint=3 do publish xxxxx/yyyyy endon ? |
You are right, this is inconsistent. I will also rename the attribute You cannot have a rule to match both click and endpoint. But in your case you can use So in your case the rule should be: |
Thank you. I'll have a play with this. |
Just to summarize and for documentation: Setting the Opple mode should be done right after pairing the device for best results. An operational device might give several MAC_INDIRECT_TIMEOUT error messages and mode setting will fail. So:
Done. |
Thanks for latest dev version. Do you want to maintain the 'Action' key? My suggestion: |
You are right, I'm moving all actions to |
Works a treat!
Thank you. |
PROBLEM DESCRIPTION
A clear and concise description of what the problem is.
Double click and long click (some keys) are not supported on the Aqara Opple switch 3 bands
ModelId: lumi.remote.b686opcn01
Double clicking the keys behaves as a single click.
Key 1 and 2 (upper row) do not respond to long click, they show as a single click.
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Backlog Template; Module; GPIO 255
:Backlog Rule1; Rule2; Rule3
:Status 0
:(Please use
weblog 4
for more debug information)TO REPRODUCE
Steps to reproduce the behavior:
Double click a key, long click key 1 or 2
using Sonoff ZbBridge with Tasmota 9.1.0
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
A correct MQTT message when double clicking a key or long clicking key 1 or 2
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered: