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

Add option to ignore failed MQTT broker connection #5093

Open
joe-sydney opened this issue Sep 8, 2024 · 1 comment
Open

Add option to ignore failed MQTT broker connection #5093

joe-sydney opened this issue Sep 8, 2024 · 1 comment
Labels
feature-request Request for new features to be added

Comments

@joe-sydney
Copy link

πŸ“‘ I have found these related issues/pull requests

Could not find related issues

🏷️ Feature Request Type

Change to existing monitor

πŸ”– Feature description

A) If the MQTT monitor is used to monitor the MQTT broker and connection to the broker fails, then the monitor should be marked as down (which I believe is the current behaviour).

B) However, in cases where the MQTT is used to monitor other applications (by subscribing to messages that those applications are publishing), then loss of connectivity to the broker should not result in the monitor being down.

Currently, I am using the MQTT monitor extensively for B) in Home Assistant, and sensor states get rather messy when the Mosquitto broker is down for whatever reason.

βœ”οΈ Solution

It would be good if the monitor configuration has an additional field to optionally ignore the connectivity status. The default behaviour could still remain as is (A), but if the option this selected, then (B) applies

❓ Alternatives

No response

πŸ“ Additional Context

No response

@joe-sydney joe-sydney added the feature-request Request for new features to be added label Sep 8, 2024
@cocoonkid

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features to be added
Projects
None yet
Development

No branches or pull requests

2 participants