[Custom component] AsusRouter integration

sesame26 · January 8, 2023, 2:20pm

I did restart my HA so not have logs available at the moment, if I enter the IP address of the router in my webbrowser it does redirect me to the Asus login page so it is available and not use any SSL protocol just enter it through http://ip adress

EdwardTFN · January 8, 2023, 2:46pm

sesame26 · January 8, 2023, 3:33pm

After full reboot of HA I hot it to work, Thanks for your reply!

h3llrais3r · January 8, 2023, 4:38pm

That’s what I was afraid for… thx for providing your feedback.

Vaskivskyi · January 8, 2023, 5:56pm

0.17.0 AiMesh support

2023-01-08

Requirements

Minimum Home Assistant version bumped to 2023.1.0

Features

Devices:
- Added device modes (Router or AiMesh node) which can be selected during initial integration configuration or via Configure option on the Integrations page
- Devices in Router mode support all the features of AsusRouter
- Devices in AiMesh node mode support the following feature groups: Main, CPU, LED, Load average, Network, Ports, RAM, Temperature. Other features are disabled as unreliable / duplicating
Added AiMesh support (FW: 386.x+ only):
- Wireless backhaul
- Wired backhaul
- Node status binary_sensor entities
- Node devices
- Node-related events: asusrouter_node_connected, asusrouter_node_disconnected, asusrouter_node_reconnected
- via_device attribute for the node devices
- AiMesh data is updated at the same rate as connected devices
Added node MAC to the connected device identity
Adjusted entities attributes to be sorted alphabetically in the frontend (except for some default attributes of device_tracker entities)
Improved generation of unique IDs
Network interfaces are renamed to more obvoius names (WLAN0 → 2.4 GHz, WLAN1 → 5 GHz and so on). entity_id will stay as they are if already in use. For new users, entity_id will have new naming

Bug fixes

Added new API endpoint to monitor online status - device trackers should become more reliable (FW: 386.x+ only)
Fixed naming of temperature sensors after bug in 0.15.0
Fixed Platform asusrouter does not generate unique IDs.
Fixed problems with unique IDs for multiple devices setup
Fixed events options

Translations

A new string Device mode was added to the configuration flow (in respect to the new device modes implemented). It still requires the following translations: cs, es, fr, nl, pt-BR, sk. You can translate it on lines 18, 31 and 111 of the corresponding traslation file (marked with [NT] as Not Translated)
A string was updated from Device trackers update to Devices / AiMesh update to signify thew same time interval for all the devices. Requires translations: cs, es, fr, nl, pt-BR, sk. Lines 49 and 141
New strings added for node events. Missing cs, es, fr, nl, pt-BR, sk. Lines 175:177

Documentation

Added scripts for automatic generation of devices and available features
Updated compatible devices list
Updated feature list to show which of features are available in which device mode

Dependencies

Bumped asusrouter library to 0.16.0

Other changes

Switched to UnitOfDataRate enum (>= 2023.1.0)
Switched to UnitOfInformation enum (>= 2023.1.0)

New modes

As you might notice, this update brings 2 different modes of device - router and node. Even though everything will be working even with many routers, some of the entities will be repeating with no actual need.

As a result - it is recommended to have 1 router and many nodes. Then all the controls will be available through the router and nodes will only have useful sensors. Also, it will automatically avoid the creation of many repeating device trackers (only device trackers from the router are correct anyway)

AiMesh documentation

https://asusrouter.vaskivskyi.com/features/aimesh.html

Support AsusRouter

Monetary support:

You can make a donation using the Buy Me a Coffee service
Thinking of buying a new Asus router to use with AsusRouter integration? Check the compatibility list in our Docs. If you will use any of the Amazon Associate links, I might get a small (1-3%) bonus from Amazon (usage of the associate links does not change the price of the items for you)

Non-monetary support:

Star AsusRouter repository
Know a person with an Asus device using Home Assistant but not AsusRouter? Let them know, AsusRouter is cool and has lots of useful features

sesame26 · January 8, 2023, 9:28pm

Unfortunately then new 0.17.0 release not is working for me, the integration not starts up properly:

This error originated from a custom integration.

Logger: homeassistant.config_entries
Source: custom_components/asusrouter/bridge.py:246
Integration: AsusRouter (documentation, issues)
First occurred: 23:24:09 (3 occurrences)
Last logged: 23:26:23

Error setting up entry 192.168.0.1 for asusrouter
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 382, in async_setup
result = await component.async_setup_entry(hass, self)
File “/config/custom_components/asusrouter/init.py”, line 24, in async_setup_entry
await router.setup()
File “/config/custom_components/asusrouter/router.py”, line 700, in setup
await self.update_nodes()
File “/config/custom_components/asusrouter/router.py”, line 807, in update_nodes
aimesh = await self.bridge.async_get_aimesh_nodes()
File “/config/custom_components/asusrouter/bridge.py”, line 257, in async_get_aimesh_nodes
return await self._get_data(self.api.async_get_aimesh)
File “/config/custom_components/asusrouter/bridge.py”, line 246, in _get_data
raw = await method()
File “/usr/local/lib/python3.10/site-packages/asusrouter/asusrouter.py”, line 834, in async_get_aimesh
await self.async_monitor_onboarding()
File “/usr/local/lib/python3.10/site-packages/asusrouter/asusrouter.py”, line 657, in async_monitor_onboarding
convert = converters.onboarding_connection(connection)
File “/usr/local/lib/python3.10/site-packages/asusrouter/util/converters.py”, line 313, in onboarding_connection
raise ex
File “/usr/local/lib/python3.10/site-packages/asusrouter/util/converters.py”, line 309, in onboarding_connection
“connection_type”: CONNECTION_TYPE[temp[0]],
KeyError: ‘5G1’

Vaskivskyi · January 8, 2023, 10:27pm

0.17.1 A bugfix

2023-01-08

Bug fixes

Fixed bug with AiMesh 5 GHz-2 connection between nodes (report #C364)

Dependencies

Bumped asusrouter library to 0.16.1

@sesame26, please, check 0.17.1

sesame26 · January 8, 2023, 10:55pm

@Vaskivskyi works with 0.17.1 !!!

EdwardTFN · January 8, 2023, 11:58pm

My HA haven’t detected this update. Is that available already?

I’m running HA 2023.1.1.

EdwardTFN · January 9, 2023, 6:08am

Now I can see it.

Vaskivskyi · January 9, 2023, 6:11am

@EdwardTFN, sorry, was already writing a reply. HACS checks for updates with some periodicity. But you can always reload HACS and it will show updates immediately

@sesame26, great! Hope, you won’t have any problems with AsusRouter

Vaskivskyi · January 9, 2023, 10:18am

Do you want to add AsusRouter to HA Core integrations?

Vote for the feature request!

EdwardTFN · January 9, 2023, 1:18pm

@Vaskivskyi, any idea here? It started when I’ve updateom from v0.16.x to v0.17.1.

2023-01-09 13:03:40.811 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration asusrouter which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

2023-01-09 13:05:06.155 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry ASUSRouter for asusrouter

File "/config/custom_components/asusrouter/__init__.py", line 24, in async_setup_entry

File "/config/custom_components/asusrouter/router.py", line 680, in setup

ValueError: Unique id 'asusrouter_7c:10:XX:XX:XX:e0_guest_5_ghz_2_1' is already in use by 'switch.router_guest_5_ghz_2_1'

Vaskivskyi · January 9, 2023, 1:28pm

@EdwardTFN, oh, it seems like it happens to some users but not everyone. Also didn’t get it during tests with migration… Issue #450.

I will try to reproduce it and fix it today, so everyone can properly migrate. In case you don’t want to wait, it will work if you just remove and set up integration again.

Sorry

EdwardTFN · January 9, 2023, 1:52pm

No problem. I can keep the issue until you have a fix, so you can use my case as a testing bed if you want, otherwise I will remove and setup again as this is not a big issue as well.

sesame26 · January 9, 2023, 3:22pm

@Vaskivskyi I am getting these errors every few hours or so

2023-01-09 14:40:12.230 ERROR (MainThread) [custom_components.asusrouter.router] Error fetching ports data: None

2023-01-09 14:40:12.233 ERROR (MainThread) [custom_components.asusrouter.router] Error fetching gwlan data: None

2023-01-09 14:40:12.241 ERROR (MainThread) [custom_components.asusrouter.router] Error fetching parental_control data: None

2023-01-09 14:40:38.231 ERROR (MainThread) [custom_components.asusrouter.router] Error fetching ram data: None

2023-01-09 14:40:38.235 ERROR (MainThread) [custom_components.asusrouter.router] Error fetching wlan data: None

2023-01-09 14:41:10.230 ERROR (MainThread) [custom_components.asusrouter.router] Error connecting to ‘192.168.0.1’ for device update: None

2023-01-09 14:41:40.230 ERROR (MainThread) [custom_components.asusrouter.router] Error connecting to ‘192.168.0.1’ for device update: None

2023-01-09 14:42:10.229 ERROR (MainThread) [custom_components.asusrouter.router] Error connecting to ‘192.168.0.1’ for device update: None

Vaskivskyi · January 9, 2023, 4:35pm

@sesame26,

Are the sensors stuck or did they recover and started updating?

Do you connect to your device with the SSL option or without? It is recommended to use an SSL connection since it is more stable on most devices

sesame26 · January 9, 2023, 5:20pm

@Vaskivskyi the sensors are available when I check, I not use SSL, to be honest I also have no idea how to do this, if I check the SSL conection box I get a “unknow error”

This error originated from a custom integration.

Logger: custom_components.asusrouter.config_flow
Source: custom_components/asusrouter/config_flow.py:863
Integration: AsusRouter (documentation, issues)
First occurred: 19:20:27 (3 occurrences)
Last logged: 19:21:59

Unknown error of type ‘<class ‘homeassistant.exceptions.ConfigEntryNotReady’>’ during connection to 192.168.0.1: (‘Cannot connect to host 192.168.0.1:80 ssl:True [None]’, None)
Unknown error of type ‘<class ‘homeassistant.exceptions.ConfigEntryNotReady’>’ during connection to 192.168.0.1: (‘Cannot connect to host 192.168.0.1:80 ssl:False [None]’, None)

sesame26 · January 9, 2023, 5:52pm

@Vaskivskyi Ok did see also needed to change the port, now did set-up with the SSL box checked and the Check SSL Certificate box unchecked… I hope this is the correct way to do it

Vaskivskyi · January 9, 2023, 6:43pm

0.17.2 Migration improvement

2023-01-09

Bug fixes

Fix removing duplicates on unique_id migration (reports #C371, #443, #450)

Translations

Completed Spanish translation (@edwardtfn)
Completed Portuguese (Brazil) translation (@edwardtfn)

Github / HACS

Added link to the AsusRouter → HA Core merge feature request

@EdwardTFN, please check the update. Migration should work better now.

@sesame26, yes. This should work well. Just make sure, that SSL is enabled in your router settings. But if it works for your now, than it’s fine