Very likely that you are simply having EMF/EMI/RMI interference issues with the Zigbee Coordinator and/or Zigbee Router, or might also be that you do not Zigbee Router devices within close range in your Zigbee network, so before you do any deeper troubleshooting (as in digging through debug logs) be sure that you are first following these best practise tips → Zigbee networks: how to guide for avoiding interference and optimize for getting better range + coverage
Seen others reported it as working fine after changing the battery and following the community best practice setup guide (at least making sure both using a long USB extension cable to a USB 2.0 port or USB 2.0 hub to avoid interference as well as making sure have enough Zigbee Router devices on the same Zigbee network), so read and make an effort to follow those best practices.
Reference:
- Rodret switch recognised, bind but no battery level or button presses recognised
- IKEA RODRET Dimmer Remote (E2201) - ZHA/Z2M - Control Light
- IKEA RODRET Dimmer Remote (E2201) - ZHA/Z2M - Control anything
- Ikea Rodret dimmer with triple click
- STYRBAR Remote control (x2), tradfri motion sensor stopped working yesterday night
Without looking at any debug logs I would in addition replace that old CC253x (CC2530/CC2531) based Zigbee Coordinator which runs an outdated Zigbee stack (that does not get any newer firmware updates) as it is no longer recommended for ZHA or Zigbee2MQTT. Refer to → https://www.home-assistant.io/integrations/zha#known-working-zigbee-radio-modules and https://www.zigbee2mqtt.io/guide/adapters/
If have issues it is recommended to upgrade Zigbee Coordinator firmware regardless of which radio adapter/model you have, (though if have an older adapter then it is unlikely there are any updates).
I would therefore suggest you begin by migrating to a more modern Zigbe radio adapter with a newer Zigbee Coordinator NCP firmware before troubleshooting that issue any deeper. So suggest you either a Texas Instruments CC2652P or an EFR32MG21 based (preferably with an external antenna like the Sonoff ZBDongle-P or the Sonoff ZBDongle-E, which by the way can both be repurposed as powerful Zigbee Router devices if flashed with alternative firmware). Check out → Zigbee buyer's guide
It is really easy to migrate to a new Zigbee Coordinator radio adapter if using the ZHA integration, see → https://www.home-assistant.io/integrations/zha#migrating-to-a-new-zigbee-coordinator-adapter-inside-zha (though do make sure to create and save a Zigbee network backup before the migration). (Migrating if using Zigbee2MQTT is more work but also doable → https://www.zigbee2mqtt.io/guide/faq/).
If you get the same issue using a newer Zigbee Coordinator with later then you should report it by posting an issue under Home Assistant core repoitory on GitHub with a debug log for diagnostics from the ZHA integration. Read → https://www.home-assistant.io/integrations/zha#reporting-issues
Again, while it might not seem related, it is highly recommended you regardless of the outcome from the above suggestions, do read and try to follow the best practice tips in this community guide linked below (which for example advice always using a long USB extension cable to a USB 2.0 port or USB 2.0 hub as well as making sure have enough “known good” Zigbee Router devices on your Zigbee network):