I am having the exact same issue as this guy:
I verified that ssh is enabled by sshing in myself.
Any thoughts?
I know this is not a solution, but have you considered using nmap instead? That way you can use it with any router not just ASUS. Also I see no difference in the desired outcome.
I’m not seeing the same error message but mine doesn’t appear to be working either. Never really marks me as not_home.
Going to change my protocol back to Telnet and see if that helps.
I’ve found NMAP to be unreliable, had it enabled for a long time and finally disabled it.
1 Like
So the original referenced topic had a solution that worked for me, setting mode to telnet.
That being said this past week, the upgrade broke my HA Raspberry Pi An1 install again, resulting in no web page generation at all and no logs?
I also have noticed problems with I-phone registration using AsusWRT mac address logging. The Asus will not show the Mac Address anymore via the admin control panel but HA will continue to falsely show I phone until I do a hard reset of the Pi. Androids, computers and Xboxes seem to work well.
Calvin
Both protocols are running the same commands on the router, so switching protocols is not going to help with device detection.
The traceback is due to a failed SSH login. If you can establish a SSH connection to your router from your Home Assistant host using the same account HA is running as, then the asuswrt component should also be able to connect, assuming the credentials are correct in the config file.
Think I got it figured out. I remembered that I did a full reset of my router so the ECDSA key fingerprint in the hass user’s ~/.ssh/known_hosts was wrong.
Running sudo ssh-keygen -f "/home/hass/.ssh/known_hosts" -R 192.168.1.1 fixed it.