I have but it’s a bit odd. If you put your input_text: inside a group and then add the group as an entity to a card on Lovelace, it’ll give you a group icon with unknown as it’s state. If you then click that, a more info window will pop up with the fully functioning tiles inside it.
I’m sure adding proper custom_ui features to Lovelace is on the list to add given how popular they are but the devs do say she’s only here to play with at the moment…oo err missus
group.inside_buttons has just input_text.inside in it.
When I first load HA no icons load either in my tiles or in the menu across the top. If I click on one of the invisible icons to load a different tab everything works fine from thereon…until another refresh.
If I load any other ‘normal’ tab first everything is fine straight away and, here’s the really weird one, if I add a normal group to the one above it also works properly.
It’s only when the tiles group is on it’s own that I get this strange behaviour. Anyone else seen this?
can we try this Lovelace next to, or maybe should i say ‘in’ our regular setup, or do we need to replace that with the Lovelace interface for the full Hassio configuration? Im a bit weary to test this experimental setup if the latter.
Not sure what im doing wrong, but for some reason I dont get the image tiles to work.
They are not displayed at all.
This is the group card withe the example tiles, unfortunately not displayed:
But I can click something under the card title, so there is something
And it is opening an popup and shows some script:
I realy need your help with this question as i belive it is a basic issue but i cant find the soultion.
I have configured a switch mqtt on my HA which is sending a code to my ESP8266 which is running an server which recives the code and turn on my AC, all is working just fine so i wanted to move to the next step which is creating a tile interface on HA to simulate my AC remote.
Using the exmples in this thread i have manged to create a basic tile with 4 objects on the row howver whatever i configured i am faling to trigger the object to send the code the same as i am pressing the mqtt switch, basicaly whan pressing each one of the 4 tiles i see system_log\write called.
What am i missing or shuld change ?
Any help will be greatly appricated!
Thanks!
Here is my last test:
groups.yaml
#######
controle_pc_fan_rgb:
name: Controle Remoto PC
entities:
- script.remote_control
Thanks for this project! It is great!
This is my TV remote (with complete functionality). The UI might not seem very intuitive because i made it especially for a TV used as a smart mirror, so most of the main panel buttons are scripts that send multiple commands to activate PIP, change channels, etc (on the mirror)
I’m using a BroadLink RM PRO+ to send the IR packet
…I should mention…this was made for a Samsung TV, so it should work on most models (as is) but you can change the packets to make it work with anything you want
Every button is a script with multiple services; one service to send a command to a broadlink (IR) to do whatever is supposed to do on the tv, and to hide and show the cards i have a service call for every other card to hide what is supposed to be hidden when that specific button/script is activated and change visibility to what i need to show up.
For example, to show the keypad card (and also the favorites menu) this is the script for it:
Sometimes simple is just as good did you by any chance use MagicMirror for the smart mirror? if so it would be really great to find out a bit more about how you achevied “panel buttons are scripts that send multiple commands to activate PIP, change channels, etc (on the mirror)”
I’m using MagicMirror, but it doesn’t really matter since PIP, channels, etc. are parts of interfacing with the TV.
I’m using a BroadLink RM PRO+ to send a IR signal to the TV (emulating the original tv remote).
Changing the source (HDMI, DTV, etc.) is seamless but unfortunately some functions like PIP require at least a confirmation on the TV UI (on my tv model) and in that case a just have a script that will send a sequence of commands through the broadlink.
For example, switching to hdmi 1 from a different source is as simple as;
(i’m sending the “return” command 3 times because it has no visual impact on the tv UI and sometimes it is not read correctly)
The scripts you see in this example (script.tv_something) are basic functions of the normal remote independently defined (because it will be easier for me to use them individually later, or if i want to modify the remote…or add some voice control )
For example script.tv_pip is: