In a template you either need to use states.domain.object.state or states('domain.object') to get the value of the entity’s state. Since you’re doing math, I’d recommend casting the state value to int or float (since typically the state is a string, even if it looks like a number.)
I’ve never used value_template in a numeric_state trigger, but the docs seem to imply it creates a variable named state which is the entity’s state object. If that’s true, then for sensor.humidity_sensor_59 you could (in theory) shorten it to state.state.
Lastly, when turning a light on or off I’d recommend using the light.turn_on and off services (as opposed to the homeassistant services. The homeassistant service will just turn around and make a call to the corresponding light service, so you might as well be more efficient and call the light service directly.)
I am not getting it to fire on. Still verifying whether it is turning off or not properly.
Part of the challenge is that the 4-in-1 sensor doesn’t transmit constant data to maximize battery life so tweaking that as well to help find the sweat spot.