[RELEASE] HD+ - Android Dashboard

jpage4500 · June 20, 2020, 2:17pm

Version 1.0.155 (beta)

I just checked in the fix for RGB and dimmer light switches (not requiring the "Light" attribute). I don't have one of these to test with but I think it should work.

I also added a 'cloud login' toggle switch in settings. Once enabled this will force all network traffic through cloud.hubitat.com. The switch only shows up if we can get the cloud API token on login (which requires the Maker API 'cloud enabled' option to be checked). This mode allows for a manual pull-to-refresh to be done anytime as well as some different logic after sending commands. I'll continue to improve it but this should be an improvement over the previous version.

make it much easier to match colors

Yeah, the more I start to think about how I'll actually use my RGB lights the more this makes sense.. not just for background tile colors but actually matching 4 outside lights so they're not all different shades or red or whatever. I'm open to any ideas.. RGB entry doesn't seem like the most user-friendly way IMO but as an 'advanced' option it certainly would be easy to add in.

the earlier version had an option to change the template for the tile

I used to let you change any device type to any other device type but realized that's probably not the right idea.. I was more trying to give a way to change between devices that shared the same common attributes.. for example a "ContactSensor" could be on a door or a window or some other place. A "Switch" could be on a light switch or it could be a fireplace. I'm still learning all of the actual uses for these things! Anyway, you can still change a ContactSensor or Switch - but I didn't think there would ever be a reason to change between a "GarageDoorControl" and a "Weather" device type or things like that..

Speaking of - I want to add Fan support.. also am looking at adding the Mode support (not as trivial though)

pat.richards · June 20, 2020, 2:36pm

just download the APk 1.0155 my Lutron cassetta wall switch is not allowing dimming just on and off and my magic light RGB bulb is only showing on and off....

also some of the devices are not showing correct status at start up...Need to do more debugging on that one

danfox52 · June 20, 2020, 4:05pm

Your latest update fixed this. Thanks

danfox52 · June 20, 2020, 4:07pm

Does this still use local when it can?

LosinIt · June 20, 2020, 8:56pm

@jpage4500, this is a great idea and thanks so much for taking it up!

LosinIt · June 20, 2020, 11:22pm

@jpage4500 I'm sure you have a LOT on your plate with this but, assuming you're keeping a TODO list, please add multisensor support for the Aeotec Multisensor 6, Inovelli 4-in-1, and @iharyadi's environment sensor (Hubitat with Homemade Temperature, Humidity, Pressure and Light sensor).

Thanks

jpage4500 · June 21, 2020, 12:12am

No - it's all cloud or all local from the toggle switch now. I was trying to figure out a way for the app to recognize it's on the local WIFI network. At least for my phone I wanted to make sure it switched back to the local IP when I was home as that's going to be the fastest response (as well as allowing the real-time websocket for pushing updates from the hub)

The best thought I had was to save the WIFI SSID that was used to initially login with. But, with newer Android OS's that requires prompting for location permission.

I used to use logic which would always try the local IP first and then fall back on the cloud connection if that failed. But, I wouldn't always want to do that as it takes some time to try the local connection first, fail and then re-try using the cloud.. and if I kept using the cloud connection how would I detect I'm home again?

Anyway, before I prompted for location permission I figured the more reliable way was a switch for always on or always off. If no one minds the location permission (I feel like a lot of people are turned off by any kind of permissions like that.. then again, maybe that's just my perception..

jpage4500 · June 21, 2020, 12:24am

I learned a little more about this. There's a semi-undocumented Maker API call to get all of the system modes and another one to set the mode. There's also an API to get/set the 'hsm' (which I just learned is the Hubitat Safety Monitor status).

Would each of these (mode and hsm) be represented by a single dashboard tile? Maybe a button with the current mode text and when pressed showed a dialog with the other modes you can switch to? I imagine it'd need to be an option since not everyone would use that.

The only other question I have about mode and hsm is how often would i need to refresh the status? I'm assuming that I won't get notified by the hub when it's changed so I'd have to periodically check

pat.richards · June 21, 2020, 12:34am

I would prefer 2 separate tiles for mode and HSM and yes a button to change Mode

I think you will get notified when mode changes at least that's my experience in Node-red

danfox52 · June 21, 2020, 12:37am

I don't use HSM, but it should be separate from modes. The mode doesn't need to be refreshed real often - once every minute would be fine - if it doesn't refresh itself.

jpage4500 · June 21, 2020, 12:38am

If you're able to send me a device log from the app (settings->about->feedback) that would have the device details which I've been using to support a device I don't have. Or, you can just send the details without using the app (see this post: Maker API - example responses for lots of various device types)

My first thought about that 6-in-1 or 4-in-1 device is -- how do you display all of those details in a tile?

I can support wider tiles.. I was thinking I might need to do that for a thermostat to be able to have an UP and DOWN button.. or, the weather or a new clock tile. I'm also a little leery about putting too much data on a single tile just because typically not everything is critical to see at a glance. Like the door sensors I have today.. they support open/closed state, battery level and the temp. But, I'm really not that interested in knowing the temp of 3 different door sensors around my house and the battery level isn't important to me at all - until it's getting time to change the battery. That's why I tried to keep these fields smaller.

Anyway, I wonder if these multi-sensor devices also could have some more important data displayed up-front and center but some of the lesser details only shown when needed or in the details popup

jpage4500 · June 21, 2020, 12:50am

I have a few devices that aren't super reliable for me either. But, that's the status I'm getting back from the hub. I also have a few devices that I suspect are at the edge of ZWave or Zigbee range because they mostly work but occasionally will fail to update (either using the app or using Google Voice).

The other thing that's annoying is that the hub doesn't handle the case where a device is off very well. My RGB lights for example can be turned off at the switch for days but the hub still reports the as ON. I feel like the hub should do a better job of polling a device and marking it as offline after so many failed attempts.. Wink did a pretty good job of this. Maybe in a future hub update...

LosinIt · June 21, 2020, 1:12am

How about a list:

Temp 72,5F
Humidity 33%
Illuninance 383
Battery 90% (this one is a crappy indicator so maybe not)

Some of them have motion as well so use the motion icon in the background? I don't know if that's possible so maybe put it at the top of the list.

That works too

Roger...

Devices

I couldn't find a way to do the JSON formatting like you did in the other post you linked.

John.Herron · June 21, 2020, 3:20am

Is it possible to do a quick check of the hub IP just to see if the port responds? No response then try the cloud address. This should be a low faster than trying to connect via the Maker API. If this is efficient enough perhaps it can be done after every command issued in the cloud. I'm not familiar with what networking options are available.

John.Herron · June 21, 2020, 3:50am

@jpage4500, A "reset" fixed this. It was probably left over stuff from manually selecting a dimmer template in a previous version.

jpage4500 · June 21, 2020, 2:25pm

Cool - thanks for the devices; there's several types I haven't seen before. I'm going to try and create a single .json file that contains every device type example I can find. By logging in to server "0.0.0.0" the app will display that file to help show what each one looks like.

I can tell it's going to get tricky when a single device does lots of different things. Only so much room in a tile today. But, maybe this is where a wider tile will have to come in..

unrelated - does anyone have a ceiling fan and would be willing to share the JSON response from the hub? I think this would be an easy device to support

also unrelated but while I'm thinking of it.. while I want to support every common device I know there's more you can do with a device than just on/off, lock/unlock, etc. I also plan to put in a better UI to handle sending any of the supported device commands.. for example, my lock supports the command "setCode". Without the app knowing what that is I'd like to make it possible to send it along with a custom lock code and then see the response back. I imagine there's hundreds of these commands out there so this seems like 1 way to make this work

LosinIt · June 21, 2020, 4:01pm

Huh?

jpage4500 · June 21, 2020, 5:29pm

If you login using server IP 0.0.0.0 the app will load a test .json file which contains several test devices. I added it for myself to view sample devices but also need it for Amazon App Store which needs to 'login' to test the app.

It works today by randomly picking from a few different devices files but I'm going to create 1 file with each device type example I can get

LosinIt · June 21, 2020, 10:45pm

You don't say what systems you are using or how you're logging in (ssh, telnet,...) so I don't know why you'd do that. 0.0.0.0 is a reserved address and can mean different things depending on the context. On my Linux systems 0.0.0.0 is another way to say localhost which is more commonly associated with 127.0.0.1.

So I guess you're logging in to whatever box you are currently on and I don't understand why you wouldn't just open the file since it's on the same system.

Anyway, if it works for you...

jpage4500 · June 22, 2020, 1:26pm

Using "0.0.0.0" for the server IP just puts the app into a test mode - that's all. Instead of loading devices from a hub it just uses a built-in JSON file. I only mentioned this because that's how I'm able to test with devices I don't have