Troubleshooting on HA

[ernst77]

Sentece testing with python command works fine and I get good responses.

The issue is when intents go live on HA, none of the temperature intents work and I cannot figure it out why. Rooms are named appropriately, I have multiple temperature sensors and climate entities for all the rooms, still getting an error.

It says that my intent was not recognised, although it is fine when I tested before on this repo.

For English I at least see responses.

My question is:

Is there a way to debug/troubleshoot errors in HA. Like for what reason command is not being recognised or what is causing the error?

• Is the entity with given name is not being found?
• Area name is not found?
• Is intent not supported yet?
• Or actually intent was not being recognised?

Would love to have a log for the errors how we have with other add-ons/supervisor.

[synesthesiam]

If you have access to your configuration.yaml file, you can add these lines to see more info:

logger:
  default: info
  logs:
    homeassistant.components.conversation: debug
    homeassistant.components.intent: debug

Regarding the temperature intents, those haven't been implemented just yet. We may not need HassClimateGetTemperature since it can be covered with HassGetState, but that only works if you don't need to average temperatures, etc.

[zolakt]

Any update on this? I have the same issue with Croatian. None of the climate intents are recognized.

[tetele]

Temperature intents don't work in HA yet, in any language. You can use "what is ?" to use the regular HassGetState intent.

[zolakt]

The question was more, are there any updates on this, possibly an eta.

As for using "what is", yeah its possible, but would require some workarounds. On all of my thermostats the state is Off/Heat, and the current temperature is an attribute. So I can get the assistant to say if it's Off or Hear, but not the actual temperature. I would need to do sensor templates for each thermostat, or something. And I have a lot of thermostats

[synesthesiam]

@ernst77 There is now an Assist debugging tool in Dev Tools that should help.

@zolakt We don't have a target release for the intent just yet. A few open questions:

1. What to do when there are multiple temperature sensors in an area? Pick the first? Average? Highest/lowest?
2. If the thermostat is in the living room, but I ask for the kitchen temperature, do we fail or report the living room temperature?

[zolakt]

I see, valid points.

1. For me personally, the most flexible option would be to let the user choose the default thermostat for an area. To put a star on it, similar (UI-wise) to how you handle multiple Assist assistants. But I think in most cases either of first/average would work.

2. You mean if you don't have another thermostat in the kitchen, and you have only the one in the living room? It should be consistent with any other device. e.g. what happens now it you ask it to turn on the kitchen light which doesn't exist, and you only have your living room light setup in ha? If you do have a thermostat in the kitchen, I don't see why would it report the living room temperature

Maybe just having HassGetAttribute/HasSetAttribute, and smartly crafted aliases would be enough to get some decent control. At least as a stepping stone to more streamlined climate intents.

[Haennetz]

@synesthesiam are there a target release to implement the intents in HA now?