Thanks for the logs!
I have already found the issue. It will be fixed either today or tomorrow and I will publish a new release with the fix
Thanks for the logs!
I have already found the issue. It will be fixed either today or tomorrow and I will publish a new release with the fix
Thanks very much!
Sorry, there is a small delay with the release. But it will be ready before the end of the year
Too many distracting factors coming and going this time of the year
2022-12-31
macmode
attribute of Guest WLAN switches / binary sensors changed to string instead of boolean. More details on the possible values here
asusrouter
library to 0.15.2
2022 was full of achievements for AsusRouter. Even though it appeared only this year, the integration has already functionality covering most of the use cases for home routers.
And even more features and improvements are coming in 2023. Including the most-awaited support of AiMesh features. Stay tuned
Obviously enough, this is the last release of AsusRouter this year
Monetary support:
Non-monetary support:
Thanks for your continious support of this briliant integration! Have a nice newyears eve and all the good fortune for 2023.
Thank you and happy new year!
This integration doesn’t produce the error messages at startup any more. However it still produces the error messages if the router stops responding (or maybe it’s if the dns service on the router stops running, because I’m using names to connect to local services not IP addresses).
For example today the log shows something bad happened. The nextdns service stopped running (don’t know why, there’s no logging info) and then a couple of minutes later the httpd service was restarted maybe by your integration?
Jan 1 14:10:22 service-event: /jffs/scripts/service-event restart httpd
I’ve increased the router logging level to see if I can get more info if it happens again. It’s happened several times in the past few weeks when nextdns stops working for no obvious reason, so I have a bash script that tries to restart it every 5 minutes. I don’t know if your integration and the nextdns service have some incompatibility?
Hey, AsusRouter by default is not pushing anything to the device, including anything connected to the running services. It can restart HTTP daemon, but only when you click the corresponding button button.{device}_restart_http_daemon
.
From the integration point of view, it just connects to the device and asks for the status (for all the entity values). If a connection cannot be established, it will try once more. Only pressing buttons or switches is actually sending something to the device.
So whatever has happened to HTTPD - that is on the device itself.
Do you by any chance use Merlin 388.1? I have noticed problems with HTTPD on my RT-AX88U with the latest Merlin and an AiMesh device connected. The HTTP Daemon is regularly stucking, which causes problems with integration and also does not allow to access the Web UI of the router.
Thanks that’s a very helpful explanation. Mine is v386.7.2 but I do have a mesh configuration, maybe that’s a factor.
Awesome! Your work and this integration are very much appreciated. Thank you.
With the new RT-BE96U and GT-BE98 models announced, it’s also time for our announcement.
Regardless of the number of changes Asus will introduce to the FW of new devices, AsusRouter will support them as soon as enough data is available.
Hi, I recently discovered home assistant and I was trying out the official asuswrt integration for my old RT-N66W (white variant of the RT-N66U) router. I noticed a lot of issues with faulty readouts and so one and now stumbled upon your custom integration. I hope this will give a lot better readouts then the original integration.
Are there any plans to migrate/intergrate your version with the official one? Because it would be better to have a single integration (IMHO).
EDIT: installed latest version, but unable to connect when setting up:
if you use duck-dns, make sure everything ok , with ur base url, and ddns.
BTW. above is NOT a “valid” error, it’s just a picture … error message use to be written to i.e. logs, maybe even with more relevant info, in regards to where the “onbekende fout” occured
Sorry, wan’t able to add a screenshot for the error in the same message.
Here the error from the logs:
For setup, I just need to enter the ip address of the router. After that, I enter username/password and I’m getting the error.
Maybe some other info.
Running RT-N66W with merlin fork:
Could it be that this version is not supported?
Cfr: Features | AsusRouter
And you have restarted HA. after installing the integration ?
Yes, now I’m trying out previous versions.
and if you i.e use Ddns, or/and have ip-bind to MAC ( of the old Router ) ? , but i asume you don’t use Ddns as you didn’t respond to my previous(first) Q
I don’t use ddns.
Maybe, seems like an “odd” version you got there, thou im not sure that should cause a connection error