Configuring Advanced Status

[apostolakisl]

I am configuring favorites with buttons on my phone with each speed of a fan.  I am tracking the fan status using a variable through a link to Alexa since there is no ISY node for this fan.

- I have 4 buttons in UD Mobile, one for Low, med, high, and off

- I want the button that represents the current state of the fan to be a different color

- The tracking variable is set to 0,2,4,6 for the various states of the fan.

The issue is that when I set a custom color for one button at one variable value, the other 3 buttons configuration changes to match.  I can't use the same variable at different values to make different buttons change color at different values.  

This is on Android.  I tried closing the app and re-opening.  No change.  

Is this a bug or just something that is going to be this way?

[Javi]

The Advanced Status (list) is linked to the Node (variable) property (value).  So the Home Tabs and any favorite  with this node (variable) as the Display-Node will use the same Advanced Status (list) as the list is linked to the Node Property not the Favorite.

I don't quite follow what you are trying to achieve, so the following is based on the assumption that you want to show the status on each button along with a different color.  If you don't need status then remove the Display Node and use Color in the favorite's editor, not the Advanced Status.

To show 3 different colors for the same node property you will need a work around as this is not a common situation.  UDM is very flexible so  there are a few ways to do this.

Using 3 variables which are all set to match the tracking variable. This can be done in a program, something like if state_var_1 changes set var_2 to equal state_var_1 && set var_3 to equal state_var_1.  Now you have a separate node which has its own Advance Status list.

Using programs with only an IF statement to match the desired status. Then in the Program's Advanced Status list change the color based on Idle-True and Idle-False (i.e. is desired status true or false).

[apostolakisl]

46 minutes ago, Javi said:

The Advanced Status (list) is linked to the Node (variable) property (value).  So the Home Tabs and any favorite  with this node (variable) as the Display-Node will use the same Advanced Status (list) as the list is linked to the Node Property not the Favorite.

I don't quite follow what you are trying to achieve, so the following is based on the assumption that you want to show the status on each button along with a different color.  If you don't need status then remove the Display Node and use Color in the favorite's editor, not the Advanced Status.

To show 3 different colors for the same node property you will need a work around as this is not a common situation.  UDM is very flexible so  there are a few ways to do this.

Using 3 variables which are all set to match the tracking variable. This can be done in a program, something like if state_var_1 changes set var_2 to equal state_var_1 && set var_3 to equal state_var_1.  Now you have a separate node which has its own Advance Status list.

Using programs with only an IF statement to match the desired status. Then in the Program's Advanced Status list change the color based on Idle-True and Idle-False (i.e. is desired status true or false).

Not wanting a bunch of colors, just two.  Here is what I want to happen:

4 button: off, low, med, high  Whichever one is the current state, is red, the others are blue.  If the fan is off, the variable is 0 and the "off" button is red, the other 3 are blue.  If I hit the "high" button, the variable changes to 6, the "off" button turns blue, the "high" button turns red.  And so on with the other two buttons.

Just your basic radio button type configuration.  Same way the KPL controlling the fan only lights the button that is currently active.

It works if I use 4 different variables, but things are already so cluttered.

But I guess you are saying that advanced configuration is tied to that node and there is only one possible advanced config per node, you can't have advanced config on the same display node behave differently for different favorites . . . end of story?

 

Edited 22 hours ago by apostolakisl

[Javi]

5 minutes ago, apostolakisl said:

But I guess you are saying that advanced configuration is tied to that node and there is only one possible advanced config per node, you can't have advanced config on the same display node behave differently for different favorites . . . end of story?

Yes, The Advanced config is linked to a node property not a favorite.

If only a boolean is required then the program route will work without the need for more variables, but you will have more programs.   

If this was a real device, not a variable, I would suggest the Favorite Type Picker which would show the command dropdown.   Another option may be the Virtual Node Server.

[apostolakisl]

14 minutes ago, Javi said:

Yes, The Advanced config is linked to a node property not a favorite.

If only a boolean is required then the program route will work without the need for more variables, but you will have more programs.   

If this was a real device, not a variable, I would suggest the Favorite Type Picker which would show the command dropdown.   Another option may be the Virtual Node Server.

Well, there was an easy fix.  I just set it to track the status of the corresponding KPL button which I already have working correctly via programs and Insteon scenes.

So each favorite display node is the corresponding KPL button and when the KPL button is on, the advanced config turns it red.  I see also that everywhere that node appears now also turns red when on, consistent with what you said.

[apostolakisl]

@Javi

One issue, when the fan is off, and the "fan off" favorite icon is turned red, the button reports "on" when the fan is off.  The button name is "fan off", so it literally says "fan off on" (over two lines), or "fan off off" when the fan isn't off.  It isn't the end of the world, but it is a bit screwy.

My goal here is to just work like a KPL.  No need for words on/off, just the color change is all that is needed, much like a KPL tells you what is going on by backlighting the one button.

In short, it would be nice to set a "display node" that actually doesn't display anything, but rather just gets you access to setting the advanced status configuration.

I have this same issue with some of pool controls showing confusing or useless info in the display section when all I really want is to be able to set the favorite icon color.

 

EDIT:  Also, why does it say "UD-Mobile-Name-Error" in the display status section?

Edited 18 hours ago by apostolakisl

[Javi]

1 hour ago, apostolakisl said:

@Javi

One issue, when the fan is off, and the "fan off" favorite icon is turned red, the button reports "on" when the fan is off.  The button name is "fan off", so it literally says "fan off on" (over two lines), or "fan off off" when the fan isn't off.  It isn't the end of the world, but it is a bit screwy.

My goal here is to just work like a KPL.  No need for words on/off, just the color change is all that is needed, much like a KPL tells you what is going on by backlighting the one button.

In short, it would be nice to set a "display node" that actually doesn't display anything, but rather just gets you access to setting the advanced status configuration.

I have this same issue with some of pool controls showing confusing or useless info in the display section when all I really want is to be able to set the favorite icon color.

Set the Formatted Value in the Advanced Configuration to a space (i.e. " ") this will remove the words off or on.  Or set it to "off" and remove "off" from the favorite name.

1 hour ago, apostolakisl said:

EDIT:  Also, why does it say "UD-Mobile-Name-Error" in the display status section?

Please show a screenshot so I know the location.  I'm in the process of many lower level changes to update the app and may have missed something.

[apostolakisl]

@JaviUsing the blank space works to make it not show the word "on", but it still shows the word "off"

 

[Javi]

Thanks,  I can't replicate the name error so please verify UDM is on 1.2.32 in a few days (currently awaiting Google's approval).  If the issue is not resolved by then try synchronization, if still not resolved send me a copy of the app backup and I'll take a look.

With regards to "off" add another customization for the value = "off" with an empty string for the formatted value. 

[apostolakisl]

26 minutes ago, Javi said:

Thanks,  I can't replicate the name error so please verify UDM is on 1.2.32 in a few days (currently awaiting Google's approval).  If the issue is not resolved by then try synchronization, if still not resolved send me a copy of the app backup and I'll take a look.

With regards to "off" add another customization for the value = "off" with an empty string for the formatted value. 

OK, the same name error message appears on all the fan speeds, fyi.  

And the radio buttons are working great now. thx.  Fixed my pool fountain buttons as well.  

[apostolakisl]

@Javi

Suggestion:  I read through the instructions linked to the advanced config via the question mark bubble, and it didn't mention that setting this up is tied to the node, not the favorite.  I think that is worth putting in there.  I would consider that to be something you might want to put as the first note about setting up advanced config since someone might easily see that and just stop before wasting any more time if they only want it to apply to that favorite.