Continuing issue with "Clear Night" during the day

[atyndall]

I'm experiencing the issue described in #74, in that the current forecast status seems to be timeshifted into the future, indicating that the forecast is "Clear, night", even though it is 3pm currently.

I'm located in Perth which is 3 hours behind the eastern states, so it does smell like some sort of timezone handling issue, as "Clear, night" is the forecast later in the evening.

I've checked the BOM website and app for my weather station, and neither of them are showing "Clear, night" as the current conditions (they're both "Sunny"). Suggests maybe there is something going on in the extension code?

Here are some API outputs: https://gist.github.com/atyndall/91f81c5fe5311070e48f5fca2bf35137

My dashboard:

BOM Website:

BOM App:

[atyndall]

Captured some more information from another occurrence. Night seems to start around 2pm?

[flybrys]

I'm getting the opposite, where it says sunny during the night

[omad]

@atyndall That's really curious. Is it still happening? From your last screenshot it looks like UTC time is being used instead.

This component converts the UTC times from the BoM API into the timezone also available from the BoM API for your configured location (available from e.g. https://api.weather.bom.gov.au/v1/locations/qd66j8/).

Things to check:

• What timezone do you have set in Home Assistant (Settings -> System -> General).
• Are the other dates within Home Assistant that are wrong?
• Are there other dates from this Integration that are wrong? (I can see that UV warning times are converted... but it's the wrong time of year for that to be apparent).
• How is Home Assistant installed? (HA Operating System/Container/Core) (This could be caused by an environment issue, if the TimeZone database is missing or faulty)

[atyndall]

Hi @omad,

It's unfortunately difficult to determine if it's still happening with the forecast, as with the history I have available currently, it has been consistently raining, so there has been no "Clear, night" forecast for a while.

I have observed some other interesting strangeness. Around the day boundaries there appear to be "unknown" data gaps that are of inconsistent timing and length. I wonder if that is related.

What timezone do you have set in Home Assistant (Settings -> System -> General).

Seems to be correctly set to my TZ

Are the other dates within Home Assistant that are wrong?

Not that I've observed. All my other sensor logging seems to be aligned correctly with my timezone.

Are there other dates from this Integration that are wrong? (I can see that UV warning times are converted... but it's the wrong time of year for that to be apparent).

I did some other spot checking, and from what I can tell at least sunset time is accurate.

How is Home Assistant installed? (HA Operating System/Container/Core) (This could be caused by an environment issue, if the TimeZone database is missing or faulty)

It was a while ago I believe it's Home Assistant Core installed on a Debian VM;

atyndall@homeassistant:~$ uname -a
Linux homeassistant 5.10.0-19-amd64 #1 SMP Debian 5.10.149-2 (2022-10-21) x86_64 GNU/Linux

[omad]

Hi @brywithawhy

I'm getting the opposite, where it says sunny during the night

That could be the same issue I'm getting, see https://github.com/bremor/bureau_of_meteorology/issues/177 for details.

[Makin-Things]

This is a BoM problem. The integration only makes available the data they publish.

[atyndall]

@Makin-Things I don't think this is a particularly reasonable response.

At all times that I have detailed, the BOM website and app (which I understand use the same API that the integration uses) have shown the accurate information. This suggests that the bug lies in this extension's interpretation of BoM's API, rather than some defect in the data they publish.

Otherwise how could the BOM website and app show the correct "Sunny" forecast while this extension shows something else?

[Makin-Things]

Firstly the BoM website doesn't use the same api, it is only used by the mobile app. The BoM do not document the api since they consider it to be a private api that nothing other than the mobile app is permitted to use (we ignore that and reverse engineered pretty much everything). If you feel like spending time and figuring it out please do and submit a PR. Unfortunately none of the major contributors have the time to commit.