-
Notifications
You must be signed in to change notification settings - Fork 878
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
领普开关KS1PRO无四按键单独事件 #699
Labels
wontfix
This will not be worked on
Comments
在开发者工具里观察它的状态可以看到有个 自动化可以参考这样写: triggers:
- trigger: state
entity_id:
- event.linp_cn_blt_3_1************_ks1bp_click_e_5_1012
not_from: unavailable
not_to: unavailable
conditions:
- condition: state
entity_id: event.linp_cn_blt_3_1************_ks1bp_click_e_5_1012
attribute: 按键类型
state: 3 |
在事件上报的参数代表是哪个按键触发了事件,因此图2事件的历史中显示不同的颜色。按键事件“按键类型”参数的定义为:
即,按键事件携带参数等于1,表示“第一个按键触发了按键事件”。 |
感谢!原来如此
…---- 回复的原邮件 ----
| 发件人 | Li ***@***.***> |
| 日期 | 2025年01月26日 11:45 |
| 收件人 | ***@***.***> |
| 抄送至 | ***@***.***>***@***.***> |
| 主题 | Re: [XiaoMi/ha_xiaomi_home] 领普开关KS1PRO无四按键单独事件 (Issue #699) |
在事件上报的参数代表是哪个按键触发了事件,因此图2事件的历史中显示不同的颜色。按键事件“按键类型”参数的定义为:
[{
"value": 1,
"description": "First Button"
},
{
"value": 2,
"description": "Second Button"
},
{
"value": 3,
"description": "Third Button"
},
{
"value": 4,
"description": "Fourth Button"
}]
即,按键事件携带参数等于1,表示“第一个按键触发了按键事件”。
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the Bug / 描述问题
没有每个按键的单独事件,仅有全部按键都会触发的事件。
How to Reproduce / 复现步骤
配对领普KS1PRO
Expected Behavior / 预期结果
有四个按键的单独事件
Reproduce Time / 问题复现的时间点
任意时间
Home Assistant Logs / 系统日志
No response
Log Timezone / 日志时区
Shanghai
Home Assistant Core Version / Home Assistant Core 版本
2025.1.2
Home Assistant Operation System Version / Home Assistant Operation System 版本
14.1
Xiaomi Home Integration Version / 米家集成版本
v0.1.5b2
Additional Context / 其他说明
The text was updated successfully, but these errors were encountered: