No device id for {"type":"PowerMetricsChangedEvent" ...

[EzequielPitton78]

[06.09.2022] [22:03:21] [WARNING] [QUICKAPP3526]: No device id for {"type":"PowerMetricsChangedEvent","created":1662494601,"data":{"consumptionPower":3179.7,"productionPower":0.0}} [06.09.2022] [22:03:21] [WARNING] [QUICKAPP3526]: No device id for {"type":"PowerMetricsChangedEvent","created":1662494601,"data":{"consumptionPower":3179.7,"productionPower":0.0}} [06.09.2022] [22:03:21] [WARNING] [QUICKAPP3526]: No device id for {"type":"PowerMetricsChangedEvent","created":1662494601,"data":{"consumptionPower":3179.7,"productionPower":0.0}} [06.09.2022] [22:03:21] [WARNING] [QUICKAPP3526]: No device id for {"type":"PowerMetricsChangedEvent","created":1662494601,"data":{"consumptionPower":3179.7,"productionPower":0.0}}

[alexander-vitishchenko]

Hi @EzequielPitton78

It looks like HC3 triggered an event that has no need to be reflected in HA event model, i.e. it is skipped by the QuickApp.

What I can do is to reduce the log message severity from WARNING to DEBUG, so it doesn't raise a false alarm.

This is not a mistake, and this log message's intention is to notify developer (me) about the need to review unsupported event type(s) and see if it should be added to the QuickApp as supported, or demoted from WARNING to DEBUG level.

Thank you for keeping me updated, Alexander

[alexander-vitishchenko]

Done

The QuickApp now distinguishes DEVICE vs SYSTEM level events => not raising attention to system level events, as only device events supported at the moment