Hi, is there someway to debug why a view isn’t loading? I am following the examples from your personal HKI… I have a Climate and Security views that are working great. I copied your media_media_view and updated it for my entities. It won’t show up. I then tried to simplify to debug with the following, and nothing shows up. I’m probably doing something stupid. Any suggestions?
Well it seems absolutely fine to me, so not sure why it doesn’t work. But your code looks absolutely fine to me. I even tested it myself on my own setup with your mediaplayer code (I obviously edited the entity). It works fine. It even shows inside of the menu (note that the frontpage shortcuts are NOT considered the menu, the menu can be accessed by pressing the menu button). Does it not show for you there either?
Can you at least get to the page at all? If yes then I should mention that only dark themes will show them properly for now (srry a bug). Light themes will show a white rectangle instead with a title above the rectangle. If no? Then remove everything except for the home/menu views and just add the media_test view and see if that works. You might want to add the following line to make it a bit easier for you since that will create a shortcut on the home page.
Ah! It does show in the Menu, but not on the main page where climate, security, etc. shows. Also do have the but with light themes :). Is it only supposed to show in the menu?
I updated my config to my full media player config… and now nothing shows up again under Menu… really weird. Here’s the code. I commented out most of the players to try and debug.
media_media_players:
title: Media
# subtitle: "[[[ if (states['sensor.media_players_playing'].state == 'Playing') return `A media player is playing right now`; else return `All mediaplayers have stopped playing`; ]]]"
columns:
buttons: 4
icon: mdi:plex
# button_badge: sensor.media_players_playing
view_selector:
columns: 3
aspect_ratio: 3/1
elements:
- name: Alexa
icon: mdi:animation-play
path: media_media_players
this_view: true
media_players:
- title: Alexa
entities:
- media_player.living_room
When using the view selector you will have to add that same addon to multiple views. Because of this HKI will not add these to the menu, since that would create a menu entry for each sub view you have created (at least that is what its intended to do).
To solve this problem, make sure to set show_in_menu: true on at least one view. Make it the view that will be opened by default when clicking on that item. Ofc if you want each of those views to showup in the menu, add the line to all views.
To solve the problem of a weird title in the menu button, use the title line for that view.
Ah… well that’s obvious now I had stuck in my head that ‘menu’ meant the menu you navigate to by hitting the navigation bar… duh… thanks! It’s so clear now!
another little question, in the notification section , in light tab , the text "… light is on " is in English. is it possible to put the text in French ? thx for your help
Yes you can fully change each name or given word. You will have to do it yourself though.
You can find perfect examples within my personal config (link in the first post).
The button size can be changed by either setting a maximum number of buttons in a row (e.g. 2) by using the columns addon. You can also change button size by using aspect_ratio within the devices addon.
This doesn’t always work as expected unfortunately, but I am currently reworking HKI to fix a lot of these issues. This will unfortunately take some time, so dont expect it this month, but maybe next month March. However the current version is pretty stable, so dont hesitate to use it already.
How I can assign addons to different places (i.e., main, sidebar, etc…)?
As reported in this link (from the documentation), I tried by adding the following statement both to standard addons and custom cards (the newer ones) but I had no success
Not in hurry… thanks for quick answer, I’ll wait for a release.
But just to understand when you refer to custom addons you mean it is already implemented in current master version, or you refer to a development version? Because I tried with no success with a custom card like this:
