Clifford W. Hansen

@Lorthiz I had a similar issue where Glow was reporting my usage as 33KW, after adding the `internal_filter: 200ms` it is now a realistic 1KW

This is a duplicate of: https://github.com/Cleanarr/Cleanarr/issues/4 Also there is a discusion thread: https://github.com/Cleanarr/Cleanarr/discussions/5 /cc @appiekap653

I have a couple of non Debian systems running ArchLinux and Alpine I know we can't support all the things ;-)

I think I get what @paulbalinnel wants. Firstly install browser-mod (https://github.com/thomasloven/hass-browser_mod) And then (from his screen shot assuming mushroom) something like the following: ```yaml type: custom:mushroom-chips-card chips: - type: entity...

Something like this: ```yaml type: custom:mushroom-chips-card chips: - type: entity entity: sensor.load_shedding_stage - type: template entity: sensor.load_shedding_stage content: |- {% if states("sensor.load_shedding_parklands") == "off" %} Starts in {{ timedelta(minutes=state_attr("sensor.load_shedding_parklands", "starts_in"))...

As per the v0.2.0-alpha the following is what I use on my dashboard ```yaml type: entities entities: - entity: sensor.load_shedding_stage - type: custom:template-entity-row icon: mdi:timer-outline name: Parklands state: '{{states(''sensor.load_shedding_parklands'')}}' secondary:...

I set up the following automation as there have been times when I have forgotten to load electricity (pre-paid user) this will send me a notification to tell me to...

Another automation I have to notify me of power outages (yes I know EskomSePush also does this :stuck_out_tongue:) Code ```yaml alias: "Eskom: Power off in 30 min" description: "" trigger:...

And of cause we have one when the stage changes Code ```yaml alias: "Eskom: Stage Change" description: "" trigger: - platform: state entity_id: - sensor.load_shedding_stage_eskom not_from: - Unknown - Unavailable...

I am seeing the same, looks like refactoring to use async is in order. I have not seen any issues being caused by this.