search

fairecasoimeme / Zlinky_TIC

Téléinformation Linky autoalimenté ZigBee 3.0
290 stars 21 forks source link

MQTT or Zigbee2MQTT multiple (too many?) log entries #183

Open jellium opened 1 year ago

jellium commented 1 year ago

Firmware used: router 13

I am not sure whether it is the expected behaviour or not, but I find that MQTT messages are numerous (and redondant).

Every 60 seconds (default configuration for measurement_poll_interval) Zigbee2MQTT's journal shows a first MQTT message, followed a few seconds later by a zlinky config: ... immediately followed by 8 (identical?) MQTT messages.

Feb 19 10:05:13 ZIGBEE2MQTT npm[22904]: Zigbee2MQTT:info  2023-02-19 10:05:13: MQTT publish: topic 'zigbee2mqtt/linky', payload '{"active_register_tier_delivered":"HP..","apparent_power":840,"available_power":45,"current_tarif":"HC..","current_tier1_summ_delivered":4798.157,"current_tier2_summ_delivered":4879.736,"linkquality":232,"meter_serial_number":"XXX","rms_current":2,"rms_current_max":90,"schedule_h_p_h_c":0,"update":{"installed_version":13,"latest_version":13,"state":"idle"},"update_available":null,"warn_d_p_s":0}'
Feb 19 10:05:38 ZIGBEE2MQTT npm[22904]: zlinky config: historique, single_phase, false, HC..
Feb 19 10:05:39 ZIGBEE2MQTT npm[22904]: Zigbee2MQTT:info  2023-02-19 10:05:39: MQTT publish: topic 'zigbee2mqtt/linky', payload '{"active_register_tier_delivered":"HP..","apparent_power":840,"available_power":45,"current_tarif":"HC..","current_tier1_summ_delivered":4798.157,"current_tier2_summ_delivered":4879.736,"linkquality":216,"meter_serial_number":"XXX","rms_current":2,"rms_current_max":90,"schedule_h_p_h_c":0,"update":{"installed_version":13,"latest_version":13,"state":"idle"},"update_available":null,"warn_d_p_s":0}'
Feb 19 10:05:39 ZIGBEE2MQTT npm[22904]: Zigbee2MQTT:info  2023-02-19 10:05:39: MQTT publish: topic 'zigbee2mqtt/linky', payload '{"active_register_tier_delivered":"HP..","apparent_power":840,"available_power":45,"current_tarif":"HC..","current_tier1_summ_delivered":4798.157,"current_tier2_summ_delivered":4879.736,"linkquality":216,"meter_serial_number":"XXX","rms_current":2,"rms_current_max":90,"schedule_h_p_h_c":0,"update":{"installed_version":13,"latest_version":13,"state":"idle"},"update_available":null,"warn_d_p_s":0}'
Feb 19 10:05:39 ZIGBEE2MQTT npm[22904]: Zigbee2MQTT:info  2023-02-19 10:05:39: MQTT publish: topic 'zigbee2mqtt/linky', payload '{"active_register_tier_delivered":"HP..","apparent_power":840,"available_power":45,"current_tarif":"HC..","current_tier1_summ_delivered":4798.157,"current_tier2_summ_delivered":4879.736,"linkquality":216,"meter_serial_number":"XXX","rms_current":2,"rms_current_max":90,"schedule_h_p_h_c":0,"update":{"installed_version":13,"latest_version":13,"state":"idle"},"update_available":null,"warn_d_p_s":0}'
Feb 19 10:05:39 ZIGBEE2MQTT npm[22904]: Zigbee2MQTT:info  2023-02-19 10:05:39: MQTT publish: topic 'zigbee2mqtt/linky', payload '{"active_register_tier_delivered":"HP..","apparent_power":840,"available_power":45,"current_tarif":"HC..","current_tier1_summ_delivered":4798.157,"current_tier2_summ_delivered":4879.736,"linkquality":216,"meter_serial_number":"XXX","rms_current":2,"rms_current_max":90,"schedule_h_p_h_c":0,"update":{"installed_version":13,"latest_version":13,"state":"idle"},"update_available":null,"warn_d_p_s":0}'
Feb 19 10:05:39 ZIGBEE2MQTT npm[22904]: Zigbee2MQTT:info  2023-02-19 10:05:39: MQTT publish: topic 'zigbee2mqtt/linky', payload '{"active_register_tier_delivered":"HP..","apparent_power":840,"available_power":45,"current_tarif":"HC..","current_tier1_summ_delivered":4798.157,"current_tier2_summ_delivered":4879.736,"linkquality":216,"meter_serial_number":"XXX","rms_current":2,"rms_current_max":90,"schedule_h_p_h_c":0,"update":{"installed_version":13,"latest_version":13,"state":"idle"},"update_available":null,"warn_d_p_s":0}'
Feb 19 10:05:39 ZIGBEE2MQTT npm[22904]: Zigbee2MQTT:info  2023-02-19 10:05:39: MQTT publish: topic 'zigbee2mqtt/linky', payload '{"active_register_tier_delivered":"HP..","apparent_power":840,"available_power":45,"current_tarif":"HC..","current_tier1_summ_delivered":4798.157,"current_tier2_summ_delivered":4879.746,"linkquality":216,"meter_serial_number":"XXX","rms_current":2,"rms_current_max":90,"schedule_h_p_h_c":0,"update":{"installed_version":13,"latest_version":13,"state":"idle"},"update_available":null,"warn_d_p_s":0}'
Feb 19 10:05:39 ZIGBEE2MQTT npm[22904]: Zigbee2MQTT:info  2023-02-19 10:05:39: MQTT publish: topic 'zigbee2mqtt/linky', payload '{"active_register_tier_delivered":"HP..","apparent_power":840,"available_power":45,"current_tarif":"HC..","current_tier1_summ_delivered":4798.157,"current_tier2_summ_delivered":4879.746,"linkquality":216,"meter_serial_number":"XXX","rms_current":2,"rms_current_max":90,"schedule_h_p_h_c":0,"update":{"installed_version":13,"latest_version":13,"state":"idle"},"update_available":null,"warn_d_p_s":0}'
Feb 19 10:05:39 ZIGBEE2MQTT npm[22904]: Zigbee2MQTT:info  2023-02-19 10:05:39: MQTT publish: topic 'zigbee2mqtt/linky', payload '{"active_register_tier_delivered":"HP..","apparent_power":840,"available_power":45,"current_tarif":"HC..","current_tier1_summ_delivered":4798.157,"current_tier2_summ_delivered":4879.746,"linkquality":216,"meter_serial_number":"XXX","rms_current":2,"rms_current_max":90,"schedule_h_p_h_c":0,"update":{"installed_version":13,"latest_version":13,"state":"idle"},"update_available":null,"warn_d_p_s":0}'

Thanks for this super project.

bosr commented 1 year ago

Salut, j'ai la même situation en v12.

À court terme, dans la page Settings (générique, pas settings(specific)) de cet appareil, j'ai mis le paramètre debounce à 30 (source ici). Ce n'est pas satisfaisant car les messages sont toujours envoyés sur le réseau zigbee, mais au moins mqtt et surtout la base de données HA prennent moins cher.

Dans mon cas, j'ai pas mal de petites variations de linkquality.

Je suis débutant dans le domaine, alors je suis preneur d'une solution propre à ce souci.

PS : I can translate that to english if it helps.

jellium commented 1 year ago

Hi @bosr, thanks for your input.

I have too set debounce to 30 (seconds) with default poll_intervalle set to 60 seconds (even though there seem to be 2 timers ongoing, one with 1 message broadcasted and one with several (8) messages broadcasted on the Zigbee network).

Also, is it normal that zlinky config: historique, single_phase, false, HC.. occurs continuously every minute or so?

And how is that line related to measurement_poll_interval? Finally, changing that last parameter measurement_poll_interval doesn't seem to change the MQTT messages broadcast frequency (even if Zigbee2MQTT is restarted after changing that parameter).