fix is being prepared
this is the main issue with the current (well, also the former) area-card: no way to have the user select any of the entities, be it camera, alert/sensor classes or the controls.
we really would need user selectable in/excludes on all of those options.
Can we please get a more likely use-case example for the " Let Assist ask a question!" function? I’d imagine most people are going to want Voice to ask a question which demands a simple yes or no answer and yet the example in the blog is a complicated one that many will struggle to translate.
I tried creating a simple question for a yes or no answer to be asked through my ESP32-box but unfortunately the question came up on the screen as text instead of a TTS output, then very quickly disappeared… Not a great start. A more user friendly example would be very beneficial.
@RenatoY that specific issue sounds like a Zigbee device firmware quirk bug which if so need to be dealt with in the upstream ZHA Device Handlers (a.k.a. zha-quirks) library that Home Assistant’s Zigbee Home Automation integration uses, so you might might want to consider also reporting it as ZHA device handler support request (if it does not already has a quirk that zha uses) or a bug report (if your device already has a quirk that ZHA uses) via a new issue there too so that community will se it. Check that put here (and in them refering those to each other) → GitHub - zigpy/zha-device-handlers: ZHA device handlers bridge the functionality gap created when manufacturers deviate from the ZCL specification, handling deviations and exceptions by parsing custom messages to and from Zigbee devices.
Hi, thanks, but in an scale from 0 to 10, what I understood from your comment is very close to zero 
Do I need to report the bug on that link you posted rather than to Home Assistant?
Thanks for changing the example automation. I just tried to import the blueprint via the My link but got:
I’m guessing it’s due to the blueprint not existing yet? Surly we need to also test that during beta…
It would still be good to have a YAML example of the yes/no automaton though.
@RenatoY Yes you should also submit an issue to that GitHub repository as well, but if that should be a ”bug report” or a ”device support request” depends if your device is currently using a ”quirk” or not in the Zigbee Home Automation integration (because if it is not then it should be a ”device support request” instead of a ”bug report”). You might better understand the underlyibg concept of quirks as ZHA device handlers (also known as Zigbee device translators and converters) if you read this guide → Zigbee Guide: How-to add/setup local custom ZHA Device Handlers (also known as ”quirks”) in the ZHA integration
AND WE’VE REACHED THE END!
Please head to the release blog thread to continue any feedback regarding this release.Thanks, y’all! 🫰🏻
