-
Notifications
You must be signed in to change notification settings - Fork 11
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
Use MQTT + Autodiscovery instead of a custom component for Home Assistant #13
Comments
@Hypfer I have recently looked into mqtt for another project and feel that I now could implement this with relative ease. Do you have experience with how to provide the autodiscovery facilities? Looking at https://www.home-assistant.io/docs/mqtt/discovery/ it appears that a json dictionary containing hass configuration posted to the right topic is sufficient. |
Yep. Exactly Here's an example for the autoconf payload of a And here's an older one for And another one. This time for
Topic: |
Z-Wave is also currently being "converted" to MQTT. Maybe there are code examples. MQTT + autodisovery + HACS installation would be great. Unfortunately I am not a programmer, but would help testing. I have a Rademacher garage door, a switchable socket and radio cover. |
Hi @gluap, thanks for sharing your great work here on github! |
To decouple the Home Assistant Host from the host with the USB Device, it might make sense to utilize the cover.mqtt integration instead of having a custom component.
The
duofern.start_pairing
andduofern.sync_devices
custom services wouldn't be possible though.We could probably map them to switch.mqtt entities
The text was updated successfully, but these errors were encountered: