First off - just found this over the weekend and THANK YOU! I spent the weekend (as an HA newbie) getting this up and running, but I think I have it all in place, including the cards, and it’s great, so thank you for taking the time to make this available.
I’m having one issue: while I can expand my “offline devices” list, when I try to expand my “online devices” list, nothing shows up. The card changes - the downward-pointing triangle flips to point up - but nothing appears.
I copied all of your card YAML directly from https://github.com/uvjim/linksys_velop - has something recently changed that might be causing this one function not to work?
Not from the UI. You can modify the config entry in the relevant JSON file and reload if you’re that way inclined. Although, removing and re-adding the integration really should t be an issue unless you renamed some entities as they’ll come back with the same names.
A bit of a teaser for something I’m working on…
The Android app now includes signal strength for the Velop nodes and also an indication for the signal strength for devices.
The Linksys application explains this as follows: -
fix regression in service handler from linting fixes
2022.8.1b3 is out: -
adopt new naming convention for HASS 2022.8.0
update cards 2 and 3 to reflect naming changes
update select entity example ui
account for SOURCE_TYPE_* deprecation
2022.8.1b4 is out: -
fix template errors for disconnected devices
update image and pre-reqs for select entity card
guard against missing properties in card 2
2022.8.1b5 is out: -
bump pyvelop to 2022.8.3
ensure all device properties are available
update card 2 YAML to refelect IPv4 or IPv6
2022.8.1 is now out. It should be available in HACS soon.
Breaking Change
If you were using the backhaul information from the Parent sensor, this has now been moved into it’s own sensor. The backhaul sensor is documented in the README, but it uses the reported RSSI value in dBm as it’s state and the attributes now hold the additional backhaul information. Card3 in the example UI has been update to reflect this.
Additional Information
Naming conventions - In HASS 2022.7.0 an entity property was introduced that determined whether the new naming convention should be used. This integration uses the existence of that property to determine how to name the entities.
As I’m sure you’re aware the default for the integration has been Velop Mesh: <identifier> for mesh entities and Velop <node_name>: <identifier> for node entities.
If you are using HASS versions prior to 2022.7.0 then this will still be the case. Any HASS version later than that will use the format detailed here and here.
If you have an existing installation of the integration your entity_ids will not change (I’ve tested that) if new entities are added in the future the naming of those entity_ids will be derived from the new entity naming convention.
No issues should be seen at all for new installations.
The example UIs in the README have been updated to be dynamic between the two conventions. However, they do not take into account a mixture of conventions, i.e. a new entity being added as per the detail above.
@judetf did you ever figure this out? I’m having the exact same issue (i.e. offline devices can expand, but online doesn’t). I’m also not seeing images for card 3’s nodes (image not found icon).
@uvjim first, this add-on is amazing. I got HACS just to use it, and very impressed. One QQ: I opted to use the non-beta when prompted in HACS. Is the YAML on GitHub tailored to the beta versions? (e.g. 2022.8.1b3 seems like the latest, but I’m on 2022.6.2)
Thanks for the kind words. The YAML you see on GitHub in the README will depend on which branch/tag you have selected - the releases are shown as tags and the main branch is essentially live development branch (after my local testing).
RE: the dropdown not showing anything. I’d be interested to know if anything appears in the HASS logs, but also in the developer tools of the browser. Navigate to the dashboard you’re using the cards on, clear the console log of the developer tools and refresh the page. That should give me an idea of what’s happening (combined with potential logs from HASS).
RE: images for the nodes… There’s a post higher up about that I think… However, the path defaults to /local/velop_nodes/<model_number>.png. You can change the path as detailed here. If you change the path then you’ll also need to enable the sensor for the node so the card can read it.
No, still having the issue, but I will dive into the HASS logs now for @uvjim to see what it shows
The images: you have to find and upload your own images - they don’t come as part of the package. So google each model type, find an image, save it as a .png file, NOTE THAT THE FILENAME IS CAPS-SENSITIVE, and save it to the specified directory, and they should appear immediately.
I don’t see anything potentially relevant in the HASS logs although I may not know what/how to look? Here’s what I’m seeing in the console log after a refresh:
Could you test using the YAML in the main repository and also that available in the tag version that matches the integration you have installed, that would be great.
@uvjim, I apologize tremendously, but I’m not sure what you are asking me to do when you say " test using the YAML in the main repository and also that available in the tag version that matches the integration you have installed." I’m happy to do whatever you need me to do, and I hate when I can’t follow instructions, but I can’t figure out what that means or what to test.
No problem. First thing to try is to grab the latest code for the card from here. There were updates to this over the last few days. The updates relate to the beta release but I see no reason that they should fail for older releases.
If the still doesn’t work, could you try the the code here - this assumes that you have 2022.6.2 of the integration installed.
Let’s stick to those things for now.
Again check logs in Home Assistant (Settings → System → Logs) and the browser developer tools (clearing the console before refresh - not sure which browser your using but forcing the cache to invalidate might help, normally CTRL+R or CTRL+F5 if on Windows).
Also, could you post a screenshot of what you’re seeing (or not seeing as the case actually is).
Okay, I tried the new code and it didn’t fix things. (I had been using the code from the second link you send - yes, I’m on 2022.6.2). However, when I did a hard-reload of the page after installing the new code, I happened to have the Developer Tools open in my browser when I clicked on the ‘expand’ arrow and this error popped up:
Screenshots of what I actually see are pretty basic. Here’s what it looks like before I expand the list:
And here’s what it looks like after I click the down-arrow to try and expand it:
Nothing is showing up in the System → Logs at all…
Last note/comment: I greatly appreciate your efforts here. Thank you for taking the time. However, I’ll also note that solving this is not critical for me. Since your code seems to be working for everyone else, I’m more than happy to live without this one feature, when the rest of what you put together is so awesome.
Right, could you try this in your card please? If this works, or at least gets us closer we’ll probably need to find out why you seem to have a device online but it doesn’t have a connection type - that’s a problem for another day though (and is possibly solved by rebooting the mesh).
I’d love to say that did it, but still no love after replacing the card code, restarting HA, and hard-reloading the dashboard page. Here’s the Developer log now:
I will restart my mesh as soon as the wife is done with her work calls!
I’m traveling at the moment, but will update again probably tomorrow.
It’s just an attribute error so I’ll check the attribute exists betore using it. That way you won’t see the error.
Also, on the Mesh device there’s an option to download diagnostics. Could you message that over to me please? I’d like to see if I can work out which device is causing this. Probably best to do that before rebooting anything as it’ll likely clear up after a reboot.