v1.5.1

Release v1.5.1

• Fix #358 - Peer reconnect fails if hub timeout before http response is received from cloud. #359

v1.5.0

• Fix memory leak in EventBroker. #351 #353
• Updated dependencies and all zetta-* to v1.0.0

v1.4.0

#332 Fixed #331

v1.3.0

New Features

• HTTP Server: x-forwarded-path accepted by default. #320
• Device: Custom error responses and HTTP status codes for actions. #322

v1.2.0

New Features

• Multiplexed ws event stream includes a filterMultiple option to reduce duplicates messages on multiple topics. #318
• Device queries allowed over multiplexed ws event stream in the format {serverName}/query/{query string}. #318

v1.1.0

New Features

• Peer connect and event websocket connection hooks. #316
• Emit error property on _peer/disconnect when peer connection fails. #317 #312

v1.0.0

Bug Fix

• Added rel["item"] to sub-entities of peer management api. #315

v1.0.0-beta.7

New Features

• Allow x-forwarded-host header to be disabled. #307

Bug Fixes

• Fix issue with a peer named with a Number equivalent greater than Number.MAX_VALUE. #309
• Fix issue server queries when no devices are in server. #297
• Fix issue server queries returning null for devices in registry but not active. #302
• Show better error message when peering fails. #304

v1.0.0-beta.6

New Features

• Multiplex Websockets: Add support for application level pings. #282 Docs
• Support TLS options on http/spdy server. #283 Docs
• Expose .available() on VirtualDevice. #285

Bug Fixes

• Extended character support #272
• Decode hub names correctly when spaces are present. #274
• Efficiently pipe request/response to peer instead of buffering response. #275
• Multiplexed Websockets: Properly return 405 when message type is unrecognized. #281
• VirtualDevice: properly update state from logs event stream. #284

v1.0.0-beta

Beta Release of v1.0.0

This is a big one, going forward with this release we will honor the semantic versioning requirements of no breaking changes until the next major release.

To install through npm you must specify the version because it's only in a beta release. npm install [email protected]

You can test peering with a heroku server we have up. http://zetta-v1-beta.herokuapp.com/

New Features

• Multiplexed websocket streams. #243 Full documentation
  • Allows for multiple event topics per websocket connection.
  • Client enabled limits of receiving only N messages on a specific topic.
  • Wildcard/Regex topics. eg. Detroit/photocell/*/value subscribe to all photocell value streams in Detroit server.
• Peer connection watchdog timer from the initiating side. Server that initiates the peering connection starts a watchdog timer to make sure the socket and zetta cloud server is still connected otherwise disconnects and reconnects. #247

Breaking Changes with < 1.0.0

• We updated a few things in the internal Z2Z protocol which will brake peering to servers not running on >= 1.0.0 #238

Other

• Fixed: zetta properly returning 404 on disconnected peers. #242
• Only throw an error in the default VirtualDevice callback if an error has been provided. #241 Fixes #240.
• Peer management updates. #239