Navigate to external device by ip address dynamically #8239
-
Here is what I am trying to do if you can help. I have some esp8266 controllers that I have made that run custom code to control things, each has a web server running on it that I can go to from a browser and configure things like schedules, device names etc. So I can have a device that turns on a light and another that turns on fishpond pump or water pump with its own schedule etc. I have mqtt homeassistant integration with autodiscovery enable, my custom esp8266 devices are automatically picked up by homeassistant without doing any configuration on homeassistant side. To change settings on these devices I simply open browser and enter the ip address of the device and the web server running on the esp8266 allows me to make any changes need. Now there could be as many as 10 of these and on my network getting dynamic IP addresses. I want to be able to navigate to UI running on these devices from homeassistant. I can turn on/off these devices from home assistant and view history from the basic lovelace UI. What I want to achieve is when I get to the more details screen of the entity or some other way have a way to add a button or support such that when clicked it navigates to the url of the entity outside of homeassistant. This would require all this to be dynamically created so that a new device connected to the network works right away without additional configuration on homeassitant. Since the entities connect to homeassistanat via mqtt there must be way to get the entity ip address on the fly and then navigate to its ip address as URL on some tap actin. I could not find this functionality anywhere on the forums. I really want that functionality or a way to be able to achieve it most importantly without having to configure homeassistant for each device. Thanks a lot, hope what I am saying makes sense and thanks for your work. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
I think this is more a backend topic. If an entity has an attribute that contains a valid HTTP or HTTPS URL we will display it as a link. So if you can get the target URL / IP in the backend and add as an attribute, the frontend would show it in the more-info dialog as it does with any other attribute. |
Beta Was this translation helpful? Give feedback.
I think this is more a backend topic. If an entity has an attribute that contains a valid HTTP or HTTPS URL we will display it as a link. So if you can get the target URL / IP in the backend and add as an attribute, the frontend would show it in the more-info dialog as it does with any other attribute.
With templating you can add custom attributes.