Fixes

1. Memory leak on content proxy server in TelemetryTV [ENG-2903]- Resolved a memory optimization issue within the Content Proxy service. This fix prevents potential performance degradation over time and improves overall system stability.

Features and Changes

1. Support Device Identifier Macros in VAST URL Requests [ENG-2843] -We have upgraded our VAST ad integration to support Device Identifier Macros. Previously, ad requests were identical across all screens, making it difficult for ad partners to track specific devices.

   With this update, you can now inject dynamic placeholders (such as device.serial_number, device.id or device.asset_id) directly into your VAST URLs. When an ad request is made, TelemetryTV automatically resolves these macros to the specific device's details.

   For example:

   • Example Configuration: https://adserver.com/vast?device_id={{device.serial_number}}

     • Resulting Request: https://adserver.com/vast?device_id=SN123456789

Fixes

1. Fix Duplicate Device Notification [ENG-2600]- Resolved an issue that caused duplicate notifications to be sent when a device went offline. Users will now receive a single, accurate notification per offline event.

Features and Changes

1. Yahoo Stock APP returns 500 [ENG-1595] - The Yahoo Stock app was encountering errors, preventing stock information from displaying. To resolve this, a different stock app is being used to utilize a new, reliable data source, ensuring stock information displays correctly again.
2. Implement VAST Tracking Support (Impressions, Errors, and Events [ENG-2617] - Added support for VAST tracking events, error, and click tracking elements. The player now automatically communicates ad impressions, playback progress, and errors to third-party ad servers, ensuring your ad partners receive accurate performance data.

Fixes

1. Overrides Not Hiding When CAP Trigger URL is Invalid or Empty [ENG-2151] - When a CAP Trigger URL returned an empty feed or invalid data, Overrides remained displayed on players even when they shouldn't have been. The Admin Settings logs showed no errors, leaving users with no way to diagnose why their CAP-triggered Overrides weren't working correctly. The system lacked validation to determine whether a CAP URL was providing valid data.

   We've improved how the platform handles invalid or empty CAP (Common Alerting Protocol) Trigger URLs for Overrides. The system now validates CAP feeds and provides clear feedback when issues occur.

2. [TelemetryTV] Ad Campaigns - Not Exporting All Bug [ENG-2245] ixed a bug affecting the "Export All Campaigns" feature where the export process would fail to complete for some users. The export function now runs successfully and includes all advertising campaigns.

Fixes

1. Duplicate asset_id when selecting devices [ENG-2546] - We have resolved an issue where users encountered errors when selecting a device if a duplicate asset_id was assigned through Google Admin or TelemetryTV. This update removes uniqueness validation for asset_id during device updates, allowing duplicate IDs within the same account.

Features and Changes

1. Support for Asset ID on All Device Types[ENG-1448] – An editable Asset ID field has been added for all non-ChromeOS devices, allowing administrators to manage unique identifiers directly within the Device Management page. Previously, only ChromeOS devices supported Asset IDs (managed through Google Admin).
   1. The Asset ID field is now available for Android and other non-ChromeOS devices.
   2. Users with access to devices can manually assign or modify Asset IDs through the Administrator Interface by selecting a device and editing its settings.
   3. This enhancement enables additional device identifiers.
   4. Note: This update does not affect ChromeOS devices or their existing Google Admin Asset ID integration.

Fixes

1. Inaccurate media file counts[ENG-2091] - Some accounts displayed incorrect media counts, causing them to hit the media limit even though they had fewer items uploaded. This was due to inaccurate playlist association data in the media repository, which inflated the total count. The calculation logic has been updated to correctly reflect each media item’s actual usage, ensuring that all media counts now accurately match the number of uploaded files within account limits.
2. Ad Campaign “Export All”[ENG-2245] - The “Export All” feature for ad campaigns was failing to complete due to timeouts. The export query and timeout threshold have been optimized to ensure that full ad campaign exports now complete successfully. This fix applies only to the “Export All” functionality and does not affect other export features.
3. Improved Validation and Logging for CAP Trigger URLs[ENG-2151] - Previously, TelemetryTV allowed non-CAP protocol URLs to be entered when configuring CAP Trigger Overrides. These invalid URLs were accepted without clear error messages, which could cause unexpected display behavior. CAP Trigger URLs are now properly validated to ensure only valid CAP feeds are accepted. In addition, the Admin App’s Settings log area now provides detailed error messages when CAP data retrieval or parsing fails, giving administrators clearer insight into any issues.

Features and Changes

1. Ad Campaign Macro Download (ENG-1146) - We have added the ability to download all ad campaigns with a single button, for customers who have many add campaigns and currently need to download them one at a time. Adding them all at once saves time and is more efficient. Now all ad campaigns are downloaded at once as separate .CSV files.
2. Offline Device Notifications (ENG-1143 - We have improved the notification system to notify users of their organization or other organizations if devices go offline for an extended period of time. Previously the device notification system could only be enabled on the device level. Notifications were sent each time a device went offline for more than 60s. Notifications were only able to send all notifications or send none for each notification method and there was no delineation per device or organization.
   The current notification system was not typically working well for deployments at scale. Users now have the ability to change the time interval for:
   1. How long a device is offline
   2. When a notification is sent out (24 hours)
   3. The ability to set recipients of notifications per device organization or per device
3. Tap Interaction (ENG-1144) - Previously it was not possible to trigger tap interactions using a mouse click or remote selection. We have updated the system to allow "Tap Interaction" to be triggered on devices by clicking with a mouse or selecting using a remote. It is now possible to trigger tap interaction with a mouse click or with a remote.
4. Device Report Export Improvements (ENG-1121) - Improvements are required to the Device Export Feature to capture more information from devices on customer's accounts. Currently the Device Report Export supports the following fields:
   • ID
   • Asset ID
   • Name
   • Status
   • Last Seen
   • Location
   • Playlist
   • Screen Orientation
   • Network SSID
   • Description
   • Errors
     These fields are helpful, but more information is needed that can be used for health monitoring and troubleshooting purposes. We have added the following fields to Device Report Feature:
   • System Information
   • Operating system
   • TelemetryTV Player Implementation/ API Enabled (PWA, Electron, Android Play Store, or Side Load)
   • Browser used
   • Device Model
   • Device Serial Number
   • Versioning Information
   • Operating system
   • Player
   • App
   • Browser
   • Cache Quota Information
   • Connection Type
   • Network SSID

Fixes

1. Device Notification Webhooks (ENG-1770) - There were two issues that could occur around device notifications:
   1. It was possible to have no offline notification generated when a device went offline.
   2. It was possible to have an offline notification generate when a device was still online.\
      
      Both of these conditions have been fixed in our latest release so that if a device goes offline, then an offline notification is always triggered, and it is not possible to get a false offline notification when a device is still online.

Features and Changes

1. Webhook URL Character Limit (ENG-1848) - Previously the character limit was 255 for the Webhook Notification field. The character limit has now been expanded to 350 characters.

Fixes

1. Uploader Only Permission Broken (ENG-1339) - When you created a with "Uploader only" permissions, you should have been able to select the folder and upload your media. Instead it was not possible to upload media at all. This has been fixed and now you can select the folder and upload media as required.

Fixes

1. Upload Failures for PDF, PPT, and PPTX Files Over 30KB[ENG-1423] - File uploads larger than 30KB (PDF, PPT, and PPTX) could fail due to a misconfigured timer. Files under 30KB were unaffected. This issue has now been resolved. The upload timer has been corrected, and larger files upload as expected.
   Maximum file size: 20MB for images, and 1GB for other file types. Due to the conversion process these limits may vary slightly.
2. Shared Counter "Delete button"[ENG-1430] - In the Web Application, attempting to delete shared counters using the Delete/Trash icon had no effect. Shared counters can now be deleted as intended using the Delete/Trash icon.
3. Delete Button Not Working in Menu App[ENG-1431] -In the Menu App, the Delete/Trash button did not work for administrators or regular users. It was not possible to delete Categories, Columns, or Items—though Prices under each Item could still be removed. All elements in the Menu App—Categories, Columns, Items, and Prices—can now be deleted as intended.

Features and Changes

1. Override API: Improve CAP Trigger Error Message[ENG-761] - TelemetryTV has improved how CAP (Common Alerting Protocol) Trigger errors are reported in logs. Previously, error messages were sometimes misleading or lacked actionable guidance. Now, the exact error code is displayed, and the error messages include troubleshooting steps.
   1. Accurate Error Codes: The correct HTTP error code is now shown. For example, a 404 error will display as 404 instead of a generic message.
   2. More Informative Error Messages: Each error message includes clear troubleshooting guidance.
   3. Automatic Deactivation: If a CAP Trigger link is broken, the trigger is automatically marked as inactive.
      Updated Error Messages

    The logs (accessible in Settings) now display improved messages:

    If your CAP Trigger is inactive, check the logs for error details and follow the suggested actions. Once the issue is  
    resolved, you can reactivate the trigger as needed.

2. Disable Playback Reporting Option[ENG-786] - We have introduced a new "Disable Playback Reporting" option, allowing you to turn off playback reporting on a per-device basis. This feature helps reduce bandwidth usage for devices where playback reporting is not required.
   1. Playback Reporting Defaults to Enabled – Ensuring normal functionality unless manually disabled.
   2. Configurable for one Device or many – Apply settings to individual devices or multiple devices at once.
   3. Device Defaults Support – Set this option as the default behavior for new devices.
   4. Accessible Under Settings → Properties
3. Share Media Folder With Affiliates[ENG-932] - We have added a new "Share with Affiliates" option for media folders, allowing resellers to share content with their affiliated accounts in a read-only mode. This ensures that affiliates can access shared media without the ability to modify, add, or remove files.
4. User Permissions: Media File Download Feature Request[ENG-956] - TelemetryTV has introduced a new permission setting that allows administrators to restrict certain user groups from downloading media files. This feature is designed to protect media assets by preventing unauthorized downloads, especially for third-party users who have access to an account.
   New "Restrict Media Download" Permission - Prevents specific user groups from downloading media files. Also removes their ability to replace media files.
   Applies to User Groups with:
   • View Access – Users can see media but cannot download.
   • Edit Access – Users can modify media but cannot download or replace files.
5. Device Report Export Improvements[ENG-1121] - We have enhanced the Device Report Export feature, adding critical system, versioning, and cache information to help customers and support teams with health monitoring and troubleshooting.
   Currently the Device Report Export supports the following fields:
   • ID
   • Asset ID
   • Name
   • Status
   • Last Seen
   • Location
   • Playlist
   • Screen Orientation
   • Network SSID
   • Description
   • Errors

We have added more fields to give more information for health monitoring and troubleshooting. These are:

• System Information
• Operating system
• TelemetryTV Player Implementation/ API Enabled (PWA, Electron, Android Play Store, or Side Load)
• Browser used
• Device Model
• Device Serial Number
• Versioning Information
• Operating system
• Player
• App
• Browser
• Cache Quota Information
• Connection Type
• Network SSID

6. Keep Users Logged in upon Account Creation[ENG-1228] - It was possible that a newly created account would not be returned to the login page. Now anytime a new account is created, it is then returned to the login page.
7. Implement "My Details"[ENG-1244] - We have added the "My Details" page, allowing you to update personal information, change your password, and manage account security and connected services.
8. Sync Media UI with Devices[ENG-1345] - We have Implemented data table and sidebar re-usable components for media.
9. SDK Not Loading in Simple Editor Type[ENG-1378] - The Simple Editor Webapp was producing a syntax error when trying to preload the SDK. This script has been fixed and the error no longer occurs.

Fixes

1. Investigate Automatic Account Expiry Issue[ENG-1180] - Recent release could cause billing accounts to automatically set to "expired" twice, disrupting their service. Some devices displayed "account expired" messages. Users were unable to access the admin portal. We have changed the way an account can become expired, leaving no way for an account to expire with an active credit card attached to it.
2. Scheduler Conflicting Time Intervals[ENG-1256] - The Scheduler used for billing time operations ran in conflicting time intervals causing subscription issues for a customer. This Scheduler error has been corrected and the time intervals conflict cannot occur anymore.
3. Investigate and Fix Duplicate Device Numbers Issue in Reports[ENG-1346] - We have fixed any duplicate numbers in the Device reports.

Fixes

1. Account Deletion Issue[ENG-1183]
   1. Previously, if an account payment failed three times, the account was marked as cancelled and eventually expired. Under certain conditions, the account and its associated data could be deleted. We have made an update to ensure that accounts will no longer be deleted, regardless of their payment status or billing issues. This change guarantees that no data associated with the account will be lost.