You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 17, 2020. It is now read-only.
This would, for example, allow Hermes to play nice with other MQTT clients on the same system. This is common on smart home controllers. It would guarantee there is no overlap.
Currently I am experiencing disconnect issues. When MQTT detects a new connection it may kill the old one. Naming the clients can help avoid this.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be great if it were possible to also set a
client ID
for the Hermes MQTT client.It could be a welcome addition to the existing MQTT options.
This would, for example, allow Hermes to play nice with other MQTT clients on the same system. This is common on smart home controllers. It would guarantee there is no overlap.
Currently I am experiencing disconnect issues. When MQTT detects a new connection it may kill the old one. Naming the clients can help avoid this.
The text was updated successfully, but these errors were encountered: