I got same thing and same issue it didn’t show but no issues with anything yet.
No, 16.14 is almost identical to 16.13 with a small but critical fix to ensure that we did not run into the same issues as encountered by @cuboy29.
1 Like
Knok on wood @posborne and @duncan
I have not had any “disconnect” since AWS had problems.
Hope my z-wave lock did not trash AWS 
Anyways, all my fibaro dimmers work great, and X fingers for a stable lock.
I know I can take the lock out of the mesh, but this is what beta is for IMHO.
As extra info i changed the DH for the fibaro dimmers to Fibaro Dimmer 2 (FGD-212) - Advanced DTH
Edith. Should not have writen this.
Went offline now.
No help in knocking 
2 Likes
A special thanks to the ST staffs for reviving my HUB so quickly saving me countless hours. Also, thanks for the additions in the packaging 
-Quang
4 Likes
Any update on a fix for Smart Lighting?
A word from AWS: https://aws.amazon.com/message/41926/
On a different note, my hub updated to 16.14 yesterday and now this:
I have an app that uses SSDP discovery - that stopped working. Once the IP discovered, it uses LAN messages to integrate to my alarm (AT&T Digital Life) - that stopped working too. I rebooted the hub and low and behold, all working fine again. Some minutes later, 30-60 minutes already passed by the time I realized the problem, boom, SSDP and LAN messaging off again. On top of that, these new logs:
8f0bb81c-8c0d-41c2-9c31-2b1446822da7 8:57:54 AM: info smartapp_pause called by smartAppName=Home Cloud Hub, value=200, smartAppVersionId=b0576b25-9755-4f2d-9658-eb58be8ecdb5
8f0bb81c-8c0d-41c2-9c31-2b1446822da7 8:57:51 AM: info smartapp_pause called by smartAppName=Home Cloud Hub, value=200, smartAppVersionId=b0576b25-9755-4f2d-9658-eb58be8ecdb5
8f0bb81c-8c0d-41c2-9c31-2b1446822da7 8:57:51 AM: info smartapp_pause called by smartAppName=Home Cloud Hub, value=200, smartAppVersionId=b0576b25-9755-4f2d-9658-eb58be8ecdb5
8f0bb81c-8c0d-41c2-9c31-2b1446822da7 8:57:51 AM: info smartapp_pause called by smartAppName=Home Cloud Hub, value=200, smartAppVersionId=b0576b25-9755-4f2d-9658-eb58be8ecdb5
8f0bb81c-8c0d-41c2-9c31-2b1446822da7 8:57:51 AM: info smartapp_pause called by smartAppName=Home Cloud Hub, value=200, smartAppVersionId=b0576b25-9755-4f2d-9658-eb58be8ecdb5
8f0bb81c-8c0d-41c2-9c31-2b1446822da7 8:57:50 AM: info smartapp_pause called by smartAppName=Home Cloud Hub, value=200, smartAppVersionId=b0576b25-9755-4f2d-9658-eb58be8ecdb5
8f0bb81c-8c0d-41c2-9c31-2b1446822da7 8:57:50 AM: trace Looking for local HCH server...
Never saw that smartapp_pause line before… This is during an SSDP request.
This is during a LAN request:
8f0bb81c-8c0d-41c2-9c31-2b1446822da7 8:59:54 AM: trace Received command ping with payload [:]
8f0bb81c-8c0d-41c2-9c31-2b1446822da7 8:59:55 AM: info smartapp_pause called by smartAppName=Home Cloud Hub, value=200, smartAppVersionId=b0576b25-9755-4f2d-9658-eb58be8ecdb5
8f0bb81c-8c0d-41c2-9c31-2b1446822da7 8:59:54 AM: trace Pinging local server at 192.168.1.252
Looks like an attempt to implement some sort of async operation for LAN requests gone awry? Looks like the “reply” to the LAN message arrives after the SmartApp has already given up waiting for it.
@Aaron who do I wake up for this? 
1 Like
Anyone know why the majority of my devices says HUB_OFFLINE unser status on the IDE? I am running the 17.7 beta firmware on the v2 hub.
Mine did the same thing immediately after the hub update, but after about a day they had all switched back to the normal online or offline status.
1 Like
A hub reboot fixed mine.
1 Like
I don’t believe there is a 16.14 thread and it looks like others are posting here.
Ever since this update I am very often having events that should only happen once happening multiple times.
For example I have an Aeotec doorbell that I send alerts to, when I send a single play it plays 6 times. It does this with my smart app, core, or hitting the beep button in the device handler.
I also on occasion get several push notifications when only one should have been sent.
I checked the logs, only one message being sent to the device as far as I can tell, repeat on the DH is set to 1. I tried rebooting my hub, no luck.
I am not aware of any trending issues post 16.14. If you haven’t already, please contact support with the approximate time of the missed/repeat events & notifications.
This same thing just happened to me. Rebuilt the pistons and everything returned to normal.
I am still seeing issues with LAN messages not being parsed by the hub. A hub restart temporarily fixes the issue, but 30 min later it starts again. Ticket #327172.
Issue started right after the hub updated itself on Tuesday.
1 Like
That happen to me few days back as well
I had just one odd event so far. A z-wave pocket socket decided to stop responding to requests to switch on/off from smartthings but continued to report energy usage and state (if I switched it on/off at the physical device).
Don’t know if it’s related but never had this issue before and the device has been in use for months.
I have a Z-Wave Plus Dragon Tec Smart Plug, which has failed to turn on and off, and also when it does it turns off on its own. I am not sure if it is the plug or the firmware.
Forgot to mention it returned to normal when I excluded it and added it back in. We should just mention these things as it could give the engineers clues as to what’s happening if it’s related. Might not be at all.
New Firmware release coming, not sure if today or later.Just got email.
Me too.
No date or time mentioned.
Oops.