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

feature request: mDNS support #49

Closed
liudger opened this issue Jan 17, 2020 · 21 comments
Closed

feature request: mDNS support #49

liudger opened this issue Jan 17, 2020 · 21 comments

Comments

@liudger
Copy link
Contributor

liudger commented Jan 17, 2020

support for Multicast DNS
This would make the device discoverable and automatically detectable for a home automation platform.
https://en.wikipedia.org/wiki/Multicast_DNS
@fredlcore
Copy link
Owner

Do you have experience with multicast libraries for the Arduino? If you could supply some code snippets including the kind of information you would like to be broadcasted, that would help.

@liudger
Copy link
Contributor Author

liudger commented Jan 17, 2020

I am no Arduino expert, when I am finished with the BSB-Lan integration for Home-Assistant I could take a look. But my only language I know by a tiny bit is Python.

@liudger
Copy link
Contributor Author

liudger commented Jan 17, 2020 •
edited

found this with a quick search. https://gist.github.com/mqu/f8d4f6877703bb39676d68733801871d
the info to send is ip-address, port, device name and maybe mac address to make it unique?
That would be enough for the beginning.

@fredlcore
Copy link
Owner

fredlcore commented Jan 17, 2020 •
edited

It would already help to define what kind of information would be necessary for your task that BSB-LAN would need to provide...
EDIT: Ok, your answer came in before I could post my question ;)...

@fredlcore
Copy link
Owner

The example looks doable, but I wonder which port to use because 8266 sounds more like a demo/example port for the ESP8266. Or can this be choosen freely for your purpose?

@liudger
Copy link
Contributor Author

liudger commented Jan 17, 2020

It should be the port that is defined in BSB_lan_config.h define Port 80
That is what I guess so the client can configure itself and communicate with BSB-Lan

@fredlcore
Copy link
Owner

No, I mean the port that the broadcast is transmitted on (which then contains the ip-address, port, device name and mac address of BSB-LAN). I'm pretty sure that this can't be port 80 because that is reserved for webservers.

@liudger
Copy link
Contributor Author

liudger commented Jan 17, 2020

Than your lucky number would be fine I guess;)

@fredlcore
Copy link
Owner

I think that won't work because the program you want to use this broadcast with expects the broadcast message on a specific port. So when you want to use it with Home Automation, you should be able to identify the port where Home Automation expects the broadcast and then I would use this port as default.

@liudger
Copy link
Contributor Author

liudger commented Jan 17, 2020

From wiki. The default is this it looks like UDP port 5353

Packet structure[edit]
An mDNS message is a multicast UDP packet sent using the following addressing:

IPv4 address 224.0.0.251 or IPv6 address ff02::fb
UDP port 5353
When using Ethernet frames, the standard multicast MAC address 01:00:5E:00:00:FB (for IPv4) or 33:33:00:00:00:FB (for IPv6)[a]

@fredlcore
Copy link
Owner

Ah, thanks, that helps a lot! However, I just found out that the Arduino Ethernet library is not able to send UDP multicast packets, only the ESP could do so. Patches for the Arduino are flying around, but to include these would be futile once people update their libraries...
https://gist.github.com/aallan/9895961

@BudBundi
Copy link
Contributor

BudBundi commented Jun 5, 2020

I found https://github.com/TrippyLighting/EthernetBonjour and the fork https://github.com/arduino-libraries/ArduinoMDNS for mDNS on Arduino

@fredlcore
Copy link
Owner

Thanks, someone in the forum also came up with a solution, I just haven't found the time to implement it...

@hacki11
Copy link
Contributor

hacki11 commented Jan 4, 2021

A more simple approach would be to include the bsblan title in unauthorized html response, too:
Currently:

<!DOCTYPE HTML>
<HTML><HEAD><TITLE>Error</TITLE>
</HEAD> <BODY><H1>401 Unauthorized.</H1></BODY></HTML>

Solution:

<!DOCTYPE HTML>
<HTML><HEAD><TITLE>BSB-LAN Web</TITLE>
</HEAD> <BODY><H1>401 Unauthorized.</H1></BODY></HTML>

Now the device can be detected automatically (at least with iobroker)

@fredlcore
Copy link
Owner

Should it say "BSB-LAN Web" or just "BSB-LAN"?

@hacki11
Copy link
Contributor

hacki11 commented Jan 4, 2021 •
edited

I would prefer the same title as from authorized site. There it is BSB-LAN Web

@fredlcore
Copy link
Owner

I know, I'm just wondering if "BSB-LAN" fits in easier in external systems because this is what people might know. Then I'd change it in all titles.

@rroblik
Copy link

rroblik commented Jan 9, 2021

@fredlcore , @hacki11

does that mean the mDNS option is abandonned ? To my mind that would be the better option to follow. I see the W5500 is compatible for example...

@hacki11
Copy link
Contributor

hacki11 commented Jan 9, 2021

Iobroker also supports detection over mdns and it would be the first choice I think.
But changing the title was low effort for a first solution.

@fredlcore
Copy link
Owner

No, it's not abandoned.

@fredlcore
Copy link
Owner

Implemented now for Ethernet connections. WiFiSpi library somehow creates neverending repeating error messages. Not sure if this is a general issue or a problem of misconfiguration or bug.

fredlcore pushed a commit that referenced this issue Jul 19, 2021
@dukess
Merge pull request #49 from fredlcore/master
1a53534 
Sync with origin
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@BudBundi @liudger @rroblik @hacki11 @fredlcore