small change request

[ChristophCaina]

Hi, just wanted to know, if the "last measurement" could be changed into "timestamp" device class, since it does not only provide a date, but also a time...

This would allow the sensor to be displayed similar to this:

rather than only showing a time stamp :)

[ProudElm]

i've been struggling to get it usefully working. I parked the issue because of performance problems at the beginning. I will take a look at this again once i have some spare time!

[ChristophCaina]

hm... I had a short look into it and payed around with some changes.

As far as I could see, changing the deviceClass to Timestamp alone does not work. It's probably because the timestamp does not provide timezone information... ?

Typical timestamp format in HA: 2023-03-06T05:42:00+00:00 2023-03-06T11:22:56.150309Z

Information provided by the sensor: 2023-03-06T14:13:19

so, probably the +00:00 at the end needs to be added in order to work properly.

I will continue to play around with this and once I got it working, I will submit an PR :)

From Developers Documentation:

Constant | Supported units | Description -- | -- | -- SensorDeviceClass.TIMESTAMP |   | Timestamp. Requires native_value to return a Python datetime.datetime object, with time zone information, or None. SensorDeviceClass.DATE |   | Date. Requires native_value to be a Python datetime.date object, or None.

[ProudElm]

Oh now i remember.. It has the do when comparing the time for if the value is to old to store i ran into problem with timezone's...

I wont be fixing that.. I cannot get the correct timezone provided from the solaredge portal, so i skipped the hole timezone aware dates in python and that worked..

[ChristophCaina]

ah okey :)

Right - with just using DeviceClass.Timestamp I am getting the following error:

    raise ValueError(
ValueError: Invalid datetime: sensor.last_measurement_1_1_1 provides state '2023-03-06 14:40:45', which is missing timezone information

Probably, the easiest way would be a template sensor which does set the DATE value as a timestamp.

I'll try to investigate deeper to see, if this can be changed at all.

[ProudElm]

Yes i know.. i stopped for a reason ;-) There were bigger problems at the time..

template sensors fix everything in HA, always :-) hahah

[ChristophCaina]

:D They do... but unfortunately, it is not really my preferred way to go with nearly 40 optimizers :D

It's really only for the missing time zone - which I think - would be "local"...

here's my current template - so maybe this is how the output could be formatted in the component itself?

{{ as_timestamp(states('sensor.last_measurement_1_1_1')) | timestamp_local }}