-
Notifications
You must be signed in to change notification settings - Fork 795
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
Add support for discovery device trigger #1090
Add support for discovery device trigger #1090
Conversation
1bda9f9
to
e6b201e
Compare
Thanks for the PR,
The auto-discovery process of RF has been deactivated because it was creating a lot of unnecessary entities into Home Assistant, in particular when there is a lot of RF devices in the neighborhood. Does this new method prevent this? |
If I understand what you mean, yes I confirm that no entities appear, this is my configuration: I have 3 gateways made with the az-delivery esp32 board each one with SRX882 and STX882. In my house there are about 30 RF devices and a lot of Bluetooth devices... that's my current board on HA: To date I have intercepted over 350 RF signals and have none of these entities |
To explain better, let's suppose that a device that doesn't belong to you emit a set of RF signals, 1145896, 1458765, 3555489. |
Confirmed, no entity for each signal. In HA it is part of the triggers, more specifically the device trigger |
db57471
to
fc0a742
Compare
🥳 Time to review the code and I provider you the pr as promised! |
* Add announce of DeviceTrigger + Update doc
In short
More
The MQTT Device Trigger platform uses an MQTT message payload to generate device trigger events in to home assistant, so it's not create a flag/state/etc on the device (like what produced by binary sensor) but just declare where the event will be raise and provide information about the event.
I used this feature in the auto discovery process for the RF module, so we can reactivate what has been deactivated here this PR #1026
It will also solve the problem #939 because the Device Trigger already has all the reset and event management logic, which by definition has no state.
Checklist: