@signageos/front-applet 6.5.2 → 6.5.4

package/CHANGELOG.md

@@ -4,6 +4,21 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
 and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
 
+## [6.5.4] - 2024-05-15
+### Fixed
+- Better description of the serial port options on BrightSign
+- Documentation patch: New section in Applet Basics for the sos.authHash used as unique device identification from Applet
+
+## [6.5.3] - 2024-04-30
+### Fixed
+- Documentation patch: Browser.open() is supported on BrightSign
+- Documentation patch: improved iFrames snippet intro text to be less scary
+- Documentation patch: Added platform-specific details for using streaming on BrightSign and Samsung
+
+## [6.5.2]
+### Added
+- Support for the `rtscts` option for the serial port configuration. This option is used when opening a serial port and determines whether to enable or disable RTS/CTS handshaking.
+
 ## [6.5.1] - 2024-04-08
 ### Fixed
 - Incompatibility with latest changes in MDC implementation
@@ -11,7 +26,6 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 ## [6.5.0] - 2024-03-20
 ### Added
 - Add support for sending MDC commands on Tizen
-- Support for the `rtscts` option for the serial port configuration. This option is used when opening a serial port and determines whether to enable or disable RTS/CTS handshaking.
 
 ## [6.4.2] - 2024-01-26
 ### Fixed

package/docs/applet-basics.md

@@ -26,6 +26,7 @@ This thread contains basic methods of every Applet used to load necessary config
 | `appletVersion`  | Returns current Applet version | JS API `4.5.0`, Front-display `7.8.0`|
 | `config` object  | Returns object with key-values set via Timing or as a bundled config| JS API `1.5.0`, Front-display `6.8.0`|
 | `config` object  | Returns object with key-values set via Timing or as a bundled config| `1.0.0`|
+| `authHash` token  | Returns string with unique device identifier | `1.0.0`|
 | `capabilities`  | Enum of device-specific capabilities and features | `1.0.0`
 
 ## Starting Applet
@@ -176,9 +177,33 @@ console.log(sos.config.imgUrl);
 ```
 
 :::note[Guide]
-[Custom variables in Applet](https://docs.signageos.io/hc/en-us/articles/4405238989458)
+[Custom variables in Applet](https://developers.signageos.io/docs/devspace-extras/env-variables-configuration)
 
-How to pass custom variables and cofiguration to your Applet
+How to pass custom variables and configuration to your Applet.
+:::
+
+## The authHash for unique device identification
+
+The `sos.authHash` is an alternative device identifier designed for secure pairing and locating devices through the REST API.
+
+1. The `authHash` is commonly used as a link between the Applet deployed on the device and the device in device management.
+1. The `authHash` is unique and can be revoked upon request.
+1. The `authHash` can be used as a universal identifier for your Applet application.
+
+The `authHash` can be retrieved from the JS SDK API - it's available as `sos.authHash`. 
+
+```javascript
+async function startApplet() {
+			await sos.onReady();
+      console.log(sos.authHash);
+}
+window.addEventListener('sos.loaded', startApplet);
+```
+
+:::note[Guide]
+[Using authHash for device identification](https://developers.signageos.io/docs/devspace-extras/sos-authhash-device-pairing.md)
+
+How to get `authHash` and use it in the REST API for device identification.
 :::
 
 ## Applet JS API version

package/docs/content/js-browser.md

@@ -33,7 +33,8 @@ Default URL can be opened and even the whitelisting/blacklisting of certain doma
 **With some limitation you can use this API also on**
 - Samsung Tizen (SSSP 4 and above); where the website is just in fullscreen without an address bar or theme options (headless mode)
 - LG webOS (webOS 3.0 and above); where the website is just in fullscreen without an address bar or theme options (headless mode)
-- Raspberry Pi and NEC Compute Module; where the website is just in fullscreen without an address bar or theme options (headless mode)
+- Linux (Fedora, Ubuntu), Raspberry Pi, NEC Compute Module; where the website is just in fullscreen without an address bar or theme options (headless mode)
+- BrightSign; where the website is just in fullscreen without an address bar or theme options (headless mode)
 :::
 
 ### Javascript

package/docs/content/js-iframes.md

@@ -13,7 +13,7 @@ description: "[Content JS API] We **do not recommend** to use iframes inside you
 ---
 
 # Iframes
-We **do not recommend** to use iframes inside your Applet. However, if you have to use it, you can add full support of the sOS JS API to every one of your iframe. Just add the JS snippet script below to every page load in iframe before ending </body>. Everything will be prepared, and you can call the very same methods as described for Applet.
+We **recommend limiting the use of iframes** inside your Applet to avoid performance hiccups. However, if you you are leveraging iframes, you can also add full support of the sOS JS API within the iframe context. Add the JS snippet script below to every page load in iframe before ending </body>. Everything will be prepared, and you can call the very same methods as described for Applet.
 
 :::warning
 The signageOS Snippet and API works **ONLY** if the iframe is served from the display's internal storage - `<iframe src="file://...`. If your iframe is served from a live URL - `<iframe src="https://your-iframe-url"...` the snippet and signageOS API will **NOT** work. This is a security limitation to prevent random site took advantage of the API and alter the display behavior. There is a simple way to [save and load your iframe from the internal storage](https://github.com/signageos/applet-examples/blob/master/examples/content-js-api/iframes). Just make sure you are using full paths in your iframe for linking javascripts and css instead of the relative ones.

package/docs/content/js-serial.md

@@ -89,7 +89,7 @@ Device address is different per platform (at least for now). Kindly find the res
 | Windows | `COM3` | `COM3` (typically, but check your Win machine if this does not work) |
 | Samsung Kiosk | `PORT1` |`PORT1`, `PORT2`, `PORT3` |
 | Android | `/dev/ttyusb0` | `/dev/ttyusb0` |
-| BrightSign | `0` | `0`, `1`, `USB:A/0`
+| BrightSign | `0` | `0` (Serial jack /dev/ttyS0), `1` (GPIO port /dev/ttyS1), `USB:A/0` (USB-to-serial /dev/ttyUSB0) |
 
 ## Serial port methods
 

package/docs/content/js-video-stream.md

@@ -154,8 +154,6 @@ document.documentElement.clientHeight as setup parameters.
 | `autoReconnectInterval` | Number  | <div class="yellow">No</div> | Interval in miliseconds between reconnect attempts  |
 | ^^                      | ^^      |              ^^              | Default value: 30000 ms                             |
 | `volume`                | Number  | <div class="yellow">No</div> | Volume of the stream                                |
-| `trackSelection`        | Object  | <div class="yellow">No</div> | Track selection options                             |
-| `drm`                   | Object  | <div class="yellow">No</div> | DRM options                                         |
 
 ### Javascript syntax
 
@@ -580,3 +578,41 @@ Although we are doing our best, following errors may occur when working with the
 | 51303 | InternalStreamError | Couldn't get stream tracks.                          |
 | 51304 | InternalStreamError | Couldn't select stream track.                        |
 | 51305 | InternalStreamError | Couldn't reset stream track.                         |
+
+## Platform-specific notes
+
+### BrightSign
+
+BrightSign allows the configuration of [buffering](https://support.brightsign.biz/hc/en-us/articles/218067097-Customizing-the-size-of-the-streaming-buffer), [latency and jitter](https://support.brightsign.biz/hc/en-us/articles/218067127-Modifying-the-latency-and-jitter-of-audio-video-streams) by adding additional query parameters to stream `uri`.
+
+#### Buffering
+
+You can modify the default buffer size by appending optional parameters to the end of a streaming URL in a BrightAuthor Video Stream or Audio Stream state (this method also applies to custom scripts). The URL parameters must be formatted as follows:
+
+```
+<streaming_url>?buffersize=<number>&vcdbsize=<number>&acdbsize=<number>
+```
+
+Example: `http://www.example.com/stream1?buffersize=10000000&vcdbsize=10000000&acdbsize=256000`
+
+Note that all buffer sizes are specified in bytes.
+
+buffersize: The size of the main buffer. Once streaming data comes into the main buffer, it is immediately split into the audio and video buffers. The default size of the main buffer is 1.5MB for HD models, 3MB for XD models, and 6MB for 4K models.
+vcdbsize: The size of the video-coded data buffer. The default size of this buffer is 3MB for HD models, 3MB for XD models, and 6MB for 4K models.
+acdbsize: The size of the audio-coded data buffer.  The default size of this buffer is 256KB for all models.
+
+#### Latency and Jitter
+
+You can modify the amount of time it takes for audio/video streams to begin playback by formatting the stream URL as follows: 
+
+```
+<streaming_url>?latency=<value_in_ms>&jitter=<value_in_ms>
+```
+
+Example: `http://www.example.com/stream1?latency=-450&jitter=50`
+
+### Samsung
+
+UDP and RTP streams are only available if you use specific version of signageOS Tizen CoreApp.
+
+Details are documented in Docs: [[Tizen] Stream playback issues & limitation](https://docs.signageos.io/hc/en-us/articles/4405387373458--Tizen-Stream-playback-issues-limitation)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@signageos/front-applet",
-  "version": "6.5.2",
+  "version": "6.5.4",
   "main": "dist/bundle.js",
   "types": "es6/bundle.d.ts",
   "files": [