Bug: First Reports

The Unofficial SmartThings Blog
Jump to: navigation, search

This page is for first report of any bugs. Just add a quick description and a pointer back to the discussion thread in the forums. The purpose of this page is to consolidate bug reports so that they are easy to find in the early stages. Please continue to report individual account issues to support. (This page is just for community use, it is not monitored by SmartThings staff.)

Bugs from a Specific Platform/Hub Update

September 2016

Hotfix September 20, 2016: multiple bugs [1]

platform update: major lag processing sensors [2]

platform update: various mode change issues [3]

Sept. 30: all scheduled tasks failing including mode changes [4]

October 2016

Multiple new reports of schedules failing and routines timing out [5]

November 2016

November 10 platform update broke the ability to change arm/disarm state in SHM for about half a day after the update completed. This was then repaired. [6]

November 10 platform update broke the ability for third-party apps to communicate with SmartThings, instead redirecting the page to the SmartThings IDE. This impacted smarttiles, google home, IFTTT, Harmony, and other services using OAUTH. This was repaired a few hours later . [7]

November 17 hub update failed for about 10% of the first set of customers, causing their zigbee devices to then be unreachable. ST halted the rollout of updates and is working on a fix for the affected customers. [8]

December 2016

December 1 update caused some initial problems, listed on the official status page. Although these were supposed to be fixed by the afternoon, multiple community members continue to report problems, particularly with zigbee devices and not being able to add new zigbee devices. It's not clear why some members are affected while others are not. Make sure you report the problem to support if you do have the issue. [/ Community discussion] Update: Smartthings staff have now confirmed that some customers were affected by multiple zigbee issues after this update. These include Motion sensors continually sending false alerts. [Staff confirmation]. Continue to report the problems to support if you have them.

Mobile App Bugs

September 2016

All 3 mobile apps were updated: multiple bugs including not being able to find smart apps, frequent log outs, modes not working, widgets not working, routines not working, not being able to view video in smart home monitor [9]

Can't find list of smartapps [10]

October 2016

Mobile app very slow [11] Staff responses in the following thread [12]

Can't log in. Confirmed by ST staff as a backend problem affecting all OSs. [13]

November 2016

Windows app frequently logs out [14]

Problems with mobile presence detection, particularly in the UK, but also some reports from the US [15]

Android app update 2.2.2 results in an error when trying to save a new Automation from multiple smartapps, including SmartLighting, Core, and Lock Manager. (The IOS version does not have the same bug.). The bug was fixed later in the day. [16]

December 2016

A mode change will occur as scheduled, but the mobile app will continue to show the previous mode until there is a hard refresh. [Community discussion]

General Platform Bugs including Mode Changes Failing, Database Corruption, IDE problems and Mysterious Events (Also see the Smartapps Section and the Platform Updates Section)

September 2016

because of the hub and platform updates this month, problems were reported as related to the update. See the platform update section for this month.

October 2016

Garage door opening and closing randomly [17]

IDE errors and severe lag ( according to ST staff this is related to the other lag and time out issues, it's not just the IDE) [18]

Mode changed mysteriously to morning in the middle of the night [19]

GITHUB format changed, can't find code [20]

Lights turning on when they were not scheduled to at the same time several days in a row [21]

Mobile app asked for authentication code, then appears to have completely reset. (Staff suggests it may just have created a new location.) [22]

November 2016

Daylight savings time fail [23]

Multiple problems reported related to the November 10 platform update. See that section above.

November 12: multiple people writing that device reports, particularly from sensors, aren't being processed. Many automation failures even though the devices show as active.. [24]

November 24: Device control and scheduling failures affecting customers on the NA01 shard. Smartthings engineering is aware of it and is working on a fix. Some customers still reporting problems on Friday morning. [25]

December 2016

December 10: Major cloud outage [official status page]

December 22: Multiple community members, but not all, reporting that routines scheduled to run at sunset never fire. The current workaround is to change the rule to run at a specific time. [community discussion]

December 27: multiple strange problems with people either unable to login or having missing devices or even a missing hub from their account. Support is aware of the problem and there have been on and off notices on the status page. [community discussion]

SmartApp and Routine Bugs

September 2016

Core: [26]

Time-based routines failing [27]

Mode changes but then nothing triggered by the mode change runs [28]

Voice notifications sometimes missed or only plays partial, multiple smartapps [29]

October 2016

Core Pistons executing randomly [30]

Scheduled apps failing [31]

November 2016

SHM screen stuck on "loading" for hours, cannot arm or disarm smart home monitor. Affecting both iOS and Android. [32]

January 2017

Multiple people reporting either security error messages or timeout messages when using either the IDE or the mobile app. Engineering staff have confirmed that this is an issue with one of the databases. It is not related to any specific smartapp, including core. It is only affecting some customers. [staff discussion]

Smart Home Monitor

September 2016

Video clips only playing if downloaded [33]

October 2016

Video clips not playing [34]

November 2016

SHM screen stuck on "loading" for hours, cannot arm or disarm smart home monitor. Affecting both iOS and Android. [35]

December 2016

Speech notifications not working with some SHM alerts. After investigation by SmartThings staff, two separate bugs were identified, and a fix has been promised soon. [community discussion]

SmartLighting

December 2016

SmartLighting has changed and now if you try to create a new automation there is no way to specify the button number that you want to use on a minimote with the stock device Handler. Any other device type handler which does not specify the number of buttons field will have the same problem. [36]. Update: this was fixed in the minimote device type handler on 6 December 2016.


By Device

September 2016

severe lag for Hue bridge [37]

Hue bridge has a bad address or some bulbs unreachable from ST ( but work OK from other apps) [38]

Hue bulbs marked as "unreachable" still work through the Hue app but don't work through SmartThings [39]

Samsung SmartThings motion sensor false positives [40]

Samsung Smartthings multisensor false positives [41]

LIFX wonky [42]

Samsung powerbot vacuum not working [43]

October 2016

Arlo clips not displaying [44]

GE/Jasco in wall switch indicator lights suddenly change behavior [45]

Multiple Hue problems, including severe lag[46]

Friends of Hue (bloom, strip) and the old Hue Lux that used to work with smart apps now don't seem to respond to smart things, although they continue to work from the native hue app [47]

SmartThings sensors keep dropping off network, or only report temperature, or battery reporting incorrect [48] (includes ST staff comments)

Sonos plays once or twice, then stops, or fails altogether [49]

Sonos stutters [50]

November 2016

November 12: multiple people writing that device reports, particularly from sensors, aren't being processed. Many automation failures even though the devices show as active. [51]

Hue bulbs showing significant delay between bulbs when a group request is processed through SmartThings, creating a popcorn effect. Reported as new in the last few weeks. [52]

Samsung smart vacuum won't connect to SmartThings even though it works fine with the Samsung smarthome app. [53]

Two people reporting that they would create a simulated switch on one day, everything would work fine, and the next day the simulated switch would have disappeared from their account. [54]

December 2016

Smartthings did a zigbee firmware update in early December to allow over the year (OTA) updates of the SmartThings branded devices. Since then, multiple community members have reported that when the OTA check occurs every day, their Osram RGBW devices do strange things, generally reverting to white and coming on full brightness. Other community members are not having a problem with these devices, so it may depend on the firmware level of the Osram device. If it happens, report it to support. [Community discussion]

The same zigbee update is causing some zigbee motion sensors to think they are supposed to be updating when they are not, and issue multiple false motion alerts, sometimes over many hours. So far this has affected both the Samsung brand motion sensors and the hue motion sensors which are connected directly to the smartthings hub. [community discussion]

Around December 15, multiple community members begin reporting that they were having odd device communication failures, and that those failures could affect devices of any protocol. The devices appear to be reporting in OK, but instructions to the devices were sometimes logged but not performed. Both Z wave and zigbee devices could be affected. Rebooting the hub might cause things to be OK for a few hours or a day or so, but then the problem would return. Support is currently collecting all reports of this issue. It is definitely not affecting all customers, but it is affecting some, and both V1 and V2 hubs have been affected. [Community discussion, including the support ticket number you should reference when reporting this problem]

January 2017

Some members report GE switches randomly changing parameters, particularly for when the indicator LED comes on. This might represent back end changes. [community discussion]

Bugs reported by developers regarding the ST groovy implementation

September 2016

"Ghost" routines (null label) [55]

December 2016

HubAction calls crashing hub [community discussion]