Integration won't start with valid credentials

Particpant commented 2 weeks ago

System Health details

System Information

version	core-2024.8.3
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.12.4
os_name	Linux
os_version	6.6.46-haos
arch	x86_64
timezone	America/Los_Angeles
config_dir	/config

Home Assistant Community Store

Home Assistant Cloud

Home Assistant Supervisor

Dashboards

Recorder

Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of any previous issues..

Describe the issue

Failed setup after installing integration - I tried the rate ID from the forum thread and that did work, though it's not accurate for me. USCA-SCSC-0400-0000

Rate IDs

USCA-PGCC-0400-0000

Reproduction steps

install integration
create account via integration gui setup flow
use confirmation link in email
supply credentials to integration
add my rate id
integration fails to setup with the error from the debug log below. ...

Debug logs

2024-09-02 15:39:23.841 ERROR (MainThread) [custom_components.midas] Unexpected error fetching midas data
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 354, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/midas/coordinator.py", line 50, in _async_update_data
    data[rid] = await self._client.async_get_rate_data(rid)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/midas/api.py", line 29, in async_get_rate_data
    return await self._hass.async_add_executor_job(self._midas.GetRateInfo, rate_id)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/california_midasapi/ratelist.py", line 44, in GetRateInfo
    pricing_response = self.__request('GET', url)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/california_midasapi/internal.py", line 21, in __request
    raise f"Error preforming request: {response.status_code} {response.text}"
TypeError: exceptions must derive from BaseException
2024-09-02 15:39:23.859 DEBUG (MainThread) [custom_components.midas] Finished fetching midas data in 1.108 seconds (success: False)

Diagnostics dump

unavailable due to integration failing to set up

Particpant commented 2 weeks ago

try this <snip, highly suspect link> select the desired compiler in the installer

Anyone else encountering the issue reported in my post should not follow the link in the quoted reply to my issue report.

rohankapoorcom commented 2 weeks ago

Seeing the same issue with USCA-PGCC-0200-0000 and USCA-XXSF-0063-0000

MattDahEpic commented 2 weeks ago

Interesting, are either of you on Community Choice Aggregation electricity plans? USCA-PGCC-0400-0000 and USCA-PGCC-0200-0000 don't seem to exist in the MIDAS database though USCA-XXSF-0063-0000 does.

rohankapoorcom commented 2 weeks ago

Yes, I'm using a Community Choice Aggregation plan in San Francisco. The first code is from PG&E and the second code is from GreenPowerSF (the CCA).

MattDahEpic commented 2 weeks ago

After a little more investigation, I think this might be on PG&E. RINs are supposed to have a specific form that has the distribution and generation listed seperately for exactly this case:

Per the MIDAS documentation CCA rates are divided into 2 RINs with the distribution one being USCA-PGXX-... and the generation one being USCA-XXSF-... but you both have "PGCC" as the delivery/generation pair while also having a second one for the CCA generation. Supporting this point is that the rates USCA-PGXX-0200-0000 and USCA-PGXX-0400-0000 both exist and seem like the rates that should be on your bill. I've reached out to the CEC to determine if this is intended and if not PG&E will likely get a letter telling them to make sure their bills are right.

Regardless, there is a bug here in that the error messages are pretty ugly. I've got a fix for that coming in the next release.

Particpant commented 2 weeks ago

For completeness' sake, I do have 2 codes, but I had initially missed that there were two, as they were on different pages. USCA-XXSF-0063-0000 is my CCA's code.

MattDahEpic commented 2 weeks ago

I've cleaned up the error messages a bit in the latest release: 0.1.3. I still want to have the integration actually check if the rates exist before letting you save so I'll leave this open for now.

As for the rates themselves the CEC has responded saying PG&E is aware and has been requested to update the RINs on bills but isn't sure when they'll do so. I'm not a PG&E customer so they're not likely to listen to me but if you feel it's worth the time you could send an email or call to PG&E letting them know the wrong RIN was on your bill.

In an effort to get you up and running until they fix the issue, I took a look into those previously mentioned XX energy code rates. If these sound like the distribution charges on your bill you might be able to use these until the real RINs start showing up and if my guess is right maybe they are the right RINs:

USCA-PGXX-0200-0000 appears to be named E-TOU-D with an off peak of 0.28973 USD/kWh and an on peak of 0.31973 USD/kWh
USCA-PGXX-0400-0000 appears to be named EV2-A with a low, medium, and high rate of 0.17882, 0.3397, and 0.40548 USD/kWh respectively

Particpant commented 2 weeks ago

It's close enough!

rohankapoorcom commented 2 weeks ago

Thank you, it's the correct one for me! Appreciate you taking the time to figure this out!

MattDahEpic / ha-midas