Another suggestion: is it possible to have the action when activating an Android Auto device automatically be the same as the action that's configured for the same device on the dashboard?
The Android Auto integration is a great concept, but in practice, it's just too complicated to use in a car. I don't want to tap here, tap there, pick a command while I'm driving. I just want to tap a device and know that it will send the command I want. The fewer taps you need to make while driving a car, the better.
On that note, I noticed something that's probably much easier to fix than this change that I suggested earlier and would accomplish the same goal: if there's a button device displayed in Android Auto, and that device only has a single button, don't prompt the user for which button they want to send -- just send "Button 1 pressed" when you tap the main icon in Android Auto.
That sounds reasonable. I think by default HD+ will toggle a light or switch but will prompt for sensitive devices like locks, valves or garage doors.. stuff you want to be deliberate with IMO.
btw - it's fine here but there is another HD+ AA thread if that's easier to track questions/suggestions
support Hubitat Security (https) for Backup and Restore to Hub
default all local requests to using https
fix using custom custom image for shortcut tiles
LOTS of changes in this one.. as such there's always a chance for an issue or 2 so please let me know if you see anything.
First off, you can now set HD+ as the default home screen. This will prevent users from exiting the app so it could be useful for the wall mounted (Kiosk) tablets. HD+ can still open up other apps (such as app shortcut links) -- something the previous 'app pinning' logic couldn't do.
I'm not sure there's a way to directly prompt you to set HD+ as the default Home app but I can open the app preferences which is usually where this setting can be changed. You can open it from menu -> Security -> Default Launcher
Next up I changed the app to use https by default for all local requests. If for some reason https doesn't work (and let me know if it doesn't), you can switch back to http. If the app is already logged-in, open menu -> Hubitat Hub -> Hub Details and enter "http://HUB_IP" (see screenshot below).
If you're not logged in yet, there's a new checkbox in the login screen which you can uncheck to use http.
Related to https, I added support for Hub Login Security (username/password). If you try to do anything that requires a Hubitat Login, HD+ will prompt you for username & password. This should work for the auto login as well as backup and restore to the Hub features.
Lastly, I added a new device type, Activity Monitor. You can add it like any other HD+ tile (menu -> edit -> add tile (+ button) -> activity monitor.
I wanted something that supplements the Battery Monitor.. I noticed I have some devices that report battery = 0 but are still reporting events. I found the Device Activity Hubitat app but it didn't really work/display on the dashboard. What I'm doing is pretty simple for now -- it'll just display devices ordered by last activity time. If you notice some devices don't have anything listed for the time -- it's a bug (feature?) that I've asked about a few times in the past but no answers yet.
Anyway, I'm open to ideas how to make this more useful.. maybe combing it with battery info as a way to identify which devices need attention.
This would be doable but wasn't a design goal I had originally or a request that has ever come in since. If you can display variables, there could be some option to write something out to a string in whatever format would work.
That's strange.. I know I get a "not secure" warning in Brave/Chrome. I just noticed that the SSL cert expired on Apr 14, 2021 so that might be why the warning.
03/10 00:03:36 E HubitatManager fetchHsm: Exception:Read error: ssl=0xb4000073bb0cb018: Failure in SSL library, usually a protocol error error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE (external/boringssl/src/ssl/tls_record.cc:592 0xb4000074eb042810:0x00000003)
Is it a Pixel 7? That's what I have too.. now I'm even more confused. I remember when first working on this app I had issues with really old devices and https.. that's likely why I was using http by default.
Are you able to use the app remotely? If so, https is working but it's this specific Hubitat SSL certificate that's causing the issue.
+1
-> 
