all other devices you mentioned, where are they grouped?
you have defined a default_view, which does 2 things:
1 it only shows the groups you define in there
2 it prevents all other non grouped entities to show up automatically.
see: https://www.home-assistant.io/components/group/
If you’d call the default_view let’s say Hue_lighting with view: yes, you create a tab to show that page, and all other entities would be displayed on the homepage (which is then made by default by HA)
Yeah, in that case you’ve configured it to to only show the Hue card on your frontend.
I presumed from you saying this…
That you had a merged list 
This is the first time I am using groups - is there a way I can just add them to the main Overview screen?
The whole idea is to expose the sensors to Homekit so I can create automation via the Home app on iOS
So what should the groups.yaml file look like? Do I actualy need it?
(Sorry, groups - never worked with it!)
Just remove the first block…
default_view: }
view: yes } Remove these completely
entities: }
- group.Hue}
Hue:
entities:
- sensor.dining_room_motion_sensor
- sensor.dining_room_temperature
- sensor.dining_room_light_level
- sensor.hallway_motion_sensor
- sensor.hallway_temperature
- sensor.hallway_light_level
Then the card you made will appear somewhere on your ‘normal’ default frontend.
well, tbh, ymmv.
It all depends on your preferences, but let me say this: smart grouping can be very very useful, and Id even see is unmissable. Not only to group the frontend into something easier to look at than all separate entities, but also to act upon. (switch off a group with all switches or automations, etc etc)
If you want everything on the first and only page, do as @anon43302295 says above. If you want ‘tabs’ create a few groups with view: yes, and have the frontend look like this:
with the added advantage of a much more responsive Homeassistant. If it has to list everything on 1 page, that becomes a very heavy page soon, and will get slower to load very soon.
OK, groups.yaml file edited and rebooting. wait wait wait
I never got an ‘Hue’ icon at the top, and the screenshot you show is very impressive, should I be expecting an icon like yours even if I have a single ‘group’?
Just reading the (https://www.home-assistant.io/components/group/) and that is taking it to the NEXT level - thank you so much for your help!
fingers crossed
you mentioned losing ‘all other devices’ so I gathered you had quite a few, and grouping these would be advisable imho. hence the screenshot of the tabs.
I do it as follows:
in configuration.yaml:
group: !include_dir_merge_named groups
that groups folder has this contents:
in the file view_tabs.yaml, I have all tabs groups, which most of the time only have groups for entities (a sporadic badge or sensor aside…):
##########################################################################################
# Groups: Views (tabs in Front-end)
##########################################################################################
lights_panel:
name: Lights
view: true
icon: mdi:light-switch
entities:
# - sensor.lamps_badge
# - sensor.lights_on
- group.lights_tiles
ikea_tradfri_system:
name: Ikea Trädfri
view: true
icon: mdi:lightbulb
entities:
- group.ikea_tradfri_groups
- group.ikea_tradfri_lights
- group.ikea_tradfri_hub
- group.ikea_tradfri_automations
- group.ikea_tradfri_sensors
- group.ikea_tradfri_remotes
philips_hue_system:
name: Philips Hue
view: true
icon: mdi:ceiling-light
entities:
- group.hue_light_control
- group.light_automations
- group.light_effects
- group.philips_hue_groups
- group.philips_hue_lights
- group.philips_hue_lights_reachable
- group.philips_hue_hub
- group.philips_hue_sensors
- group.philips_hue_rest_sensors
- group.philips_hue_switches
etc etc
hope this helps.
WOW - absolutely fantastic!! - what a great community and thank you both so much for your help.
I can finally see all the sensors and this will be a great building block for my future plans!
Thank you for the groups thing, definately something I will be looking at as it looks seriously amazing!
Pretty sure it will pass WAT (wife-approval-test)!
Very happy - thank you!
The custom Hue Sensor component is excellent but sometimes I noticed ghost triggering. After much debugging, it turns out my Philips Hue Switch at the main door (furthest away) disconnects and reconnects from the Hue hub sporadically.
This causes a change in the “reachable” attribute which triggers the automation. I’ve edited my copy of the Hue Sensor custom component to remove the “reachable” attribute and it has been great since. Putting it out there in case someone else encounters the same.
Thanks plasma16, can you please elaborate a bit more what you have done. I found out that I get a double delivery of of every key press on the Hue switch after 5mins. Is this related or something else?
Thanks
My template sensors have stopped working and report None. They worked for ages but not now. I re-downloaded the custom components and replaced the hue sensor folder but no change.