threeAxis is a vector map of Acceleration (g-force … scaled -2g to +2g, or maybe -8g to +8g, I’m guessing).
However, the actual physical device returns a true / false (1 / 0) value as well to indicate active or inactive.
I presume that the physical device filters out trivial changes (or not?), because I don’t see any filtering in the SmartSense Multi device handler code:
So what would I use as code in the CSS? Here is what I have now.
/ATTIC FAN/
.tile.acceleration {background-color: #b24747;}
.acceleration.active:before {color: #006778;}
.acceleration.inactive:before {color: #9F792C;}
I am embarrassingly weak in SmartTiles CSS tweaking; I haven’t had to grow this skill because there are so many clever folks here with the right answers!
It does take some trial and error … so it is worth tweaking a different device instance that you can actually activate with some “vibration / acceleration”; you might be able to create a Virtual or Simulated device, actually, for testing.
If you aren’t able to create a test, I’ll try to create a simulated / virtual device and see the effect of the tweaks.
Quick skim of this thread gives me the impression you might have better selectivity by including the Theme Class in the selector for each Customized CSS line too. But what you have is either correct, or pretty close.
e.g.,
.theme-cobalt .switch {background-color: #006666}
.theme-cobalt .dimmerLight {background-color: #004c4d}
.theme-cobalt .light {background-color: #004c4d}
Thanks that would be appreciated as I don’t want to screw it up more than I already have.
Hello, Grant here from ZEE. We are trying to make it a simple swap over as much as we can. We appreciate it is a big ask. Our vision for ZEE is not just another HA hub. We have been building industrial automation systems and in wall mounted touch screen controllers as part of C-BUS automation systems for high end houses for 10 years now. We know a bit about automation and a lot of the complexities. We will share in the next couple of days our draft design we are working towards for the production model - it will look very slick I can assure you of that (not like the flaky design mentioned in these posts!). This ZEE Smart Controller will have built in 2 light dimmer circuit controls and 2 relay circuit controls.
A big part of our lead time is getting the UL certification and testing. We have already informally started that process with a UL testing lab and are on the right track.
We see the ad-hoc nature of many systems and sole reliance on a cellphone as a limitation. Cellphone/Tablet control will be secondary for ZEE.
Being wired to the mains offers a number of advantages in our opinion. Turns all those existing lights into SmartThings and creates an interface to control other SmartThing devices.
The ZEE controller also has built in temperature and humidity sensors that work best in a static location.
Also, the mains module would need to be installed by a qualified electrical installer, but if you want to install yourself, at least turn the power off first!
I can share more if interested. We have put a lot of thought into this.
I am trying to change the color for the dimmer, but the code above only changes it for the switches not the dimmer. Tried many different ways but no luck. Anyone have any ideas?
The list above missed “.dimmer” itself.
Thanks that did the trick!
So has anyone had any luck using Tasker to unlock an Amazon Fire 7" tablet? I’ve tried everything I’ve found on the subject and nothing seems to work. I have the tablet mounted in the bedroom and can make Tasker turn off the screen (which locks the device) no problem — using mode changes. I’d like the tablet screen to be on when in various home modes and then have the screen off in away/sleep modes. I currently have it setup to turn the screen brightness all the way down, but the screen is still far too bright to leave on when trying to sleep.
I know you said you’ve tried all kinds of things. So, this one is probably already a no-go, but have you looked at this thread yet?
If you want to give that idea (or something related) a try, I’d be happy to assist.
I have the same issue with this tablet. The best I could do was to lower screen brightness, start the clock and put the clock in night mode.
Alternatively, you could create a scene in tasker where the screen is entirely black.
uh-oh…I just got a Fire 7" tab to see how it works with SmartTiles, etc. Hopefully I won’t run into this issue. If I do though, I’ll be right back here to get on the right page. 
I too have the very nice (especially at 35bux!!) 7" Fire Tablet.
For $35 I do not care too much about it, and as such, the first thing I did was download Amazon-Fire-5th-Gen-SuperTool-old.zip from http://rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool.
I can confirm a) everything works as outlined on this web site, b) the web site itself is malware free, and c) so is the ZIP file.
First thing I did was to ROOT it, then put the Nova Launcher on it, followed by all my usual Google goodies. Also removed the lock screen ads.
Now admittedly I have NOT used Tasker in any capacity, but if I were a betting man, I’d wager it will work. The Amazon Fire OS is heavily modified, and by doing the above, it brings it more in line with a standard Android device IMO.
Thanks
Johan
I rooted mine also. Still no luck getting rid of the lock screen. I think a custom ROM is necessary but would love to be proven wrong.
I wonder if anybody in this thread has figured out a solution to the lock screen issue yet…
I’m going to cross this proverbial bridge in a few months ( <2 ) time. For what I paid for it, I should have bought 4-5, but I digress.
I believe the tool I quoted contains a backup mechanism as well. I would definitely try another ROM on it.
J
I picked up a couple of Kindle Fires for £5 each but have also found them to be less than ideal - I don’t like the screen on all the time, but there’s no functionality to put the device to sleep and wake it back up without using the power button, which is hidden where I want to put mine.
So I’m stuck using a Blackberry Playbook, which at 99p is the best bargain and supports tapping on the screen to wake up - but it’s a bit old and slow, and whilst ST looks OK on a couple of browsers, it’s still slow to refresh and sometimes the auto refresh can be a bit janky. I’ll come downstairs in the morning and it’ll still say whichever lights were on when I used my “Going to bed” rule are still on, even though they’ve been off for 8 hours. Chrome on an Android tablet doesn’t seem to suffer from slowdown or the refresh issue, but I’ve not yet found a tablet that I can tap on the screen to wake up like I can the Playbook.
So, do you actually need the touch-to-turn-on-screen option, or would turning it on via motion in the room be OK? If the motion route would work for you, this thread has the answer…
…that is, as long as you can use SharpTools, Tasker and Secure Settings on the tablet.
Or is this not even possible on a rooted Fire?
Well, even if that doesn’t work on a Fire, I got some other tablets which at a push I’d dedicate to the cause - an nVidia Tegra Note (Android 5.1 7") and some older Samsung ones that are still on 4.2 or something. They’ll definitely run Tasker and Secure Settings, got no experience of SharpTools.
The problem with that is the tablet lives in one of the only rooms that doesn’t have motion sensors! However that could be overcome, just at a huge cost in comparison to the tablet… I wonder if putting a multisensor on the back of it and using the vibrate sensor would be a nicer option, that’s almost tap-to-wake just in a hugely round-the-houses way involving the device firing a signal across the internet just to turn its own screen on 
I actually sort of like the vibration sensor idea. Hadn’t thought of that. You could also use a smart button/switch of some sort (Flic?). I will give it a try sometime, just to see how well it works.
Regardless of which sort of device you use as the trigger though, the method in the thread I linked to above should still be viable as a way of getting that trigger to result in something happening on the Android.