Login attempt or request with invalid authentication - even after component removed

Hello friends - I have been getting constant login attempt failures and the IP addresses in question were for two wireless tag managers. I decided to simply remove the entire Wireless Tag integration, i.e. commented out from the config file, removed any reference to the wireless tags in the UI etc. However after restarting the login attempt failures persisted!

Wondering if someone else has or has had similar issues? Searched the posts here and on Reddit as well but the funny thing about the above is that nothing in the config file would expose these two specific IP addresses to HA so a bit lost.

p.s. running Hassio (latest).

This problem seems wide spread with as many different solutions as there are posts. I just upgraded to .104.3 and I am getting all kinds of these errors. I have multiple Lan-based apps running on Pcs or PI’s that send sensor update info to HA. This has been working fine until I recently updated from 100.3 to 104.3 To make matters worst, I can roll back 0.104.3 to 100.3 but the errors persists. Only option was to restore from a previously created imah=ge file of .100.3 Unless I can figure out what is goiung on I am stuck at that version.

I’m experiencing this also caused by wireless tag integration. I too commented out the configuration and the error persists. Turns out you can edit the URLs for RESTful calls in the tag list. Removal of the integration does remove these URLs, which is why the error will persist.

Seeing this here too. Trying to set up wirelesstag integration to do things. Monitoring of state is working fine, but push notifications aren’t working. I’m seeing the login failures. I’m using http and my LAN is a trusted network. Ideas?

I have noticed this recently with the wireless tag hub having login failures. Did anyone have any luck resolving this? I am still getting sensor updates into HA. I do have the hub on a separate LAN but this hasn’t been an issue in the past. I noticed this started in the last couple of weeks.

I ended up re-installing (was migrating to a NUC anyway). Now use the new auth method so need to insert a bearer token for it to work. I use a http proxy middleware to do this. similar to this post (but the json proxy package didn’t work for me): Wirelesstag local url calling working wih new auth methods

Edit: also need to change a line of code in the wireless tag component (i.e. need to make it custom) so not exactly for everyone…

1 Like

I gave up and implemented a workaround until this is resolved. Someone developed a device handler and smart app for Smartthings that works pretty well. So I repurposed an old Smartthings hub and integrated with HA for the sole purpose of tracking these Wireless Tags. It’s working pretty well with the temperature and humidity sensors where latency isn’t really an issue. But I’m bouncing info through at least maybe three cloud services, so it leaves a little to be desired on the patio door sensor. All in all, it’ll work until this gets figured out.