HoneyComb menu stopped working - service call removed

Configuration Frontend
,
1

Hi,

I’m using the Honeycomb menu in a floorplan. Recently it stopped working because the depreciated service call was removed.
So, I updated my yaml but its still not working. Based on docs I had to change the service call to a fire-dom-event. However, when I do, it still does not work.

Below is a sample of the Yaml and the error message.

Error in the logs:
Uncaught error from Chrome 135.0.0.0 on Windows 10 TypeError: Cannot read properties of null (reading ‘addEventListener’) zt.close (/hacsfiles/honeycomb-menu/honeycomb-menu.js:257:973) /hacsfiles/honeycomb-menu/honeycomb-menu.js:119:3195 window.honeycomb_menu (/hacsfiles/honeycomb-menu/honeycomb-menu.js:119:3901) HTMLBodyElement. (/hacsfiles/honeycomb-menu/honeycomb-menu.js:119:4110) pe (/hacsfiles/ha-floorplan/floorplan.js:52:482) Pi.handleActions (/hacsfiles/ha-floorplan/floorplan.js:131:19122) me.onClick (/hacsfiles/ha-floorplan/floorplan.js:131:17855) /hacsfiles/ha-floorplan/floorplan.js:52:3424

Yaml code:

                - entities:
                    - fan.master_bed_room_fan
                    - fan.south_bed_room_fan
                    - fan.north_bed_room_fan
                  tap_action:
                    action: fire-dom-event
                    honeycomb_menu:
                      buttons:
                        - icon: mdi:information-variant
                          tap_action:
                            action: more-info
                        - icon: mdi:fan-off
                          active: '[[[ return entity.attributes.speed == "off" ]]]'
                          tap_action:
                            action: call-service
                            service: fan.set_preset_mode
                            data:
                              entity_id: entity
                              preset_mode: "off"
                        - icon: mdi:fan-speed-1
                          active: '[[[ return entity.attributes.speed == "slow" ]]]'
                          tap_action:
                            action: call-service
                            service: fan.set_preset_mode
                            data:
                              entity_id: entity
                              preset_mode: slow
                  state_action:
                    action: call-service
                    service: floorplan.class_set
                    service_data:
                      class: >-
                        ${(entity.state === "on") ? "fan-" +
                        entity.attributes.preset_mode : ""}
2

For me with the last update, both floorplan and honeycomb works. Have you tried reinstalling both plugins?

3

Thxs for the reply. I redownloaded both floor-plan and honeycomb, same issue.
If I specify one entity, like the following, it works.
If I have a list of entities, in the original post, it does not:

                 tap_action:
                    action: fire-dom-event
                    honeycomb_menu:
                    entity: fan.master_bed_room_fan
                      buttons:
                        - icon: mdi:information-variant
                          tap_action:
                            action: more-info
                        - icon: mdi:fan-off
4

There is probably a conflict, probably because floorplan doesn’t use config as a normal lovelace card and therefore honeycomb can’t assign the correct entities.

Anyway, try to assign entity to a button, or use variables. My config looks like this

menu

5

Thxs for the reply.
However, this will not work for me.
For my honeycomb menu, each position (0 thru 5) does an operation for the entity under - entities

In your case, you have hard coded the entity, for each position.

One work around for me, maybe is to use a script and pass in the entity.
I think that was what you were referring to by using variables.

I think right now, I’ll back out honeycomb menu version to the previous version.
I’m going to write this up as an issue.

6

No, variables in honeycomb uses a similar way as custom:button-card via template… in readme you have an example how to use it…