First let me say ‘thank you’ for the integration and the work you put in on it.
For those systems running HAOS, Python should already be 3.10. I’m fine with dropping 3.9 support, but we will need to hear from others.
First let me say ‘thank you’ for the integration and the work you put in on it.
For those systems running HAOS, Python should already be 3.10. I’m fine with dropping 3.9 support, but we will need to hear from others.
I’m running HAOS, so either way is fine with me.
Version 0.13.1 of AsusRouter is already available in HACS. Please, check it out - it should work with HA 2022-12 without any problems with dependencies.
This is absolutely perfect - thank you!
Perfect, many thanks.
Probably you have already noticed, that lots of 802.11ax routers started receiving updates to the latest 388.x firmware, with some new features and some changes to the old ones.
For me and AsusRouter as well, the plan is to fully support these builds. And the first new feature, coming to the integration from branch 388 will be the support of WireGuard
Since Merlin 388.1 is already out of beta, I am glad to announce, that AsusRouter will fully support it!
The only minor problem is for temperature sensors for WiFi modules, which are unavailable because of one more change in the routers’ API endpoint. This will be fixed in the next release (but the fix itself is ready now).
The native 388 builds of AsusWRT are already supported as much as possible.
The only problem you will experience for now - OpenVPN clients and servers are broken. This is connected to a completely new way of working with VPN released in 388. The fix is already planned.
Fix for OpenVPN on native builds
I will try to implement the new VPN features as soon as it is possible. But you know, Decembers are a bit of a busy time, so let’s say closer to the end of January.
WireGuard support
I don’t have any experience with WireGuard, so understanding and implementing the new feature will require some time. But since the feature is fully supported by my testing device, the currently expected timeframe is January-February
No-spoiler alert
Some new cool features are also expected in AsusRouter at the beginning of the year. I am quite sure, you guys will like it.
A bit about what AsusRouter has already achieved:
As usual, please don’t be afraid to suggest new features and report bugs. All the reports are welcome and if possible all of the issues are solved. You can fill in a report in AsusRouter GitHub or here.
There is always a way to make AsusRouter even better. Let’s do it.
You can always support the development of AsusRouter using the BuyMeACoffee service:
Have a nice holiday time!
and with holidays, guests are relatives are coming for visits to our places. Connecting to our WiFi and…
… adding tons of device_trackers to HA which we will never actually use.
Happened to you? I can easily relate. And now the new version of AsusRouter is here to help you with the HA mess.
asusrouter.remove_trackers
serviceProbably, you have noticed, that you cannot just easily remove entities, even if the device did not appear online for a long time. This is done by purpose - device trackers are watched all the time (so HA will notice when it appears online again).
With the new service, you can mark unwanted entities as non-watched. This will allow you to remove the entities.
Please, keep in mind:
Now, that Merlin 388.1 is officially released as stable, AsusRouter is adding support for the new way of reporting WiFi module temperatures.
Already available in HACS
If you are interested in what else is planned for AsusRouter, please refer to this post.
Please, don’t forget about the active deprecation warning for some parameters (entity_id
, mac
and name
) of asusrouter.device_internet_access
service. More details were here. They will be removed in version 0.15.0 and should not be used anymore.
Your suggestions on how to improve AsusRouter documentation are always welcome.
Found an error or something missing? Let me know - so I can fix it.
Is the service asusrouter.remove_trackers
only for entities created with devices, or would we be able to remove entities that show the MAC addresses? I tried using the service on entities without an associated device, but am still not able to remove it after. Maybe I’m doing something wrong?
Thanks again for your awesome work and continued development of this awesome integration!
Hey,
You should be able to remove any device_tracker
entity, which is not reported by your router anymore (regardless of whether a device is created in HA).
It might be, your router is still reporting the device (if it was connected recently enough and your router didn’t clean up yet). In this case, it should be possible after the router reboot.
Should be like on the sequence of the snapshots
Please, check whether the device reboot helps. Or whether it works with some other device_tracker
Thanks to Nyaran, AsusRouter once again has a complete Spanish translation.
Currently, AsusRouter has full support for the following languages:
and partial support for:
Are you fluent (or just good) in some languages? Help me translate AsusRouter.
Even if you don’t know how to create a Pull Request to the AsusRouter repo, just create a new issue or let me know in any way you prefer - I will help you to prepare all the needed.
May I create a PR directly at the main branch?
Yes. It’s completely fine to create PR to the main branch. In case something will be wrong, I will help you with edits before merging it
By the way, we already got the French translation
Hi, I can do Portuguese (Portugal) translation.
Just tell me how
I am preparing a translation into cs (Czech Republic).
One item is not entirely clear to me and that is interval_light
. Is it a light data update or something else?
Yes, this string is for the time interval for the LED binary_sensor / switch update. But since it is supposed to be also used for Aura RGB (when implemented), it’s called a general ‘light’ data.
Hey. You would need to:
Fork
button on the top right (on desktop)custom_components/asusrouter/translations/
path and create a new file named pt.json
- that would be a file for Portuguese.en.json
there - that is the English translation with all the needed fieldskey: value
pair. You need to translate only values (on the right from the :
, on the snapshot values are marked in blue)Keep in mind, there are many strings repeating twice
P.S. If you don’t feel confident enough with creating PR or using GitHub, you can just copy the content of the English translation ( ha-asusrouter/en.json at main · Vaskivskyi/ha-asusrouter (github.com)), translate all the values and save the new file on your PC (or other device) and send it to me via email: [email protected]. I will add it to the integration.
I added a translation of cs.json (Czech) to the main branch (merge request).
I hope I didn’t do something wrong.
Thanks a lot! It’s great!
Thanks to @pepe59 and novisys, AsusRouter got translated to Czech and French!
Which totals in 5 fully-supported languages:
and partial support for:
I think we are doing great!
Everyone is welcome to submit a new language support for AsusRouter
I have it translated into the Slovak language, where do I send the json file?
You probably can add the file directly to the repository folder: https://github.com/Vaskivskyi/ha-asusrouter/tree/main/custom_components/asusrouter/translations
You will find a button “Add file” in the top-right of the box with the other files.
thx
add file is not possible but create new and then paste code is possible