I cannot find any docs on this, and search only show answers from 2018 or so where they needed a hack with a Python script, template, etc (I hope its no longer that convoluted)
I want only to…
Set state to ON for binary_sensor.front_door_lock_current_status_of_the_door
That sensor exists due to the Zwave integration, but its not used and it never changes, and I have a use for it.
You can override its state in the dev tools, but it will be restored to its true value after a restart. A sensor isn’t normally something that can otherwise be set (it’s a sensor, after all). Why not disable the entity if you don’t need it?
I want an Automation to do it, not manually (dev tools).
I didnt want to create yet-another-helper (I have a ton already)… and if I replace the locks, the newer version locks use that sensor so all I’d need to do it delete the automation I created to set them, and everything would still work as designed.
I understand that it would reset on startup, but that is easily mitigated in the automation
The issue is that you don’t know when it will “reset”… sure it will reset on startup, but there is always a possibility that the integration will set the state at any point in time.
There is no service to set the state of a binary sensor. They are changed by device processes, not automation. Use the input boolean helper, that’s what it is for.