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?
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
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)
-----------------------------------------------------------
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?
