tronikos
tronikos
Anyone else? For me the fix worked.
The mitigation is to un-expose all your scripts or just the problematics ones until Shulyaka submits a fix.
What are the benefits? Is the idea to point to the firmware files we built? It's not clear from the documentation whether the update happens fully automatically or the user...
I can fix it locally in my browser developer tools with this CSS: `word-break: break-all;` With it: Without it: But since this applies to many pages I don't feel comfortable...
If this ever gets implemented we should be careful to not cause #515
It's expected for some sensors to be updated more frequently than `econet_update_interval`, e.g. if you thermostat requests the datapoints. For my HPWH to limit the state changes I have: ```yaml...
You default `econet_throttle_interval` to `econet_update_interval`. I'm confused how this change will throttle updates. Won't updates still be sent every 30s by default? From https://esphome.io/components/sensor/index.html#throttle-average > For example a throttle_average: 60s...
This has been working fine for me, including Google Drive backups. Did you update the whisper addon to 2.1.2?
I'm using generic-x86-64. What's your architecture? Maybe model files follow a different pattern in different architectures? Or maybe supervisor treats the pattern differently in different architectures?
The `tts.cloud_say` is only available if you have set it up using yaml. This is the same with other TTS integrations, e.g. Google translate. You need to use `tts.speak`. Note...