This trend is getting really tedious to be honest, and it really shows the immaturity of the developers of not thinking things through. Honestly I never liked the concept of agile development. Developing at such a rapid pace with no time to think through good/solid design concepts may well be this project’s downfall.
They seriously need to have a stable branch for backwards compatibility, and only introduce breaking changes when they are finally ready to make it release 1.0.0. But who am I to complain? I’m not involved in the development at all. So really need to suck it up, and do all the necessary changes to make Google Assistant work again.
Note this walk-through is aimed for Home Assistant 0.80 and above.
Bits are bits - and your computer playback will always be perfect. Right?
Do not answer that - the above is a rhetorical question.
No matter how good your computers are - once in a while you may find your computer is running fine one minute but suddenly crash in the next.
The rarer this phenomenon occurs, the harder it is to troubleshoot the cause.
There are many reasons why a system may crash this way. More often than not, the main cause is simply badly written software. The less usual suspects are leaky motherboard capacitors, poor quality ‘Yumcha’ power supply and issues like over heating.
However, there is one component that is often overlooked, and this component can cause unpredictable system or software failure. This component is the main focus of this article, and you you probably already know what that is: