Smartthings-MQTT No Data

Configuration
1

I am trying to get Smartthings mqtt working, just like everyone else :unamused:

I’m running ubuntu in a VM on an ESXI host, smartthings & HASS VM are on different vlans. I’ve tried to point the smartthings MQTT device to both my public and private IP. My only guess is that my MAC address is somehow incorrect.

I am able to see traffic coming in on port 2080 from my router, and if I browse to http://myaddress:2080 I see “Cannot GET /”

Smartthings-Bridge Config

{
  "broker_host": "10.10.120.11",
  "broker_port": 1883,
  "preface": "smartthings",
  "state_suffix": "state",
  "command_suffix": "cmd",
  "login": "username",
  "password": "password",
  "bridge_port": 2080
}

starting version 3.2.2
info: Starting SmartThings MQTT Bridge - v1.3.4
info: Loading configuration
info: Loading previous state
info: Perfoming configuration migration
info: Saving current state
info: Connecting to MQTT at mqtt://10.10.120.11:1883
info: Configuring autosave
info: Configuring API
info: Listening at http://localhost:2080

MQTT-Broker

{
“plain”: true,
“ssl”: false,
“anonymous”: false,
“logins”: [
{
“username”: “username”,
“password”: “password”
}
],
“customize”: {
“active”: false,
“folder”: “mosquitto”
},
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”
}

starting version 3.2.2
1516915070: mosquitto version 1.4.12 (build date 2017-06-01 13:03:46+0000) starting
1516915070: Config loaded from /etc/mosquitto.conf.
1516915070: Opening ipv4 listen socket on port 1883.
1516915070: Opening ipv6 listen socket on port 1883.
1516915070: Warning: Mosquitto should not be run as root/administrator.
1516915082: New connection from 10.10.120.11 on port 1883.
1516915082: New client connected from 10.10.120.11 as mqttjs_9001c0b3 (c1, k10, u’username’).
1516915104: New connection from 172.30.32.1 on port 1883.
1516915104: New client connected from 172.30.32.1 as hass-1 (c1, k60, u’username’).

My homeassistant config.yaml

mqtt:
broker: localhost
discovery: true
discovery_prefix: smartthings
protocol: 3.1
keepalive: 60
client_id: hass-1
username: username
password: password

2

Since you have to provide the MAC address, it probably only works on the same layer 2 network. Try moving SmartThings and the bridge to the same VLAN.

3

You are correct my friend. Thank you, I should have realized that. I don’t understand why that is a thing, but it is :man_shrugging:

Anyone in the future with this issue, it is impossible at this time to have smartthings and the bridge be in a different subnet or network.

The traffic will send it seems(The packets make it to my firewall !). I’ve looked at the source and to the best of my limited ability, I can’t understand why a MAC is even necessary.

Perhaps if I spoof the router outbound NIC, the connection will work?

1 Like