-
Notifications
You must be signed in to change notification settings - Fork 361
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
Add support 090615.switch.akpro4 #1547
Comments
I am unable to use 'action' as an automation trigger, and I am not sure where the issue lies. |
The lumi.remote.b286opcn01 can use action as a trigger condition, with multiple options such as button_1_single, button_2_single, and more available for selection.
I want to implement this method as a trigger condition. |
I don't understand your question. Above is all the information you need to use the automation. |
The 090615.switch.akpro4 cannot use action as a trigger condition like the lumi.remote.b286opcn01. |
You needs to collect debug logs for this device. |
Debug Log:
|
Please show info (from notification) for your device |
Debug log:
|
|
I see in the log that you are receiving events from this device. I don't understand what exactly you're missing. |
Sorry, my question caused a misunderstanding. I am using the 090615.switch.akpro4 as a wireless switch. For example: For the device lumi.remote.b286opcn01, Action can be selected as a trigger condition in automation.
However, the 090615.switch.akpro4 does not have the Action option.
Using Action as a trigger condition allows for simple execution of automation, so I would like to use this method as the trigger condition for automation. Thank you for your attention! |
Ah. It's because you using custom (not built-in) converter. You should write state triggers. They always works fine. |
Thank you! Do you have any plans to update xiaomigateway3 in the near future? |
I'm not sure. Lots of other projects. Just on the queue for now. |
The text was updated successfully, but these errors were encountered: