Show only one page?

[michaelothomas]

I've successfully built a page to show on my pixoo64. However, it's still cycling through old pages? I have a configuration with one page which I have saved multiple times and it appears to be cycling through old versions. Which leads me to believe that there is some fixed number of pages somewhere. But I don't understand how to control this. :/

My config:

- page_type: components
  components:
    - type: image
      position:
        - 0
        - 0
      image_data: >-
        (big blob of data I won't post here)
      resample_mode: box
      height: 64
    - type: text
      content: "Trump: {{ states('sensor.trump') }}%"
      position:
        - 0
        - 20
      font: PICO_8
      color:
        - 204
        - 36
        - 26
    - type: text
      content: "Harris: {{ states('sensor.harris') }}%"
      position:
        - 0
        - 30
      font: PICO_8
      color:
        - 50
        - 85
        - 164

[michaelothomas]

I tried factory resetting my Pixoo64 but it seems HA was holding on to the bad images. Ultimately fixed my problem by uninstalling and reinstalling this integration.

It would be amazing if this integration could give some control over the state it is holding on to? Even a simple reset button somewhere would have saved me a bunch of trouble.

In any case, thanks for making this!

[michaelothomas]

Followup question: is the bug here that the integration should be clearing all state and resetting all timers each time I save a new config?

[michaelothomas]

After watching my Pixoo64 for a day or two I realized the problem was still there. The page changes were just subtle and rare and I wasn't noticing them.

After some debugging, I believe I've found the problem in sensor.py. When the configuration is updated a new instance of Pixoo64 is created but the old instance is kept alive by its update task, which is still running. So you end up with a bunch of instances of Pixoo64 which each have stale copies of the page data. This results in multiple update tasks fighting for who gets to show their page and chaos ensues.

I've fixed the problem by keeping a reference to the Pixoo64 instance and cancelling its update timer before creating the new instance (see code snippet below). I'm not fluent in github, otherwise I'd submit a pull request.

It seems from the comment in async_schedule_next_page that the author believed the update task would be cancelled automatically. It's not clear to me if this was a misunderstanding or if HA's behavior has changed.

_PIXOO64_INSTANCE = None

async def async_setup_entry(hass: HomeAssistant, config_entry: ConfigEntry, async_add_entities):
    global _PIXOO64_INSTANCE
    if _PIXOO64_INSTANCE and _PIXOO64_INSTANCE._update_task:
        _LOGGER.debug("Cancelling pre-existing update task")
        _PIXOO64_INSTANCE._update_task.cancel()

    _PIXOO64_INSTANCE = Pixoo64(config_entry=config_entry, pixoo=hass.data[DOMAIN][config_entry.entry_id]["pixoo"])
    async_add_entities([ _PIXOO64_INSTANCE ], True)

[gickowtf]

@SB2DD hey do you have any time to take care of this?

[SB2DD]

Sure, I’ll take a look!

[SB2DD]

I've successfully been able to reproduce the bug in HA 2024.10.0. I'm creating a PR right now (#89)

[gickowtf]

I have just published it. Thank you