'unknown error' at configuration when submitting lat and long about bureau_of_meteorology

[bremor]

Haven't done it, but will do it. Have created an issue so i don't forget.
#18

[bremor]

Thanks for reporting a problem. Would you mind sharing your lat/Lon? You can round to two decimal places if you would like to hide your exact location

[snowgumrd]

Sure.
Lat: -37.78
Lon: 145.17

[bremor]

I'm not sure what happened here, I don't get an error using those coordinates. I do have some suggestions:

• Was your internet down at the time?
• Can you try uninstall/reinstall the entire integration?
• Can you try different coordinates?
• Is there anything unique about your environment that is worth mentioning?

[snowgumrd]

I'm not sure what happened here, I don't get an error using those coordinates. I do have some suggestions:

• Was your internet down at the time?
• Can you try uninstall/reinstall the entire integration?
• Can you try different coordinates?
• Is there anything unique about your environment that is worth mentioning?

Nope. Internet is fine.
Tried removing and reinstall, it didn't work either.
I tried melbourne CBD co-ordinates. No luck.
My home assistant instance is run on a QNAP NAS. Might that be the cause? I've got lots of integrations running but every one is unique I guess.

[bremor]

Mate, i'm totally stumped. It looks like your system is failing to bind to a local port maybe? Might be a restriction on your QNAP? Might be worth some googline that specific error,
Cannot connect to host api.weather.bom.gov.au:443 ssl:default [Cannot assign requested address]

[snowgumrd]

Mate, i'm totally stumped. It looks like your system is failing to bind to a local port maybe? Might be a restriction on your QNAP? Might be worth some googline that specific error,
Cannot connect to host api.weather.bom.gov.au:443 ssl:default [Cannot assign requested address]

Actually, now that you mention it, i had a similar issue with the solcast integration. I had to change SSL as no to get it working.

How would I go about doing that with this integration?

[bremor]

Do you mean you had to change it to http or you had to turn off ssl cert validation?

[snowgumrd]

Do you mean you had to change it to http or you had to turn off ssl cert validation?
In the py, I had to override
ssl = false

[bremor]

Within collector.py, try updating the following line and then reboot, there are three occurances. If this works I will include it in the next release.

            response = await session.get(url)

to

            response = await session.get(url, ssl=False)

[snowgumrd]

Within collector.py, try updating the following line and then reboot, there are three occurances. If this works I will include it in the next release.

            response = await session.get(url)

to

            response = await session.get(url, ssl=False)

That did it! Clearly there's a pattern here. Should I be concerned about not using SSL?

[bremor]

Your environment maintains a list of trusted certificate authorities, which would normally be kept up to date automatically. The ssl cert that BoM are using is signed by "DigiCert Global Root CA". So if you can, you should install this Root CA into your trusted certificate store in your environment. I’m thinking it’s best if I don’t put ssl=False into the next release.

Subject | DigiCert Secure Site ECC CA-1
Valid from 15/Feb/2019 to 15/Feb/2029
Issuer | DigiCert Global Root CA

[bremor]

I have release version 0.7, but I have also created a new branch for you where SSL is disabled. I will maintain this branch, the only difference will be that ssl=False bit. It will only ever appear in "beta versions"

[DavidFW1960]

did you add back day 6 yet?

[snowgumrd]

I have release version 0.7, but I have also created a new branch for you where SSL is disabled. I will maintain this branch, the only difference will be that ssl=False bit. It will only ever appear in "beta versions"

Cheers mate! Thanks for your help.