Shay Levy

The sensor reports it's value should only increase: https://github.com/magico13/ha-emporia-vue/blob/c1aaac407560e9c91ffdc2c016c368ade2a0b0a8/custom_components/emporia_vue/sensor.py#L112-L113 In order to allow decreasing the sensor should report `STATE_CLASS_TOTAL` https://developers.home-assistant.io/docs/core/entity/sensor/ In addition the usage of state classes as strings is...

@knuckleheadsmiff the sensor needs to be changed as I explained in https://github.com/magico13/ha-emporia-vue/issues/101#issuecomment-1030584225 there is nothing else to be done. Using virtual sensors will not be approved. Sensors should represent the...

> You may already notice this in the logs but, I set up PowerShell to watch the tail of the logs as I changed device states. When I change the...

> I think I have seen this before and it was declined as adding way to much complexity to the code base, and what is the benefit of have integrations...

> The SmartThings app does this and it's not a confusing mess. It simply lets me manage two independent instances (one for each house) and as far as the app...

When implementing an entity you can return a different icon for each state (taking in mind that architectural discussions are for someone who wants to implement something in core). A...

Shelly integration does not support this feature, we currently have other Shelly features with higher priority that are already in work so I can't update on a timeline for that.

The sensor in your linked picture was changed to use an update sensor in https://github.com/home-assistant/core/pull/78305, unfortunately the migration is broken so the legacy sensor is not removed. On the same...

Closing this issue, regardless if this is related to a device problem or not, we are not going to change values reported by the device. If you believe the value...

@Vadoal please update the issue description to English to avoid closing it, Thanks 👍