Include the signals as sensors for visualizing PV activity

[diestrohs]

Hi,
could you please include the following signals as sensors for visualizing PV activity:
"pvAction": "disable"
"pvRemaining": 107
"disableDelay": 180

The "pvAction" signal changes based on PV activity as follows:
"aktiv" → Sufficient PV power available
"disable" → Insufficient PV power, activating the timeout
"inactiv" → No PV power available even after the timeout

The "disableDelay" signal indicates the set timeout duration.

thank you

:

[marq24]

is 'pvRemaining' also a TimeStamp (seconds remaining?) - I could not check this myself here locally (at least not now)...

[diestrohs]

yes, there are seconds remaining (timeout)

[diestrohs]

Hi, seems to be working great!

[alexonbandit]

Hi @diestrohs, lovely dashboard! Would you willing to share your yaml for the evcc part?
Many thanks in advance!

[diestrohs]

I can do it, but it's not completely finished yet

[stefanriegel]

can you share the E.V. Charger Card/Yaml? love your implementation

[kwitt21]

@diestrohs
I would also highly appreciate if you could share this. This card is exactly what I´d like to have on a small display near the charger!

// UPDATE //
I wonder if this card would nicely fit on a shelly wall display....

[diestrohs]

Hello, I will publish the Card.
Give me a few days to document everything, otherwise there will be too many questions.

[diestrohs]

The first version of my cards you ca find on my git repository

[diestrohs]

Hi,

Would it be possible to send 'pvRemaining' as a raw value in Seconds, instead of a timestamp '0001-01-01T00:00:00Z', similar to 'Ladedauer' and 'Laderestzeit'?

Background: To achieve a countdown display like:
3:00m, 2:59m, 2:58m, 2:57m … 5s, 4s, 3s, 2s, 0s,
the following conversion is currently required:
{% set given_time = states('sensor.evcc_garage_pv_remaining') %}
{% if given_time != 'unknown' %}
{% set given_time = as_datetime(given_time) %}
{% set current_time = now() %}
{% set time_difference = given_time - current_time %}
{% set minutes = (time_difference.total_seconds() // 60) | int %}
{% set seconds = (time_difference.total_seconds() % 60) | int %}
{% if minutes > 0 %}
{{ minutes }}:{{ '%02d' | format(seconds) }}m
{% else %}
{{ seconds }}s
{% endif %}
{% endif %}
Would it be possible to avoid this conversion by directly providing the value as a duration instead of a timestamp?

Thank You

[marq24]

mhhh - the default HA Entity widget is display timestamps, exactly like you would expect it... and indeed LadeRESTZeit and Ladedauer are indeed in duration format...

Background: To achieve a countdown display like:
3:00m, 2:59m, 2:58m, 2:57m … 5s, 4s, 3s, 2s, 0s,

as I tried to say, IMHO this is already part of the default HA-GUI components - if a custom component does not handle this correctly, then I would want to fix that in the custom component - instead of 'patching' it in the integration... OR (like you already solved it) for the individual's who want's to have the value in a duration - make a helper sensor ;-)

[stroh66]

Hi,

Would it be possible to send 'pvRemaining' as a raw value in Seconds, instead of a timestamp '0001-01-01T00:00:00Z', similar to 'Ladedauer' and 'Laderestzeit'?

Background: To achieve a countdown display like: 3:00m, 2:59m, 2:58m, 2:57m … 5s, 4s, 3s, 2s, 0s, the following conversion is currently required:

{% set given_time = states('sensor.evcc_garage_pv_remaining') %}
{% if given_time != 'unknown' %}
  {% set given_time = as_datetime(given_time) %}
  {% set current_time = now() %}
  {% set time_difference = given_time - current_time %}
  {% set minutes = (time_difference.total_seconds() // 60) | int %}
  {% set seconds = (time_difference.total_seconds() % 60) | int %}
  {% if minutes > 0 %}
    {{ minutes }}:{{ '%02d' | format(seconds) }}m
  {% else %}
    {{ seconds }}s
  {% endif %}
{% endif %}

Would it be possible to avoid this conversion by directly providing the value as a duration instead of a timestamp?

Thank You

[diestrohs]

Hi,
with the following adjustments in your source code, it achieves exactly the desired result:
in const.py:

#    ExtSensorEntityDescriptionStub(
#        tag=Tag.PVREMAINING,
#        icon="mdi:sun-clock",
#        entity_category=EntityCategory.DIAGNOSTIC,
#        #state_class=SensorStateClass.MEASUREMENT,
#        device_class=SensorDeviceClass.TIMESTAMP,
#        #device_class=None,
#    )
    ExtSensorEntityDescriptionStub(
        tag=Tag.PVREMAINING,
        icon="mdi:sun-clock",
        entity_category=EntityCategory.DIAGNOSTIC,
        state_class=SensorStateClass.MEASUREMENT,
        native_unit_of_measurement=UnitOfTime.SECONDS,
        suggested_unit_of_measurement=UnitOfTime.MINUTES,
        device_class=SensorDeviceClass.DURATION,
        suggested_display_precision=0
    ) 

in init.py:

#                elif tag == Tag.PVREMAINING:
#                    # the API just returns seconds here - but we need to convert it to a datetime object so actually
#                    # the value is 'now' + seconds...
#                    if value != 0:
#                        value = datetime.now(timezone.utc) + timedelta(seconds=value)
#                    else:
#                        value = None

Here is the result:

Can the update interval be adjusted in any way? Currently, it is around 30 seconds.

Best regards

[marq24]

looks like you haven't understood my initial reply to this subject... of course it's possible to adjust the code like this (btw. that's the purpose of a pull request)...

You want (for your special card, that replicate the evcc look & feel) to have the value in seconds - The default HA GUI need a timestamp in order to display information in the "2min 56sec" format. There had been users requests in the past, to ensure, that this info will be a timestamp in HA. You want it different.

There are now multiple approaches;

1. you create your fork, make any modification you like - and simply everybody who like, can use your forked repository - that's open-source - and you can fulfill your local requirements
2. you can create a PullRequest that introduce a new/additional sensor that will display the value in seconds, so all users who prefer the current existing sensor are not fed up (and would not reopen Implement device_class property for charging plan end time sensor #93 )

[stroh66]

Hi, I'm generally open to anything, and thank you for your work.
Regarding Option 1: That doesn't help anyone.
Regarding Option 2: I see them as different things that are unrelated:

• Charging schedule with start and stop as timestamps (absolutely correct)
• Charging duration, charging remaining, and PV remaining as durations

Ultimately, anything can be done, with a little imagination.