Announcement

Collapse
No announcement yet.

Unsure what I’m doing wrong..

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Unsure what I’m doing wrong..

    I have mqtt install on my unraid server and connected to node red but cannot seem to get mcsmqtt to connect to the broker.. I’m I doing something wrong? Also I noticed in the newest update that mcsmqtt can be broker less? How would I maybe just go that route to node red if that’s possible?
    Attached Files

    #2
    It looks to me as if your setup to a broker is reasonable and the mosquitto log does show a connection was made, but lost.

    I did a little test with another client connecting and with mcsMQTT connecting and found the following in the mosquitto log. The other client also had a socket error when I closed down that client. This is normal behavior. For your HS case are there any errors in the HS log that may provide some clues? There is also a debug capability that may have more info that is enabled at the top of the general tab.

    To use the internal broker you will remove the Broker IP from mcsMQTT setup. In node-red you will use the IP of your HS install which looks to be 172.16.16.40 in this specific case. You will first need to shut down mosquitto if it is also running on the HS computer.

    Code:
    Another client connection
    
    1519733765: mosquitto version 1.4.14 (build date Mon, 10 Jul 2017 23:48:43 +0100) starting
    1519733765: Using default config.
    1519733765: Opening ipv4 listen socket on port 1883.
    1519733765: Opening ipv6 listen socket on port 1883.
    1519733777: New connection from 192.168.0.173 on port 1883.
    1519733777: New client connected from 192.168.0.173 as 15b090f7-da39-4e91-b42c-585f77e56768 (c1, k60, u'root').
    1519733777: Sending CONNACK to 15b090f7-da39-4e91-b42c-585f77e56768 (0, 0)
    1519733777: Received SUBSCRIBE from 15b090f7-da39-4e91-b42c-585f77e56768
    1519733777:     # (QoS 2)
    1519733777: 15b090f7-da39-4e91-b42c-585f77e56768 2 #
    1519733777: Sending SUBACK to 15b090f7-da39-4e91-b42c-585f77e56768
    1519733777: Received PUBLISH from 15b090f7-da39-4e91-b42c-585f77e56768 (d0, q1, r0, m2, 'vacuum/status', ... (272 bytes))
    1519733777: Sending PUBACK to 15b090f7-da39-4e91-b42c-585f77e56768 (Mid: 2)
    1519733777: Sending PUBLISH to 15b090f7-da39-4e91-b42c-585f77e56768 (d0, q1, r0, m1, 'vacuum/status', ... (272 bytes))
    1519733777: Received PUBACK from 15b090f7-da39-4e91-b42c-585f77e56768 (Mid: 1)
    1519733781: Socket error on client 15b090f7-da39-4e91-b42c-585f77e56768, disconnecting.
    
    mcsMQTT connection
    
    1519733955: New connection from 192.168.0.173 on port 1883.
    1519733955: New client connected from 192.168.0.173 as mcsMQTT on Dell-PC (c1, k60, u'root').
    1519733955: Sending CONNACK to mcsMQTT on Dell-PC (0, 0)
    1519733955: Received PUBLISH from mcsMQTT on Dell-PC (d0, q0, r0, m0, 'Dell-PC/mcsMQTT/LWT', ... (6 bytes))
    1519733955: Received SUBSCRIBE from mcsMQTT on Dell-PC
    1519733955:     # (QoS 0)
    1519733955: mcsMQTT on Dell-PC 0 #
    1519733955: Sending SUBACK to mcsMQTT on Dell-PC

    Comment

    Working...
    X