I created a monitor for the Texas Electricity Grid by scraping ERCOT’s web page. If anyone is interested in recreating it, here is the configuration.yaml entry:
sensor:
- platform: rest
scan_interval: 300
unique_id: ercot_status
icon: mdi:transmission-tower
name: Ercot Status
resource: "https://www.ercot.com/api/1/services/read/dashboards/daily-prc.json"
value_template: "{{value_json.current_condition.state}}"
json_attributes_path: "$.current_condition"
json_attributes:
- energy_level_value
- title
- condition_note
- eea_level
- platform: template
sensors:
ercot_status_condition:
friendly_name: "Ercot Grid Condition"
icon_template: >-
{% if states.sensor.ercot_status.attributes.eea_level != 0 %}
mdi:alert
{%else%}
mdi:transmission-tower
{%endif%}
value_template: >-
{% if states.sensor.ercot_status.state == 'normal' %}
The grid is operating under normal conditions.
{% elif states.sensor.ercot_status.state != 'normal' and states.sensor.ercot_status.attributes.eea_level == 0 %}
Energy conservation is requested.
{% elif states.sensor.ercot_status.attributes.eea_level == 1 %}
Energy Emergency Level 1 - Emergency operations have begun due to low power reserves, but there are no controlled outages at this time. Energy conservation is requested.
{% elif states.sensor.ercot_status.attributes.eea_level == 2 %}
Energy Emergency Level 2 - The emergency level has been raised due to continued low power reserves. Energy conservation is requested. It is advised to create a plan in case controlled outages are needed later. Those with critical medical needs should register with their local utility and have a backup plan.
{% elif states.sensor.ercot_status.attributes.eea_level == 3 %}
Energy Emergency Level 3 - The highest level of emergency operations. Local electric utilities have been instructed to begin controlled outages. Health and safety should be made a priority by using city or county instructions and resources. Energy conservation is critical.
{%endif%}
Here is an updated sensor. I missed the system reserve (prc_value) attribute. It’s the same data as the reserve gauge sensor above but it can all be pulled as one request.
Did you have to do anything special to get Smart Meter Texas working? I had it working for a while then the addon lost the ability to log in. I can log in manually with the same credentials but the addon won’t work for me.
I had the same issue. It actually will prevent the HA restore from completing. If you still have it installed I would recommend uninstalling it. I learned that the hard way.
I’m using the node-red implementation.
The instructions are a bit out of date. Below are the changes I had to make to get it to work.
Very cool. I looked into Smart Meter TX a while ago, but my utility (City of Austin) did not support it. Will check again to see if anything has changed.
This is somewhat untested but in theory, it should work. These 2 sensors return the least amout of forecast committed & total capacity for the day. My thought is if forecast availability drops below X (like last July) then do something.
I think ERCOT publishes a re-forecast every 5 minutes. Currently, the scan interval is set at 1 hour but that should be more than adequate.
So, the ERCOT grid gauge from the scrape was working perfectly, but then Home Assistant notified me that scrape had been moved and would break after two revisions. It was kind of cryptic, but I think the reason for the notice was that there is now a scrape integration in HA core.
I installed the integration and attempted to transfer the settings into the configuration with no luck.
Has anyone else moved this to the scrape integration, and if so what were the config parameters that needed to be entered?
Hi Mike - I’ve been using this method for a Scrape sensor successfully, until it stopped working on June 8. The data source is still there, but my sensor is showing “unknown”. I can’t decipher the Select logic,so could you provide the updated configuration to use to get this working again? Thanks!