Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Multiple Network Cards - Selection to listen on specified device #67

Closed
ViP3R76 opened this issue Apr 14, 2021 · 4 comments · Fixed by #184
Closed

Multiple Network Cards - Selection to listen on specified device #67

ViP3R76 opened this issue Apr 14, 2021 · 4 comments · Fixed by #184
Assignees
@DutchmanNL
Labels
dependencies Pull requests that update a dependency file enhancement New feature or request question Further information is requested

Comments

@ViP3R76
Copy link

ViP3R76 commented Apr 14, 2021

Szenario:
Mehrere ETH Karten im System vom Adapter

Auswahl:
Welche Netzwerkkarte soll auf die Auto-Discovery hören, oder Option auf "Listen all".
@ViP3R76 ViP3R76 added the enhancement New feature or request label Apr 14, 2021
@DutchmanNL DutchmanNL added the question Further information is requested label Nov 1, 2023
@DutchmanNL
Copy link
Contributor

ich habe mir die discovery function angeschaut, die unterstützt leider keine binding fuel listening interfaces.
Frage waehre also ob es notwendig ist, wen ja koennte man eventuell etwas mit Filterung machen das er alles oder nur den IP-Range nimmt den man selektiert.

Bitte um Rückmeldung op wünschenswert und waehre auch gut zu wissen warum es implementiert werden sollte da ich allgemein davon ausgehe das man alle esphome devices die sich im netzwerk befinden auch discoveren möchte

Logging habe ich inzwischen optimiert, also wen man z.b. andere devices hat mit anderen password etc kommt die connect/fail Meldung nur noch einmal

@DutchmanNL
Copy link
Contributor

es scheint doch eine Möglichkeit zu geben binding fuel den listener zu machen, werde es bei Gelegenheit testen.implementieren

@ViP3R76
Copy link
Author

ViP3R76 commented Nov 2, 2023

Ja das wäre was. Kann das bei Bedarf auch testen, hab ja aktuell 3x ETH integriert für verschiedene Bereiche.

@DutchmanNL DutchmanNL added the dependencies Pull requests that update a dependency file label Nov 12, 2023
@DutchmanNL
Copy link
Contributor

waiting for dependency to solve auto discovery twocolors/esphome-native-api#23

DutchmanNL pushed a commit that referenced this issue Nov 12, 2023
chore: release v0.5.0-beta.0
f80c9a9 
* (DutchmanNL) Admin interface redesigned to JSON-Config relates #171
* (DutchmanNL) Backend massages implemented to Add/Modify/Delete devices
* (DutchmanNL) Device connection handling and visibility of devices improved
* (DutchmanNL) Auto device discovery temporary disabled due to external bug, relates #175
* (DutchmanNL) Possibility added to exclude IP-Addresses from device discovery, relates #175
* (DutchmanNL) Allow Selection to listen on specific interface or all for device discovery resolves #67
* (DutchmanNL) State implemented to show current connection status (unreachable/disconnected/connected) to improve management of devices
* (DutchmanNL) Several bugfixes, resolves #181 resolves #
@DutchmanNL DutchmanNL mentioned this issue Nov 12, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DutchmanNL DutchmanNL

Labels
dependencies Pull requests that update a dependency file enhancement New feature or request question Further information is requested
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

merge release update from branch to main DrozmotiX/ioBroker.esphome
2 participants
@DutchmanNL @ViP3R76