Closed meyerrj closed 1 year ago
Is this needed? I was able to connect successfully today.
I'll try testing against the www.
subdomain again, but last I had attempted about a month or so ago I appeared to be blocked by Akamai. I've only been successful with the base domain as the target URL.
@meyerrj Does this work for you after the recent change to the server? This branch is still failing for me
Sorry, I haven't had a chance to test.
It appears to be broken all around though at the moment, seems like they changed something on the servers again...
The base domain now appears to terminate any HTTPS connections. I'm getting a PR_CONNECT_RESET_ERROR with Firefox. Not even getting response headers. I can also confirm that the www subdomain is still blocking me as well (Akamai).
https://github.com/home-assistant/core/issues/57582 has a lot of others reporting other broken integrations as well over the past few days, even those that used Node-RED. 😣
That's unfortunate 😞. Thanks for investigating.
Since this hasn't been merged, I'm going to toss in my confirmation that this PR fixes the problem. I copied the examples from this repo, supplied my un/pw, and neither example worked. I manually merged this PR to my pip install and the examples now work.
Confirmed it does work. I'll go ahead and merge.
Glad to see that this patch still works, and thanks for merging it in! :)
Changes the base hostname to just smartmetertexas.com
The base domain is now part of the SSL certificate's SAN: https://github.com/home-assistant/core/issues/57582#issuecomment-1287929568
This change should help resolve the issue here: https://github.com/home-assistant/core/issues/57582