-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Possibility to add sensorname prefix #3
Comments
I use this to monitor multiple machines myself and it organizes sensors into devices, not just entities. When you create automations you can select the appropriate machine device name then select the sensor (assuming you use the GUI). Does that work for you? |
Ah great. I would still prefer to reflect the machine name in the entity name, but I would be fine with the devices. Where are they organised as devices? In MQTT there is a device with the host name, but it there are no entities associated with that device. |
Go to the Devices tab and you should see a unique device for each machine. |
I found it, thank you very much. |
I successfully adapted your code to include sensor name prefixes. Are you open to pull requests or should I keep the code for myself? |
Sure, please do and I'll review. I may want to do it a little different though |
It would be great to add the possibility to add a prefix to the entity names of the sensors. I will install this on more than one machine and it would be terrible if I had to change every single sensor in home assistant. Here is a config option which lets one choose to set a prefix:
And here is a function which checks if the option is set and runs itself:
The variable
SENSOR_PREFIX
would have to be added to the sensor names.I am not good at programming, and I am not yet very familiarly with this awesome program, that is why I didn't create a pull request. For example, I don't know if it is common to define a function and then run it immediately afterwards. If I can help in anyway, please say so.
The text was updated successfully, but these errors were encountered: