Navigate to ip address on tap action

Tags: #<Tag:0x00007f326ebb35f8>

I have a couple of esp8266 devices each running a webserver that has UI to configure those devices. Each of these devices uses the homeassistant mqtt auto discovery feature and l am able to see my lights or switches and manipulate them from homeassistant. I use default Lovelace UI nothing custom.

What l would like to achieve is when in homeassistant for example l can tap on the device name say “Kitchen Light” . This currently takes me to another screen still in homeassistant where l can look at history. Is there a way in that next screen l could tap or double tap on the name again but this time it should navigate to an external url in this case the ip address of that device as reported to mqtt. The ip address is already known due to the mqtt integration.

I want a solution that l do not need to update on each auto discovered device. Has anyone done that or offer any help.

This would prevent me from having to leave homeassistant find the ip address of the device launch browser and do my configuration and then comeback to homeassistant. The device ip addresses are on dhcp its tedious and would be nice to do it all from homeassistant.

Have a look at tap actions:

In particular,

navigation_path which takes you to another Lovelace view, and

url_path, which links to external websites.

However these actions can only be used in certain places like Lovelace buttons, Lovelace entities cards (tapping anywhere on the whole card, not just the row item), picture glance card, etc…

Have a browse through the Lovelace cards looking for the ones that support tap actions (right hand list):

As I wrote here in your cross-post: URLs in attributes will be rendered as clickable links in the more-info starting with the next release. So with templated attributes you could probably solve it.

Thank you looking forward to the next release. In my case the url would be dynamically created as


Where the IP address reported by mqtt is used.
Also users that do need this feature can have a check box or something to disable or enable globally. The intend being that its setup once and any future autodiscovered entity inherits the behavior without further homeassistant configuration required.

I think that is a very niche requirement that does not apply to most users. But since you can handle that yourself with templates and the new URL rendering, that is solvable.