I’ll change the mode in the dashboard (say from Home to Night) and the Night tile will change to green, but the “Current Mode” tile will still be on Home.
In my IDE log, it says
error: java.net.UnknownHostException: http: Name or service not known @ line 508
debug: notifyWidget http://http://…/widgets/modeNight [mode:Home, auth_token: …]
I also noticed the same error when my temp sensor reported new data. The dashboard had the old value until I manually refreshed.
Also open your log in a separate window and then do the auth, then back in the log window click on the dashing access link so it only shows dashing, do you see any errors?
this is what it renders and the items are not the “things” I have. On the auth page I have selected only one of my things and this dashboard still renders the same.
@cassmie did you update main.erb in /hadashboard/Dashboards/ ? you need to update the widgets for your items. See Changing Widgets about 3/4 way down the page at https://github.com/FlorianZ/hadashboard
got all the way to opening the app for the first time before authorizing through smart things and it says my credentials not set. But the config variable matches my heroku email exactly. Any thoughts?
@willb: This one is easy, because there is really only one way you can get this error and that’s if the environment variable is not set Even if you set it to the wrong email address, you won’t get that error.
So my best guess is that you have a typo in the variable name itself.
Run this command to display all the config variables set for the app, and make sure that you spelled HEROKU_OAUTH_EMAIL correctly.
BTW, I also had an HP Touchpad laying around that gets even less use than my Nexus 7 and I set everything up on it just to see how it would look.
With zero modifications to any code, it has a clean 7x5 screen, with a little bit of unused space on the bottom. The same motion based/turn screen on functionality still works, and I’m still using the same app here:
For seemeless fullscreen capability without any hoops to jump through. Because of the extra row of tiles, and the physically larger screen having a slightly more impressive aesthetic to it, I might end up using an HP Touchpad for my build instead. They can be found used for about the same price as a used Nexus 7 as well.
Cons:
You need to get Android running on it and such, but there are tools nowadays that make it possible for anyone to do it now. The process a couple years ago was much more involved.
The tablet itself is physically thicker. This may/may not matter to you depending on mounting apparatus.
@florianz: Very nicely done, not just the actual code but the amount of time that you have spend writing documentation to make it so easy for others to get up and running. It was super painless to setup. Going to take a look at writing a dimmer widget when I get a chance, too much stuff on the go right now. The only issue i’m having and hopefully you can point me in the right direction is setting up tasker. I installed android on an old touchpad but I’ve never used android before so i’m not really sure where to go from there. I installed the apps and motion sensor seems to work, I setup a profile in tasker with intent received org.jastrazb.move.ACTION_GLOBAL_BROADCAST now i’m lost.
I forget if the plugin is automatically enabled on install, so just open it up like any app and make sure you activate it. I’ve actually even verified this works on an HP Touchpad with Android (CM11) installed. Oddly enough I mentioned this a couple posts ago.
@hawesg: What @bmmiller said. Also, if you want to go the route of listening to the intent: There is some old documentation floating around online. The author changed the prefix of the broadcast intent below:
I don’t remember off the top of my head (have to check when I get home) what the new prefix is, but if you go to the “Help” page in the motion detector app, it’s noted there.
@florianz thank god I thought I was loosing it, I ended up going with the plugin that Brandon posted for simplicity sake. @bmmiller thanks I thought I remembered someone posting something when I read through the thread but couldn’t find it when it came time to set everything up.
I was never able to get the smoke/co widgets to work properly. Not sure why but I think it has to do with their calls. I also have failed at a thermostat dashboard but have an idea on another way to go about it. Time will tell.
On a positive front, I found a way to lock the tiles in place on Android and iOS as well as some other mobiles.
In summary open hadashboard/assets/javascripts/application.coffee and add the following two lines at the bottom, following properly formatting.
Even if you set it to the wrong email address, you won’t get that error.
