Sounds like you are hitting the same issue I am: https://github.com/home-assistant/core/issues/39873
2 Likes
Where did you see the error message about the depreciated login?
chrome developer tools under the console tab and you can see the failures under the network tab
1 Like
Can anyone get a condition like this to work?
conditions:
- condition: numeric_state
entity_id: sensor.test
below: input_number.temperature_test_threshold
Because I cant. Issue:
In my case it was solved upgrading firmware… There was an update in my Shelly EM.
Check it… And good luck! 
1 Like
Wow guys, you’re really cooking on full gas, first 114 and now 115. Amazing releases of features.
Hi;
After updating from 112 to 115 my Xiaomi Switch does not work any more with Home Assistant.
But the behavior is curious: If I click the button the state doesn’t change, but if I see the info for this entity the change is registered.
Can anyone shed some light on this?
trigger:
- platform: event
event_type: xiaomi_aqara.click
event_data:
event_id: binary_sensor.switch_xxxxxxxxxxxx
click_type: single
Thank you very much for your help!
Thx, a restart thit the trick.
i’m running into an issue with mysensors
before the update everything was running fine, its still is but in my Log i have these errors
Logger: mysensors
Source: /usr/local/lib/python3.8/site-packages/mysensors/init.py:67
First occurred: 10:21:36 PM (1 occurrences)
Last logged: 10:21:36 PM
Not a valid message: too many values to unpack (expected 5)
and
Logger: mysensors.message
Source: /usr/local/lib/python3.8/site-packages/mysensors/message.py:58
First occurred: 10:21:36 PM (1 occurrences)
Last logged: 10:21:36 PM
Error decoding message from gateway, bad data received: 14;255;3;0;22;28;1;1;0;16;1
there were more but i tried to restart and updated to 0.115.2 but still see these errors
nothing changed from my end, but is there a place i should look into?
thanks
Yes the entities with, say, a click state, have been done away with and replaced with events.
1 Like
I have found the issue causing the extra cpu load allthough there was nothing in the logs when turning on debug logging for homeassistant.event.
I had one template sensor which was using {{ states | ... }}. Once I removed that the cpu load is back to the 0.114 level. Wasn’t even using that sensor 
so not missing anything here. Thanks for the quick help.
Thanks nickrout;
Can you explain me how to configure my automations with the new feature?
How can I do to click the button and trigger an action?
Thank you again!
An event is also available as a trigger when using the UI automation editor.
1 Like
Improve performance of accessing template state by bdraco · Pull Request #40323 · home-assistant/core · GitHub should make these much faster in 0.116.
1 Like
I have read the documentation you post.
I think I am already configuring my automation as an event.
I don’t find anything that I could be doing wrong.
My trigger has the following form:
trigger:
- platform: event
event_type: xiaomi_aqara.click
event_data:
event_id: binary_sensor.switch_xxxxxxxxxxxx
click_type: single
See my post here:
2 Likes
I have the sonos integration, but when I click on the browser I just get " Local library not found."
Is there something that I need to do in order to get the media into HA?
That trigger code works for me. Are you sure the issue isn’t elsewhere in that automation?
I use zigbee2mqtt, so slightly different, but this is how I use the button in an automation.
# XIAOMI BUTTON #
- alias: Xiaomi Button
initial_state: True
trigger:
platform: mqtt
topic: 'zigbee2mqtt/0x00158d000155d403'
condition:
condition: template
value_template: "{{ 'single' == trigger.payload_json.click }}"
action:
service: light.toggle
entity_id: light.steps
1 Like