Is there a way to hide the icon? That would be awesome.
I’m not really sure but I don’t think I could do it.
Again, these plugins only deal with the control portion of the entity. the rest is controlled by the entities card (or whatever other card you are using).
At least I think that’s the way it is.
I’ll definitely look into it when I get the chance. It seems to be a popular request.
For anyone using the cover-control-button-row…
I had an issue on github that said the “close” button isn’t working but the other two were ok.
Is anyone else seeing this?
Hey cool Plugins!
I’ve built a group of two cover the buttons are working correct but the status on the button is wrong. Do you have any suggestion?
Is it possible to set the tilt position?
- closePosition: 0
customClosedText: 0%
customMidClosedText: 10%
customMidOpenText: 50%
customOpenText: 100%
customText: true
entity: group.schlafzimmer_jalousien
midClosePosition: 10
midOpenPosition: 50
name: Jalousien
openPosition: 100
type: 'custom:cover-position-preset-row'
- closePosition: 0
customClosedText: 0%
customMidClosedText: 10%
customMidOpenText: 50%
customOpenText: 100%
customText: true
entity: cover.schlafzimmer_links_jalousie
midClosePosition: 10
midOpenPosition: 50
name: Jalousie links
openPosition: 100
type: 'custom:cover-position-preset-row'
- closePosition: 0
customClosedText: 0%
customMidClosedText: 10%
customMidOpenText: 50%
customOpenText: 100%
customText: true
entity: cover.schlafzimmer_rechts_jalousie
midClosePosition: 10
midOpenPosition: 50
name: Jalousie rechts
openPosition: 100
type: 'custom:cover-position-preset-row'
As an FYI, a couple oif things…
First, I just released an update the fan control row to allow the medium speed button to be hidden for use with two speed fans.
the two remaininjg speeds need to be “low” & “high” for the row to work.
And I also released an update to the Covcer Control Row so you can hide the “Stop” button. I never realized some covers don’t support that function and it was a FR.
I had a request (A LOOOOONG time ago…sorry) to create a single button toggle control for controlling binary type entities.
I finally got around to finishing it.
Here it is:
I just submitted it to be included in HACS so it should be there soon.
Here is how it looks with the different config options described at the github site:
I’ve had a few requests to make the buttons resizable so I finally got around to doing it.
All of the plugins buttons should be completely resizable now with the latest updates.
Also I just created a new fan control row for use with the new fan speed percentages:
I’m still working on another one using preset modes but I haven’t been able to get any answers on how exactly they work.
There’s now a new plugin for you to try out for use with fans using preset modes.
try it out here:
It’s not in HACS yet and TBH, there seems to be a pretty bad backlog of repos that need to be added to the HACS default list so I’m not sure when this will get added to HACS. So you will likely need to install this manually if you want to try it out.
It will look the same as my other plugins and will be just as theme-able.
And I have it set up for fans to use either two or three preset modes.
Give it a try and let me know (as usual) if you have any issues.
There is an example fan config for ta template fan using a broadlink remote in my Home-Assistant Repository if you need any suggestions on how to get the fans set up to work.
how come it is only now I notice your plugins?!
maybe because I was explicitly looking for add confirmation (and/or lock) · Issue #186 · thomasloven/lovelace-slider-entity-row · GitHub a lock on the sliders… you don’t happen to have thought of that yourself for the Cover control row do you Finity?
Somehow I don’t get it that this has been so neglected in core HA, securing a toggle (and the slider for that matter) on these very important parts of the interface…
I can use the toggle-lock-entity-row by Thomas on a toggle, or the successor by Ian, but for covers this is missed thus far. Forcing us to create custom-buttons (maybe the core button entity row could do so too, but it requires subscripts)
How cool would it be if we could unlock/lock a slider, slide it, after which it locks again…
second question if I may: I use the Somfy TaHoma set My position command to allow me to do:
footer:
type: buttons
entities:
- entity: script.garage_lamellen_open
icon: mdi:arrow-up
# name: Open
- entity: script.garage_lamellen_my
name: My
show_icon: false
- entity: script.garage_lamellen_close
icon: mdi:arrow-down
# name: Close
in the footer. Could this be an option for you card too? (id really like to be able to use these 2 buttons you offer, but it would require the possibility to customize the service on the middle button)
1 Like
I don’t know! But you don’t know what you’ve been missing! 
No and I doubt I could even have the skills to do it if I wanted to.
What “2 buttons” would those be?
Right now I have a total of 8 plugins for various scenarios. two of them dealing with covers.
If you could create a template cover out of your scripts then you could easily use my cover control buttons to do whatever you wanted in the stop button script.
Ah yes, I’ll have a look at that, didnt try the template up to now. Only been playing with covers, and covers groups.
thats a typo, sorry. Autocorrect…big fingers
meant to say 3… as you show in your repo, replacing the current arrow/stop/down icons
template cover coming up next 
thanks
1 Like
Also, I’ve requested that the old speed list options should be kept and I’ve had a suggestion from a dev that if a FR gets enough votes they would implement it.
Here is the FR. Please go there and vote it up.
1 Like
No, according to the screenshot everything looks OK to me.
I assume you’ve installed the plugin, added it to the resources and restarted/reloaded lovelace?
TBH, I’m not sure how to add the plugin using the UI editor. I never use them. I do everything manually in YAML.
But your YAML in the manual editor looks OK as far as I can see.
1 Like
Add this to your js file:
window.customCards = window.customCards || [];
window.customCards.push({
type: "cover-control-button-row",
name: "Cover control button row",
description: "A card to display your cover controls in a button row.",
preview: false,
});
That will make it show up in the + Add Card screen.
please let me ask, the first line, why is it like that? Why the || construction?
(asking because I use the same type of code in custom-ui, and only the [] seems to suffice?)
Monkey see monkey do, I copied my answers from Bram’s cards 
2 Likes