Hi,
Due to the license, I would like to inform you that we are evaluating use of IRDB as one source for an IR learning/blaster project.
The project is currently an unnamed prototype. It is an ESP32-based device that can learn IR commands and also send candidate IR commands from known code sources.
A typical use case would be:
- a user has a TV, receiver, AC, etc.
- our backend suggests possible IR commands for that device/function
- the hardware sends one command, for example Volume Up
- the user verifies whether the real device reacted
- if it worked, the command can be saved for that user’s setup
We would prefer to import selected IRDB records into our own backend, convert/cache them in our own normalized format, and preserve clear source attribution, rather than depending on live access to the IRDB repository at runtime.
We would of course include the required IRDB notice/attribution, and if we collect new codes or useful compatibility findings, we would be happy to discuss contributing those back to IRDB.
A couple of questions:
- Is this import/cache/use-from-our-own-backend model acceptable under the IRDB license?
- If the prototype later becomes a commercial product/company, would the same use still be acceptable as long as we follow the attribution/license requirements?
- Since we do not have finished hardware units yet, how should we think about the “up to three fully licensed copies/units” clause?
If this use is not acceptable, no problem, we will skip IRDB as a source.
Thanks for maintaining IRDB. It looks like a very useful resource.
Hi,
Due to the license, I would like to inform you that we are evaluating use of IRDB as one source for an IR learning/blaster project.
The project is currently an unnamed prototype. It is an ESP32-based device that can learn IR commands and also send candidate IR commands from known code sources.
A typical use case would be:
We would prefer to import selected IRDB records into our own backend, convert/cache them in our own normalized format, and preserve clear source attribution, rather than depending on live access to the IRDB repository at runtime.
We would of course include the required IRDB notice/attribution, and if we collect new codes or useful compatibility findings, we would be happy to discuss contributing those back to IRDB.
A couple of questions:
If this use is not acceptable, no problem, we will skip IRDB as a source.
Thanks for maintaining IRDB. It looks like a very useful resource.