random and frequent device screen refresh resulting in battery drain

[inyourskull-sketch]

Using Seed studio e1001 device with trmnl firmware v1.6.9 with inker ver 0.3.1.
Devices refresh screen in the most random frequency. 9 mins, 2mins, 1mins.... resulting in battery drain.
API request were set to 900s as well as playlist showing only one screen for duration set to 900s.

Is there way to set the screen refresh rate?

[wojo-o]

Hey, do you only have configured custom widget on screen or other widget like weather or live clock?

[kfattum]

My instance also has this error: in response to a request to /api/display the device receives a random "refresh_rate"
`

[inyourskull-sketch]

Hey, do you only have configured custom widget on screen or other widget like weather or live clock?

Thanks.
On the screen, I have two built-in widget "Date Display" and "Battery Status"
as well as several custom widgets from two data sources set to 900s refresh interval.

[wojo-o]

Thanks for respond. I will look at it and try to find this bug.

[wojo-o]

hey I found it and fix it. there was some issue with dynamic refresh rate for every date connected widget, please let me know if issue is solved on your instances. Thanks for that issue!

[kfattum]

version 3.2. I removed the live clock, set the Duration to 3600 s for the screen in the playlist, and 3600 s for the Data Sources. I added the Static Image, Custom Widgets, Text Block, and Battery Status widgets to the screen. I expected to get a refresh_rate of 3600 (set in the playlist), but I got 900

[inyourskull-sketch]

hey I found it and fix it. there was some issue with dynamic refresh rate for every date connected widget, please let me know if issue is solved on your instances. Thanks for that issue!

Thanks for the quick fix.
I can confirm that the refresh interval is now correctly set to 900 seconds as configured.

[kfattum]

@wojo-o Wait, the issue isn't actually resolved. I set the duration and data sources to 3600s, but the system is still stuck at 900s. It looks like the custom refresh rate is still being overridden. Please reopen this issue.

[wojo-o]

Let me check what is overwriting refresh rate.

[wojo-o]

Hey I just dropped new release please check if problem is solved on your instance.

[kfattum]

The original issue is resolved, thanks!

However, I noticed a minor bug in v3.3. When changing the playlist duration (e.g., 3600 to 3599) or saving a screen in the editor, the system initially sends refresh_rate: 1. This results in unnecessary additional screen refreshes.