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

[EDH-3635] - System distributes Metering Data with not existing datetime value #138

Open
EinarArro opened this issue Dec 3, 2024 · 0 comments
Labels
critical Will be fixed as soon as possible

Comments

@EinarArro
Copy link
Collaborator

Problem

When GO sends the metering data and the pS value is in Estonian format the way, that it's the missing hour from the spring daylight saving time change, that doesn't exist (because of 23h day), then the System doesn't respond with error, but processes the data, stores it to pS 00:00 and even distributes the wrong data to OS.

Steps to reproduce

NB! I don't know, how to reproduce that issue in the DEV environment. It was reported by the OS from Live. But it seems, that you have to send metering data message, that contains pS value "2024-03-31T03:00:00+03:00" (this value cannot be translated to UTC)

Expected result

System identifies the error and responds accordingly.

Actual Result

  • System processes the data and if I'm not mistaken, then stores the value to 00:00 hour.
  • System creates DD message, that contains "pS": "2024-03-31T03:00+03:00":
[
    {
        "meterEic": "hidden",
        "periods": [
            {
                "r": "PT1H",
                "aI": [
                    {
                        "pS": "2024-03-31T00:00+02:00",
                        "outQty": {
                            "rTime": "2024-12-01T16:23:46.544Z",
                            "rType": "E",
                            "kwh": 4.271
                        }
                    },
                    {
                        "pS": "2024-03-31T01:00+02:00",
                        "outQty": {
                            "rTime": "2024-12-01T16:23:46.544Z",
                            "rType": "E",
                            "kwh": 4.433
                        }
                    },
                    {
                        "pS": "2024-03-31T03:00+03:00",
                        "outQty": {
                            "rTime": "2024-12-01T16:23:46.544Z",
                            "rType": "E",
                            "kwh": 4.4
                        }
                    },
                    {
                        "pS": "2024-03-31T04:00+03:00",
                        "outQty": {
                            "rTime": "2024-12-01T16:23:46.544Z",
                            "rType": "E",
                            "kwh": 5.408
                        }
                    },
                    {
                        "pS": "2024-03-31T05:00+03:00",
                        "outQty": {
                            "rTime": "2024-12-01T16:23:46.544Z",
                            "rType": "E",
                            "kwh": 4.378
                        }
                    },
                    {
                        <--removed content -->
                    }
                ]
            }
        ]
    }
]

Impact (If known)

OS-s cannot process the DD message, because they try to parse the value "2024-03-31T03:00+03:00"

Work-a-round

Use only UTC, but we cannot force that.

@EinarArro EinarArro added the MVP label Dec 3, 2024
@kristjanZ kristjanZ added critical Will be fixed as soon as possible and removed MVP labels Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
critical Will be fixed as soon as possible
Projects
None yet
Development

No branches or pull requests

2 participants