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
Currently the callback receives the device id and protocol name from ESPiLight. However, it would be useful to know what kind of device it was, available under protocol_t - devtype and hwtype. This would allow some automated processing by the callback, such as creating an MQTT discovery topic for a temperature sensor. It's not a perfect approach but it could allow for a bit more flexibility.
The text was updated successfully, but these errors were encountered:
Currently the callback receives the device id and protocol name from ESPiLight. However, it would be useful to know what kind of device it was, available under protocol_t - devtype and hwtype. This would allow some automated processing by the callback, such as creating an MQTT discovery topic for a temperature sensor. It's not a perfect approach but it could allow for a bit more flexibility.
The text was updated successfully, but these errors were encountered: