Hello,
We have FMS500 and FMS500 lite devices and they are visible but the last data transmission is from 4 Jan 2025.
This is the explanation of the manufacturer
Our existing communication/telemetry protocol (“BCE simple communication protocol”) that impacts FM-500 & FMS500 series devices (https://docs.google.com/document/d/1TZCsx4zYiEj6JWrDRXx-tK3We_9YaCQzyWoF-gmO8lk/edit) has a custom TIME format that is meant to overflow 28bits on Sat Jan 04 2025 18:48:30 GMT+0000.
Customers, that have direct integration of this protocol in their own backend services, need to make the following changes to avoid device data registration issues due to incorrect timestamp after January 4th, 2025:
Example of time conversion: Time before conversion: 1199158468, 03:34:28 01/01/2008 → Time after conversion: 1736029378, 22:22:58 04/01/2025
Can you help us solve this issue?
We checked now but the it still shows last data transmission from 4.01.2025
Have you tried the preview version?
We have not. Can you send me a link for it?
It's working on the preview version!
Thank you!
Hello,
We have FMS500 and FMS500 lite devices and they are visible but the last data transmission is from 4 Jan 2025.
This is the explanation of the manufacturer
Our existing communication/telemetry protocol (“BCE simple communication protocol”) that impacts FM-500 & FMS500 series devices (https://docs.google.com/document/d/1TZCsx4zYiEj6JWrDRXx-tK3We_9YaCQzyWoF-gmO8lk/edit) has a custom TIME format that is meant to overflow 28bits on Sat Jan 04 2025 18:48:30 GMT+0000.
Customers, that have direct integration of this protocol in their own backend services, need to make the following changes to avoid device data registration issues due to incorrect timestamp after January 4th, 2025:
Example of time conversion: Time before conversion: 1199158468, 03:34:28 01/01/2008 → Time after conversion: 1736029378, 22:22:58 04/01/2025
Can you help us solve this issue?