Closed sermayoral closed 8 months ago
Not sure if it's because you're in a different region so not sure if that may be the issue, but I cannot reproduce. First, are you sure you're running v3.3.8?
Can you please enable debug logging and post the logs when creating a new timestamp variable to see if they show anything that may help.
You are completely right. I wasn't running v3.3.8. I thought i was. Very strange. Sorry :-(
An important fact. In my screenshots, the date format is dd/MM/yyyy instead of MM/dd/yyyy. It can be very confusing
Setting a value creating a new timestamp sensor doesn't crash anymore :-). Although the date you enter is in UTC, and then it is converted to your time zone:
My timezone is GMT+1:
It also happened in your screenshots, So I guess it's done on purpose.
Also, updating a timestamp sensor seems to have no effect
Last change and last update attributes change, but the state doesn't it:
Thanks
I just noticed that I think you are trying to update the value of an existing variable using the Configuration page. In general, that won't work. You need to call one of the Variable Services to update (variable.update_sensor
). When I update a timestamp Variable Sensor using variable.update_sensor
it updates for me.
I'll still look to add a timezone selector when creating a new timestamp Variable Sensor but no eta on that.
https://github.com/enkama/hass-variables/issues/102 still persists in v3.3.8.
The problem occurs when you fill out this window:
Getting the following error and the variable unavailable:
If you leave "initial value" empty, it works.