I figured it out eventually…
To style, I added a custom.css file to /config/www and added it as a Stylesheet Resource.
I had to set both :host and body to get it to work on mobile and web.
:host, body {
--honeycomb-menu-background-color: #0000008e;
--honeycomb-menu-active-background-color: #0000008e;
--honeycomb-menu-disabled: #312f178e;
--honeycomb-menu-icon-active-color: #eec33d;
--honeycomb-menu-icon-color: #ffffff;
}
Hi,
just a heads up. With the latest IOS version, honeycomb menu is working on iPhones 
Great extension and now also an excellent addition to ios phone GUIs!!
Buenas tardes, tenia funcionando el menu y post actualizacion del CORE me deja de andar. A alguien le paso?
Hambiente:
Home Assistant 2023.8.1
Supervisor 2023.08.1
Operating System 10.4
Frontend 20230802.0 - latest
Codigo:
type: custom:button-card
icon: mdi:home-assistant
name: + Info.
tap_action:
action: call-service
service: honeycomb
service_data:
active: true
buttons:
- icon: mdi:window-shutter-open
name: Subir persianas
tap_action:
action: call-service
service: script.subir_persiana_planta_baja
- icon: mdi:lightbulb-group-off
tap_action:
action: call-service
service: script.apagar_luces_planta_baja
aspect_ratio: 4/2
styles:
card:
- height: 100%
grid:
- position: relative
custom_fields:
notification:
- background-color: |
[[[
if (states[‘counter.luces_planta_baja’].state == 0)
return “green”;
return “red”;
]]]
- border-radius: 50%
- position: absolute
- left: 60%
- top: 0%
- height: 40px
- width: 40px
- font-size: 15px
- line-height: 40px
custom_fields:
notification: |
[[[ return Math.floor(states[‘counter.luces_planta_baja’].state) ]]]
state:
- value: 1
styles:
card:
- box shadow: 0px 0px 20px 3px green
icon:
- color: var(–paper-item-icon-active-color)
name:
- color: white
state:
- color: white
label:
- color: white- value: 0
styles:
label:
- color: rgba(0, 0, 0, 0.0)
Efecto:
Big change in button-card 4.0.0 breaks honeycomb-menu.
Temporary workaround is to downgrade button-card in HACS to 3.5.0.
I have the honeycomb menu working in general, but I’m looking to setup templating. I have followed the example shown here. It appears, however, that the template isn’t getting propogated through to the specific call. See below.
#### HONEYCOMB TEMPLATES
#honeycomb_menu_template: <<<- is this needed as a header???
timeout: # <<<- can this be any label, or are there pre-defined template names?
animation_speed: 10
variables:
timer: null
setpoint: null
buttons:
- entity: '[[[ return variables.timer ]]]'
show: '[[[ return variables.timer ]]]'
icon: mdi:auto-mode
tap_action:
action: toggle
- entity: '[[[ return variables.setpoint ]]]'
show: '[[[ return variables.setpoint ]]]'
icon: mdi:timer-edit-outline
tap_action:
action: more-info
Following on from that in the same yaml file is my actual call attempting to use the template defined above (I’m using ha-floorplan) - I’ve shortened the precursor config, but have left the main headings to show the indentation.
### Dashboard config using ha-floorplan
views:
- title: floorplan
cards:
- type: vertical-stack
cards:
- type: custom:floorplan-card
#-----
rules:
#-----
#### Honeycomb Popups configuration (WITH TEMPLATE)
- name: Honeycomb Popups
entity: sensor.timeout_floodlight
tap_action:
action: call-service
service: honeycomb
service_data:
template: light
variables:
timer: sensor.timeout_floodlight
setpoint: input_number.timeout_floodlight_sp
This is the call without using a template, and this works:
#### Honeycomb Popups configuration (NO TEMPLATE)
- name: Honeycomb Popups
entity: sensor.timeout_floodlight
tap_action:
action: call-service
service: honeycomb
service_data:
entity: sensor.timeout_floodlight
animation_speed: 10
buttons:
- entity: switch.enable_floodlight_timeout
tap_action:
action: call-service
service: switch.toggle
service_data:
entity_id: entity
icon: mdi:auto-mode
- entity: sensor.timeout_floodlight_sp
tap_action:
action: more-info
icon: mdi:timer-edit-outline
Any thoughts would be appreciated.
it doesn’t work properly for me if I use template, I have it similar to you. floorplan in dashboard with button cards. I’m not developer, but I think in my case I have conflict with button cards template I use. On the other hand, since the last update it works fine everywhere including ios devices. 