Xiaomi Mi Router 3g + Padavan = Dont work device_tracker

Configuration
1

I have a Xiaomi Mi Router 3g and I flashed padavan custom firmware on it.
My configuration.yaml settings did not work.

Configuration.yaml

asuswrt:
  host: 192.168.0.1
  username: admin
  password: pass123

device_tracker:
  - platform: asuswrt
    consider_home: 180
    interval_seconds: 60
    new_device_defaults:
      track_new_devices: false
      hide_if_away: false

I also ran these procedures described at final https://www.home-assistant.io/components/asuswrt/

  1. SSH or Telnet into the router. (default ssh [email protected])
  2. Run the following command to find the file:
$ find / -name "dnsmasq.leases"
  1. Copy or remember the full path of, example: /tmp/dnsmasq.leases
  2. Create the folder if it does not exist:
$ mkdir -p /var/lib/misc
  1. Add the linking process to the routers started script (one line):
$ echo "/bin/ln -s /tmp/dnsmasq.leases /var/lib/misc/dnsmasq.leases" >> /etc/storage/started_script.sh
  1. Reboot the router or link the file:
$ /bin/ln -s /tmp/dnsmasq.leases /var/lib/misc/dnsmasq.leases
2

Hi,

this is my config that works for me:

asuswrt:
  host: 192.168.0.1
  username: !secret asuswrt_login
  password: !secret asuswrt_pass 
  protocol: ssh
  

device_tracker:
  - platform: asuswrt
    new_device_defaults:
      track_new_devices: False
      hide_if_away: True

… so only difference is “protocol: ssh”

Did you turn on SSH on Router side?

image
image706×116 28.8 KB

3

This is my router setting.
Can you compare with yours and see if there are any differences?

image
image1054×1123 339 KB

image
image1055×1173 264 KB

4

Worked!
I excluded known_devices and restart homeassistant.

1 Like
5

Capturar

Help-me, please.

The component device_tracker asuswrt don’t correctly tracker.

This device should be 100% online, but connects and disconnects only on device_tracker / homeassistant. In the real world he stays connected all the time.

Does anyone have the same problem? Is it a configuration error?

6

Have the same issue. Try to set this option in your device yaml config file:

api:
  reboot_timeout: 0s