Smartthings MQTT Bridge

[Simmo]

Hi,

Please can someone help, I have had all this working for about 8 months or so, but it all just stopped yesterday without me having changed anything, here is what i am seeing:

STBridge

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://172.17.0.1:1883
events.js:160
      throw er; // Unhandled 'error' event
      ^
Error: Connection refused: Not authorized
    at MqttClient._handleConnack (/usr/lib/node_modules/smartthings-mqtt-bridge/node_modules/mqtt/lib/client.js:735:9)
    at MqttClient._handlePacket (/usr/lib/node_modules/smartthings-mqtt-bridge/node_modules/mqtt/lib/client.js:296:12)
    at process (/usr/lib/node_modules/smartthings-mqtt-bridge/node_modules/mqtt/lib/client.js:238:12)
    at Writable.writable._write (/usr/lib/node_modules/smartthings-mqtt-bridge/node_modules/mqtt/lib/client.js:248:5)
    at doWrite (/usr/lib/node_modules/smartthings-mqtt-bridge/node_modules/readable-stream/lib/_stream_writable.js:237:10)
    at writeOrBuffer (/usr/lib/node_modules/smartthings-mqtt-bridge/node_modules/readable-stream/lib/_stream_writable.js:227:5)
    at Writable.write (/usr/lib/node_modules/smartthings-mqtt-bridge/node_modules/readable-stream/lib/_stream_writable.js:194:11)
    at Socket.ondata (_stream_readable.js:555:20)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)

Mosquitto broker:

1541698808: New connection from 172.30.32.1 on port 1883. [ERROR] Auth error with login 1541698810: Socket error on client <unknown>, disconnecting. 1541699061: Client a3bb2d8b-92e4-4cf9-a938-a588a12d4d68 disconnected. 1541699089: New connection from 172.30.32.1 on port 1883. 1541699089: New client connected from 172.30.32.1 as a03b6f50-4851-4099-8d5c-5f70bcd2de94 (c1, k60). 1541699195: New connection from 172.30.32.1 on port 1883. [ERROR] Auth error with login 1541699196: Socket error on client <unknown>, disconnecting.

As mentioned I have not been in or changed anything to do with mqtt or ST.

Please help

[stratplayer]

I had same with my zigbee2mqtt. Same error message.

Lots of people had issues with MQTT this weeks after an update to v3 of addon.

I had to restart from scratch as my SD got in a right state!

To get around that issue I had to create a MQTT user to connect with in Mosquitto as the anonymous was set to False.

I still have to re-add Smartthings addon, so will no doubt have same issue. But I will again be using a user created as mentioned previously

[blaha (Ben Nelson)]

I’m affected, but I couldn’t get authorization to work. Even a user that OwnTracks uses with my mosquitto broker successfully was refused.

[stratplayer]

Im thinking of ditching Smartthings altogether as I use zigbee2mqtt and Xiaomi sensors, the Samsung hub was what I bought before I got into HomeAssistant. There is nothing on it that I haven’t done with Xiaomi now… could be time for Ebay I think and no more half measures of 1yr old addons with no updates

[blaha (Ben Nelson)]

Turned out my /opt/mqtt-bridge/config.yml was formatted incorrectly with tabs instead of spaces.

[AlmostSerious (Marcus Peters)]

There was an update on the Plugin… it changed something in the authorization. This works for me:

{
  "logins": [],
  "anonymous": true,
  "customize": {
    "active": true,
    "folder": "mosquitto"
  },
  "certfile": "fullchain.pem",
  "keyfile": "privkey.pem"
}

[El_Duderino (Lance)]

I’m getting the following error log in Mosquitto broker. Anyone have any ideas why? Smartthings bridge appears to be working correctly, but the actions are not being picked up by MQTT:

[xamindar (Jared)]

This is driving me nuts. It simply wont work. Anyone have any idea why?
The MQTT Broker log shows this:

[INFO] Setup mosquitto configuration
[WARN] SSL not enabled - No valid certs found!
[INFO] No local user available
[INFO] Initialize system configuration.
[INFO] Initialize Hass.io Add-on services
[INFO] Initialize Home Assistant discovery
[INFO] Start Mosquitto daemon
Error: Unable to open include_dir ‘/share/mosquitto’.
Error found at /etc/mosquitto.conf:27.
Error: Unable to open configuration file.

[mikecoscia]

What is the correct way to setup a dimmer? If I select them as “switch level” in the ST smartapp, they do not work. They won’t turn on/off and it is not updating the state of the switch. If select them as “switch” the also do not work. This is how I had them set up in the yaml files…

switch.yaml

- platform: mqtt
      name: OFC Lights
      state_topic: "smartthings/OFC Lights/switch/state,"
      command_topic: "smartthings/OFC Lights/switch/cmd,"
      payload_on: "on"
      payload_off: "off"
      retain: false

lights.yaml

- platform: mqtt
      name: "Office Lights"
      state_topic: "smartthings/OFC Lights/level/state"
      command_topic: "smartthings/OFC Lights/level/cmd"
      brightness_state_topic: "smartthings/OFC Lights/level"
      brightness_command_topic: "smartthings/OFC Lights/level/set"
      brightness_scale: 100
      payload_on: "on"
      payload_off: "off"
      retain: false

[TerroBladeZ]

you dont need MQTT bridge anymore. Smartthings has been integrated into HA.

SmartThings

[123 (Taras)]

“integrated into HA” is a work in progress. Many but not all components are currently represented and there’s an important architectural difference. The SmartThings integration requires your Home Assistant server to be accessible from the internet whereas the MQTT bridge does not. Conversely, the MQTT Bridge requires an MQTT Broker whereas the SmartThings integration does not.

[dwinnn]

Here is an example of an MQTT light (which is appropriate for a dimmer) in HA that works with SmartThings . makes sure to include in lights.yaml or lights: section to recognize as a dimmer. This only works for white bulbs. If you want color bulbs, let me know.

If you compare with your yaml, you will notice some errors. Also make sure your MQTT bridge SmartApp in SmartThings is configured to send data of all your devices. You have to manually go through and select each device in the settings to have it included by the SmartApp.

- platform: mqtt
  name: "Stairs"  
  command_topic: "smartthings/Stairs/switch/cmd"
  brightness_command_topic: "smartthings/Stairs/level/cmd" 
  state_topic: "smartthings/Stairs/switch/state"
  brightness_state_topic: "smartthings/Stairs/level/state"
  brightness_scale: 100
  payload_on: "on"
  payload_off: "off"

Your SmartThingsBridge Hass.io settings should look something like this, specifically the preface, state suffix and command suffix.

{
  "broker_host": "172.17.0.1",
  "broker_port": 1883,
  "preface": "smartthings",
  "state_suffix": "state",
  "command_suffix": "cmd",
  "login": "stbridge",
  "password": "passwordhere",
  "bridge_port": 2080
}

[mikecoscia]

Thank you! I noticed that the other day and got it up and running without issues. Just need to figure out how to excluded some of the items, as I have duplicate devices from running certain apps in both hubs (i.e. harmony, nest, etc.)

[TerroBladeZ]

Just my opinion and not being rude. This thread started asking for help with the trouble user was having. Instead of wasting time setting up this bridge and have problems, if you have your HA exposed this is the best thing you can do. Also in the future you dont have to worry about any breaking changes

[123 (Taras)]

@TerroBladeZ

Instead of wasting time setting up this bridge and have problems, if you have your HA exposed this is the best thing you can do

The new SmartThings integration is a welcome addition. However, the need to expose one’s system to the internet is a significant requirement (and a non-trivial undertaking). I agree that for those who already have done it, the new SmartThings integration becomes a more attractive option.

Nevertheless, in terms of functionality and performance, it’s not yet an equivalent replacement for the SmartThings bridge. Anyone currently considering it needs to understand if its limitations impact them.

@TerroBladeZ

This thread started asking for help with the trouble user was having

Yes but there are also threads seeking assistance, and reporting problems, for the SmartThings integration (i.e. it’s not without its own challenges). Currently, the winning solution depends upon the user’s needs and operating environment. Perhaps in the future, the SmartThings integration will become the hands-down winner.

SmartThings Integration: Temperature sensors not updating every time

I’m running Home Assistant 0.88.1 and have an integration with SmartThings setup. I’ve noticed since updating to 0.88.1 that my temperature sensors are not always getting an update every time the sensor updates SmartThings. I do not see any warnings or errors in the logs for SmartThings but it can be hours between updates from SmartThings to Home Assistant when I can see multiple updates within the SmartThings app in the device history. Is anyone else experiencing this issue?

Dimming with New SmartThings Integration

Is anyone experiencing issues with dimming lights through the new SmartThings integration? I can turn lights on and off without issue, but the dimming function doesn’t do anything (and doesn’t display the correct value). Likewise, if I turn the light on with the dimmer slider, the light does not come on.

SmartThings Integration - Missing Switch and Button

Testing out the new SmartThings Integration. I have it working with some of my devices showing up in HA, but I have a couple of devices not showing up : Aeotec Smart Switch 6 Using Device Handler jbisson : Aeon Labs Smart Switch 6 Gen5 It list the capabilities as: Actuator, Color Control, Configuration, Energy Meter, Polling, Power Meter, Refresh, Sensor, Switch, Switch Level. AeotecWallmote Quad Using Device Handler erocm123 : Aeon WallMote It list the capa…

[TerroBladeZ]

Lol your posting issues if there are non with the bridge. Also there are fixes for the issues you posted. I have been using this bridge since 2 years. I am just saying that use the new integration so you can report problems and it gets fixed.

[123 (Taras)]

All I’m saying is there are two solutions available and users need to understand their respective strengths and weaknesses.

[B.A.Baracus (Bosco Albert Baracus)]

Been using the bridge for a LONG time, it has its quirks, that’s for sure, but what I really like is even when Smartthings cloud takes intermittent naps or internet access is cut off, HASS can still treat it like a slave locally.

However, after trying the component, it does seem to control OSRAM Lightify RGBW LED strips properly whereas the bridge could not.

[Matt112 (Matt)]

Here is my error, Your configuration contains extra keys that the platform does not support.
Please remove [payload_off].

 binary_sensor:
     - platform: mqtt
       device_class: motion
       state_topic: "smartthings/Kitchen Motion Sensor/motion/state"
       name: 'Kitchen Motion Sensor'
       payload_on: "active"
       payload_off: "inactive"

Any ideas on how I can fix this?

[123 (Taras)]

@Matt112

Your configuration contains extra keys that the platform does not support.
Please remove [payload_off].

That doesn’t seem right. According to the documentation for MQTT Binary Sensor, payload_off is a valid key.