hmm.. maybe there's a bug there. I don't think I've ever tried using times like that. Mine's set to 6 AM to 11 PM I believe
I may have to look into rooting them too. I think two of the three I can.
I rooted 2 or 3 2017 fire tablets and it was a major pain.. the hardest thing was opening it up and having to use a paperclip or something while sending some payload from Linux.. but it did work at least.
I was setting it to full 100% with this (and 75%, 50%, 25% when the battery gets to 15%, 10% and 5% respectively)
I can change this to BRIGHTNESS_OVERRIDE_NONE instead of 100% which should use your system setting. The only possible problem would be if you have it set to less than 75% by default -- the low battery will actually make it brighter. But, at least it wouldn't have any effect if that setting was off.
/**
* Default value for {@link #screenBrightness} and {@link #buttonBrightness}
* indicating that the brightness value is not overridden for this window
* and normal brightness policy should be used.
*/
public static final float BRIGHTNESS_OVERRIDE_NONE = -1.0f;
That all makes sense, and I would expect that if the Low Battery Dim Screen option was turned on. In my case I have it off, so I would expect the screen brightness to be the device's setting. If it is enabled, is there a way to read what the device setting is at and then increment it down? The brighter the screen, the faster you are going to use up the battery. I thinking about your case here. If your PS doesn't supply enough voltage to last the day, starting at 100% brightness seems like it would last less. But starting at the device setting, say 50%, your battery could possible make it longer in the day until the screen started dimming down. Of course a good chunk of this all goes out the window if you are using adaptive brightness.
Some follow up questions to help me to understand how your app functions. Hubitat Package Manager shows that it installs a driver for HD+. Does this driver handle the communication between the Android app and with Maker API?
If that's true:
Could the driver write directly to Hub Variables using the Rule Machine API?
Could the driver subscribe to Hub Variable update events?
No, there's 2 Hubitat device drivers but neither of them replace MakerAPI. I've considered trying to write a Hubitat app that would do just that.. similar to how SharpTools which has a built-in app. I'm no where near experienced enough of a Groovy dev though to do this though.
But, if I could I would! Not that there's anything wrong with MakerAPI -- the only major thing I'd like to add to it is some way to push out device changes to the phone when you're remote (cloud mode).
version 1.0.2520 (beta)
That's my hope but let me know if it doesn't seem to work
is there a way to read what the device setting
I couldn't find a way to check this in code 
But starting at the device setting, say 50%, your battery could possible make it longer in the day until the screen started dimming down
Yeah, I'll have to experiment with it.. I was really just trying to figure out how to get more power to the tablet since I'm probably underpowering it. I have 3 other wall mounted devices and they have no problem running all day at full brightness.. only difference is they're plugged into the wall and 7" tablets too so guessing they draw less too.
My eyes thank you!!!!
The device setting was to turn off the display after 30 seconds of inactivity. I swore I put this higher in the past. Regardless, it's set to 30 minutes now.
I disabled the "keep screen on while charging" debug option. Set the Keep Awake between 6 AM and 2 AM, and enabled the screensaver with a 5 minute timeout. I also enabled the "wake on motion" and "wake on motion from devices" options. I'll keep and eye on the tablet for the evening and see what happens. I won't be up past 2 AM though. 
EDIT: 3 hrs in and the screen is still on as it should be. Much better than going blank within 2 minutes.
EDIT 2: I couldn't sleep, so I was up after 2. The tablets went semi-dark, as expected. I could see that they were still on with some lighting, but the screen was blacked (really more greyed) out. For those that woke on motion, they did. Thanks for the suggested settings.
I think starting with build 2514, the counters on the devices stopped showing those that are on/open. In my screenshot here, you can see I have a window open, but there is no yellow number next to the total device count. My Locks/Garage does the same thing, but in this screenshot everything is closed and locked. It looks like folders still count the devices though. My Rooms folder shows how many rooms have something turned on. In this case I have 1 room with at least 1 thing on.
There was a bug with the folder status (on/off bubbles) that I fixed. Maybe I missed something - let me try to reproduce.
What's in the Rooms folder? Is that an icon you picked?
Yes, I selected that icon. It's a folder that contains more folders to represent each room in the house. I like the concept of long pressing and holding to turn everything in a particular room off. (Kids...) I also have a Lights/Fans group that contains ALL the lights, switches, fans, etc. But scrolling through that can be a headache. Separating them into their respective room makes it easy. I know I want to turn the fan on in the office, I click on Rooms, Office, Office Fan.
Any chance of this happening in the near future? I would flag each dashboard file.
version 1.0.2531 (beta)
The big change in this version is adding support for a device activity tile.. which is basically me trying to come up with a valid reason (in Google's mind anyway) to ask for the activity permission (which is highly recommended if you're using the app for presence or location tracking)
No idea if it'll help get the app approved on Google Play but it's worth a shot..
More info on device activity tile here
I also did a little more tweaking of the low battery feature. This time if it's enabled and the battery is < 5%, I'm enabling the screen saver. Just another option for keeping the device alive while keeping the app running
I forgot to mention this in the release notes but this should be fixed too
Yep... Fixed. Thank you again for all your amazing work.
Says to use the tile driver and select device activity in drop down but it doesn't seem to have that option?
I didn't actually think anyone was going to try adding this.. my main goal initially was to have a valid reason to give Google for using the activity recognition permission in the app. It's optional but recommended if you want to use either presence or location features in the app.
I have an updated HD+ device driver that I need to update which has it.. just haven't had a lot of time. I'll get it updated as soon as I can though
No that's fine I was only going to test it for you. However I'm assuming I can continue using the feature via the location device as well? That's currently how I get the state data I need.
Yep the location tracking which sends your location also sends device state.. I didn't change anything there. So technically you can get this data to the Hub already.. I just wanted to create something simple in the hopes that I can explain it to the Google review team
Just wanted to update that the Sonos custom text input for tts has been working great. We have been using it. Thanks!
@jpage4500, I'm not aware of anything like this in HD+ and I kinda like what this guy wants to do, albeit in Node-Red dashboard. I can see where I may use the same kind of display in HD+ if I could.
It looks like Google Play approved the app so you should start getting updates again!
Download the Hubitat app
