core: Invalid authentication from wirelesstagmgr.lan

The problem

With Wireless Tag Manager’s IP address included in Trusted Networks configuration, notifications of "Login attempt or request with invalid authentication from wirelesstagmgr.lan (192.168.x.xxx) occur until banned by ip_ban_enabled.

Environment

arch x86_64
chassis embedded
dev false
docker true
docker_version 19.03.11
hassio true
host_os HassOS 4.15
installation_type Home Assistant OS
os_name Linux
os_version 5.4.72
python_version 3.8.5
supervisor 249
timezone America/Denver
version 0.116.4
virtualenv false
  • Home Assistant Core release with the issue: 116.4
  • Last working Home Assistant Core release (if known):
  • Operating environment (OS/Container/Supervised/Core): HassOS 4.15
  • Integration causing this issue: Wireless Sensor Tags
  • Link to integration documentation on our website: Wireless Sensor Tags

Problem-relevant configuration.yaml


homeassistant:
  auth_providers:
   - type: homeassistant
   - type: trusted_networks
     trusted_networks:
       - 192.168.x.0/24
       - 192.168.x.xxx <-- Wireless Mgr IP
       - 127.0.0.1
       - fd00::/8
http:
  # Uncomment this if you are using SSL/TLS, running in Docker container, etc.
  # server_port: 8123 - for duckdns
  # ssl_certificate: /ssl/fullchain.pem
  # ssl_key: /ssl/privkey.pem
  ip_ban_enabled: true
  login_attempts_threshold: 15

wirelesstag:
  username: !secret wirelesstag_usr
  password: !secret wirelesstag_psswd

#binary.yaml
- platform: wirelesstag
  monitored_conditions:
    - presence
    - motion
    - door
    - battery

#switches.yaml
- platform: wirelesstag
  monitored_conditions:
    - motion
    - humidity
    - temperature

binary_sensor: !include binary.yaml
switch: !include switches.yaml
sensor: !include sensors.yaml

Traceback/Error logs

No errors reported to HA log


Additional information

I’m running http only and Wireless Tag Manager IP is included in trusted networks as mentioned in the documentation. login errors began to occur following binary sensor configuration. A typical Call URL listed in the Wireless Tag App looks like this: http://192.168.x.xxx:8123/api/events/wirelesstag_update_tags. All sensors and switched appear in the entities list under developer tools.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 19 (7 by maintainers)

Most upvoted comments

@bh56 @garyak As an update - I’m in progress with the fix in @cloud_push brunch of my wirelesstagpy lib (with instant help from @wirelesstags guys), but be aware that the fix will completely remove the notion of local push and will introduce cloud-driven push (in reality it appears that local push is driven by a cloud push as well, so new impl will work even faster)…

I removed the URLs and disabled local calling in the Wireless Sensor Tags web app, but, strangely, something is putting the URLs back and enabling local calling again. Does the Home Assistant integration do so by itself? If so, can it be disabled? yes, the current implementation of integration enables local calling itself. if you want to not use local push - you can remove any notions of binary events monitoring from yaml.

Sergey, First off thanks for you contribution here. It’s really appreciated. Understand this is more of a hobby. I might take a look at your code and see if I can offer any further insight. Any chance you can share what wirelesstag suggested to you to give me some further background?

No expectations on timing Sergey. Thank you for pursuing a solution.