Moving Lovelace items between views

The most recent HA blog states

One of the directions we care about most for Home Assistant is making it simpler to pick up and use, without compromising on capability. It’s something we have been working toward for a long time, and it runs through our roadmap and goals for this year. We cannot do it overnight though, so we keep listening to your feedback to make sure we are fixing the things that actually get in your way. If there is something you would like to see, we would love for you to weigh in. Every comment helps shape what comes next.

So here’s mine:

If I have two views in Lovelace (Home and Office) and I have a card on Home that I now want to be on Office instead, it should be simple and easy to move it.

It is not.

First, after entering edit mode, I try dragging the card to the Office tab. The drag is rejected — it should be accepted and the card moved to the last place on the Office page. (Bonus point for “spring-loading” it, where hovering over the tab for a second or two opens the tab and then you can drop the card exactly where you want it. I suspect macOS’s drag handling is spoiling me there, though :slightly_smiling_face:)

Second, I click on the three dots of the card. I should see a “Move To…” menu item. There isn’t one. There should be, and it should work the same way as dragging to the tab.

Third, I see that there is “Copy” (and “Cut” for braver souls). I click it, then navigate to the Office page. I press ⌘V. Nothing happens.

I click the “add card” button, expecting to see a message saying that there’s a card on the clipboard, and asking if I want to paste it. I don’t. I press ⌘V. The previous clipboard entry is pasted into the search box — HA doesn’t even seem to have copied anything!

I’m sure I have copied things elsewhere in HA, then gone to an “add” dialog and it’s detected that the clipboard has something relevant and offered to paste that. I wish I could remember where so I could give an example. But that’s what needs to happen here.

To move a card, I have to:

  • Edit the card
  • Go into the code editor
  • Copy the YAML
  • Go to the destination
  • Create a new card of the same type
  • Go into the code editor
  • Paste the copied YAML over the top of the existing YAML
  • Save
  • Go back to the original page
  • Delete the old card

WTH is this so complicated? Does everyone else always put things in the right place and never need to move them? Or is there some way of actually doing this easily that’s just very well concealed and not at all intuitive?

Bonus WTH: if you’re running the “native” app on macOS, copy DOESN’T WORK AT ALL. Not even if you select some text and hit ⌘C — you have to access HA in a browser if you want to copy stuff. ⌘C doesn’t work, the “copy” buttons in the UI don’t work — nothing does.

(Apparently the “native” macOS app is actually the iOS app running under some layer that Apple’s provided, and in true Apple style they haven’t bothered to make it Just Work™ because “it’s only the Mac, it doesn’t matter any more; go and add new features to iOS intead of fixing bugs on macOS”.

It would be lovely if the Mac HA app was actually Mac-native and didn’t keep trying to act like it was on an iPad…)

My apologies for the rantiness, but this is incredibly frustrating. I can’t be the only person who’s having trouble here — can I?

All of those methods work for me in Chrome browser on Linux mint or windows. I still prefer to copy the yaml though, but that is probably as I have been doing that way for years.

It is if you use a masonry view.

It’s only sections views that don’t have this and there are already feature requests on GitHub for it. Go vote for them.

That’s the way to make users feel welcome…

What?

All I did was correct your incorrect statements.

Here, have a participation award to make up for your hurt feelings at being corrected:

:star:

Where? There are 9999999999999 issues

Discussions, not issues. Use the search.

You joined in 2020?? It feels like you are gaslighting a bit!

Ah, and there I was thinking moderators were going to set a good example of the way discussions should be carried out.

But here’s a quick tutorial in case you don’t understand:

It’s only sections views that don’t have this and there are already feature requests on GitHub for it. Go vote for them.

Curt. Dismissive. “How dare you clutter up my forum with your putrid whining”.

It’s only section views that don’t have this. These issues are already open on GitHub - it would help get them looked at sooner if you voted for them.

(list of issues)

Helpful. Yes, it takes more of your time to answer like that — I appreciate that. But didn’t your parents tell you “if you can’t say anything nice, don’t say anything at all”?

It seems like you are the one who has hurt feelings at being corrected.

In any case, you still can’t drag a card from a masonry view to another view, so masonry cards don’t even solve the problem.

Factual != curt.

But here let me try to not inflame your persecution complex:

Dreadfully sorry but you seem to have incorrectly read my post. I did not mention issues. I mentioned feature requests. These are handled in GitHub Discussions that I linked to above.

They do have a GUI “move” option though. Almost as easy as dnd. This is likely how sections would have to be moved between views or dashboards too.

OK, i found it in 8888 discussions, sending for others:

See, wasn’t that hard to do it yourself.

I am supposed to use an unusable masonry view just because of that thing that is irritating me every week? It is just 50 lines of code!

You do you. Personally I use sections and it annoys me too. Which is why I opened the feature request instead of ranting ineffectually on these forums.

Are you using HACs addons in the masonry view?

And I see that voting (even if I voted) does basically nothing - there are discussions with 1 and 5683 votes - all in the same state.
The thing that does something are PRs.

I am not using mansory view.

let me re-phrase… Are you using HACs addons in your Dashboards?

Indeed but we are not all blessed with that ability nor the willingness to use an over confident predictive text bullshit machine to do it for us.

What is happening in this thread omg :sob: