Just a heads up. I’ve pushed a new release today. The only real things in there are preparing for the HASS 2021.11 release. They shouldn’t break anything mind you so just raise an issue on Github if you spot anything.
This is the new functionality added. Essentially I’ve made all binary sensors and sensors have the diagnostic category.
The Mesh device will also have the configuration_url set so that it’ll link to the primary node.
You may have spotted that there’s a couple of big things hiding in there (UPnP support and preventing duplicates). You shouldn’t really notice these but they mean the following…
For those that remove the integration, or are new users, the primary node should now be automatically discovered for you. When you configure you will still need to supply the password, timer details and select your device trackers.
Switches have now been given the configuration category which should help with the layouts in Lovelace.
For those interested in what happens when adding the integration for new or existing users and when duplicates are prevented, I’ve written up what I’ve tested: -
New (manual) = created with unique_id
New (SSDP) = primary node automatically populated, created with unique_id
Existing (no unique_id, SSDP enabled) = unique_id populated when discovered
Existing (no unique_id, no SSDP) = no unique_id
Existing (no unique_id, no SSDP, try to add duplicate) = unique_id populated, duplicate aborted
Existing (unique_id, try to add duplicate) = duplicate aborted
The unique_id in each case is the serial number of the primary node. This was made more awkward by the fact that I missed adding the unique_id in the initial releases. Hopefully no-one should even notice a difference mind you. This essentially means that if you replace your primary node, then you’ll probably be safer removing the integration and re-adding (unless you fancy manually modifying the YAML file for config entries).
Hello
I really liked your Lovelace layout and would like to use it, but when I copy the yaml and paste it in my lovelace I get all kinds of errors. I guess most of them are errors on intendations, but it is hard to see them all with so much code. Is there a way to just copy into the file and it works? I have installed all the cards you have used as well
The only thing I don’t get to work is the pictures of the nodes on card 3. I see in line 61 that there is a line with entity_picture. I uploaded an image to my www folder and changed line 61 to /www/velop_nodes.png/
But I still don’t get an image on the card.
Ah yes. I should probably have been a bit more explicit about that.
The images should be placed in a folder called velop_nodes in the www folder and named according to the model number and in PNG format. Hopefully the below screenshot shows what I mean. You may also need to force reload the page (shortcut for that typically depends on browser but CTRL + F5 normally does it).
Hi, I’m really new to Home Assistant and I really don’t know how to install your custom integration.
I got 5 nodes that I would love to integrate into my setup. Can you please guide me as to how to install your integration.
Thank you in advance.
Unfortunately, I am not able to log in. Logging in via https://linksysremotemanagement.com works. If I use the same password for “192.168.178.54”, I cannot log in: Continuous loop.
Did the integration find your router automatically?
Are there any logs in Configuration --> Logs?
Based on the screenshot I would guess that you’re router is actually 192.168.178.1 rather than .54 - you could try that if the router wasn’t automatically found.
I see. I haven’t enabled bridged mode on any of the nodes. Currently my primary node is plugged into the back of the router. If none of the nodes are acting as a gateway then the auto-discovery won’t work. It may also be that the JNAP API responds differently.
If you click on those messages in the log screen (the ones in your screenshot) could you send over the logs?
I’ve switched a node to bridged mode now but it doesn’t look like it’s going to give you much information. It seems to respond to all the same queries but can’t distinguish between node types. However, this may just be to do with how I have it working (I’ve left my main mesh up and running - too disruptive to take it down and just plugged this one in to check how it responds).
If you’re up for running some commands against yours we can see if yours behaves the same. The commands can be executed using Postman and I can build you a collection to just run to get back the results.
Also, the password you’ll need to use is the one that you use to login directly to the node (not via the Internet based service). So in your case, if you were to navigate to 192.168.178.54 you should see a Linksys page that will allow you to login (you may have to click a link towards the bottom of the page first. It’s the password you use there that you’ll need to use for the integration.
I did add the bridge manually to mine HA instance but it didn’t show much to do with the mesh due to the aforementioned thing of not recognising the node types.