Skip to content
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

emulated_hue + alexa + 0.35.2 #5054

Closed
splunty opened this issue Dec 23, 2016 · 3 comments
Closed

emulated_hue + alexa + 0.35.2 #5054

splunty opened this issue Dec 23, 2016 · 3 comments

Comments

@splunty
Copy link

splunty commented Dec 23, 2016

Home Assistant release (hass --version):
0.35.2

Python release (python3 --version):
3.4.2

Component/platform:
emulated_hue + alexa

Description of problem:
Domains light, script and scene are exposed to Alexa through emulated_hue. When running homeassistant 0.35.2, Alexa is able to discover and successfully use all three domains. But, when using script or scene, she responds with, "Sorry the device X is not responding. Please check its network connection and power supply."

This error does not happen using homeassistant 0.34.4. In this version, she responds with, "okay." In both versions, the scripts and scenes perform the correct functions.

Expected:

Problem-relevant configuration.yaml entries and steps to reproduce:

emulated_hue:
  type: alexa
  host_ip: 192.168.0.11
  listen_port: 8300
  expose_by_default: true
  exposed_domains:
    - light
    - script
    - scene

scene:
  - name: tv_led_scene
    entities:
      light.tv_led:
        state: on

homeassistant:
  customize:
    scene.tv_led_scene:
      friendly_name: TV LED
      emulated_hue_name: "TV Backlight"

Traceback (if applicable):

Additional info:

)

@badgerhome
Copy link

+1 I have exactly the same issue since upgrading.

@badgerhome
Copy link

Tested with this: 0206461 and is working.

@pvizeli
Copy link
Member

pvizeli commented Dec 29, 2016

Leave a comment

@pvizeli pvizeli closed this as completed Dec 29, 2016
@home-assistant home-assistant locked and limited conversation to collaborators Mar 30, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants