Lovelace UI not reading Raw configuration editor correctly annymore after update

Don’t know if this is the right spot for this.

But turned out that after the last update (0.115.1) things broke up a little bit for me. At least how it seems to me.

I’m having configured a horizontal stack with 3 buttons in Lovelace UI, the middle of it shows the HASS update status and I’ve configured the tap and hold action both for “more-info”.

It’s also saved like this in the Raw configuration editor.

          - cards:
              - entity: zone.home
                hold_action:
                  action: call-service
                  service: homeassistant.restart
                icon: 'mdi:restart'
                icon_height: 80px
                name: Restart HASS
                show_icon: true
                show_name: true
                show_state: false
                tap_action:
                  action: none
                type: button
              - entity: binary_sensor.updater
                hold_action:
                  action: more-info
                icon_height: 80px
                name: New Version
                show_icon: true
                show_name: true
                show_state: false
                tap_action:
                  action: more-info
                type: button
              - entity: zone.home
                hold_action:
                  action: call-service
                  service: hassio.host_reboot
                icon: 'mdi:restart-alert'
                icon_height: 80px
                name: Restart Host
                show_icon: true
                show_name: true
                show_state: false
                tap_action:
                  action: none
                type: button
            type: horizontal-stack

But when I re-open the Lovelace UI it forgets about it’s settings. The moment I select the middle (updater) button, the tap and hold action settings are gone and the “close” button down right, changes to “safe” without having made anny changes myself.

This also applies after rebooting or reloading the snapshots. It also happend that vallues of the other buttons changed.

You should create an issue for this here:

1 Like

Thanks for directing me to the right place. I assumed that it was here.

I’ve tried to help the community/developers reporting this possible issue. And so I looked at the page and the form you’ve mentioned in your reply. But it’s not verry inviting reporting this issue seeing the recommended list to fill in here. It will just cost me too much effort/time.

But thanks for guiding me into the right direction :+1:

If you don’t fill out an issue it is unlikely to get fixed.

You’re right in that!
I’m quite bussy at the lately. But will consider it when I have time for it.

But I believe the given form is a bit too strickt and overwhelming, and can prevent people to report possible errors or issues.

Maybe it’s an option also making a second and more simple way for reporting? I understand that it’s too timeconsuming for the developers to check every simple (and possible) report when missing the asked information as in the form. But when multiple people report the same issue, it can be interesting to take a closer look at it? Just an idea, trying to make things simpler and easier :slight_smile:

The information is required to identify the problem. It’s really not that difficult to fill out.