[Bug]: Feed quantity gets reset after HA

[pergolafabio]

What happened ?

Hi, im using an Plaf301 , when i define the cups in this entity :

if i then press the button to feed, 4 cups are served!!
But after HA restart, that entity gets reset back to 1? shouldnt it be sticky?

I also notice another feed entity , its a "number", but i cant enable it, it always gets disabled automatilcy ...
Maybe the number entity is sticky? whats the difference between the select and the number?

below logs when i enable the entity

Relevant log output

2025-11-18 20:53:44.187 WARNING (MainThread) [custom_components.petlibro.devices.feeders.one_rfid_smart_feeder] manual_feed_quantity is None for xxx, setting default to 1.
2025-11-18 20:54:46.279 WARNING (MainThread) [custom_components.petlibro.binary_sensor] Device Petlibro Sale is offline.
2025-11-18 20:54:46.288 WARNING (MainThread) [custom_components.petlibro.number] Feed unit mismatch, reloading integration.

[FeliGoblin]

Heya :)
The Number entity is for other measurement units (other than cups), OR for when you have "Set Manual Feed amount by Portions" enabled in the integration settings.

Neither of them are "sticky", but that's probably something we could implement.
@jjjonesjr33 I need to finish my wiki entry first but I could do this if you like

[pergolafabio]

yes, is you could implement that it would be sticky, thats great, now on every restart i need to change again the amout of cups i want to feed

[C4-Dimitri]

@FeliGoblin, we also need to do this for sensor and stuff too across restarts anyway using RestoreEntity mixin.

This would save us recording false sensor data during startup, as sometimes sensors are currently set to 0 or 1 for example when the API data hasn't been fetched yet.

[jjjonesjr33]

@FeliGoblin

It might make sense for the data not to reset when the integration reloads, but honestly, it’s also useful to see when the data is actually pulled during loading. It does trigger my current automations on restart, which has actually been kind of handy. I could always set up automatic timers to check the devices at set intervals, but… idk. I do see the value in keeping the manual feed settings persistent after a reboot, though. If we go the route of storing data between reboots, we might also need a generic device or sensor for “Last Time Data Polled/Fetched.”

[C4-Dimitri]

“Last Time Data Polled/Fetched.”

Agree, probably best to add.

At a stretch for your current way you could manually trigger after each HA reset using the uptime sensor.

But we should definitely be restoring last values into sensors rather than writing false data to history stats just because API data isn't fetched yet.

[pergolafabio]

Is this being worked one?

Btw, i saw a new firmware for my pet libero one device, 2.0.47

Anyone tried it?

[pergolafabio]

Hi Guys, can the select entities changed so they have the last state restored?

i still need to have this automation :-)

- alias: 'Petlibro change amount of cups'
  initial_state: 'on' 
  trigger:
    - platform: homeassistant
      event: start
  action:
    - action: select.select_option
      data:
        option: ³/₁₂
      target:
        entity_id:
          - select.petlibro_pepe_manual_feed_quantity
          - select.petlibro_sale_manual_feed_quantity

[pergolafabio]

i also see always these when i restart HA:

2026-06-08 19:43:24.039 WARNING (MainThread) [custom_components.petlibro.devices.feeders.one_rfid_smart_feeder] manual_feed_quantity is None for A, setting default to 1.
2026-06-08 19:43:24.043 WARNING (MainThread) [custom_components.petlibro.devices.feeders.one_rfid_smart_feeder] manual_feed_quantity is None for B, setting default to 1.