Andrew J.Swan
Andrew J.Swan
> (Oh and I do think we should be able to deviate from the usual expectations, but we should at least be clear about what is different) Or at least...
> What was the main reason we didn't go for deprecating the current tts service? I also don't understand the reason, it's a simple and convenient method. The new option...
> Oh I mean the `tts.google_cloud_say` service. Ideally everyone should move to the other service. I also mean it, it was simple and convenient, the new service is a bit...
> the old `tts.google_cloud_say` should still work All integrations that migrated to GUI over the last 5 years retained full functionality, or had a warning that this or that would...
Not everyone is sending data to analytics, so why create another Issue when we have this?
I will not make changes to the documentation, I believe that this should be done by the one who made the change. In my opinion, PR policy is exactly this:...
Same with **BT Proxy in Shelly**, all entities have the status `Unavailable`. Although the integration itself found the washing machine, and shows the correct serial number. In the Shelly settings...
https://github.com/denysdovhan/ha-lun-misto-air/pull/14
> Looks like AppVeyor have nothing I looked through everything I could find, it looks like AppVeyor either deletes the status, or doesn't publish it, or there's some other problem....
I can't figure out how to check, GitHub shows that the PR check failed, but the badge still hasn't appeared. https://github.com/andrewjswan/esphome-config/pull/7 https://github.com/andrewjswan/esphome-config/pull/6