#Create navigation tabs

1 messages · Page 1 of 1 (latest)

neon dome
#

Right now I have this where the lights would be on the bottom and the home map as the main way of navigating between each room. However I'm very confused on how when I press a button on the home I would change which buttons would be visible on the bottom. I've tried the browser mod and just got nowhere with it. Any help would be appreciated.

pale mauve
#

While I don't use the Picture Entity card myself, it is a pretty popular and powerful card. Generally, though, users will "put" the items on the card itself rather than relying on secondary buttons. (So, a light icon in the garage will turn on/off the light.) I don't think it is really used for navigation purposes.
But that's okay, because if you want to use it for navigation then that's what we're gonna go for.

#

A quick side note: I'm going to change the terminology being used. Instead of navigating, we're going to be selecting. Navigating refers to changing to a different view/subview or different dashboard, which, I'm assuming, not what you're trying to do but instead keep everything contained below the image. So, we're going to be selecting which room is being shown.

#

Your set-up will be a bit different because you have to "put" the buttons on the image to perform the selecting. Again, since I don't know much about the Picture Entity card, I don't know the best way to do this. I imagine you would want to use a Perform Action, but perhaps someone will chime in and expand on this part for me. The rest of the concept with the helper entity, tap actions, and conditional cards would be the same.

neon dome
#

is that possible at all?

pale mauve
#

Sorry for the late reply. I'd been meaning to get back here to write a response. The set-up would be roughly the same. You would still use the helper entity and tap_actions.
Your on/off buttons would probably need to rely on a script to help with the "logic" in terms of using the helper entity to determine which batch of lights are supposed to get turned on or off.

#

There's a couple of things that I don't like about your design. (If you like it, cool. This is just my two cents and maybe something to consider.)

  1. I don't like the individual button for on and the other for off.
  2. There's no way of having the button be dynamic to the point of "showing" you if the light(s) are on or off. Which, subsequently, a single button wouldn't be able to properly handle turning off the lights if they're already on a vice versa.