-
-
Notifications
You must be signed in to change notification settings - Fork 100
trigger status notifications for all connectors #365
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
trigger status notifications for all connectors #365
Conversation
Codecov Report
@@ Coverage Diff @@
## main #365 +/- ##
==========================================
+ Coverage 86.19% 86.51% +0.32%
==========================================
Files 10 10
Lines 1188 1194 +6
Branches 174 177 +3
==========================================
+ Hits 1024 1033 +9
+ Misses 94 92 -2
+ Partials 70 69 -1
Continue to review full report at Codecov.
|
return False | ||
"""Trigger status notifications for all connectors.""" | ||
return_value = True | ||
for id in range(0, 1): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use self._metrics[cdet.connectors.value].value
here instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does need to be known, so the number of connectors should be retrieved before sending the triggers.
Perhaps in the |
Is it for only 1 (ie 0 and 1) connector or will it handle say 0, 1 and 2? |
Yes. We could support more than one connector, but to display the info in separate sensors we would need to know how many there at setup, or create the additional sensors on the fly, which is messy. So, let's just keep the two sensors for connector=0 and connector=1 as is, and store additional info for other connectors in extra_attributes. |
Agree 👍 |
No description provided.