I’ve been having sync issues every now (maybe every few weeks) and I have to launch the TCP app and re-discover the bulbs to get the random one to stop blinking.
Between these problems and the weirdness going on with the Hue bulbs, it makes me wonder if ST is 100% reliable when it comes to lighting.
Mine seem to be staying connected, but sending commands to them is spotty. Even worse when trying to send commands to them from my Logitech remotes. I end up using the TCP app a lot which kind of defeats the purpose of them.
That’s what I do as well… a good deal of the time things work, but there are times when things will go horribly wrong and either nothing will work, or the bulbs will just start blinking and I have to fire up the TCP app and re-discover to get them to stop (even if I don’t have to re-add them).
I’m really, really looking for something that just works, all the time, without a hitch. I love the extensibility that ST offers, but I don’t think they’ll get into the bulb game anytime soon and we’ll have to live with 4-5 hubs and somewhat spotty integration some of the time.
Failed after 2 weeks on my first ST hub. I was really hoping to be past this.
Still failing for me. @twack
Are you using the TCP connect from the ST apps, or did you install it from my github links?
Twack
TCP Connect through the mobile app. if I should be using the git, let me know and I’ll switch over.
Failed again overnight.
Check your notification/logs. It’s quite likely that your hub disconnected and reconnected during the night as they rolled out various platform changes. I have found that that can cause connection loss with other cloud services.
Thanks for the thought JD but I see nothing in the logs that says that. Also, it must have failed before 9:30pm Eastern last night because that’s when the lights should have been turned off.
Failed again overnight. This time I do see errors that are showing up in the messages section of the app. Error 400. Reauthorizing through TCP connect fixed it again.
Still having this issue every week or so. I’m going to update support.
just pressing next in TCP connect fixes it.
Same here. @twack are you still working on this one?
Are you seeing the issue when trying to turn them on/off via the tile in the mobile app? Or, is this happening in a routine or smart lighting?
I’m noticing the physical lights are not on or off as scheduled with the dashboard “lights and switches” app.
I then look at the lights in ST Things view and ST shows that they are on or off when the opposite is true. I try to toggle them through ST and nothing happens. The ST app shows that they are going on or off, but the physical light doesn’t change on/off. I open the TCP native app and their true status shows and I can control them.
Then I just open TCP Connect in ST and hit next a few times and then I can control them again through ST through all methods (dashboard, things view, routines, SHM, etc). It works fine for a week or two then the same thing occurs.
Been having the same issue myself. They will randomly stop functioning every other day or so and I’ll be getting the messages “TCP Lighting is having Communication Errors. Error code = 500. Check that TCP Gateway is online.” Though my gateway is definitely online and functioning.
@twack Perhaps it’s better to do local communication between SmartThings and the TCP Hub? I know this is possible as I had it working with my NinjaBlocks, though I didn’t develop it myself (wish I knew how). This would also help take additional stress off the cloud servers you guys use.
It was possible until TCP closed the local interface in a firmware update. We are forced to use the cloud to cloud.
When did it get locked down locally? It was working a few months ago.
I also know local commands were never “supported” according to TCP (or whatever the name of the company that sells the lights is), it was done off the books by reverse engineering them.
Around a year ago actually. They used to have a web interface that you could connect to on the hub itself. They pushed out a string of updates that broke the connection to SmartThings and then finally disabled the local interface altogether.
Yes, this changed things requiring authorization again, but you can still do it locally. I recall this cause the NinjaBlock “smartapp” (or driver as they call it) functioned fine and then stopped functioning around the same time as well. After it was fixed, it still worked locally.