Firmware Update - 11/17/15 - Version 14.13

[SBDOBRESCU (Bobby)]

Mike, check this out:

Need help troubleshooting!

What if I didn’t have time to catch support on chat??? Me: and I have an instance of the same app, upstairs and that continues to work fine support: I’m not sure, Mode Lighting is a custom SmartApp so I’m not really familiar with it Me: ok, let me switch to Smart Lighting then…and see if that works Me: it won’t work, I am wasting my time and yours…It’s the same incident I had for the past 3 weeks, just different devices… Me: it’s because of the setLevel bug whatever that is support: hmm, setlevel should have been addressed by the appengine update Me: when was that? support: should have been today, this morning Me: I’ve recreated Smart Lighting instance …it’s called Motion Hallway Dimmer 1 …going now to test it Me: Man!..yup…it’s fixed! Me: thank you support: well that’'s good!

[gusmorgan (Gus)]

soon…the same way they promise resolution to all the support tickets…soon…i have some open a year or more and they keep saying soon. they either hope i forget or they later say they have more important things to do or they promise the next update will fix the issue. unfortunately, ST is more of a hobby than a reliable smart home. promises promises

[Sticks18 (Scott G)]

Probably right when I get home from work, sunset routines are firing and I actually need it operational…

[Mike_Maxwell]

I don’t use setlevel via smart Lighting in any of my automations, my issue is that I’ve never been able to change the icons for dimmers…

[danrey (Dan)]

Still no update here. Still showing 14.00008. No info shared from Smartthing on if they are finished or delayed.

[sidjohn1]

Update window is from from 9 am-12 pm PT… Sounds like things are right on time to me if some users have received the update. I just got mine a few min ago… chill out.

[danrey (Dan)]

I be chilling but curious. 12 PM PT would be 2 PM CT and it now 3:27 PM CT here. Just saying.

[Mike_Maxwell]

14.8???, how did you end up with some bastard interim version?, official production release was 13.13 AFAIK.
BTW, I have the update, and notice no difference.

[danrey (Dan)]

Today was first time I have checked version, and it showed it was updates 10-22 to version 14.00008. Maybe it was in response to a support ticket. If it was it did not fix the problem.

[bamarayne (Jason "The Enabler" as deemed so by @Smart)]

Mine was 14.8 before the update… Maybe it’s time zone? Maybe that’s the reason that the bugs seem so random, there are different hub versions out there not being updated?

[thrash99er (Morgan)]

Mine is still 000.013.00013 shouldn’t it be updated by now??

[tgauchat (ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)]

@thrash99er

Mine is still 000.013.00013

That is a Hub V1 firmware version number. I highly suspect this update only affects Hub V2.

[stevesell (Steve S)]

Any idea what the improvements are for SHM?

[rob_gore (Rob)]

My Hub has been updated, just checked:

hubcoreVersion: 000.014.00013

Don’t everyone loose hope!

Most likely a long rolling update.

[brianjlambert]

Can anyone confirm that v1 hubs will receive the update? Or is this just a v2 fix?

[cpnwingit]

Still waiting patiently here on the east coast…14.00008

[Djobo (Maxime Gauthier)]

I checked the firmware version when I came back from work and its installed, but I noticed that my Nest Thermostat integration is not working well anymore: it looks like I cant send it commands to control it although I can still get the current live status from it.

Anyone else having problems with their Nest integration?

[mnflanagan97]

Same problem with Nest.

[bamarayne (Jason "The Enabler" as deemed so by @Smart)]

Try rebooting your hub.

[mnflanagan97]

Issue with Nest started before the firmware update.

There is a solution that worked for me:

Nest Thermostat

A simple fix might be to mod the code to add the following function to the Nest device type: def updated() { log.debug "Updated" data.auth = null } After installing and publishing that code, you’ll need to open the Nest device Preferences and resave them. This resets the authentication any time the Preferences are changed. Seems like a safe and reasonable permanent solution – worked for me. Also a lot less hassle than deleting and re-adding the device.