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

Alexa - Climate device is unresponsive. #107475

Closed
berniecruz opened this issue Jan 7, 2024 · 23 comments · Fixed by #107673
Closed

Alexa - Climate device is unresponsive. #107475

berniecruz opened this issue Jan 7, 2024 · 23 comments · Fixed by #107673

Comments

@berniecruz
Copy link

The problem

Alexa says that climate device is unresponsive but the device is being triggered. The rest of my devices have no issues.

What version of Home Assistant Core has the issue?

2024.1.2

What was the last working version of Home Assistant Core?

2023.12.4

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

Amazon Alexa

Link to integration documentation on our website

https://www.home-assistant.io/integrations/alexa/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Jan 7, 2024

Hey there @home-assistant/cloud, @ochlocracy, @jbouwh, mind taking a look at this issue as it has been labeled with an integration (alexa) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of alexa can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign alexa Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


alexa documentation
alexa source
(message by IssueLinks)

@jbouwh
Copy link
Contributor

jbouwh commented Jan 7, 2024

Can you provide some more information about the climate entity (see developer tools) and what command you are trying to give using Alexa?

@jbouwh
Copy link
Contributor

jbouwh commented Jan 8, 2024

Please can you share the state of the climate entity at the moment it is failing and you request it turns on (before and after):

https://my.home-assistant.io/redirect/developer_states/

@jbouwh
Copy link
Contributor

jbouwh commented Jan 8, 2024

Just dis some tests with a single and double setpoint thermostat, but I cannot find any issues in reporting the mode, current or target temperature.

@Franvcg
Copy link

Franvcg commented Jan 9, 2024

I'm having the exact same problem, Alexa says my device (climate entity) is not responding and yet the AC unit is turned on or off as expected. On mine, the entity's state at the moment just before I ask for it to be turned on is "off" and then "cool" just after. The exact opposite happens when I ask to turn it off.
Asking alexa to change the climate entity's temperature (mine is in celsius) works just fine with no comment regarding device's responsivity.

@jbouwh
Copy link
Contributor

jbouwh commented Jan 9, 2024

Please can you share the state of the climate entity at the moment it is failing and you request it turns on (before and after):

https://my.home-assistant.io/redirect/developer_states/

My question for the device status still stays.

@KC-inDomus
Copy link

Please can you share the state of the climate entity at the moment it is failing and you request it turns on (before and after):
https://my.home-assistant.io/redirect/developer_states/

My question for the device status still stays.

Same here.
Happens with every climate.* entities - despite from the status and the integration that generate them. Does the same with a Tado climate, a template climate and so on. The funny things is that everything works fine, the command is executed. But alexa simply says that the device "did not respond".

@jbouwh
Copy link
Contributor

jbouwh commented Jan 9, 2024

Without the entity state I cannot try to reproduce anything.

@KC-inDomus
Copy link

Without the entity state I cannot try to reproduce anything.

[climate.living] state: auto/off/heat

@jbouwh
Copy link
Contributor

jbouwh commented Jan 9, 2024

Without the entity state I cannot try to reproduce anything.

[climate.living] state: auto/off/heat

Please can you share the state of the climate entity at the moment it is failing and you request it turns on (before and after) using:

https://my.home-assistant.io/redirect/developer_states/

@berniecruz
Copy link
Author

berniecruz commented Jan 9, 2024

The Alexa app displays "device is unresponsive" after issuing the command to turn on or off the entity. But the entity will trigger. When you refresh the app, it returns to its normal state and it shows ON or OFF. There is a momentary disconnection of the Alexa app to HA.
I restored the old core. I will update when I get home and do what you are asking.

@berniecruz
Copy link
Author

The state shows OFF or COOL only upon issuing the command. The state did not show unavailable but Alexa still responds "hmm guest room ac is not responding".
off
cool

@Franvcg
Copy link

Franvcg commented Jan 9, 2024

Please can you share the state of the climate entity at the moment it is failing and you request it turns on (before and after):
https://my.home-assistant.io/redirect/developer_states/

My question for the device status still stays.

I told you the exact status of the climate entity according to your link, it's either cool or off, exactly as shown on @berniecruz screenshot.

@jbouwh
Copy link
Contributor

jbouwh commented Jan 9, 2024

The state shows OFF or COOL only upon issuing the command. The state did not show unavailable but Alexa still responds "hmm guest room ac is not responding". off cool

Thanks, can you copy/past post the attributes please?

@berniecruz
Copy link
Author

hvac_modes: off, heat_cool, cool, heat, fan_only, dry
min_temp: 16
max_temp: 30
target_temp_step: 1
fan_modes: auto, low, medium, high, quiet
swing_modes: off, both, vertical, horizontal
friendly_name: Guest Room AC
supported_features: 41
current_temperature: 24
temperature: 22
fan_mode: auto
swing_mode: off

@KC-inDomus
Copy link

hvac_modes: heat, off
min_temp: 15
max_temp: 31
target_temp_step: 0.1
current_temperature: 18.3
temperature: 21
hvac_action: heating
friendly_name: Cuccia gatto
supported_features: 1

@Franvcg
Copy link

Franvcg commented Jan 9, 2024

Mine is:

hvac_modes: heat, cool, dry, fan_only, auto, off
min_temp: 16
max_temp: 30
target_temp_step: 1
fan_modes: medium, min, max, auto
swing_modes: off
current_temperature: 26
temperature: 21
fan_mode: min
hvac_action: off
swing_mode: off
econo: off
turbo: off
quiet: off
light: off
filters: off
clean: on
beep: off
sleep: -1
last_on_mode: cool
swingv: off
swingh: off
fix_swingv: off
fix_swingh: off
friendly_name: Ar Condicionado
supported_features: 41

@KC-inDomus
Copy link

KC-inDomus commented Jan 9, 2024

I suppose the issue lie on Climate component integration and not Alexa component integration. If the latter, each single entity should have problems, which is not. I advise checking Climate code's latest changes.

@Franvcg
Copy link

Franvcg commented Jan 9, 2024

I agree, asking for alexa to change temperature (instead of turning on/off) works fine, also controlling other components (including asking to turn on/off) with alexa such as RGB lights also works fine.

@carferrer
Copy link

Same problem with mqtt climate device.

@jbouwh
Copy link
Contributor

jbouwh commented Jan 9, 2024

Thnx for all the state updates. It helped me to find the issue. I'll open a PR to fix the regression.

@KC-inDomus
Copy link

KC-inDomus commented Jan 9, 2024

Thnx for all the state updates. It helped me to find the issue. I'll open a PR to fix the regression.

thanks to you 👍

@carferrer
Copy link

State details mqtt climate:

hvac_modes:

  • "off"
  • cool
  • heat
    min_temp: 16
    max_temp: 32
    target_temp_step: 1
    fan_modes:
  • Bajo
  • Alto
    current_temperature: 24
    temperature: 25
    fan_mode: Bajo
    friendly_name: Aire Salón
    supported_features: 9

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
6 participants