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
Could the configured control mode be added to the discovery payload? Perhaps something like:
{
"~": "ratgdo-41533",
"name": "Door",
...
"device": {
"name": "ratgdo-41533",
"identifiers": "ratgdo-41533_C8:C9:A3:18:F1:04",
"manufacturer": "Paul Wieland",
"model": "ratgdo",
"sw_version": "2.57",
"configuration_url": "http://192.168.1.109/",
"control_protocol": "drycontact" # <---- add this or "secplus1" or "secplus2" etc.
}
}
This would help my UDI Polyglot plugin better understand the capabilities of the ratgdo device with the connected GDO. I do appreciate the change already in place to only publish the light discovery messages if not "drycontact" mode.
The text was updated successfully, but these errors were encountered:
I suppose if adding a new key would upset HomeAssistant for some reason, it could always be added to the "model" value, e.g.: "model": "ratgdo-drycontact"
Could the configured control mode be added to the discovery payload? Perhaps something like:
This would help my UDI Polyglot plugin better understand the capabilities of the ratgdo device with the connected GDO. I do appreciate the change already in place to only publish the light discovery messages if not "drycontact" mode.
The text was updated successfully, but these errors were encountered: