Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow protocol lookup from API? #45

Open
ligius- opened this issue Sep 29, 2019 · 1 comment
Open

Allow protocol lookup from API? #45

ligius- opened this issue Sep 29, 2019 · 1 comment

Comments

@ligius-
Copy link

ligius- commented Sep 29, 2019

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.

@puuu
Copy link
Owner

puuu commented Sep 30, 2019

If you are interested in devtype, you are welcome to submit a pull request. hwtype is always RF433 and does not need to be exposed.

If I look at the definition of devtype_t, I wonder if this is useful for your use case. There is no type temperature sensor, olny WEATHER.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants