@revlis240 This is probably not helpful but I found a stable alternative in using Home Assistant as my front end and Smartthings as my backend for Z-Wave and Zigbee. As such, I switched from the @LeeFL implementation on ST to https://www.home-assistant.io/integrations/nx584/ on Home Assistant. Works great but certainly not a ST solution. Cheers!
Thanks, I will check it out!
Im gonna lose my mind, would love some help. I tried Michaels suggestion, and it didnt really work, here are my notes:
What exactly didn’t work? Had you removed the child devices beforehand? Were they added again when running the modified DHT? If I know more on what went wrong perhaps I can help.
Hey guys, sorry for being late to the ‘party’ here.
The “ACK Required” bit isn’t an error, that’s just part of the verbose logging so that I can see what’s going on. (the ACK would have been sent)
If the update happens on a refresh, but not automatically then, although network connections are ok (in general), something is preventing SmartThings from receiving/handling messages that it didn’t initiate.
My first check would be to check that the IP address that the device has for SmartThings is correct (you fixed the inverse, but perhaps not this way round).
When you hit refresh, it’s SmartThings initiating the request, so the device can respond without the IP that it has stored for SmartThings being correct.
When an event happens it needs that stored IP address in order to know who to send the event to, and this is what may be failing.
Via the web interface, go the the Setup page on the device, and make sure the IP address stored there for the SmartThings hub is correct. (and if not then update it, and click Submit)
If that is already correct, or if you still have issues after correcting it, then I’d check your router/firewall, since it’s possible that your router may be blocking the port used.
Hello @LeeFL,
I was having the exact same issues as @revlis240 and all ip config was correct. The issues were completely resolved when I removed all child devices and recreated them.
Btw, is there an easy way to create the child devices without the old app? Perhaps from the new app or the smartthings account (web)?
Thanks,
Michael
For what its worth my own alarm panel integration on Hubitat should provide a drop in replacement for LeeFL’s integration here. You just need to install either
- Hubitat package manager, and then search for my integration (set it up in a virtually identical way to here)
- Two device handlers listed on the thread
Don’t know if it has been fully tested by anybody but happy to help troubleshoot over there if needed, should support everything that this integration supports.
As for getting ST working, the device handler I have written for Visonic alarms should allow you to create the children from the ESP bridge device, though that does require some tiny modifications to Lee’s code, which Im not sure has happened yet. The device handler for this is now fully supported by this one
1 Like
I do have a new firmware in-progress, which I should be able to share in a day or two, that should allow SmartThings zone child-device removal/creation via the web-interface, without using the SmartThings app at all. (and all other things previously done via the SmartThings app also).
It is definitely some weird issue with the SmartThings servers that seems to be causing these issues, and is unfortunately outside of my control (assuming that the IP settings in both the device (for SmartThings IP) and within SmartThings (for device IP) are correct.)
Hey guys
Yes I made triple sure that the IP addresses match on both the local bridge and the DHT.
I just give up on ST. Im totally in agreement with LeeFL that this is an ST problem, I watched the live data for 30 minutes last night, and while it captured me opening the window 100% of the time, it only captured me closing the window 30% of the time. So clearly the settings are all right, but ST is just choosing to ignore commands at random.
Hubitat arrived today, cant wait to install it this week!!
I must state to anyone reading that none of the issues I’ve experienced has anything to do with LeeFL’s equipment, which has been 100% reliable 100% of the time. This is strictly an ST issue, I will report back to this thread with my experience going from ST to HE along with CJCharles’ software.
Thanks again for all the help guys 
@LeeFL,
I seem to have misplaced my copy of the setup docs for your stuff and am wanting to apply the latest updates. Can you provide a link to the docs? I found one a bit of the way up in the thread, but it seemed to be a dead link. Thanks!
Problems again 
My debug log is something like the following:
Failed to connect to SmartThings when sending Status Update: IPReceived message: 070102020202020202 - ACK Required
Received message: 070102020202020202 - ACK Required
Received message: 0406015813F00102 - ACK Required
Received message: 05000000800100000000 - ACK Required
Received message: 070302020202020202 - ACK Required
Failed to connect to SmartThings when sending Status Update: IPReceived message: 070302020202020202 - ACK Required
Received message: 070302020202020202 - ACK Required
Received message: 070302020202020202 - ACK Required
Received message: 0406015813F00002 - ACK Required
Received message: 05000000800000000000 - ACK Required
Received message: 070102020202020202 - ACK Required
Received message: 0406015813F00102 - ACK Required
Received message: 05000000800100000000 - ACK Required
Received message: 070302020202020202 - ACK Required
Failed to connect to SmartThings when sending Status Update: IPReceived message: 070302020202020202 - ACK Required
Received message: 070302020202020202 - ACK Required
Received message: 070102020202020202 - ACK Required
Received message: 0406015813F00102 - ACK Required
Received message: 05000000800100000000 - ACK Required
Received message: 070302020202020202 - ACK Required
Failed to connect to SmartThings when sending Status Update: IPReceived message: 070302020202020202 - ACK Required
Received message: 070302020202020202 - ACK Required
Received message: 070302020202020202 - ACK Required
Received message: 0406015813F00002 - ACK Required
Received message: 05000000800000000000 - ACK Required
Received message: 070102020202020202 - ACK Required
Failed to connect to SmartThings when sending Status Update: IPReceived message: 070102020202020202 - ACK Required
Received message: 070102020202020202 - ACK Required
Received message: 070102020202020202 - ACK Required
Received message: 0406015813F00102 - ACK Required
Received message: 05000000800100000000 - ACK Required
Received message: 070302020202020202 - ACK Required
Failed to connect to SmartThings when sending Status Update: IPReceived message: 070302020202020202 - ACK Required
Received message: 070302020202020202 - ACK Required
@LeeFL any ideas why it seems to be communicating most of the times but not all? IPs are correctly set and as far as I can tell my LAN has no issues.
Hey @mpikounis
Hmmm, that is strange. I’ve never seen that before.
That means as it sounds, that when trying to send a status update it’s failing periodically, but it looks like not after every status change.
Unfortunately that message is getting truncated (so it’s not listing the IP it’s trying to use).
Is it definitely updating SmartThings some of the time ?
If so then it seems like it’s either the WiFi connection, your router dropping packets, or SmartThings failing to open a connection sometimes. (that error happens before it’s even tried to send the update, that’s just opening the connection)
Sure Chris, latest install doc is here: -
https://www.amazon.com/clouddrive/share/lGv0vNdziVA9vlDGs6ZBodQvAVmT5P9oGRXsw28ZWLj
Hey guys
I spent a few hours to get this set up on Hubitat and im happy to report that my sensors that Ive been monitoring have been 100% spot on.
So theory confirmed: my local setup (routers, IP assignments, etc) were all just fine. This is a ST issue.
Im surprised me and Michael are the only ones experiencing issues, but now that I have confirmed Hubitat to be the 100% I was looking for, I’ll be spending boatloads of time setting that up. Its definitely more involved (as my lights are all Tuya based, and that doesnt work with hubitat without flashing), but I think will be worth it in the end.
Thank @LeeFL for the feedback. Can we make a firmware with a more detailed log that lists the IP it
Is failing to connect to, the port and the device it is trying to update?
If it was a wifi issue shouldn’t it just delay the update rather than fail? And when it fails is there logic to retry the update in say 1 or 2 seconds later?
Also, how can I change the WIFI your device is connecting to? I can install a spare wifi hub right next to the alarm to make sure reception is good
Thanks much!
Can I suggest you try restarting your ST hub. Various people have had similar issues over the past 6 months on my own integration, which normally improve after a reboot…
@mpikounis I’ll see if I can improve the retry attempts, but there is some level of retry built in, and I’ve never ever seen an issue with it failing. TBH I suspect the issue is more likely with the ST hub (have you tried restarting that?), but can’t rule out WiFi issues.
It was supposed to be logging the IP, but it seems that message was getting truncated and I didn’t realize (because I’ve not seen it actually happen before).
I can fix that fairly easily, and will include it in my next release (which will support easier setup without the old ST app)
Thanks for the suggestion. I rebooted it and I will monitor it.
In the meantime I ordered a Hubitat hub and I will migrate everything there once it arrives. The local execution sounds like a blessing after all the trouble with SmartThings