# Google's text to speech node - stuck with weird problems
**URL:** https://discourse.nodered.org/t/googles-text-to-speech-node-stuck-with-weird-problems/98819
**Category:** General
**Created:** [24 August 2025 21:12 UTC](https://discourse.nodered.org/t/googles-text-to-speech-node-stuck-with-weird-problems/98819 "2025-08-24T21:12:00Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [24 August 2025 21:12 UTC](https://discourse.nodered.org/t/googles-text-to-speech-node-stuck-with-weird-problems/98819/1 "2025-08-24T21:12:00Z")
Node:
`node-red-contrib-tts-ultimate`
I've got some stuff with TTS messaging happening and most of the time it works fine.
_Though thinking about it, there are things happening in the past which may be included with this problem._
Does anyone use it?
Any _limits_ on how big a message you can send it?
```auto
Today's forecast for Ashfield. temperature now 13.9 degrees and stable to 14.1 degrees. Winds West South Westerly at 5 knots veering to West North Westerly at 3 knots. Cloud coverage mostly cloudy decreasing to clear
```
and
```auto
Today's forecast for Ashfield. temperature now 18.6° and decreasing to 12°. Winds Southerly at 6 knots veering to West North Westerly at 5 knots. Cloud coverage mostly cloudy increasing to overcast
```
The second one works, the first one errors.
(Side note)
Realised it was a bit old so tried to update THAT node.
Didn't.
Log (part)
```auto
-----------------------------------------------------------
2025-08-24T21:12:16.826Z Install : node-red-contrib-tts-ultimate 3.0.1
2025-08-24T21:12:16.817Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --omit=dev --engine-strict node-red-contrib-tts-ultimate@3.0.1
2025-08-24T21:12:31.531Z [err] npm error code ERESOLVE
2025-08-24T21:12:31.532Z [err] npm error ERESOLVE could not resolve
2025-08-24T21:12:31.533Z [err] npm error
2025-08-24T21:12:31.535Z [err] npm error While resolving: node-red-contrib-ui-led@0.4.8
2025-08-24T21:12:31.535Z [err] npm error Found: node-red-dashboard@3.6.0
2025-08-24T21:12:31.535Z [err] npm error node_modules/node-red-dashboard
2025-08-24T21:12:31.535Z [err] npm error node-red-dashboard@"~3.6.0" from the root project
2025-08-24T21:12:31.535Z [err] npm error
2025-08-24T21:12:31.535Z [err] npm error Could not resolve dependency:
2025-08-24T21:12:31.535Z [err] npm error peer node-red-dashboard@"^2.23.3" from node-red-contrib-ui-led@0.4.8
2025-08-24T21:12:31.535Z [err] npm error node_modules/node-red-contrib-ui-led
2025-08-24T21:12:31.535Z [err] npm error node-red-contrib-ui-led@"~0.4.8" from the root project
2025-08-24T21:12:31.535Z [err] npm error
2025-08-24T21:12:31.535Z [err] npm error Conflicting peer dependency: node-red-dashboard@2.30.0
2025-08-24T21:12:31.535Z [err] npm error node_modules/node-red-dashboard
2025-08-24T21:12:31.535Z [err] npm error peer node-red-dashboard@"^2.23.3" from node-red-contrib-ui-led@0.4.8
2025-08-24T21:12:31.535Z [err] npm error node_modules/node-red-contrib-ui-led
2025-08-24T21:12:31.535Z [err] npm error node-red-contrib-ui-led@"~0.4.8" from the root project
2025-08-24T21:12:31.535Z [err] npm error
2025-08-24T21:12:31.535Z [err] npm error Fix the upstream dependency conflict, or retry
2025-08-24T21:12:31.535Z [err] npm error this command with --force or --legacy-peer-deps
2025-08-24T21:12:31.535Z [err] npm error to accept an incorrect (and potentially broken) dependency resolution.
2025-08-24T21:12:31.537Z [err] npm error
2025-08-24T21:12:31.537Z [err] npm error
2025-08-24T21:12:31.537Z [err] npm error For a full report see:
2025-08-24T21:12:31.537Z [err] npm error /home/pi/.npm/_logs/2025-08-24T21_12_18_626Z-eresolve-report.txt
2025-08-24T21:12:31.550Z [err] npm error A complete log of this run can be found in: /home/pi/.npm/_logs/2025-08-24T21_12_18_626Z-debug-0.log
2025-08-24T21:12:31.577Z rc=1
```
I'm confused.
Do I need to update all mentioned nodes first?
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [24 August 2025 21:36 UTC](https://discourse.nodered.org/t/googles-text-to-speech-node-stuck-with-weird-problems/98819/2 "2025-08-24T21:36:19Z")
# HUGE UPDATE
After a bit of digging...
# Seems messages are _LIMITED_ to 33 words.
Any more and it will error.
So just to let you know.
Seems that is/WAS the problem.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [25 August 2025 08:26 UTC](https://discourse.nodered.org/t/googles-text-to-speech-node-stuck-with-weird-problems/98819/3 "2025-08-25T08:26:26Z")
The npm warning is probably because you are running out of date versions of the led node and the dashboard. I suggest you update all the nodes that are out of date.
---
### Author:  [@StrongTown](https://discourse.nodered.org/u/StrongTown)
#### Post date: [29 August 2025 11:58 UTC](https://discourse.nodered.org/t/googles-text-to-speech-node-stuck-with-weird-problems/98819/4 "2025-08-29T11:58:19Z")
FWIW, I’ve been using Cepstral TTS for over 5 years now and find it to be incredibly realistic and efficient. There is no limit on the # of words you need spoken.
You can test voices on their site ([https://www.cepstral.com/](https://www.cepstral.com/)) or even install a voice for your own system for testing however to use the voice without beeps costs only ~$30 (one time) for a life time license. There are many voices to choose from.
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [29 August 2025 12:28 UTC](https://discourse.nodered.org/t/googles-text-to-speech-node-stuck-with-weird-problems/98819/5 "2025-08-29T12:28:57Z")
I'll maybe look into / at it one day.
I (alas) am kinda getting used to the one voice.
---
### Author:  [@StrongTown](https://discourse.nodered.org/u/StrongTown)
#### Post date: [29 August 2025 14:15 UTC](https://discourse.nodered.org/t/googles-text-to-speech-node-stuck-with-weird-problems/98819/6 "2025-08-29T14:15:17Z")
If you do, try out the ‘Callie’ voice. That’s the one I’ve been using. I think it’s their best.
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [12 September 2025 14:16 UTC](https://discourse.nodered.org/t/googles-text-to-speech-node-stuck-with-weird-problems/98819/7 "2025-09-12T14:16:11Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.