Domoticz

Is this normal AutoDiscovery log? Isn't a device supposed to be dicovered only once?
Did a zwave JS UI docker install yesterday. On the JS UI everyhing seems to work fine.
Devices are made on Domoticz site. Switching devices on DZ site does not work. To busy with discovering?

2024-02-13 19:06:56.143 Status: zwave-js-ui MQTT AD: discovered: thermostaatBadkamer (thermostaatBadkamer_battery_islow_1)/thermostaatBadkamer (thermostaatBadkamer_battery_islow_1) (unique_id: zwavejs2mqtt_0xe0d0c0b_80-128-1-isLow)
2024-02-13 19:06:56.245 Status: zwave-js-ui MQTT AD: discovered: thermostaatBadkamer (thermostaatBadkamer_notification_power_management_battery_maintenance_status_2)/thermostaatBadkamer (thermostaatBadkamer_notification_power_management_battery_maintenance_status_2) (unique_id: zwavejs2mqtt_0xe0d0c0b_80-113-2-Power_Management-Battery_maintenance_status)
2024-02-13 19:06:56.346 Status: zwave-js-ui MQTT AD: discovered: thermostaatBadkamer (thermostaatBadkamer_battery_level_2)/thermostaatBadkamer (thermostaatBadkamer_battery_level_2) (unique_id: zwavejs2mqtt_0xe0d0c0b_80-128-2-level)
2024-02-13 19:06:56.447 Status: zwave-js-ui MQTT AD: discovered: thermostaatBadkamer (thermostaatBadkamer_battery_islow_2)/thermostaatBadkamer (thermostaatBadkamer_battery_islow_2) (unique_id: zwavejs2mqtt_0xe0d0c0b_80-128-2-isLow)
2024-02-13 19:06:56.549 Status: zwave-js-ui MQTT AD: discovered: badkamerVloerEnLed (badkamerVloerEnLed_switch)/badkamerVloerEnLed (badkamerVloerEnLed_switch) (unique_id: zwavejs2mqtt_0xe0d0c0b_82-37-0-currentValue)
2024-02-13 19:06:56.650 Status: zwave-js-ui MQTT AD: discovered: badkamerVloerEnLed (badkamerVloerEnLed_temperature_air)/badkamerVloerEnLed (badkamerVloerEnLed_temperature_air) (unique_id: zwavejs2mqtt_0xe0d0c0b_82-49-0-Air_temperature)
2024-02-13 19:06:56.751 Status: zwave-js-ui MQTT AD: discovered: badkamerVloerEnLed (badkamerVloerEnLed_electric_kwh_value)/badkamerVloerEnLed (badkamerVloerEnLed_electric_kwh_value) (unique_id: zwavejs2mqtt_0xe0d0c0b_82-50-0-value-65537)
2024-02-13 19:06:56.853 Status: zwave-js-ui MQTT AD: discovered: badkamerVloerEnLed (badkamerVloerEnLed_electric_w_value)/badkamerVloerEnLed (badkamerVloerEnLed_electric_w_value) (unique_id: zwavejs2mqtt_0xe0d0c0b_82-50-0-value-66049)
2024-02-13 19:06:56.955 Status: zwave-js-ui MQTT AD: discovered: badkamerVloerEnLed (badkamerVloerEnLed_switch_1)/badkamerVloerEnLed (badkamerVloerEnLed_switch_1) (unique_id: zwavejs2mqtt_0xe0d0c0b_82-37-1-currentValue)
2024-02-13 19:06:57.058 Status: zwave-js-ui MQTT AD: discovered: badkamerVloerEnLed (badkamerVloerEnLed_electric_kwh_value_1)/badkamerVloerEnLed (badkamerVloerEnLed_electric_kwh_value_1) (unique_id: zwavejs2mqtt_0xe0d0c0b_82-50-1-value-65537)
2024-02-13 19:06:57.161 Status: zwave-js-ui MQTT AD: discovered: badkamerVloerEnLed (badkamerVloerEnLed_electric_w_value_1)/badkamerVloerEnLed (badkamerVloerEnLed_electric_w_value_1) (unique_id: zwavejs2mqtt_0xe0d0c0b_82-50-1-value-66049)
2024-02-13 19:06:57.263 Status: zwave-js-ui MQTT AD: discovered: badkamerVloerEnLed (badkamerVloerEnLed_switch_2)/badkamerVloerEnLed (badkamerVloerEnLed_switch_2) (unique_id: zwavejs2mqtt_0xe0d0c0b_82-37-2-currentValue)
2024-02-13 19:06:57.365 Status: zwave-js-ui MQTT AD: discovered: badkamerVloerEnLed (badkamerVloerEnLed_electric_kwh_value_2)/badkamerVloerEnLed (badkamerVloerEnLed_electric_kwh_value_2) (unique_id: zwavejs2mqtt_0xe0d0c0b_82-50-2-value-65537)
2024-02-13 19:06:57.468 Status: zwave-js-ui MQTT AD: discovered: badkamerVloerEnLed (badkamerVloerEnLed_electric_w_value_2)/badkamerVloerEnLed (badkamerVloerEnLed_electric_w_value_2) (unique_id: zwavejs2mqtt_0xe0d0c0b_82-50-2-value-66049)
2024-02-13 19:06:57.569 Status: zwave-js-ui MQTT AD: discovered: badkamerVloerEnLed (badkamerVloerEnLed_temperature_air_3)/badkamerVloerEnLed (badkamerVloerEnLed_temperature_air_3) (unique_id: zwavejs2mqtt_0xe0d0c0b_82-49-3-Air_temperature)
2024-02-13 19:06:57.671 Status: zwave-js-ui MQTT AD: discovered: scrBadkamer (scrBadkamer_position)/scrBadkamer (scrBadkamer_position) (unique_id: zwavejs2mqtt_0xe0d0c0b_Node7_position)
2024-02-13 19:06:57.774 Status: zwave-js-ui MQTT AD: discovered: scrBadkamer (scrBadkamer_switch)/scrBadkamer (scrBadkamer_switch) (unique_id: zwavejs2mqtt_0xe0d0c0b_7-37-0-currentValue)
2024-02-13 19:06:57.877 Status: zwave-js-ui MQTT AD: discovered: scrBadkamer (scrBadkamer_electricity_power)/scrBadkamer (scrBadkamer_electricity_power) (unique_id: zwavejs2mqtt_0xe0d0c0b_7-49-0-Power)
2024-02-13 19:06:57.979 Status: zwave-js-ui MQTT AD: discovered: scrBadkamer (scrBadkamer_electric_kwh_value)/scrBadkamer (scrBadkamer_electric_kwh_value) (unique_id: zwavejs2mqtt_0xe0d0c0b_7-50-0-value-65537)
2024-02-13 19:06:58.081 Status: zwave-js-ui MQTT AD: discovered: scrBadkamer (scrBadkamer_electric_w_value)/scrBadkamer (scrBadkamer_electric_w_value) (unique_id: zwavejs2mqtt_0xe0d0c0b_7-50-0-value-66049)
2024-02-13 19:06:58.183 Status: zwave-js-ui MQTT AD: discovered: cvKetel (cvKetel_switch)/cvKetel (cvKetel_switch) (unique_id: zwavejs2mqtt_0xe0d0c0b_13-37-0-currentValue)
2024-02-13 19:06:58.287 Status: zwave-js-ui MQTT AD: discovered: pirTuin (pirTuin_motion)/pirTuin (pirTuin_motion) (unique_id: zwavejs2mqtt_0xe0d0c0b_28-48-0-Motion)
2024-02-13 19:06:58.390 Status: zwave-js-ui MQTT AD: discovered: pirTuin (pirTuin_temperature_air)/pirTuin (pirTuin_temperature_air) (unique_id: zwavejs2mqtt_0xe0d0c0b_28-49-0-Air_temperature)
2024-02-13 19:06:58.492 Status: zwave-js-ui MQTT AD: discovered: pirTuin (pirTuin_illuminance)/pirTuin (pirTuin_illuminance) (unique_id: zwavejs2mqtt_0xe0d0c0b_28-49-0-Illuminance)
2024-02-13 19:06:58.594 Status: zwave-js-ui MQTT AD: discovered: pirTuin (pirTuin_motion_sensor_status)/pirTuin (pirTuin_motion_sensor_status) (unique_id: zwavejs2mqtt_0xe0d0c0b_28-113-0-Home_Security-Motion_sensor_status)
2024-02-13 19:06:58.697 Status: zwave-js-ui MQTT AD: discovered: pirTuin (pirTuin_battery_level)/pirTuin (pirTuin_battery_level) (unique_id: zwavejs2mqtt_0xe0d0c0b_28-128-0-level)
2024-02-13 19:06:58.799 Status: zwave-js-ui MQTT AD: discovered: pirTuin (pirTuin_battery_islow)/pirTuin (pirTuin_battery_islow) (unique_id: zwavejs2mqtt_0xe0d0c0b_28-128-0-isLow)
2024-02-13 19:06:58.902 Status: zwave-js-ui MQTT AD: discovered: muurschakelaarWC (muurschakelaarWC_switch)/muurschakelaarWC (muurschakelaarWC_switch) (unique_id: zwavejs2mqtt_0xe0d0c0b_30-37-0-currentValue)
2024-02-13 19:06:59.004 Status: zwave-js-ui MQTT AD: discovered: zolderMuurSchakelaar (zolderMuurSchakelaar_switch_1)/zolderMuurSchakelaar (zolderMuurSchakelaar_switch_1) (unique_id: zwavejs2mqtt_0xe0d0c0b_62-37-1-currentValue)
2024-02-13 19:06:59.108 Status: zwave-js-ui MQTT AD: discovered: zolderMuurSchakelaar (zolderMuurSchakelaar_switch_2)/zolderMuurSchakelaar (zolderMuurSchakelaar_switch_2) (unique_id: zwavejs2mqtt_0xe0d0c0b_62-37-2-currentValue)
2024-02-13 19:06:59.221 Status: zwave-js-ui MQTT AD: discovered: gangMuurSchakelaar (gangMuurSchakelaar_switch_1)/gangMuurSchakelaar (gangMuurSchakelaar_switch_1) (unique_id: zwavejs2mqtt_0xe0d0c0b_63-37-1-currentValue)
2024-02-13 19:06:59.322 Status: zwave-js-ui MQTT AD: discovered: gangMuurSchakelaar (gangMuurSchakelaar_switch_2)/gangMuurSchakelaar (gangMuurSchakelaar_switch_2) (unique_id: zwavejs2mqtt_0xe0d0c0b_63-37-2-currentValue)
2024-02-13 19:06:59.424 Status: zwave-js-ui MQTT AD: discovered: woonkamerMuurSchakelaar (woonkamerMuurSchakelaar_switch_1)/woonkamerMuurSchakelaar (woonkamerMuurSchakelaar_switch_1) (unique_id: zwavejs2mqtt_0xe0d0c0b_64-37-1-currentValue)
2024-02-13 19:06:59.526 Status: zwave-js-ui MQTT AD: discovered: woonkamerMuurSchakelaar (woonkamerMuurSchakelaar_switch_2)/woonkamerMuurSchakelaar (woonkamerMuurSchakelaar_switch_2) (unique_id: zwavejs2mqtt_0xe0d0c0b_64-37-2-currentValue)
2024-02-13 19:06:59.628 Status: zwave-js-ui MQTT AD: discovered: thermostaatBritt (thermostaatBritt_thermostat)/thermostaatBritt (thermostaatBritt_thermostat) (unique_id: zwavejs2mqtt_0xe0d0c0b_Node69_thermostat)
2024-02-13 19:06:59.730 Status: zwave-js-ui MQTT AD

Every line is one member from a device discovered (members are fi: Watts, Volts, kWh, state, etc)
Are devices discovered more than once?

yes, they are discivered every 3 seconds. Had to turn off status and info log messages in the AD hardware section, to get my log readable again.

Check with mqtt explorer if your discovery topics in mqtt topic homeassistant gets updated from Zwave-JS-UI constantly.
If so you did something wrong in Zwave-JS-UI.

I have the same issue after a reboot. It does Not Stop to discover. Only way to Stop ist to delete all Messages with mqtt Explorer.