Fork github.com/huin/goupnp to add open-home support
Go to file
2022-11-01 20:02:13 +01:00
cmd refactor: rename go module 2022-11-01 20:02:13 +01:00
dcps refactor: rename go module 2022-11-01 20:02:13 +01:00
example refactor: rename go module 2022-11-01 20:02:13 +01:00
httpu #48: Add local address information 2022-03-22 09:50:46 +00:00
scpd Reorder items in generated source files. 2022-03-13 09:02:29 +00:00
soap Consolidate V1 SOAP type data into the SOAP package. 2022-03-24 19:46:39 +00:00
ssdp refactor: rename go module 2022-11-01 20:02:13 +01:00
v2alpha Add documentation links to service docs. 2022-06-13 18:06:03 +01:00
.gitignore add support for Open Connectivity Foundation DCPs 2022-03-22 18:18:01 +00:00
device.go refactor: rename go module 2022-11-01 20:02:13 +01:00
go.mod refactor: rename go module 2022-11-01 20:02:13 +01:00
go.sum Factor code template into a file. 2022-03-24 19:46:39 +00:00
go.work chore: add go.work and v2alpha/go.mod. 2022-03-24 19:46:39 +00:00
goupnp.go refactor: rename go module 2022-11-01 20:02:13 +01:00
goupnp.sublime-project Add Sublime Text project file. 2018-10-13 13:37:27 +01:00
GUIDE.md Fix inconsistent indents in GUIDE.md examples. 2021-02-21 12:36:27 +00:00
LICENSE Update email address. 2017-08-03 10:08:12 +01:00
Makefile add support for Open Connectivity Foundation DCPs 2022-03-22 18:18:01 +00:00
network.go refactor: rename go module 2022-11-01 20:02:13 +01:00
README.md Add notes about v2alpha. 2022-03-24 19:46:39 +00:00
service_client.go refactor: rename go module 2022-11-01 20:02:13 +01:00
workspace.code-workspace fix: vscode workspace 2022-03-24 21:35:10 +00:00

goupnp is a UPnP client library for Go

Installation

Run go get -u github.com/huin/goupnp.

Documentation

See GUIDE.md for a quick start on the most common use case for this library.

Supported DCPs (you probably want to start with one of these):

  • GoDoc av1 - Client for UPnP Device Control Protocol MediaServer v1 and MediaRenderer v1.
  • GoDoc internetgateway1 - Client for UPnP Device Control Protocol Internet Gateway Device v1.
  • GoDoc internetgateway2 - Client for UPnP Device Control Protocol Internet Gateway Device v2.

Core components:

  • GoDoc (goupnp) core library - contains datastructures and utilities typically used by the implemented DCPs.
  • GoDoc httpu HTTPU implementation, underlies SSDP.
  • GoDoc ssdp SSDP client implementation (simple service discovery protocol) - used to discover UPnP services on a network.
  • GoDoc soap SOAP client implementation (simple object access protocol) - used to communicate with discovered services.

Regenerating dcps generated source code:

  1. Build code generator:

    go get -u github.com/huin/goupnp/cmd/goupnpdcpgen

  2. Regenerate the code:

    go generate ./...

Supporting additional UPnP devices and services:

Supporting additional services is, in the trivial case, simply a matter of adding the service to the dcpMetadata whitelist in cmd/goupnpdcpgen/metadata.go, regenerating the source code (see above), and committing that source code.

However, it would be helpful if anyone needing such a service could test the service against the service they have, and then reporting any trouble encountered as an issue on this project. If it just works, then please report at least minimal working functionality as an issue, and optionally contribute the metadata upstream.

Migrating due to Breaking Changes

  • #40 introduced a breaking change to handling non-utf8 encodings, but removes a heavy dependency on golang.org/x/net with charset encodings. If this breaks your usage of this library, you can return to the old behavior by modifying the exported variable and importing the package yourself:
import (
  "golang.org/x/net/html/charset"
  "github.com/huin/goupnp"
)

func init() {
  // should be modified before goupnp libraries are in use.
  goupnp.CharsetReaderFault = charset.NewReaderLabel
}

v2alpha

The v2alpha subdirectory contains experimental work on a version 2 API. The plan is to eventually create a v2 subdirectory with a stable version of the version 2 API. The v1 API will stay where it currently is.

NOTE:

  • v2alpha will be deleted one day, so don't rely on it always existing.
  • v2alpha will have API breaking changes, even with itself.