Skip to content

Update DNS-SD servicetype to 's2connect' #63

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

Merged
wcoenraads merged 1 commit into from
Mar 10, 2026
Merged

Update DNS-SD servicetype to 's2connect' #63

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions website/docs/communication-layer/discovery-pairing-authentication.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -351,11 +351,11 @@ DNS-SD is used for automatically discover S2 nodes from an S2 node that is deplo
* To advertise a [long polling endpoint](#long-polling) so other initiator S2 nodes in the LAN could connect to this S2 node
* To discover an S2 node of which the RM is deployed in the WAN, but that also has a presence in the LAN.

S2 uses the service type `s2emp` (short for S2 Energy Management Protocol) and exclusively uses tcp, since it is an HTTP based protocol. S2 uses the following DNS-SD values:
S2 uses the service type `s2connect` and exclusively uses tcp, since it is an HTTP based protocol. S2 uses the following DNS-SD values:

| DNS-SD property | Value for S2 |
| --- | --- |
| Service type | `_s2emp` |
| Service type | `_s2connect` |
| Protocol | `_tcp` |
| Port | No fixed port, decision is up to the implementation |
| Subtypes | `_cem` and `_rm` |
Expand Down Expand Up @@ -390,11 +390,11 @@ The receiver of the service description **must** use the URL provided in the TXT

> Scanning for S2 endpoints could for example be done using the following [avahi](https://avahi.org/) command:
>
> `avahi-browse -r _s2emp._tcp`
> `avahi-browse -r _s2connect._tcp`
>
> Registering an S2 endpoint could for example be done using the folling avahi command:
>
> `avahi-publish-service -s "EVSE1038" _s2emp._tcp 443 "txtvers=1" "e_name=brand" "deployment=LAN" "pairingUrl=https://EVSE1038.local:443/pairing/" --sub _rm._sub._s2emp._tcp`
> `avahi-publish-service -s "EVSE1038" _s2connect._tcp 443 "txtvers=1" "e_name=brand" "deployment=LAN" "pairingUrl=https://EVSE1038.local:443/pairing/" --sub _rm._sub._s2connect._tcp`

## The pairing token, the pairing S2 node ID and the pairing code

Expand Down