The Dapper Digital Butler: AI-Powered Daily Briefings

Blueprints Exchange
, , , ,
2

Excellent idea, excited to get this up and running!

Iā€™ll keep playing with it but right now with the conversation agent set to Ollama using Qwen2.5 model Iā€™m getting the "Extra keys not allowed @ data[ā€˜entity_idā€™]ā€ error you mentioned unfortunately.

3

Hi,
Thanks for that, Iā€™ll try with that on mine and see if I can sort that, are you running local?
Cheers
Mark.

4

Yes, local Ollama in docker on unRaid (HA also in docker). HA does talk to the Ollama instance (I can ask it to switch on the lights etc and that works OK).

5

Iā€™m getting this error as well, though Iā€™m using gpt in HAOS

6

Works well with Alexa speakers any way to make it work with Google speakers?

7

Maybe Iā€™m being dumb here, but I wanted to play the briefing over my Sonos speakers, but donā€™t have a notify for them, and donā€™t see an obvious work around like I can see for Alexa.Also, notify.notify was the notation that worked over the default for me.

8

Thank you for this. No matter what weather provider I select, I never see forecasts in the briefing. Is this expected?

1 Like
9

This blueprint was definitely vibe coded, so I donā€™t think the OP will be able to help you all debug it. It still contains boilerplate suggesting the OP could ask for money.

Buy Me a Coffee (Optional: Replace with your link or remove)

Screenshot from 2025-05-30 20-49-00

10

At least the working code is provided. I know another person here that teases the working code in YT videos then puts the code behind a paywall.
We are all entitled to ask to be paid, and we are also free to not use the service.

That said, you donā€™t know because this person has not responded which way they are working.

I have a buy me a coffee in my byline but have never asked for something before helping people. Itā€™s there because people have asked if they can support me or thank me for what I provided.

11

My first reply wasnā€™t very clear.

  1. I donā€™t think this blueprint works as written. As several users have mentioned, it throws the same extra data error mentioned in the troubleshooting section. The Troubleshooting section suggests opening a ticket with Home Assistant Core for what is more likely a bug in the blueprint.
  2. Further evidence that the blueprint hasnā€™t been proofread or tested? The footer contains a placeholder ā€œbuy me a coffeeā€ link- plus a note from the LLM to the author that this should be edited or removed before posting.

Letā€™s not encourage Home Assistant Community to be filled with AI Slop.

5 Likes
12

OK, understood.
Flag it then for the mods to pull it. I wasnā€™t picking up on that and I agreeā€¦

1 Like
13

AI-generated stuff should not be posted here. And I would suggest the same about a description. If someone cannot explain something in a simple and structured form (hence using AI for this) - they do not understand it. Sorry, did not want to offend anyone. But using AI for simple task is too much.

1 Like
14

Is the blueprint ai or the post? I havenā€™t tried it.

15

The post is AI 100%. The code is tons of jinja and maybe 40 emojiā€™s. If the OP is not able to answer questions, they didnā€™t write thatā€¦