2nd Pid Controller will not work

Hi,
today I have installed a 2nd Pid-Controller on my installation.

The first one is working for a while ( used for heating in the kitchen). No I will use a 2nd one in the living room.
I created a 2nd rule from the ui with a PID-Controller. The setup is the same as for the first one.

The rule with the controller itself seems to work, But after changing the setpoint, the Reset command is not working.

Here is my setup from the working one:

configuration: {}
triggers:
  - id: 19fc1495-36b4-49a7-9a2c-2dc132bd4a69
    label: PID Controller Trigger
    configuration:
      iInspector: KUET_iInspector
      setpoint: KUET_SetPoint_Heat
      kp: 65
      pInspector: KUET_pInspector
      kdTimeConstant: 0
      dInspector: KUET_dInspector
      input: KUAQ_T_Temperature
      eInspector: KUET_eInspector
      kd: 0
      commandItem: KUET_PidCommandItem
      ki: 0.4
      loopTime: 60000
    type: pidcontroller.trigger
conditions: []
actions:
  - inputs: {}
    id: "1"
    configuration:
      itemName: KU_Pid_out
    type: core.ItemCommandAction

and here a part of the loggfile after changing the setpoint

2023-12-27 10:39:52.696 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'KUET_PidCommandItem' received command RESET
2023-12-27 10:39:52.700 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'KUET_PidCommandItem' changed from NULL to RESET
2023-12-27 10:39:52.703 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'KUET_PidCommandItem' changed from RESET to NULL
2023-12-27 10:39:52.713 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'KUET_Th_Valve_Position' received command 33
2023-12-27 10:39:52.714 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'KUET_Th_Valve_Position' predicted to become 33
2023-12-27 10:39:52.720 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'KUET_Th_Valve_Position' changed from 0 to 33

So the Rule/controller changes the reset back to Null after doing something.

Here is the setup from the second:

configuration: {}
triggers:
  - id: b5633be2-6c6e-4921-8cf9-c0166d64c544
    label: PID Controller Trigger
    configuration:
      setpoint: WZET_SetPoint_Heat
      iInspector: WZ_iInspector
      kp: 65
      pInspector: WZ_pInspector
      kdTimeConstant: 0
      dInspector: WZ_dInspector
      input: WZAQ_T_Temperature
      eInspector: WZ_eInspector
      kd: 0
      commandItem: WZ_PidCommandItem
      ki: 0.4
      loopTime: 60000
    type: pidcontroller.trigger
conditions: []
actions:
  - inputs: {}
    id: "1"
    configuration:
      itemName: WZ_Pid_Out
    type: core.ItemCommandAction

and here the log part

2023-12-27 10:41:01.128 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'WZ_PidCommandItem' received command RESET
2023-12-27 10:41:01.800 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'WZET_SetPoint_Heat' received command 19
2023-12-27 10:41:01.805 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'WZET_SetPoint_Heat' changed from 1 to 19
2023-12-27 10:41:01.817 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'WZ_Pid_Out' received command -5779.189222333376
2023-12-27 10:41:01.820 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'WZ_pInspector' changed from -1123.2 to 46.799999999999926
2023-12-27 10:41:01.824 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'WZ_iInspector' changed from -5825.9928271333765 to -5825.989222333376
2023-12-27 10:41:01.827 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'WZ_eInspector' changed from -17.28 to 0.7199999999999989

here you can see that the controller item received the reset, but did not change it back to null as on the working one.

I compared all items needed for this rules. On both the rule to sent a reset is working, because we can see the reset in the logging.
But I did not do any reset.

Has someone an idea wht’s going wrong, or where can I debug something?

Ok, solved the problem by myself. A restart of the openhab service solved the problem. After that both pid controller instances were working.