I’ll have a look tonight and see whether my button has these sort of topics; can’t say I had thought to look at the zigbee2mqtt mqtt structure before.
Percent 20 percent ftw
Same here - family and I find it quiet funny that Google sounds a 22|bit|percentage|bonkers|22. 
Can’t see anything that has caused this in the changes but I’m sure the top guys will sort it out soon enough.
Have you tried it without a template and just hardcoded text, to see if it is actually the template that’s the issue? TTS to my Alexa devices is working fine via the custom Alexa Media Player notify platform with and without templates, so it may be that it is nothing to do with the template and something to do with the Google TTS platform (if that’s what you’re using).
Edit: Found this issue on GitHub:
I updated to 113.1 on sunday successfully. Everythings running smooth. But I do not have any issue logs since then. Even failing scripts during development haven’t been added. Yesterday I had an entry in homeassistant.log regarding a depricated configuration entry but it wasn’t shown in the frontend. Has anything been changed in handling of log entries?
Yeah thanks. Saw the GitHub issue.
Haven’t tried it without template yet, but seems the issue is clear, so I’ll wait it out for now.
Hope the devs fix this per 113.3 …
I can confirm that also without template the issue is there…
Interestingly enough, typing any text at Google Translate and hitting the speaker symbol yields the expected result 
https://translate.google.com/#view=home&op=translate&sl=en&tl=nl&text=This%20is%20a%20test
I usually wait till the weekend to do an update so if I need to fix anything I’ve got plenty of time. This time, however, I did the update on a weeknight and everything broke! HA was starting up but nothing was loading. To make matters worse my wife’s sister was staying with us for a couple of days. I lost a lot of WAF when they couldn’t turn the tv or the lights on!
I narrowed it down to my sensor.yaml file and then went through them all one at a time. The problem ended up being that I had a sensor with a scan interval set to .1 (dont ask). Have now changed it to:
scan_interval:
milliseconds: 100
and all is good again!
Thanks for all your hard work devs
That is a ridiculously fast scan interval.
Yea I know, maybe I’m going about it the wrong way but its the only way I can get my light switch as responsive as I want it!
its a press switch (not toggle) connected to a digital input of a relay module set up like this:
- platform: snmp
name: "Living Room Switch"
host: 192.168.1.100
port: 161
community: public
baseoid: 1.3.6.1.4.1.42505.8.2.1.1.7.0
scan_interval:
milliseconds: 100
then an automation which switches the lights when the state switches from 0 to 1. The faster the scan interval the less I have to hold the press switch down!
Feel free to correct me. I’m pretty new.
And I actually can’t reproduce here if I trigger the tts.google_translate_say service manually (on 0.113.0) 
That’s because the issue was introduced in 0.113.2.
That seems to do the trick.
Thats good because I didn’t like having to create the automation through the GUI just to get the ‘new style’ of event.
Interesting indeed - I just upgraded to 0.113.2 and was able to reproduce, rolling back to 0.113.0 let the issue disappear again (after cleaning the TTS cache / trying with another message in my case)
Here’s how you can roll back -
- Open homeassistant in google chrome
- Right-click on the web-page.
- Choose “Inspect” from the menu
- Select the “Console” tab in the window.
- Paste the following in the console window:
document.querySelector('home-assistant').hass.callApi('post', 'hassio/homeassistant/update', {version: '0.113.1'})
1 Like
I have this service inside an automation:
- service: tts.google_translate_say
entity_id: media_player.sonos
data_template:
message: >-
Temperatura esterna {{ states('sensor.temperature_158d0001b95f60') }} {{ state_attr('sensor.temperature_158d0001b95f60','unit_of_measurement') }}
Which was working ok since i upgraded HA to the last 0.113.2. Now my sonos doesn’t spell anymore the correct temperature. What is changed about this in 0.113.2?
EDIT: I found it’s a bug introduced in 0.113.2 so waiting for a fix!
1 Like
There are several other lighting technologies available that are responsive without requiring a 100 ms polling cycle (they require no polling because they are event-based). What was the attraction to a switch employing the SNMP protocol?
Out of curiosity, how many SNMP-based lights are being polled and what brand of device uses this protocol?
This is my 50 cents on the topic. Hope that it will help someone.
New Home Assistant Automations and Scripts Running Modes Explained
VIDEO 
https://youtu.be/I2Ogsq3LJhM
BLOG POST 
https://peyanski.com/home-assistant-automations-and-scripts
Big credits to @pnbruckner for his very important clarification about the running modes and HA front end.
@pnbruckner you can skip to this time to see my credits to you - https://youtu.be/I2Ogsq3LJhM?t=667
Cheers,
Kiril
Anybody else experiencing an overall slowdown of the Home Assistant, mostly noticeable on the lovelace interface?
I’ve been noticing that roughly 4 hours after a restart the Home Assistant starts to slow down, the lovelace interface takes a long while to load and sometimes some sections don’t even load at all. The automations go out of sync and those that are triggered in short time intervals (like every 10 seconds) start to overlap.
When I go into the templates screen to test and it takes about 3 to 5 seconds for any changes to the template to resolve.
I also start noticing a lot of warnings in the home-assistant log:
2020-07-29 13:34:34 WARNING (MainThread) [homeassistant.components.automation] Kitchen Motion Daylight Automation: Already running
2020-07-29 13:34:36 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
2020-07-29 13:34:40 WARNING (MainThread) [homeassistant.components.sensor] Updating systemmonitor sensor took longer than the scheduled update interval 0:00:30
2020-07-29 13:34:42 ERROR (zeroconf-Engine-5445) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/aiopylgtv/webos_client.py", line 373, in consumer_handler
while not closeout_task.done():
UnboundLocalError: local variable 'closeout_task' referenced before assignment
2020-07-29 13:35:21 WARNING (MainThread) [homeassistant.components.automation] match sensor to boolean: Already running
2020-07-29 13:35:28 ERROR (MainThread) [homeassistant.components.upnp] Timeout fetching Internet Home Gateway Device data
2020-07-29 13:35:31 WARNING (MainThread) [homeassistant.components.automation] match sensor to boolean: Already running
2020-07-29 13:36:03 WARNING (MainThread) [homeassistant.components.automation] match sensor to boolean: Already running
The more time elapses the worse the slowdown gets
2020-07-29 15:15:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.monitor_del_servidor_http_interno is taking over 10 seconds
2020-07-29 15:15:02 WARNING (MainThread) [homeassistant.helpers.entity] Update of calendar.family_calendar_importants is taking over 10 seconds
2020-07-29 15:15:06 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.solar_production is taking over 10 seconds
2020-07-29 15:15:07 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.wol_nas is taking over 10 seconds
2020-07-29 15:15:07 WARNING (MainThread) [homeassistant.helpers.entity] Update of weather.openweathermap is taking over 10 seconds
2020-07-29 15:15:09 WARNING (MainThread) [homeassistant.helpers.entity] Update of light.cama_de_la_recamara_principal is taking over 10 seconds
2020-07-29 15:15:09 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.spotify_totoromty is taking over 10 seconds
2020-07-29 15:15:11 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.cpu is taking over 10 seconds
2020-07-29 15:15:11 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.processor_use is taking over 10 seconds
2020-07-29 15:15:16 WARNING (MainThread) [homeassistant.components.automation] match sensor to boolean: Already running
2020-07-29 15:15:17 WARNING (MainThread) [homeassistant.components.automation] timeout ticker: Already running
2020-07-29 15:15:17 WARNING (MainThread) [homeassistant.components.sensor] Updating command_line sensor took longer than the scheduled update interval 0:01:00
2020-07-29 15:15:17 WARNING (MainThread) [homeassistant.components.calendar] Updating google calendar took longer than the scheduled update interval 0:01:00
2020-07-29 15:15:18 WARNING (MainThread) [homeassistant.components.sensor] Updating rest sensor took longer than the scheduled update interval 0:00:30
2020-07-29 15:15:18 WARNING (MainThread) [homeassistant.components.switch] Updating wake_on_lan switch took longer than the scheduled update interval 0:00:30
2020-07-29 15:15:18 WARNING (MainThread) [homeassistant.components.weather] Updating openweathermap weather took longer than the scheduled update interval 0:00:30
2020-07-29 15:15:19 WARNING (MainThread) [homeassistant.components.light] Updating flux_led light took longer than the scheduled update interval 0:00:30
2020-07-29 15:15:19 WARNING (MainThread) [homeassistant.components.media_player] Updating spotify media_player took longer than the scheduled update interval 0:00:30
2020-07-29 15:15:20 WARNING (MainThread) [homeassistant.components.sensor] Updating ios sensor took longer than the scheduled update interval 0:00:30
2020-07-29 15:15:20 WARNING (MainThread) [homeassistant.components.sensor] Updating cpuspeed sensor took longer than the scheduled update interval 0:00:30
2020-07-29 15:15:21 WARNING (MainThread) [homeassistant.components.sensor] Updating systemmonitor sensor took longer than the scheduled update interval 0:00:30
Didn’t experience this in 0.112.4