Hi,
We are providing HbbTV services for some TV broadcasters in Turkey. In our HbbTV application, we generate a unique device id and store this data on the device both in a cookie and on local storage. Additionally we store the opt-in choice of the user as well. But on some older devices (especaially with Tizen 4.0), the data we have stored is lost and the TV device generates new device ids and asks the user’s opt-in choice repeatedly. When we check the logs at the backend, we see that more than hundred deviceids have been generated with the same remote IP (the same TV Device) in 24 hours.
Also when we check the user agent string , we see that it is not static. There is a suffix at the end “VID/” and the numbers are incrementing.
2025-06-09 01:25:07 HbbTV/1.2.1 ( DRM;Samsung;SmartTV2018;T-KTM2LDEUC-1341.2;KantM2_LITE;) Tizen/4.0 ( TVPLUS SmartHubLink 360avc) Chrome/56 VID/1
2025-06-09 01:26:32 HbbTV/1.2.1 ( DRM;Samsung;SmartTV2018;T-KTM2LDEUC-1341.2;KantM2_LITE;) Tizen/4.0 ( TVPLUS SmartHubLink 360avc) Chrome/56 VID/3
2025-06-09 01:26:42 HbbTV/1.2.1 ( DRM;Samsung;SmartTV2018;T-KTM2LDEUC-1341.2;KantM2_LITE;) Tizen/4.0 ( TVPLUS SmartHubLink 360avc) Chrome/56 VID/4
2025-06-09 01:27:16 HbbTV/1.2.1 ( DRM;Samsung;SmartTV2018;T-KTM2LDEUC-1341.2;KantM2_LITE;) Tizen/4.0 ( TVPLUS SmartHubLink 360avc) Chrome/56 VID/6
2025-06-09 01:27:51 HbbTV/1.2.1 ( DRM;Samsung;SmartTV2018;T-KTM2LDEUC-1341.2;KantM2_LITE;) Tizen/4.0 ( TVPLUS SmartHubLink 360avc) Chrome/56 VID/7
2025-06-09 01:28:13 HbbTV/1.2.1 ( DRM;Samsung;SmartTV2018;T-KTM2LDEUC-1341.2;KantM2_LITE;) Tizen/4.0 ( TVPLUS SmartHubLink 360avc) Chrome/56 VID/8
To be able to implement the opt-in flow without disturbing the viewer, we should be able to store our data persistently on the device.
How can we handle the situation?
Best regards,