Trouble with fibaro flood sensor

Because my zwave stixck (aeon labs 7) has a lot of ‘jammed’ errors, I start looking if a node is causing trouble.
It seems that some sensors do send loads of messages. What mostly works to reduce the amount of messages: exclude the sensor, reset the sensor and include again.
Now I ran into a problem with a fibaro flood sensor. Exclusion is working, but factory reset is not possible.
According to the manual: hold the tmp button until the led is yellow, release the tmp button, push again then the led turns red: done.
BUT the led never comes to yellow. It starts blue, then green, then blue, then green for as long as you hold the tmp button.
Does anyone know how to overcome this problem?
To get an idea of the meassages it sends (after exclusion/inclusion, but without reset)

2024-05-23 21:54:07.599 INFO Z-WAVE: [Node 172] Metadata updated: 49-0-Air temperature
2024-05-23 21:54:07.601 INFO Z-WAVE: [Node 172] Value updated: 49-0-Air temperature 22.3 => 21.7
2024-05-23 21:54:07.772 INFO Z-WAVE: [Node 172] Metadata updated: 49-0-Air temperature
2024-05-23 21:54:07.774 INFO Z-WAVE: [Node 172] Value updated: 49-0-Air temperature 21.7 => 21.7
2024-05-23 21:54:07.954 INFO Z-WAVE: [Node 172] Metadata updated: 49-0-Air temperature
2024-05-23 21:54:07.958 INFO Z-WAVE: [Node 172] Value updated: 49-0-Air temperature 21.7 => 21.7
2024-05-23 21:54:08.307 INFO Z-WAVE: [Node 172] Metadata updated: 49-0-Air temperature
2024-05-23 21:54:08.310 INFO Z-WAVE: [Node 172] Value updated: 49-0-Air temperature 21.7 => 21.7
2024-05-23 21:54:08.486 INFO Z-WAVE: [Node 172] Metadata updated: 49-0-Air temperature
2024-05-23 21:54:08.490 INFO Z-WAVE: [Node 172] Value updated: 49-0-Air temperature 21.7 => 21.7
2024-05-23 21:54:08.805 INFO Z-WAVE: [Node 172] Metadata updated: 49-0-Air temperature
2024-05-23 21:54:08.806 INFO Z-WAVE: [Node 172] Value updated: 49-0-Air temperature 21.7 => 21.7
2024-05-23 21:54:09.089 INFO Z-WAVE: [Node 172] Metadata updated: 49-0-Air temperature
2024-05-23 21:54:09.093 INFO Z-WAVE: [Node 172] Value updated: 49-0-Air temperature 21.7 => 21.7
2024-05-23 21:54:09.166 INFO Z-WAVE: [Node 172] Metadata updated: 49-0-Air temperature
2024-05-23 21:54:09.171 INFO Z-WAVE: [Node 172] Value updated: 49-0-Air temperature 21.7 => 21.7
2024-05-23 21:54:09.189 INFO Z-WAVE: [Node 172] Metadata updated: 49-0-Air temperature
2024-05-23 21:54:09.195 INFO Z-WAVE: [Node 172] Value updated: 49-0-Air temperature 21.7 => 21.7
2024-05-23 21:54:09.285 INFO Z-WAVE: [Node 172] Metadata updated: 49-0-Air temperature
2024-05-23 21:54:09.289 INFO Z-WAVE: [Node 172] Value updated: 49-0-Air temperature 21.7 => 21.7
2024-05-23 21:54:09.312 INFO Z-WAVE: [Node 172] Metadata updated: 49-0-Air temperature
2024-05-23 21:54:09.315 INFO Z-WAVE: [Node 172] Value updated: 49-0-Air temperature 21.7 => 21.7
2024-05-23 21:54:09.393 INFO Z-WAVE: [Node 172] Metadata updated: 49-0-Air temperature
2024-05-23 21:54:09.395 INFO Z-WAVE: [Node 172] Value updated: 49-0-Air temperature 21.7 => 21.7
2024-05-23 21:54:09.475 INFO Z-WAVE: [Node 172] Metadata updated: 49-0-Air temperature
2024-05-23 21:54:09.479 INFO Z-WAVE: [Node 172] Value updated: 49-0-Air temperature 21.7 => 21.7

Look at the parameters for that sensor and set it to interval longer that a couple of hundredths of a second is the obvious but required first step. Or just remove it and throw it away.

Looks like it is set to report on any change. This must stop…