Hi, New to hass.io and have just set up MQTT using the Mosquitto add-on. I have connected my phone via Zanzitto which seems to be working OK despite disconnecting frequently (not sure if that’s supposed to happen). The one thing that is puzzling me is I keep getting the following coming up in the logs.
1519052330: New connection from 54.191.90.143 on port 1883.
1519052336: Socket error on client <unknown>, disconnecting.
Is this normal?
Thanks
I got the same issue. I think it’s an Sonoff basic (withTasmota ) that is not working correct. Do you have sonoff basics running in your house?
No. The only mqtt device I have is the device tracker.
I get the same thing, same ip address, I can’t figure it out.
I thought it was the sonoff. When i disconnect the sonoff ,this ip still keeps connecting.
I have the same issue. Looking up the IP in the internet, I get the following data:
_Source: whois.arin.netIP _
_Address: 54.191.90.143Name: _
AMAZO-ZPDX8
Handle: NET-54-188-0-0-1
Registration Date: 10/5/16
Range: 54.188.0.0-54.191.255.255
Org: Amazon.com, Inc.
Org Handle: AMAZO-47
Address: EC2, EC2 1200 12th Ave South
City: Seattle
State/Province: WA
Postal Code: 98144
Country: United States
I would better understand it (but not accept it), if I had Alexa but I don’t have any Amazon components installed…
hmmm… I don’t like the idea that an Amazon server is trying to connect to my Raspberry Pi.
My relevant settings are the following:
What I don’t understand either is how they found my IP? Does DuckDNS send my Hassio IP to Amazon or is some component in Hassio sending my IP to Amazon…?
I have a weird situation. After updating Mosquitto add-on, my D1Mini not connecting. After hours of research, I got to know that since version 4.1 of the addon, an explicit ACL definition is now required. SO, I created acl list and updated my users in accesscontrollist.
user mqtt
topic readwrite #
Later, receiving many errors. So, I re-installed the addon, but getting same errors,
[12:27:58] INFO: Setup mosquitto configuration
[12:28:00] INFO: Found local users inside config
[12:28:06] INFO: Initialize Hass.io Add-on services
[12:28:06] INFO: Initialize Home Assistant discovery
[12:28:06] INFO: Start Mosquitto daemon
1567580286: Loading config file /share/mosquitto/acl.conf
1567580286: mosquitto version 1.6.3 starting
1567580286: Config loaded from /etc/mosquitto.conf.
1567580286: Loading plugin: /usr/share/mosquitto/auth-plug.so
1567580286: ├── Username/password checking enabled.
1567580286: ├── TLS-PSK checking enabled.
1567580286: └── Extended authentication not enabled.
1567580286: Opening ipv4 listen socket on port 1883.
1567580286: Opening ipv6 listen socket on port 1883.
1567580286: |-- *** auth-plug: startup
1567580286: Opening websockets listen socket on port 1884.
1567580287: Opening ipv4 listen socket on port 8883.
1567580287: Opening ipv6 listen socket on port 8883.
1567580287: Opening websockets listen socket on port 8884.
1567580288: Warning: Mosquitto should not be run as root/administrator.
1567580289: New connection from 192.168.1.52 on port 1883.
[INFO] found mqtt on local database
1567580297: New client connected from 192.168.1.52 as Bedroom_control_panel (p2, c1, k10, u'mqtt').
1567580311: New connection from 172.30.32.1 on port 1883.
1567580312: Socket error on client <unknown>, disconnecting.
1567580312: New connection from 172.30.32.1 on port 1883.
[INFO] found homeassistant on local database
1567580320: New client connected from 172.30.32.1 as auto-548FF2EF-84E5-471E-335D-C96E0AB0F072 (p2, c1, k60, u'homeassistant').
1567581533: New connection from 192.168.1.52 on port 1883.
[INFO] found mqtt on local database
1567581541: Client Bedroom_control_panel already connected, closing old connection.
1567581541: New client connected from 192.168.1.52 as Bedroom_control_panel (p2, c1, k10, u'mqtt').
1567582088: Saving in-memory database to /data/mosquitto.db.
the above IP 192.168.1.52 is belongs to my d1mini which have Tasmota firmware controlling my bedroom relays.
When I checked on tasmota console, it’s connected to MQTT and sending
MQT: d1mini01/tele/STATE
MQT: d1mini01/tele/SENSOR
d1mini01/tele/HASS_STATE
to MQTT broker. But in my hass, the switches are not connected. MQTT: Mosquitto broker integration is empty (no devices registered). I have no idea to whom that IP 172.30.32.1 belongs to. It just randomly appeared the device auto-548FF2EF-84E5-471E-335D-C96E0AB0F072.
I’ve observed this issue started when I updated the add-on. Did I miss anything? I’ve tried many things and couldn’t fix this issue.
he is mine
my wemos mqtt config
the consol
in the switch.yaml
#=======================================================================
#
#=======================================================================
- platform: mqtt
name: "Office Fan"
state_topic: "stat/SONOFF-FAN/POWER1"
command_topic: "cmnd/SONOFF-FAN/POWER1"
payload_on: "ON"
payload_off: "OFF"
optimistic: false
qos: 0
#=======================================================================
see clear as mud
I don’t see this issue reported as bug. Is this happening only for few people? or did we miss something?
I know it’s against ACL definition rules. Just try to mark "active": false in Mosquitto broker config. It just worked for me… magically…
In the ACL file add a homeassistant user as well with readwrite # and active true
Still facing the same error. worked for some time with config "active": false and later getting same error. Added homeassistant user in ACL file
user homeassistant
topic readwrite #
still receiving same error
1567845664: Socket error on client <unknown>, disconnecting.
[INFO] found homeassistant on local database
/bin/auth_srv.sh: line 15: echo: write error: Broken pipe
Is there any way I can install old version? It seems like it’s a bug with v5.0.
After few weeks banging my head, tried ALL possible things I can do to make MQTT works, FINALLY found a solution that may not possible for others. Used a single login for all add-ons and Mosquitto as well and jst DID NOT created MQTT user in users section and my devices are appeared in states ans overview MAGICALLY.
Now my only concern is this,
1569658930: New connection from 172.30.32.1 on port 1883.
[INFO] found homeassistant on local database
1569658938: New client connected from 172.30.32.1 as auto-6F381B95-CB08-856B-AC00-A79A37E1D44C (p2, c1, k60, u'homeassistant').
1569658938: Client auto-6F381B95-CB08-856B-AC00-A79A37E1D44C disconnected.
1569658938: New connection from 172.30.32.1 on port 1883.
1569658938: New client connected from 172.30.32.1 as auto-F0038532-EAD9-D2B8-686C-09A0CE19D75A (p2, c1, k60, u'homeassistant').
1569658938: Client auto-F0038532-EAD9-D2B8-686C-09A0CE19D75A disconnected.
1569658938: New connection from 172.30.32.1 on port 1883.
1569658938: New client connected from 172.30.32.1 as auto-DE532E54-A094-020E-E3D8-E93D125CA9E7 (p2, c1, k60, u'homeassistant').
1569658980: New connection from 192.168.1.52 on port 1883.
[INFO] found sam on local database
1569658989: New client connected from 192.168.1.52 as Bedroom_control (p2, c1, k30, u'sam').
1569658990: Client Bedroom_control disconnected.
1569658995: New connection from 192.168.1.52 on port 1883.
1569658995: New client connected from 192.168.1.52 as Bedroom_control (p2, c1, k30, u'sam').
1569660025: Saving in-memory database to /data/mosquitto.db.
1569660792: Client Bedroom_control has exceeded timeout, disconnecting.
1569660825: New connection from 192.168.1.52 on port 1883.
[INFO] found sam on local database
1569660833: New client connected from 192.168.1.52 as Bedroom_control (p2, c1, k30, u'sam').
1569661826: Saving in-memory database to /data/mosquitto.db.
1569663627: Saving in-memory database to /data/mosquitto.db.
1569665428: Saving in-memory database to /data/mosquitto.db.
I have no idea about the IP 172.30.32.1 and device auto-F0038532-EAD9-D2B8-686C-09A0CE19D75A.
Any idea about K codes? like k30 and k60?