Try to run
hass --script check_config
Performance improvement for motion sensor now merged to the main branch. Also added some error checking
Have you tried to understand the error message? It says where the mistake is.
yes, in event_data … but don’t see anything wrong in it …
hints for you…
it means event_data is under automation. It should be under trigger. check your indentation
damn, I never get it right at first try. Thanks, now no error.
But it does not perform the play/pause on the media_payer …
p.s. question: in front end it is signaled the click or the hold (double click is not, and simple short click I think not … just waiting for 1,5second I would say it shows the check mark)
since a click happens to fast, it doesn’t make sense to update the front end just to show a flash
event data, correct the event_daata indentation
alias: Turn on bedroom Lights when click
trigger:
platform: event
event_type: click
event_data:
entity_id: binary_sensor.switch_158d00010f42a5
click_type: single
action:
service: light.toggle
entity_id: group.lights_chambre
github still says last change 4 days ago in master branch :\
My bad, forgot to sync
thanks ! is there a way to poll temp/hygro value from sensors every 5 seconds ? my automations won’t work reliably when usin temp max/min
Not quite sure why your automation won’t work but there’s a good reason to disabled polling.
es I understand that. So now it shows the HOLD, correct?
You can better have a look at the history graph then the current state since it goes to fast.
Just to double-check, some of you are running on 0.36.1 and this component is working fine?
yes 0.36.1 and no errors
@rave as far as I know you got 2 gateways right?
Did you figure out how they communicate? Is is via WiFi or ZigBee?
Is one going in a concept of ‘primary mode’?
And if it’s ZigBee, do they have to be in radio-range of each other to work/not interfere?
For those who have this issue, I guess it was related for having the plug switch registered in xiaomi gateway but it was turned off. After turning it on, the errors are gone!
I believe Hub to hub communication is through wifi since the hub itself never initiate the joining process. And really, the only time they’ll need to communicate is when you setup an automation in its app across multiple hub
In essence, they’re 2 different hub with its own devices.
For anyone having issues with initial setup and pairing the hub to your wifi network try temporarily disabling 5ghz Wifi on your router and rebooting. This fixed my problem with a TP-Link router.
I knew my hub was OK as I did a test run on my workplace network when I received it and paired all my sensors. When I got home I was unable to get it to connect to my home wifi, connection would time out every time. I tried changing wifi channels, reinstalling the app, using different devices, an android emulator, even different power points.
Once I disabled the 5ghz it connected straight away. I have experienced this same problem with Google Home.