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.
@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
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
@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)
@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 
0.17.2 
Migration improvement
2023-01-09
Bug fixes
Translations
- Completed Spanish translation (@edwardtfn)
- Completed Portuguese (Brazil) translation (@edwardtfn)
Github / HACS
- Added link to the
AsusRouter→HA Coremerge 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
Since the lastest:
Logger: homeassistant.config_entries
Source: helpers/entity_registry.py:695
First occurred: 21:27:45 (2 occurrences)
Last logged: 21:36:38
Error setting up entry 192.168.2.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 680, in setup
entity_reg.async_update_entity(
File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 749, in async_update_entity
return self._async_update_entity(
File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 695, in _async_update_entity
raise ValueError(
ValueError: Unique id 'asusrouter_24:4b:fe:e4:ff:80_temperature_2_4_ghz' is already in use by 'sensor.rt_ac86u_temperature_2_4_ghz'
Debugging doesn’t show anything else.
Edit:
Forget it. Working with 0.17.2!
0.17.3 
A new bugfix for older devices
2023-01-09
Bug fixes
- Fixed issue for the devices with missing
label_macvalue from NVRAM (some older devices with Merlin builds) preventing AsusRouter from start (report #451)
Dependencies
- Bumped
asusrouterlibrary to0.17.0
@Ostracizado, sorry, I was already typing that with the latest version everything should work fine
Users with no problems regarding the mentioned issue do not need to urgently update.
P.S. Sorry for the double release today. Did not want to go to sleep and keep users with an unresolved bug.
0.17.4 One more
2023-01-09
Bug fixes
- Fixed bug in the backend library bothering some users with older FW
Dependencies
- Bumped
asusrouterlibrary to0.17.1
5 Likes
Is it just me or is the documentation hard to understand? I would love to see some code examples in the documentation. Like one thing i want to know is how to i use parental control or device control? Is it not possible to make a list with ”flex-table-card” with name/ip/Mac/parental control for an example? Right now the only information i have found is make a automation and a Button that triggers it to turn on/off parental control that would make me have to create 40ish automations and that aint that great solution…
Search the Forum for flex-table-card, i know it’s there, unfortunately, i deleted the “flex-table-card” i made on “trackers” ( remember flex-table is rows (with columns) from 1 and the same sensor/entity so i doubt you can squeeze in “parental” options, as i don’t see this in the “Trackers” attributes
And it’s basic text-table, last time i looked at it
Quite common some people make Groups, for certain i.e. devices, and “apply” an automation or in other means a script etc., to the Group.
So the first think for you to consider is, do you need a group or groups for your “Parental” feature “turn on/off”, will all be turned on/of at same time/conditions, or what ? , Your “plan” is what sets the requirements, 1 automation ?, 2, 40 ?
I don’t use parental control, but I do have a dashboard using flex-table-card which might be easy to add additional info you need:
type: custom:flex-table-card
sort_by:
- devices+
entities:
include: sensor.aimesh_router_connected_devices
columns:
- data: devices
modify: x.ip
hidden: true
- data: devices
name: ' Device Name'
icon: mdi:devices
modify: x.name
- data: devices
name: ' Address'
icon: mdi:ip-network
modify: x.ip
- data: devices
name: ' MAC'
icon: mdi:barcode-scan
modify: x.mac
- data: devices
name: Connection type
modify: x.connection_type
- data: devices
name: AiMesh node
modify: >-
x.node.replace('7c:10:XX:YY:ZZ:60','Node').replace('7c:10:XX:YY:BB:e0','Router')
card_mod:
style: |
ha-card {
box-shadow: none;
background: none;
}
1 Like
Info yes, but i think he means a “Button” for turn Parental on/of ( and there is no such in the “Trackers” entities), so i think inte that case ( as your lists ) maybe he could use auto-entities, but im sure he dont want to sit and click/choose individual Buttons every now and then … so im pretty sure his only option is Automation/Automations ( And i.e groups )
1 Like
Hi, Yevhenii!
Thanks for your amazing work!
I am running HA core 2022.11.5. I installed AsusRouter via HACS (v 1.29.1), and I am wondering why I am stuck at version 0.14.3 when you already released 0.17.4. It’s not particularly critical for me, but I thought I ask. Is the HACS repository running behind? (Or are you just “too fast” releasing new versions?)
When I was digging around, I found that on top of the AsusRouter page in HACS, there is a button supposedly pointing to the new release. However, this button actually points to https://raw.githubusercontent.com/Vaskivskyi/ha-asusrouter/releases, which leads to a 400: invalid request error in my case. Could this possibly have anything to do with it?
I thought it was worth reporting that when I was running both AsusWRT and AsusRouter at the same time, it made my AC68P router crash pretty frequently. (Like more than once per day.) What happened was that the router apparently ran out of memory (could not allocate memory errors in the router log), even though the RAM was somewhere in the 70% range. Restarting the router got it going again, but only for so many hours.
I removed AsusWRT, and now it’s running stably, using somewhere like 56-62% RAM.
Of course, you could ask why I would do such a thing and run both AsusWRT and AsusRouter at the same time. Answer is that I was simply testing them simultaneously to figure out which one I would like more. Well, apparently, that’s not a great idea, and I thought I share this here so that others don’t make the same mistake.
Hehe, i can’t tell for sure, but yes i also lately seen info in regards to an update, but seen no update-info in my HA … HACCS / Integration , at the 3 dots, you’ll also see " Re download " , that give you the latest ver.
Disable the other … or in fact, uninstall AsusWrt 
( I i did the same " disabled " AsusWrt until i decided to remove it )
Hello,
Versions up to 0.16.1 are available for HA version 2022.11.5 which you have. Versions 0.17.0+ are only for HA 2023.1.0+
That is strange that your HACS does not show any updates. Might be you actually need to reload HACS integration if it has stuck
Ah, thanks so much!
Well, I did the “redownload” thing, but then got an error message “You are running Home Assistant version '2022.11.5', but this repository requires minimum version '2023.1.0' to be installed.”
Well, that explains it! I will wait a few more days, until things around the new 2023.1 release have settled.