AsusWRT not tracking any device

Configuration
1

I recently updated my router to version 380.66_2 and home assistant to 0.46.1 and since that my devices are not tracking, they are stuck in a state of home or not_home but they never update. For example my iPhone is currently sitting with me at work but HA says its at home.

Im using the AsusWRT component via SSH, i have confirmed i can login to the router with credentials supplied to HA, i have updated my /home/homeassistant/.ssh/known_hosts file.

I can see if i query the HA service (sudo systemctl status [email protected] -l) that there is a process for SSH connected to the router and it never goes away which makes sense based on the changes in this version of HA, ive checked DNSMASQ on the router and the ARP cache and both are correct.

Im at a loss on how to make this work.

Edit: so 30 minutes after my service has started i get this in the log:

2017-06-13 15:32:33 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from asuswrt took longer than the scheduled scan interval 0:00:30
2017-06-13 15:33:00 ERROR (Thread-1) [homeassistant.components.device_tracker.asuswrt] Connection refused. SSH enabled?

Edit2:

So now getting this logged very often:

2017-06-13 16:02:00 WARNING (Thread-3) [homeassistant.components.device_tracker.asuswrt] Could not parse lease row: b'cat /var/lib/misc/dnsmasq.leases\r'
2017-06-13 16:02:00 WARNING (Thread-3) [homeassistant.components.device_tracker.asuswrt] Could not parse lease row: b'192.168.1.83 dev br0 lladdr a0:02:dc:0a:b6:fc STALE\r'
2017-06-13 16:02:00 WARNING (Thread-3) [homeassistant.components.device_tracker.asuswrt] Could not parse lease row: b'192.168.1.8 dev br0 lladdr 00:17:88:23:48:12 REACHABLE\r'
2017-06-13 16:02:00 WARNING (Thread-3) [homeassistant.components.device_tracker.asuswrt] Could not parse lease row: b'192.168.1.7 dev br0 lladdr 00:04:20:f7:0a:ff STALE\r'
2017-06-13 16:02:00 WARNING (Thread-3) [homeassistant.components.device_tracker.asuswrt] Could not parse lease row: b'192.168.1.254 dev br0 lladdr b8:27:eb:a1:b2:c5 STALE\r'
2017-06-13 16:02:00 WARNING (Thread-3) [homeassistant.components.device_tracker.asuswrt] Could not parse lease row: b'192.168.1.84 dev br0 lladdr 68:54:fd:2c:bb:08 REACHABLE\r'
2017-06-13 16:02:00 WARNING (Thread-3) [homeassistant.components.device_tracker.asuswrt] Could not parse lease row: b'192.168.1.6 dev br0 lladdr ec:e5:12:00:b3:58 STALE\r'
2017-06-13 16:02:00 WARNING (Thread-3) [homeassistant.components.device_tracker.asuswrt] Could not parse lease row: b'192.168.1.3 dev br0 lladdr b8:27:eb:9b:bd:d1 REACHABLE\r'
2017-06-13 16:02:00 WARNING (Thread-3) [homeassistant.components.device_tracker.asuswrt] Could not parse lease row: b'192.168.1.4 dev br0 lladdr b8:27:eb:ec:4a:03 DELAY\r'
2017-06-13 16:02:00 WARNING (Thread-3) [homeassistant.components.device_tracker.asuswrt] Could not parse lease row: b'192.168.1.237 dev br0 lladdr ac:3c:0b:14:68:0c STALE\r'
2

MY TPLink device tracking component also broke and I’m pretty sure it was the .46 update

3

@eximo84 did you ever get this figured out. I know it is 9 months later but I seem to be having a similar issue where my devices are getting updated. They are stuck with home or not_home or people show up at my home who are not actually there (at least I don’t think they are) I don’t get those errors but I have the same symptoms and i am on an Asus router.

4

I ended up using telnet instead. Annoying as it was working so well.