No subscribers

[jeremyfry]

When the bridge starts up it registers with my broker fine, but it does not have any subscriptions. I checked the state.json and get the follow:

{ "subscriptions": [], "callback": "", "history": { "smartthings/Entry Light/switch": "off", "smartthings/Busters/switch": "off", "smartthings/Garage Lights/switch": "on", "smartthings/Pantry Door/contact": "open", "smartthings/Front Door/lock": "unlocked" }, "version": "1.3.3" }

If I manually add in a subscription and restart the container it does register properly but the callback doesn't get populated and I get a Error from SmartThings Hub: Error: Invalid URI "http:///".

It's worth noting that Smartthings -> bridge -> broker communication is working properly and events come through (which I assume is what populated the history). But I can't get MQTT -> bridge -> smartthings communication functioning properly.

[jeremyfry]

I was able to add in the callback manually as well pointing it at my smartthings hub ip:port and everything is now working. It's not intended to have to manually add each subscription and the callback though is it?

[stjohnjohnson]

@jeremyfry sorry for the long delay. That information should have been populated by SmartThings automatically. If it's not being added, that's very strange.

[asnandrey]

I'm having same problem where SmartThings is not receiving messages back from MQTT topics.

SmartThings-->MQTT (works) MQTT-->SmartThings (broken)

It seems like @jeremyfry has fixed it. Can you list out the steps?

[jeremyfry]

Unfortunately my original 'fix' was to simple go into the state.json file and under subscriptions manually add all the items I wanted.

I no longer have this issue though. There were no code changes to my setup as everything is in docker containers and have been rebuilt in a long time. However I did change my network setup which was probably overly complex before. I had been running a router behind router, across different subnets to isolate my ISP router from my home network. I've since switched a single router solution and things work as expected now.

Sorry I can't be of more help.

[asnandrey]

Ok. Sure. Thanks for your response. My setup is simple and issue is that MQTT is not talking back to SmartThings.I will check it all again.On Jul 19, 2017 2:30 PM, Jeremy Fry [email protected] wrote:Unfortunately my original 'fix' was to simple go into the state.json file and under subscriptions manually add all the items I wanted. I no longer have this issue though. There were no code changes to my setup as everything is in docker containers and have been rebuilt in a long time. However I did change my network setup which was probably overly complex before. I had been running a router behind router, across different subnets to isolate my ISP router from my home network. I've since switched a single router solution and things work as expected now. Sorry I can't be of more help.

—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or mute the thread.