-
Notifications
You must be signed in to change notification settings - Fork 69
Sensor Naming Convention #48
Comments
HI @aFrankLion thanks for your suggestion, I've updated the README. I will leave this 'issue' open so that others can make suggestions on the naming convention if they have ideas. My own thought is just to append 'hue' to the start of the sensor names, so you would get sensor.hue_Living_room_2 for example. |
Perhaps the entity registry be utilised to allow renaming the sensor in homeassistant? |
@aFrankLion I think your suggestion that |
I had the same issue with a sensor named "Dining room" changed to "Dining motion room". |
Depends on #115 |
Can i ask if the issue is still open? I have the same problem.... But i read too late of this issue. |
Stale |
The sensor naming convention in parse_sml() in the file /custom_components/sensor/hue.py works well for the default naming convention of Hue sensors (e.g., Office sensor, Living room sensor) by inserting "motion" into the penultimate position in the name, e.g.:
However, user-defined sensor names can lead to inconsistent and awkward entity_id's in Home Assistant. For example, I had Hue sensors with the following custom names:
These Hue sensor names led to following entity_id's with the current Hue-sensors-HASS naming convention:
The simplest solution may be just to recommend in README.md to use the default Hue naming convention for sensors. A second possible approach is to drop the insertion of "motion" into the Hue sensor name. A third possible approach could involve parsing the current sensor names and cleverly naming them (e.g., does the name contain "sensor" or "motion" already, if so..), though this would be difficult to define to cover all possible names well.
The text was updated successfully, but these errors were encountered: