Is the intended use for sensors.yaml to be for ever changing data or can it be used as a placeholder for static data that does not change?
It is not used for data, but to define sensors, and yes, sensor definitions can sometimes change.
I have data from nut on my Pi’s that the integration did not create sensors for. But its data that I’d would still like to have handy. I am familiar with first add the nut add-on and then integration and I have dumped the diagnostics. For whatever reason sensors are not being created. So I thought this might be a way. I just want to have easy and quick access to the s/n’s. So from what I read I thought using sensors.yaml might work for my use case.
I’m not familiar with the nut integration, but sensors.yaml is where you would manually define the sensors
thank you for confirming that. The missing data from nut can be another battle down the road. I am not sure if the nut addon \ integration is in step with the actual software or if its behind a revision or two.