Closed mschingel closed 1 year ago
So, the good news for you is that I've also reworked the device details as well. In the version I have locally I have the ability to pause/resume Internet access, rename and delete if need be.
I'll have to have a look at how easy it would be to port that into this card for you.
RE: DHCP reservations. The library currently doesn't support that so that isn't possible at the moment. In fact I don't use the DHCP server on the Velop so I'd need to have a look at how it's done.
Quick question that should make my life easier... Do you know how to use custom button card templates?
Yes I know a little bit, and it doesnt seem too difficult as long as I know what to put where and possibly why. Styling seems hard for me but yea I can use it and figure it out.
RE: DHCP reservations. The library currently doesn't support that so that isn't possible at the moment. In fact I don't use the DHCP server on the Velop so I'd need to have a look at how it's done.
I probably shouldn't use the DHCP on the velop either, so do you bridge your velops to a router behind the mesh? I am considering doing that but I got 100+ ip assignments to consider and don't know how my Velops will handle bridge mode. For the MX4200 that is a troublesome router to begin with... I will research doing a DHCP server separate. I recently added tplinks loadbalancer behind my router to support 2 wans for internet.
In which case hopefully this will work for you...
You'll need to add these to the following to the custom:button-card templates area - see here
edit: I missed a template - sorry.
I probably shouldn't use the DHCP on the velop either, so do you bridge your velops to a router behind the mesh? I am considering doing that but I got 100+ ip assignments to consider and don't know how my Velops will handle bridge mode. For the MX4200 that is a troublesome router to begin with... I will research doing a DHCP server separate. I recently added tplinks loadbalancer behind my router to support 2 wans for internet.
I'm in the UK and use my ISP provided router in modem only mode and the Velop to provide the entire Mesh. DHCP is provided by a Pi-Hole on the network. I have a few services on the network where I reserver the IP on the Pi-Hole (for legacy reasons). However, Pi-Hole doesn't really need reservations as devices get the same IP address each time due to both the lease time and the fact that the Pi-Hole uses an algorithm to determine the served IP rather than just using the next available address.
Button Card Templates
Help me out, where would I enter the Template data? Someplace there, i just pasted it in and it still gave me errors
So in Raw configuration editor
you'll need a section called button_card_templates:
if you don't already have one, create it at the top of all the text. Then paste the templates in from the previous message, making sure they are indented correctly. As an example mine looks like the following screenshot: -
Thanks I had template: your code.
udpated with button_card_templates: and i see the buttons now. Looks good! Thanks!
I won't update the README with this as it's a little more intricate than I wanted for the examples. Hopefully it'll just work for you and you'll be able to maintain it if changes are needed.
As I learn more and more I am certain this will make due. Thanks a bunch!
No problem. I'll close this off now.
@uvjim
Anyway by chance you can help me fix this:
linksys_velop_mesh: variables: mesh: | [[[ if (entity) { let config_entry_id = hass.entities[entity.entity_id].config_entry_id let mesh_device = Object.entries(hass.devices).filter(([device_id, device_details]) => device_details.config_entries.indexOf(config_entry_id) != -1 && device_details.model.startsWith("pyvelop")) if (mesh_device.length) { return mesh_device[0][0] } } ]]]
I think its broken since the latest update... I cannot figure out what is wrong with the Mesh part. I am getting a Key error when I rename , delete, or pause internet. I know this was fixed in the Node cards but I tried to remake the Mesh part with the code you had but failed.
I tried to place this Object.keys(this.hass.devices).filter(key => this.hass.devices[key].config_entries[0] == config_entry_id && this.hass.devices[key].model.startsWith("pyvelop")) after let mesh_device =
Edit: I Can get it work by editing the mesh code at the break by replacing it with the key from the Developers Service feature found in the yaml there. But I assume fixing the code is the correct way so that others can enjoy these features.
Hello,
I will start by saying I know that this request is a stretch! You mentioned multiple times you are focusing your time on a different dashboard for the Velops which I respect. However I use your existing examples in the readme as that's all I have to go by and with your recent update to the services I know we can have the ability to rename devices. Could you add that function to the Device Detail Card? Also if its not to much to ask, the ability to then reserve the DHCP IP for it?
This is my use case: Your cards fit perfectly for my Portrait monitor so I enjoy the layout you originally took.