-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
MQTT Plugin #2666
Comments
Logs with debugging disabled s6-rc: info: service s6rc-oneshot-runner: starting |
I'm confused, what's the issue? Your logs with debugging disabled don't show any errors or anything wrong. Your logs with debugging enabled look fine too. What am I missing? |
It was Cleared up with me what I was seeing was home assistant Supervisor sending and closing connection , The Problem I originally had was Unauthorized user - disconnecting. My Next step is SSL/TLS which I need for info on installing |
But I am Trying to Configure the SSL/TLS for the Mosquitto Broker - Have not come across any walk through or files that I could edit |
2022-09-22 20:57:57: New connection from 172.30.32.1:57280 on port 1883. |
Anyone have any answers why this occurred ?? |
same problem. MQTT Broker will not start---- where can i find a older version? |
Try rebooting host ?? |
@4noxx try rebooting host ?? |
probably the same as |
'error: received null username or password for unpwd chec' |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Describe the issue you are experiencing
Works with debugging enabled but without has issues like client unknown Closed connection and Rejected unauthorized user disconnected
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Other (e.g., Raspbian/Raspberry Pi OS/Fedora)
Which add-on are you reporting an issue with?
Mosquitto broker
What is the version of the add-on?
6.1.3
Steps to reproduce the issue
Disabling Debugging will reproduce issue
Anything in the Supervisor logs that might be useful for us?
Anything in the add-on logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: