Sensors and Life360 no longer show status in Webcore. Did I break something?

[Mebejedi]

These used to show open/closed, temperature, and presence. How would I fix this?

They register in ST.

[jkp]

Piston editor shows NaN for device attributes

The v0.3.109.20181207 update introduces a known bug as a trade-off for restoring access to the dashboard for a growing group of webCoRE users. You will see the following until this workaround can be removed: [47%20AM] For the past few months, the SmartThings platform has experienced degraded performance in retrieving device information. Users with a large number of devices (generally > 100) experienced recurring errors when loading the dashboard – the more devices the more often the dashboar…

webCORE Dashboard Completely Broken. Please Help [UndeclaredThrowableException]

I’ve released a dirty fix for the timeouts. v0.3.109.20181207 - BETA M3 - Dirty fix for dashboard timeouts: seems like ST has a lot of trouble reading the list of devices/commands/attributes/values these days, so giving up on reading values makes this much faster - temporarily?! The problem is the ST platform timing out (there’s an execution limit of 20s) while reading the list of devices - we’re reading all selected devices with their commands, attributes, and values - I gave up on the valu…

[Mebejedi]

Thank you. So this will remain a problem for awhile, then?

[ipaterson]

Well, it doesn’t seem like anyone had their dashboard loading issues resolved by the workaround, so I suspect that the next release in January will either revert that change or put it behind a preference to avoid breaking the device status for everyone.

[Mebejedi]

If it’s a growing problem, does that mean there are there just too many ST or Webcore users for the system to keep up with?