Please check the following requirements below, please produce the state transition diagram of a UML state machine. Thank you >>>> The system monitors temperature and humidity, entering an emergency mode if these exceed set thresholds. It operates in three states: ON, OFF, or PAUSE. In ON state, a 'shut off' event turns it OFF, ending its operation. If power is lost in ON mode, it shifts to PAUSE, using battery power for 10 minutes before either resuming ON (if power returns) or turning OFF. Initially, ON state starts in IDLE, which can't last over 2 minutes without exiting ON. IDLE transitions to ACTIVE at 6AM if configured, or upon receiving an 'activate' event otherwise. The system reverts to IDLE at 11PM or if 'deactivate' is triggered during ACTIVE. In ACTIVE, a green LED is on, which turns off when exiting ACTIVE. In ACTIVE state, the system starts in CONFIGURING mode to establish temperature and humidity thresholds. If inactive for over 2 minutes in this mode, it beeps and enters ERROR mode. A 'reset' event or detecting a null value in either variable can bring it back to CONFIGURING. During MONITORING, the core function, a 'set' event allows revising the configuration. This adaptability means the system can adjust its settings on the fly without interrupting its primary monitoring tasks. If any configuration is incomplete or null, the system uses ERROR mode as a checkpoint to ensure integrity before resuming operations. In READY mode, the system awaits a temperature threshold value, initiating a sequence: **1. Upon receiving the temperature threshold, the system enters WAIT_FOR_H mode, anticipating the humidity threshold. If a new temperature value is input, it updates and stays in WAIT_FOR_H. Entering the humidity threshold shifts the system to VALIDATING mode. After 5 seconds in VALIDATING, it checks for null values. If a null is found, the system exits CONFIGURING; otherwise, it completes the configuration.** **2. The system allows updating a single threshold during its operation. If the actor updates the temperature threshold without adjusting humidity, they must signal completion with a 'done' event. The system then validates the new temperature threshold as in step 1, without requiring the humidity threshold to be reset or entered again.** In MONITORING mode, the system begins in READING, assessing temperature and humidity to identify if they're within normal or critical ranges. Exceeding thresholds triggers an EMERGENCY mode shift. Post-EMERGENCY, a 'reset' event returns the system to READING, not immediately looping back to EMERGENCY due to anticipated environmental changes. In READING, the system enters an IDLE state, quickly reads environmental data, and within 10 seconds, classifies each reading as normal, medium, or high. The highest status between temperature and humidity dictates the action: medium triggers an orange LED; high triggers a red LED; normal causes no indicator to light. The system then transitions to PROCESSING, resets the LEDs, reassesses the environment after 10 seconds, and repeats the assessment and indicator cycle.