[bug] User-created IR-Sets do not appear in the dropdown when creating a new remote, but block creating a new ir-set with the same name

[zucki]

Is there an existing issue for this?

• [X] I have searched the existing issues

Description

I created an ir-set by my own for a new remote in the web-configurator. Later I deleted the remote in the web-configurator as I wanted to re-create the ir-dataset. If I do now want to create a blank dataset with the same name as before, I got an errormsg "Data already exists". But the dataset with the name does not appear in the dropdown list shown when creating a new remote. So I can neither use the already existing set nor creating it again with the same name.

How to Reproduce

1. create a new remote with custom ir dataset in the web-configurator
2. delete the remote in the web-configurator
3. create a new remote
4. create a new ir custom set with the same name as the dataset created in step one

Expected behavior

the already created custom ir dataset should be either appear in the dropdown list of a new remote or there should be a possibility to delete custom ir datasets

System version

v1.0.3

What part of the system affected by the problem?

Web Configurator

Additional context

No response

[martonborzak]

Thanks for the report. We are aware of this and working on a fix already.

[zehnm]

The current web-configurator UI for managing IR is quite basic at the moment. The Core-API already provides more functionality to manage custom IR datasets.

An old custom IR dataset can be selected in the "Add a new IR device" dialog with typing custom or learn in the manufacturer search box and then selecting Custom - learned IR codes:

Yes, not very intuitive at the moment :-)

If you don't mind using manual API calls in the meantime:

Retrieve all custom codesets:

curl 'http://$IP/api/ir/codes/custom?page=1&limit=100' -u 'web-configurator:$PIN'

Delete a codeset (if it's no longer used):

curl --request DELETE 'http://$IP/api/ir/codes/custom/$DEVICE_ID' -u 'web-configurator:$PIN'