You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Great work! Glad to see this is working for so many users. Having a small issue myself.
I am running Homeassistant / smartthings-mqtt-bridge via docker on a unRaid instance (same IP address - ports exposed via router)
I am using cloudMQTT as the broker
Smartthings:
I have set up the smartthings device handler / device / application and have exposed some devices.
I have configured the smartthings device for my local IP address (but have also tried external) with port 8080 and the Mac address of my UnRaid box
I've tried switching a few lights on and off and note that the event log for the MQTT device says: "smartthings sent deviceNotification command to MQTT" this is the same event that gets logged for any device activity. I notice that other people are seeing the entire MQTT message - so maybe the issue i s here.
info: Starting SmartThings MQTT Bridge - v3.0.0
info: Loading configuration
info: Loading previous state
info: Perfoming configuration migration
info: Saving current state
info: Connecting to MQTT at mqtt:///m20.cloudmqtt.com:10664`
CloudMQTT:
log only shows:
2018-11-29 13:23:12: Received PINGREQ from 586280c9-1cae-4f67-b037-6cc3c0e74a5a
2018-11-29 13:23:12: Sending PINGRESP to 586280c9-1cae-4f67-b037-6cc3c0e74a5a
2018-11-29 13:24:12: Received PINGREQ from 586280c9-1cae-4f67-b037-6cc3c0e74a5a
2018-11-29 13:24:12: Sending PINGRESP to 586280c9-1cae-4f67-b037-6cc3c0e74a5a
Shows no Received messages in the websocks ui
Any ideas? Not really sure how to troubleshoot.
The text was updated successfully, but these errors were encountered:
Hey,
Great work! Glad to see this is working for so many users. Having a small issue myself.
Smartthings:
Bridge:
Log only shows
CloudMQTT:
log only shows:
Shows no Received messages in the websocks ui
Any ideas? Not really sure how to troubleshoot.
The text was updated successfully, but these errors were encountered: