TTS gone in HA/MSR?
-
Hi!
Since a couple of days, I'm not able to use the TTS in MSR (HA). I haven't done anything else but updated HA. Don't know if that's the source of the problem. Have this happened to anyone else, or is it just me?
When I searched in the HA community, there seems to be a croud of people having this issue - but they often refers to Alexa, so they may not have my problems.I took a snapshot of a MSR instance, where it shows that the TTS is missing. I use to have 4 different TTS engines to choose from - now I have none. Am I alone in this?
-
Mine is working fine. You don't give any versions of anything, and that's always helpful, especially when you are asking questions in the context of having just upgraded something in your environment from one version to another. You don't say if you've tried launching the action from the Home Assistant UI, which is also a good starting point. You didn't mention if you've restarted MSR after upgrading Home Assistant, which is also a good idea (read: required).
Any problem like this, your first job is to make sure the service is working at all on the hub/platform. Then work toward MSR from there.
-
Mine is working fine. You don't give any versions of anything, and that's always helpful, especially when you are asking questions in the context of having just upgraded something in your environment from one version to another. You don't say if you've tried launching the action from the Home Assistant UI, which is also a good starting point. You didn't mention if you've restarted MSR after upgrading Home Assistant, which is also a good idea (read: required).
Any problem like this, your first job is to make sure the service is working at all on the hub/platform. Then work toward MSR from there.
@toggledbits
My bad. It's working fine in HA (2021.8.6), when I launch it from "Developer Tools" - "Service", but not in MSR (latest-21221-4a447cb). I have restarted MSR and did a hard refresh in the browser, Chrome (Version 92.0.4515.131). I tried both the Windows bare metal installation and on my Home Assistant blue (Odroid). Same result. I first thought it was a fault in HA, but it must be something with MSR. -
I'm not having any issues with TTS on 2021.8.6, either Google or Microsoft as the engine.
Have you checked the entity ID, and that the canoncal entity ID of your media player matches what you've put into
local_hass_devices.yaml? -
I'm not having any issues with TTS on 2021.8.6, either Google or Microsoft as the engine.
Have you checked the entity ID, and that the canoncal entity ID of your media player matches what you've put into
local_hass_devices.yaml?@toggledbits
Whoops... I forgot that when I updated the last time, I didn't copy my edited my local_hass_devices.yaml. Now I've taken my old edited copy, and now it works! Thanks once again! Sorry for the inconvenience.
/Fanan -
When you upgrade, you don't need to create entire new directories and structures. Just unzip the package files over the existing directory. The release package does not include the
storageorconfigorlogsdirectories, so these will not be overwritten and thus preserved. The only thing recommended beyond that is to runnpm upgrade --no-save(but I usually announce when that is required, otherwise, it's optional). -
By the way, I would also note that 2021.8.6 is not a currently supported version of Hass, and you probably have a warning about that in the UI. There may be other issues, since breaking changes to their APIs are not unusual.
-
By the way, I would also note that 2021.8.6 is not a currently supported version of Hass, and you probably have a warning about that in the UI. There may be other issues, since breaking changes to their APIs are not unusual.
@toggledbits do you recommend us to wait with the HA upgrades in the future? Until it's supported by MSR?
-
Any time you upgrade to a version that isn't supported, you run the risk that a change to the Home Assistant APIs won't be handled properly by the HassController class in MSR. In the last six months, there have been two changes that have changed their API significantly enough to cause issue, and in one of those two cases, it was total shutdown.
