Possibly a lame question, but how/where can I see which version of the Weather Forecast Blueprint I currently have installed?
I can see on GitHUB that the latest is 2025318, but which version do I have?
Iāve found that if you use Google Generative AI (Gemini) instead of ChatGPT, it doesnāt pronounce the *'s. However, it does spell out km/h instead of saying Kilometers per hour. Iād love to get that corrected.
Put an addition near the top of your prompt reminding the LLM that
You are servicing a voice interface and should NOT use markdown under any circumstances it produces confusing output when read aloud.
Itās not perfect but it calms it down a lot. The problem is the llm is generating markdown text elements and your TTS isnāt filtering them (itās a known with the default piper)
Hey, overall Iām loving the large LLM weather blueprint. Iām using OpenWeather Map as the source data and Google Generative AI for the LLM side.
It works fairly well, but it persists in spelling out KM/H instead of speaking ākilometres per hourā. Iāve tried adding āpronounce km/h as kilometres per hourā to the default four time prompts, but the output is unchanged.
Also, if one uses ChatGPT, there are many colons and asterisks that get pronounced. Iāve not found a way to stop that when using Chat GPT.
How does one edit the base prompt that the script sends to the LLM?
Iām experienced with HA, but quite new to this LLM stuff as I just built a few Wyoming Satellites a few days ago.
Also, many thanks for all you do!!
You have multiple things. Spelling kmh is different than markdown. We can clamp markdown with one statement because itās all part of one construct.
The default prompt is the one inside settings on the configure button under the integration. My markdown clamp os literally the third thing listed.
Alternately you can use a different TTS enginenthat filters it
The km/h would require a different tack and wonāt be universal to LLMs. You could try donāt abbreviate (as a generalization) in the prompt but itās probably too broad.
That said both are technically out of the scope of Fezā blueprints. So if you want to chase it down youāll want to open a separate thread.
Makes sense⦠Iāve updated the description to contain āPronounce km/h as kilometres per hour.ā and that fixes it nicely. Rather than fight with markdown, Iāll use the Goggle Generative AI as it understands that markdown should not be pronounced.
Greatly appreciated!