Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect date time displayed at object browser #2102

Closed
mcm1957 opened this issue Sep 8, 2023 · 2 comments · Fixed by #2104
Closed

Incorrect date time displayed at object browser #2102

mcm1957 opened this issue Sep 8, 2023 · 2 comments · Fixed by #2104
Labels

Comments

@mcm1957
Copy link
Contributor

mcm1957 commented Sep 8, 2023

Describe the bug
DATES stored as string are displayed with wrong information

To Reproduce
Steps to reproduce the behavior:

  1. create a state with type STRING and role DATE
  2. store the value "08.09.2023"
  3. admin object browser displays "Wed Aug 09 2023 00:00:00 GMT+0200 (Mitteleuropäische Sommerzeit)"

Expected behavior
The correct date should be displayed

Screenshots & Logfiles
You may check adapter weatherunderground
Sometimes (depending on values) the string "invalid Date" is displyed too (see issue iobroker-community-adapters/ioBroker.weatherunderground#191)

Versions:

  • Adapter version: 6.9.2 (works as expected with 6.4.4)
  • JS-Controller version: 4.0.24
  • Node version: v18.16.0
  • Operating system: Windows 11

Additional context
NOTE: The used string format "dd.mm.yyyy" is not officially supported by js. So this format does N OT meet the spezifications for role "date". For me it would be OK to close the issue with "correct the adapter" too. But it should be considered that maybe more than one or two aapters are effected.

@mcm1957 mcm1957 changed the title Incorrect date time displyed at object browser Incorrect date time displayed at object browser Sep 8, 2023
@Feuer-sturm Feuer-sturm added the bug label Sep 9, 2023
@mcm1957
Copy link
Contributor Author

mcm1957 commented Sep 9, 2023

Writing the date text using correct javascript format (yyyy-mm-dd) solved the problem for weatherunderground.

@foxriver76
In my oppinion we could close here - there are enough other tasks to do. But I will leave the decision to core devs, so I only leave this note.

@foxriver76
Copy link
Collaborator

At least there was a bug, because we wanted to show the original string if Invalid Date cases happen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants