-
-
Notifications
You must be signed in to change notification settings - Fork 30.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add HTTP(s) protocol support to Asuswrt #71899
Conversation
Hey there @kennedyshead, mind taking a look at this pull request as it has been labeled with an integration ( |
"""Return a dictionary of available sensors for this bridge.""" | ||
|
||
|
||
class AsusWrtLegacyBridge(AsusWrtBridge): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be removed, there is no real point in dividing into 2 versions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And when doing that also remove me as code-owner would be good. (moved on from hass)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My idea was to maintain both considering the variety of routers in circulation. Can we wait for other opinions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My idea was to maintain both considering the variety of routers in circulation. Can we wait for other opinions?
... Could't "commend out" or "strike-through" this, but i finally got it up and running, everything works as expected(from what i can see) ... i apologize for my inpatient nature, but im to old to deal with that :)
.........
If you want "assistant" in troubleshooting your "proposed" actions to verify
https://github.com/ollo69/ha_asuswrt_custom/tree/master/custom_components/asuswrt_custom , you better "shoot when the powder is dry" ... im currently without device-tracking and all, as i installed asuswrt_custom, and nothing works, hour ago today i had both ASUSWRT AND AsusRouter integrations working , so i might run out of patience, or time for testing/playing around :)
....
PS: Im still available (for testing purposes) just to justify my conscience :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
... Could't "commend out" or "strike-through" this, but i finally got it up and running, everything works as expected(from what i can see) ... i apologize for my inpatient nature, but im to old to deal with that :)
Never mind, good to know that this work for you. Any suggestion that may come using this implementation are welcome👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have just finished "evaluate" Asus_Router-Custom integration, and i fall back to ASUSWRT, Would be great if You could bring this Integration upto-date, and maybe as you mentioned in "#72591" ADD a few more sensors.
What first come to my mind, was (beside WAN_IP-Sensor) also Router-uptime.sensor
HA " UPnP/IGD " Core-Integration, include these 2 sensors, but from a usage-perspective would it be great if we don't have to use 2 different Core-Integrations, to get info's from the Router
Personally im not interested in DL/UL-Total or Speed etc., But essential info and "Tracking" initially, And using only 1 integration for this :)
As of now i have to use ASUSWRT for it's "Tracker" and "Connected Devices" AND UPnP/IGD, for "RouterUptime" and "WAN_IP"
f3a57e3
to
c1d260b
Compare
c1d260b
to
461d1d6
Compare
b8e05a8
to
79593c1
Compare
79593c1
to
d04e5bb
Compare
aa70cab
to
fdb9649
Compare
fdb9649
to
96378c6
Compare
@ollo69 does this PR need further review? |
PR must be approved (and merged) by HA dev team. |
96378c6
to
d69af6a
Compare
d69af6a
to
2a18047
Compare
@frenck can this be added into the next minor or major release? |
@kennedyshead can you approve / merge this PR if everything looks ok? |
PR must be reviewed by HA teams member and only them can merge PR in dev branch. |
db2c361
to
be1f862
Compare
Pinging @frenck again to see we can get this merged soon |
Please don't ping for reviews. As a matter of fact, I personally skip PRs asking for it (to prevent pinging from actually working). There is a large queue of PRs to review. If you want things to go faster, please, join in helping out by reviewing the queues. ../Frenck |
220d760
to
4d00beb
Compare
8b12bf1
to
f997aaf
Compare
30e7111
to
1e8b926
Compare
I put this PR in draft waiting for review of PR #84152 |
I close this PR, replaced by PR #95720 |
Proposed change
This PR add the support to
HTTP
andHTTPS
protocols to AsusWRT integration using this library.HTTP protocol is the same used by the
ASUS Router
phone app provided by Asus, so potentially all devices that work with the application should be supported. This protocol in my tests is more reliable in device presence detection, and it also have the advantage to require less information for configuration, and therefore simplifies the initial and option config flows.Sensors for the moment are limited to
Download
,Upload
and related speeds, more sensors are available but I will leave this for future PR.Support to existing
SSH
andTELNET
protocol is maintained for compatibility, and config flow requests additional parameter in a second step only when one of this protocols are selected.Type of change
Additional information
Checklist
black --fast homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests: