I am running NodeRed v3.1.0 on a RPi. I have a flow that uses the node-red-dashboard:ui_audio node to output text-to-speech. I had been working as it should. However, I have noticed lately that Chrome browser will not speak, whereas it used to and I have not changed anything. I have tried the Chrome app on W10, W11,Linux Mint and MacOS and none of them will speak the output of this node. On the other hand, I have tried Firefox, Safari and Microsoft Edge and all of them DO speak. SO, I am thinking something is broken in the nodes ability to speak through Chrome. Has anyone else noticed this? Does anyone know how to fix this or how I would contact the author of this node to find out more about this?
Thanks...Arnie
Have you checked the browser dev-tools console for any errors?
I do know that Google have a tendency to tighten up security settings from time-to-time, often before other vendors.
Of course, if you have Microsoft Edge (or Vivaldi, Brave, ....), you have essentially the same browser as Chrome - just without the Google spyware they have a tendency to include.
