MastroPino
(Andrea Calabrò)
May 17, 2017, 7:59am
1725
Hi mates, can some one help me with this automation? I asked on another topic but no one, sadly, answered me
I’m trying to bind long press for dim+ an Yeelight but I can’t figure out
Here there is the link to my post for see the automation:
Hi there, can some one help me with this automation? I can’t really figure out
- alias: Comodino Andrea Dim+
trigger:
platform: event
event_type: click
event_data:
entity_id: binary_sensor.switch_158d00012641b4
click_type: hold
action:
service: light.turn_on
entity_id: light.comodino_andrea
data_template:
brightness: '{{states.light.comodino_andrea.attributes.brightness + 10}}'
Cheers!!!
flyguy
(Nigel Tee)
May 17, 2017, 8:36am
1726
How is it sensitive? It drops just a little when i switch off my lights. Then it doesnt update. So i waited for about 1 minute, switch my gateway light on and i can see the reading drops to 350 from 1190.
It seems that the light sensor does not update it’s values automatically until i switch the lights on or off.
flyguy
(Nigel Tee)
May 17, 2017, 8:37am
1727
yea. I think so too. they must have used the motion sensor to help the light sensor.
MastroPino
(Andrea Calabrò)
May 17, 2017, 9:21am
1728
Thanks for sharing!
One more think, for revert you can use:
iptables -nL --line-numbers
this will show the number of each records in every group
iptables -D FORWARD <record number>
Replace with the number of record that you want to remove
Cheers
hijinx
(James)
May 17, 2017, 11:22am
1729
Hey all. New gateway f/w is out 1.4.1_146
Any reports on new functionality? Or issues?
Mukund
(Mukund)
May 17, 2017, 11:36am
1730
Just updated the firmware and restarted ha. All good so far.
They just use it as a trigger to turn on the gateway light when there is motion and shut it off when no motion is registered for a few minutes.
I see that protocol version updated. Now it’s 1.0.7. I think they’ve changed something in status report message for sensors.My magnet sensor which was not opened for one month now reports status unknown. Maybe ghost issues was solved on FW level.
According to the developer of the firmware, this update should include a fix for that!
I imagined that, but I don’t have the motion sensor, but if I enable the automation without the sensor it just won’t work
Where did you get this info? Any link?
It seems is true. My magnet sensor reports close in heart_beats. And I don’t touch it for month or maybe more.
With the Aqara wireless wall switch (dual paddle) you can press both buttons at once. When i do that i see the following in the HASS logs
17-05-10 20:08:58 DEBUG (Thread-5) [custom_components.xiaomi] PUSH >> <Entity Wall Switch (Left)_158d000183f688: off>: {'dual_channel': 'both_click'}
17-05-10 20:08:58 DEBUG (Thread-5) [custom_components.xiaomi] PUSH >> <Entity Wall Switch (Right)_158d000183f688: off>: {'dual_channel': 'both_click'}
However when i try to hook into this event in HASS i have had no joy. See my attempt below
trigger:
platform: event
event_type: both_click
event_data:
entity_id: binary_sensor.wall_switch_left_158d000183f56e
I think support will need to be added at the component level to get this to work as it comes in on the dual_channel & not channel_0 or channel_1 like regular click do.
Nice to hear that it is working better! He told me that in an email. Xiaomi support redirected me to him when I reported the issue.
Yes, it forces you to select a motion sensor
Do you know whether it also resolves the issue where a closed sensor is reported open after power cut?
I don’t know that. He just said that he fixes ghost issues lol
syssi
May 18, 2017, 6:57am
1742
You’re right. There is no support for dual channel / both click events in the homeassistant component so far.
zajnic
(Zach)
May 18, 2017, 9:01pm
1743
Just sharing information, I have updated my gateway to 1.4.1_146.0141 and it’s still working fine with home-assistant.
1 Like
Hogesyx
(Hogesyx)
May 19, 2017, 5:13am
1744
Thanks man, was just about to ask that!