You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment when a sensor needs to be named most are using something like: sensorname_location_x to be able to identify the sensor. As an example suppose you have 2 temperature sensors inside a kitchen area they would be named:
temperature_kitchen_1 temperature_kitchen_2
This could be automated by extending the nameable class to allow a name definition as:
name:
- shortname: temperature
- location: kitchen
- idx: 1
the generated name would be: temperature_kitchen_1 and this would be used in the object_id generation.
This would still allow compatibility with the old definition: name: temperatur_kitchen_1
The new definition would allow applications/reporting to give shortname, location and index information by adding routines: get_name_shortname(), get_name_location() and get_name_id(). As a example use case these is feature request 1171.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
At the moment when a sensor needs to be named most are using something like: sensorname_location_x to be able to identify the sensor. As an example suppose you have 2 temperature sensors inside a kitchen area they would be named:
temperature_kitchen_1
temperature_kitchen_2
This could be automated by extending the nameable class to allow a name definition as:
the generated name would be:
temperature_kitchen_1
and this would be used in theobject_id
generation.This would still allow compatibility with the old definition:
name: temperatur_kitchen_1
The new definition would allow applications/reporting to give shortname, location and index information by adding routines:
get_name_shortname()
,get_name_location()
andget_name_id()
. As a example use case these is feature request 1171.Beta Was this translation helpful? Give feedback.
All reactions