The subscriptions-transport-ws protocol is no longer maintained. It's better to have an option to support graphql-ws protocol

You've got me confused. According to https://developer.tibber.com/docs/overview#breaking-websocket-change, it is graphql-ws that is no longer maintained?

Now, connecting to wss://websocket-api.tibber.com/v1-beta/gql/subscriptions using graphql-ws I get:

failed to WebSocket dial: expected handshake response status code 101 but got 503. retry in second... client

Using graphql-transport-ws and

options := &websocket.DialOptions{
	Subprotocols: []string{"graphql-transport-ws"},
	HTTPClient: sc.websocketOptions.HTTPClient,
}

I get:

2022/11/16 19:16:25 {"type":"connection_terminate"} client
2022/11/16 19:16:25 {"type":"connection_init","payload":{"token":"5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE"}} client
2022/11/16 19:16:25 {"id":"869c7de7-eb08-4b1d-93d8-bf747d674bfb","type":"start","payload":{"query":"subscription ($homeId:ID!){liveMeasurement(homeId: $homeId){power,lastMeterConsumption,lastMeterProduction,currentL1,currentL2,currentL3}}","variables":{"homeId":"96a14971-525a-4420-aae9-e5aedaa129ff"}}} client
.2022/11/16 19:16:25 failed to read JSON message: failed to get reader: received close frame: status = StatusCode(4400) and reason = "Invalid message received". Retry connecting... client

which I would read as "connection successful, transfer not".

So I'm wondering: what is missing here and how to proceed?

implement graphql-ws protocol #38

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions