Fix best_practices.markdown formatting typo (#36687)

This commit is contained in:
louis-pre 2025-01-03 11:33:13 -08:00 committed by GitHub
parent 42607fd107
commit ca7fc591a7
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -58,7 +58,7 @@ English has pretty simple grammar rules, but there are languages where definite
Assist leverages domains to define the proper verbs for the action being taken (for example, turning on/off a `light`, or a `fan`, opening/closing a `cover` with a `door` `device_class`, opening/closing a `valve` or locking/unlocking a `lock`.).
It might not bother anyone to have a `switch.main`_valve in the UI instead of a valve, but you cant ask Assist to open the main valve if the main valve is a switch. If it was a `valve.main_valve`, then the former sentence would have worked without a hitch.
It might not bother anyone to have a `switch.main_valve` in the UI instead of a valve, but you cant ask Assist to open the main valve if the main valve is a switch. If it was a `valve.main_valve`, then the former sentence would have worked without a hitch.
To prevent this, you can use either the [Change device type of a switch integration](/integrations/switch_as_x/) or create virtual entities using [template](/integrations/template/) entities or Generic X (e.g. [generic thermostat](/integrations/generic_thermostat/)).