You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure how this could be accomplished in the schema, but it would be helpful to prevent having both a t_set_number and a t_set_output, because behaviour in that case is undefined and an update to one does not change the value in the other. (That wouldn't make sense: there is no way in which an output can report back.)
Right now this will likely result in a warning about duplicate defines, which is something but not great. This should be validated at the Python stage if at all possible.
The text was updated successfully, but these errors were encountered:
* Add sm_active (Summer Mode) and dhw_block (Domestic hot Water blocking) Switches
* Update README.md with new switches
---------
Co-authored-by: PxPert <[email protected]>
cadavre
pushed a commit
to cadavre/esphome-opentherm
that referenced
this issue
Apr 26, 2024
I'm not sure how this could be accomplished in the schema, but it would be helpful to prevent having both a
t_set_number
and at_set_output
, because behaviour in that case is undefined and an update to one does not change the value in the other. (That wouldn't make sense: there is no way in which an output can report back.)Right now this will likely result in a warning about duplicate defines, which is something but not great. This should be validated at the Python stage if at all possible.
The text was updated successfully, but these errors were encountered: