andig
Das ist grausig viel Logik. Warum muss der modbus Service etwas vin templates wissen? Die sollten ihm egal sein! Spannend ist allerdings die Modbus Config. Dafür hatte ich keine gute...
> Die zu ermittelnden Register lädt er aus dem Template zur Laufzeit, Die gehören in den Serviceaufruf. HA zeigt wie's geht: service: homeassistant/entities?uri={uri}&domain=sensor Die `uri` wird dynamisch vom UI da...
Checks gerne ein, ich kann auch testen.
@iseeberg79 @naltatis we need to trigger the service _only_ if all required fields are present. We're already (sort of) doing this for authorisation (see Viessmann): ```yaml auth: type: viessmann params:...
> I think it's important to allow flexibility here. As URI is required for TCP it could get build by http or https, host+port - because templates are using it...
> uri={host}:{port} That's ugly since it will create a non-empty parameter in the device case. But can be worked around in the backend. Makes sense that parameters still need to...
> Then the first server string where all placeholders can be filled would be used. Drawback with this solution is that we'd have to repeat static values I like the...
> Maybe it would also be fine to introduce a dedicated modbus (meta)-param and keep the logic of "required params for tcp/serial" in UI. Like it! Advantage: much less copy/paste...
The race is not in setting the logger but in setting vs. using it as the stack trace shows.
We have english docs, too ;)