You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be possible to have a date column where the data for the field came in in an ISO format 2023-10-22T20:30:00+00:00`` and the results is displayed in the time of the local time zone ... ideally in a user defined formatIn HA the template command is ``{{ as_timestamp(state_attr('binary_sensor.octopus_energy_target_test','target_times')[0]['valid_from']) | timestamp_custom("%A %R") }}
I have played around with this and got it to work partially but with no real success
It would also be useful to be able to format the outputted string maybe using some of the standard datetime format codes.
This would be particularly useful when interfacing to 'Bottlecap Dave's Octopus Energy Integration' where he quotes times always in UTC to get Agile Windows for charging and discharging
Of course if anyone can assits me in anyway then I would be more than welcome.
The text was updated successfully, but these errors were encountered:
Would it be possible to have a date column where the data for the field came in in an ISO format
In HA the template command is
2023-10-22T20:30:00+00:00``
and the results is displayed in the time of the local time zone ... ideally in a user defined format``{{ as_timestamp(state_attr('binary_sensor.octopus_energy_target_test','target_times')[0]['valid_from']) | timestamp_custom("%A %R") }}
I have played around with this and got it to work partially but with no real success
It would also be useful to be able to format the outputted string maybe using some of the standard datetime format codes.
This would be particularly useful when interfacing to 'Bottlecap Dave's Octopus Energy Integration' where he quotes times always in UTC to get Agile Windows for charging and discharging
Of course if anyone can assits me in anyway then I would be more than welcome.
The text was updated successfully, but these errors were encountered: