So I was going to read through this all…until I realized it wasn’t ending and there were 600 posts.
Did anybody happen to post anything good about a wall mount for a nexus 7 by any chance?
Somebody should make some good looking ones and sell them to ST Community 
(and yes, I would consider yours good looking OP).
No one submitted this to me… or did I miss it?
Yeah, it’s getting slightly out of control. Having said that, there were only a handful of posts about custom frames. You can use the search function to limit the search to this topic, and look for something like “frame”.
Is anyone showing acceleration on their dash? I have multi-sensor on our washing machine, so it alerts us when it’s done, but I don’t see an existing widget that suits it.
This is a huge thread. It’s like we need a new one with not only the original post (cause it’s amazingly good) and the current state of things. I want to add my Nest thermostat to this but have no clue if it’s possible yet.
I (and SmartThings) also need to thank @florianz. I was ready to switch to Wink because of Relay. For some reason I searched for it on here and then found this thread. I then proceeded to be BLOWN away and now find myself taking a stab at this.
@ronnycarr: how can I change to the theme that you are using vs. the gray theme?
@Jsalicru you’ll need to manually change the colors in the css file for each widget. Doing this you’ll be able to create any color theme of your choice.
Wow! That looks great. I really like the color scheme. Could you share how you integrated the music controller into the dashboard? Also, is it possible to integrate spotify using their web API? Could you share what you’re using to switch apps? I’m looking for something simple and intuitive to use on my Nexus 7.
Greetings all! I’m new to the SmartThings community. I’ve been thoroughly impressed with all of the awesome things everyone has created in the development community. This dashboard is my favorite, by far.
I’ve had it up and running for almost a week. However, I’ve recently run into what appears to be an authorization issue that I’m hoping someone can help root cause. The symptoms seem similar to some of the issues encountered by others about a month ago when there were oauth issues.
I can authorize devices for use on the dashboard via the app. When I attempt to authorize on the web I see the list of devices I’ve authorized on my device. Clicking the authorize button redirects me to my dashboard. However, none of the tiles reflect the correct state. If I return to the authorization page online, I see that all of the previously authorized devices are no longer authorized (all are unchecked).
If I authorize all devices again via the app and go directly to my dashboard page, the dashboard correctly displays the state on page load. However, the tiles do not update when changing the state of any authorized device.
I checked that all config entries are correct, I’ve tried using all new config entries, I’ve tried starting from scratch and still appear to have the same issue.
Any help is greatly appreciated! Thanks.
It looks like there was another background update pushed to the SmartThings platform yesterday and it appears to be impacting the OAuth workflow. Basically, any mobile app or web app that uses OAuth can successfully complete the authorization and get the necessary token for viewing/controlling your devices, but the list of devices is not properly being saved.
I don’t personally use the Home Automation Dashboard, but I imagine it is using the OAuth workflow and is probably suffering a similar fate as IFTTT, Harmony, and other apps that use OAuth. The simple workaround for this is to switch back to the main SmartThings mobile app and authorize Things for the SmartApp in question.
Check out the video showing the workaround applied to my Android app, SharpTools (Tasker and Widgets for Android):
Thanks! Your video appears to confirm the behavior I’ve seen attempting to authorize devices for the dashboard. I’ve been authorizing via the SmartThings app, in the interim, just as you’ve suggested in the video. This at least allows me to control the devices in my home.
However, I hope that a permanent fix is in the works. Otherwise, tiles on the dashboard will only be as current as the last page refresh.
I have nest on my dash. It’s really easy to add - just add the gem reference, and copy over the files, bundle install then push it all up to heroku.
See on my repo: https://github.com/phae/hadashboard/commit/9cb5b96e2f75e760d6c766a745e8f051f6074491
And the widget reference: https://github.com/Eric-Gonzalez/nest-dashing-widget
Thanks for flagging this. We have identified the issue and we have a fix in the works. We’re planning a release to address this issue on Monday. Sorry for the inconvenience and thanks to both of you!
Yes, I had this issue with my Harmony. Thanks for catching this.
Good news! Thanks for the update.
I need a little help. Somewhere I screwed up and I think the short of it is that my local files and the heroku files are out of sync. Even if I pull from heroku then edit my erb, commit then push the change I will get an application error. I end up reverting Heroku back and it works again, but I’d like to update my files.
Help?
Whats the error that you are getting?
"An error occurred in the application and your page could not be served. Please try again in a few moments.
If you are the application owner, check your logs for details."
Where else could I get a more detailed log?
the command “heroku logs” will give you recent log history.
2014-12-14T04:23:43.405806+00:00 heroku[api]: Release v33 created by xxxxxxxx@gmail.com
2014-12-14T04:23:44.112509+00:00 heroku[web.1]: State changed from up to starting
2014-12-14T04:23:46.615777+00:00 heroku[web.1]: Stopping all processes with SIGTERM
2014-12-14T04:23:46.875217+00:00 heroku[web.1]: Starting process with command bundle exec thin start -R config.ru -e production -p 21726
2014-12-14T04:23:49.060884+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.1/lib/backports/std_lib.rb:9:in require': cannot load such file -- nest_thermostat (LoadError) 2014-12-14T04:23:49.060905+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.1/lib/backports/std_lib.rb:9:inrequire_with_backports’
2014-12-14T04:23:49.060908+00:00 app[web.1]: from /app/jobs/nest.rb:1:in <top (required)>' 2014-12-14T04:23:49.060909+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.1/lib/backports/std_lib.rb:9:inrequire’
2014-12-14T04:23:49.060911+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.1/lib/backports/std_lib.rb:9:in require_with_backports' 2014-12-14T04:23:49.060912+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/dashing-1.3.4/lib/dashing/app.rb:157:inblock in require_glob’
2014-12-14T04:23:49.060914+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/dashing-1.3.4/lib/dashing/app.rb:156:in each' 2014-12-14T04:23:49.060916+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/dashing-1.3.4/lib/dashing/app.rb:156:inrequire_glob’
2014-12-14T04:23:49.060917+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/dashing-1.3.4/lib/dashing/app.rb:167:in <top (required)>' 2014-12-14T04:23:49.060919+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/dashing-1.3.4/lib/dashing.rb:3:inrequire’
2014-12-14T04:23:49.060922+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/dashing-1.3.4/lib/dashing.rb:3:in <top (required)>' 2014-12-14T04:23:49.060924+00:00 app[web.1]: from config.ru:2:inrequire’
2014-12-14T04:23:49.060926+00:00 app[web.1]: from config.ru:2:in block in <main>' 2014-12-14T04:23:49.060929+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:55:ininitialize’
2014-12-14T04:23:49.060932+00:00 app[web.1]: from config.ru:1:in <main>' 2014-12-14T04:23:49.060928+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:55:ininstance_eval’
2014-12-14T04:23:49.060930+00:00 app[web.1]: from config.ru:1:in new' 2014-12-14T04:23:49.060933+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.2/lib/rack/adapter/loader.rb:33:ineval’
2014-12-14T04:23:49.060936+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.2/lib/rack/adapter/loader.rb:33:in load' 2014-12-14T04:23:49.060938+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.2/lib/thin/controllers/controller.rb:182:inload_rackup_config’
2014-12-14T04:23:49.060939+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.2/lib/thin/controllers/controller.rb:72:in start' 2014-12-14T04:23:49.060941+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.2/lib/thin/runner.rb:199:inrun_command’
2014-12-14T04:23:49.060942+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.2/lib/thin/runner.rb:155:in run!' 2014-12-14T04:23:49.060943+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.2/bin/thin:6:in<top (required)>'
2014-12-14T04:23:49.060947+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/bin/thin:23:in load' 2014-12-14T04:23:49.060948+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/bin/thin:23:in'
2014-12-14T04:23:49.709956+00:00 heroku[web.1]: State changed from starting to crashed
2014-12-14T04:23:49.701014+00:00 heroku[web.1]: Process exited with status 1
2014-12-14T04:23:50.114248+00:00 heroku[router]: at=error code=H10 desc=“App crashed” method=GET path="/" host=xxxx-woodland-8447.herokuapp.com request_id=**3 fwd=“xxx.xx.xxx.xx” dyno= connect= service= status=503 bytes=
2014-12-14T04:23:57.085295+00:00 heroku[router]: at=info method=GET path="/events?lastEventId=&r=9356952868402004" host=xxxx-woodland-8447.herokuapp.com request_id=<removed fwd=“xxx.xx.xxx.xx” dyno=web.1 connect=0ms service=91598ms status=200 bytes=1020
2014-12-14T04:23:56.480115+00:00 heroku[web.1]: Error R12 (Exit timeout) -> At least one process failed to exit within 10 seconds of SIGTERM
2014-12-14T04:23:56.480332+00:00 heroku[web.1]: Stopping remaining processes with SIGKILL
2014-12-14T04:23:57.830339+00:00 heroku[web.1
]: Process exited with status 137
2014-12-14T04:23:58.955980+00:00 heroku[router]: at=error code=H10 desc=“App crashed” method=GET path="/events?lastEventId=&r=8780705893877894" host=xxxx-woodland-8447.herokuapp.com request_id= fwd=“xxx.xx.xxx.xx” dyno= connect= service= status=503 bytes=
2014-12-14T04:24:02.002369+00:00 heroku[router]: at=error code=H10 desc=“App crashed” method=GET path="/events?lastEventId=&r=2639680583961308" host=xxxx-woodland-8447.herokuapp.com request_id= fwd=“xxx.xx.xxx.xx” dyno= connect= service= status=503 bytes=
2014-12-14T04:24:06.949377+00:00 heroku[router]: at=error code=H10 desc=“App crashed” method=GET path="/events?lastEventId=&r=7044556769542396" host=xxxx-woodland-8447.herokuapp.com request_id= fwd=“xxx.xx.xxx.xx” dyno= connect= service= status=503 bytes=
2014-12-14T04:24:16.296318+00:00 heroku[router]: at=error code=H10 desc=“App crashed” method=GET path="/events?lastEventId=&r=2054878994822502" host=xxxx-woodland-8447.herokuapp.com request_id= fwd=“xxx.xx.xxx.xx” dyno= connect= service= status=503 bytes=
2014-12-14T04:24:32.954310+00:00 heroku[router]: at=error code=H10 desc=“App crashed” method=GET path="/events?lastEventId=&r=0587037808727473" host=xxxx-woodland-8447.herokuapp.com request_id= fwd=“xxx.xx.xxx.xx” dyno= connect= service= status=503 bytes=
2014-12-14T04:24:50.039342+00:00 heroku[router]: at=error code=H10 desc=“App crashed” method=GET path="/events?lastEventId=&r=4734081297647208" host=xxxx-woodland-8447.herokuapp.com request_id= fwd=“xxx.xx.xxx.xx” dyno= connect= service= status=503 bytes=
2014-12-14T04:25:06.959156+00:00 heroku[router]: at=error code=H10 desc=“App crashed” method=GET path="/events?lastEventId=&r=0110315717756748" host=xxxx-woodland-8447.herokuapp.com request_id= fwd=“xxx.xx.xxx.xx” dyno= connect= service= status=503 bytes=
2014-12-14T04:25:23.948171+00:00 heroku[router]: at=error code=H10 desc=“App crashed” method=GET path="/events?lastEventId=&r=7119517179671675" host=xxxx-woodland-8447.herokuapp.com request_id= fwd=“xxx.xx.xxx.xx” dyno= connect= service= status=503 bytes=
2014-12-14T04:25:47.540301+00:00 heroku[router]: at=error code=H10 desc=“App crashed” method=GET path="/events?lastEventId=&r=9266149369068444" host=xxxx-woodland-8447.herokuapp.com request_id= fwd=“xxx.xx.xxx.xx” dyno= connect= service= status=503 bytes=
2014-12-14T04:26:04.044535+00:00 heroku[router]: at=error code=H10 desc=“App crashed” method=GET path="/events?lastEventId=&r=0219495799392462" host=xxxx-woodland-8447.herokuapp.com request_id= fwd=“xxx.xx.xxx.xx” dyno= connect= service= status=503 bytes=
2014-12-14T04:26:10.895575+00:00 heroku[api]: Rollback to v32 by xxxxxxxxx@gmail.com