-
Notifications
You must be signed in to change notification settings - Fork 648
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
Publish GPIO settings with MQTT is not included in HA auto discovery #3302
Comments
The reason simply is that I was not aware of it when I implemented the discovery topics. |
@Dag0d I am happy to extend the discovery topics to reflect the control topics we have.
They are already documented in https://jomjol.github.io/AI-on-the-edge-device-docs/MQTT-API/#control How ever I struggle to get them working (make them show up in HA). I tried it like in https://community.home-assistant.io/t/add-entity-to-mqtt-device/540949/7 but nothing showed up in HA. |
@caco3: I only have it already implemented for flow start:
|
@Slider0007 Nice. Can you prepare a branch with it? I then can check to extend it. Other question:
|
If I remember right, there is no specific reason. Maybe a small safety feature to not disturbing the cycle by mistake, but in the end only definition... |
ok, then I will throw it out. |
I have it already implemented the same way (with payload) in my fork and the start trigger is working in home assistant. So there should be no limitation, but still could be removed. |
@caco3: I prepared a branch with the possible changes for the flow start button discovery: https://github.com/jomjol/AI-on-the-edge-device/tree/extend-ha-discovery It's not tested yet, though. Can be extended further... |
The Problem
When GPIO Pins are configured they are published to MQTT if "GPIO1 Enable MQTT" is checked this is as expected.
But it is not included in the HA auto discovery message.
Maybe there was a reason behind this decision, if so I´m happy to hear it.
Version
1.5.7 and 1.6.0 RC2
Logfile
I guess no need for a log file
Expected Behavior
No response
Screenshots
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: