wirelesstag local url calling

[tube0013]

Home Assistant release with the issue:

0.72.1

Last working Home Assistant release (if known):
NA

Operating environment (Hass.io/Docker/Windows/etc.):

hass.io
Component/platform:

https://www.home-assistant.io/components/wirelesstag/

Description of problem:

tagging @sergeymaysak
question RE local tag URL calling.

I see the url calling on the wireless tag site to use my local ip address. for sensors:

http://192.168.1.xxx:8123/api/events/update_tags

and binary sensors:

http://192.168.1.xxx:8123/api/events/binary_event

this works for a few hours, then I go back and check and the urls have been re-written to my outside domain name which will not work over http...

All sensors get changed to:

http://DOMAIN:8123/api/events/wirelesstag_update_tags

Some Binary Sensors get changed to:

http://DOMAIN:8123/api/events/wirelesstag_binary_event

I'm not sure why this is happening, and know it makes the local url calling not work.

Are the original urls in the pull request for the component still accurate? maybe these URLs should be added to the documentation?

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

[sergeymaysak]

@tube0013 - I have updated my dev environment to latest 0.73-dev and trying to reproduce the issue you faced. So far no luck. Please note - from release 0.72 - wireless tags platform is integrated with hass and does not require custom_components setup. I would recommend disable custom_components with tags if you have it. Secondly - please just try to restart hass - I do local url calls registration during every hass start. Let me know results. I left my dev setup active for a while to see if I can catch your issue after some hours. Also note - "wirelesstag_binary_event" and "wirelesstag_update_tags" is expected form of urls in "official release".

[tube0013]

Okay I updated my URLS to my local IP and the "wirelesstag_binary_event" and "wirelesstag_update_tags". and restarted HA (0.73.0 running Hassio, and I've removed the custom-component version since this was released in HA). (should these URLs be defined in the docs so people know how to configure this?)

After the restart the URLs are again updated to my domain name instead of the local ip address. I comment out the basename_url defined in my configuration.yaml which points to my domain name so things like tts with google work. after doing that and restarting HA, Wirelesstag urls are rewritten to my local ip address again (correctly).

So it seems when the component registers for local push, it some how re-writes the URLs with the basename_url?

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

[sergeymaysak]

WirelessTag platform has been updated to address this issue. HASS v. 0.79 includes this update. Basically I've reworked the part which determined base_url to be used for url calls from tag manager back to hass - so now it uses real local ip address instead of url specified by end user in config (which can be a domain url for remote access). So issue should resolved now. (pull request with changes: #16353)