# Defining Custom Sensor Inputs

**URL:** <https://community.ecumaster.com/t/defining-custom-sensor-inputs/3117>\
**Category:** EMU PRO\
**Created:** [January 28, 2025, 10:30pm UTC](https://community.ecumaster.com/t/defining-custom-sensor-inputs/3117 "2025-01-28T22:30:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Slash200](https://dub1.discourse-cdn.com/flex013/user_avatar/community.ecumaster.com/slash200/32/4792_2.png) [@Slash200](https://community.ecumaster.com/u/Slash200)\
**Post date:** [January 28, 2025, 10:30pm UTC](https://community.ecumaster.com/t/defining-custom-sensor-inputs/3117/1 "2025-01-28T22:30:46Z")

</div>

Hello,

Will there be a official way to configure custom sensor inputs in a future version?  
The workaround of defining a custom table and assigning the input to another (default) input to make the configuration and then unassigning it is a bit odd.

(source [Custom input sensor definition](https://community.ecumaster.com/t/custom-input-sensor-definition/914) )

Best regards

---

<div class="post-metadata">

**Author:** ![mkuklis\_ECUMASTER](https://dub1.discourse-cdn.com/flex013/user_avatar/community.ecumaster.com/mkuklis_ecumaster/32/104_2.png) [@mkuklis\_ECUMASTER](https://community.ecumaster.com/u/mkuklis_ECUMASTER)\
**Post date:** [January 29, 2025, 11:36am UTC](https://community.ecumaster.com/t/defining-custom-sensor-inputs/3117/2 "2025-01-29T11:36:37Z")

</div>

Hi,  
It’s waiting on the to-do list.  
The plan is to have a dedicated custom sensor configuration in the Project Tree, allowing custom names for the sensors.

Many features were postponed because of the DI development. Most of that development is done, and we are returning to implementing the more basic features from the list.