-
-
Notifications
You must be signed in to change notification settings - Fork 32k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Alexa improvements #10632
Alexa improvements #10632
Conversation
This is awesome! 👍 |
@balloob (calling you out since I believe you own the skill) you should be aware of special requirements for |
Also we need a way to blacklist or whitelist entire domains just like Haaska. Unsure how best to do this since |
🤗 |
I noticed last night that when asking alexa to run a Scene, it worked, but it returned an error. But having that Scene triggered via a Routine, it worked without Alexa mentioning an error. I'll try to get some logs next time. |
Nice! For filtering, let's use the entity filter helper. (In a future PR) Configuration via the cloud. cloud:
alexa:
filters:
include_domains:
include_entities:
exclude_domains:
exclude_entities: This will make it easier for us in the future to make a UI for it 👍 Update: I initially included that we shouldn't use customize but put that under cloud config instead, but realized that we lose context. |
hass.states.async_set( | ||
'{}.test'.format(domain), 'off', { | ||
'friendly_name': "Test {}".format(domain) | ||
}) | ||
|
||
call = async_mock_service(hass, domain, 'turn_on') | ||
call = async_mock_service(hass, 'homeassistant', 'turn_on') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason we would change this to homeassistant
instead of directly calling the domain? Saves 1 service call -> faster.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh I guess it doesn't work for groups.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in this PR since time is of the essence for Alexa.
THIS IS A HUGE DEAL!!!!!! Thanks everyone! |
HUGE indeed....thanks a lot! |
Great work! We are still limited by Amazon by having us saying "Alexa, ask to...." and the manual dual configuration in both HA and ASK, right? This was/is the main reason for the great Haaska which is running great on the V2 api. Configure the lambda once and no need to ever touch it again. |
Very excited for this!! 😁 |
* Initial scene support * Initial fan support * ordering * Initial lock support * Scenes cant be deactivated; Correct the scene display category * Initial input_boolean support * Support customization of Alexa discovered entities * Initial media player support * Add input_boolean to tests * Add play/pause/stop/next/previous to media player * Add missing functions and pylint * Set manufacturerName to Home Assistant since the value is displayed in app * Add scene test * Add fan tests * Add lock test * Fix volume logic * Add volume tests * settup -> setup * Remove unused variable * Set required scene description as per docs * Allow setting scene category (ACTIVITY_TRIGGER/SCENE_TRIGGER) * Add alert, automation and group support/tests * Change display categories to match docs * simplify down the display category props into a single prop which can be used on any entity * Fix tests to expect proper display categories * Add cover support * sort things * Use generic homeassistant domain for turn on/off
* Initial scene support * Initial fan support * ordering * Initial lock support * Scenes cant be deactivated; Correct the scene display category * Initial input_boolean support * Support customization of Alexa discovered entities * Initial media player support * Add input_boolean to tests * Add play/pause/stop/next/previous to media player * Add missing functions and pylint * Set manufacturerName to Home Assistant since the value is displayed in app * Add scene test * Add fan tests * Add lock test * Fix volume logic * Add volume tests * settup -> setup * Remove unused variable * Set required scene description as per docs * Allow setting scene category (ACTIVITY_TRIGGER/SCENE_TRIGGER) * Add alert, automation and group support/tests * Change display categories to match docs * simplify down the display category props into a single prop which can be used on any entity * Fix tests to expect proper display categories * Add cover support * sort things * Use generic homeassistant domain for turn on/off
Hey guys! Got excited when the latest release of HA brought me to this page and I saw that there is fan support. I'm just a little confused as to how it functions? In the API/pi/lights, it seems that my fan is still listed as a dimmable light, I'm assuming this is not for the emulated hue and requires me to setup the lambda API? Can someone please point me to what I need to configure in order to ask Alexa to set my fan speed? Thanks a bunch!!
|
Description:
This is me trying to match the major functionality of Haaska and because @maddox begged and pleaded for me to do so 😝
Adds support for the following domains:
alert
automation
cover
fan
group
lock
media_player
scene
Adds customize attributes
alexa_hidden
- hide from Alexaalexa_name
- change name displayed/used by Alexaalexa_description
- change description shown in AlexadisplayCategories
alexa_display_categories
- set displayCategories, useful for things likemedia_player
(TV
/SPEAKERS
) orscene
(ACTIVITY_TRIGGER
/SCENE_TRIGGER
)Change description to entity ID instead of empty string so it looks better in Alexa app
Change manufacturer name from Unknown to Home Assiatant as per discovery recommendations and so it looks better in Alexa app
Minor grammar/readability fixes
Checklist:
If the code does not interact with devices:
tox
run successfully. Your PR cannot be merged unless tests pass