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!
Here’s a sensor for the current wholesale price per kilowatt. I needed something that would alert me so that I would know to dump the Powerwalls to the grid. Normally the wholesale price is around $0.02. Yesterday it hit nearly $5.00. It is one of my first sensors and some of my first Jija, so feedback and tips welcome. It basically loops through the JSON response and delivers the wholesale average that corresponds to the highest timestamp in the record.
- platform: rest
scan_interval: 900
unit_of_measurement: "$"
unique_id: ercot_realtime_system_wide_prices
icon: mdi:transmission-tower
name: "ERCOT Realtime Wholesale per kWh"
resource: "https://www.ercot.com/api/1/services/read/dashboards/systemWidePrices.json"
value_template: >-
{% set nsmi = namespace(max_interval = 0) %}
{% set nshba = namespace(hbBusAvg = 0) %}
{% for data in value_json.rtSppData %}
{% if data['interval'] > nsmi.max_interval %}
{% set nsmi.max_interval = data['interval'] %}
{% set nshba.hbBusAvg = data['hbBusAvg'] %}
{% endif %}
{% endfor %}
{{nshba.hbBusAvg/1000}}
Thank you so much for this info. I was struggling with the github config. I was able to get it to collect data but the Current Reading sensor didn’t work in the Energy Dashboard. Your changes work great!
I did have to remove the smartmetertexas: value at the top of the smt package and also added a sensor for the hourly energy reading.
This post might be redundant but hopefully this helps another following mnewm4’s great templates.
I did some tinkering and reading through this thread and had to make changes to get this working for me as of 8 September 2023. I am running:
Home Assistant 2023.9.0
Supervisor 2023.08.3
Operating System 10.5
Frontend 20230906.1 - latest
I added this into my configuration.yaml to add the sensors ‘sensor.ercot_status’ (for the text conditions in the later Markdown card) and ‘sensor.ercot_reserves’ (for the needle gauge card) into the “sensor:” section of the file.
configuration.yaml:
sensor:
# there may be tons of other sensors in here already
- 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
- prc_value
- datetime
- platform: template
sensors:
ercot_reserves:
unique_id: ercot_grid_operating_reserves
friendly_name: "Ercot Operating Reserves"
unit_of_measurement: MW
icon_template: mdi:transmission-tower
value_template: >-
{{states.sensor.ercot_status.attributes.prc_value.replace(",", "") }}
I then added these into a default Lovelace card of “Vertical Stack” with the following yaml code:
If the Markdown card doesn’t work on a copy and paste, then double check that the copy paste operation from your browser over to your card yaml input didn’t insert and create extra line breaks. For example, the “<td align… </ha-icon></td>” should be on one line and “<td colspan… </td>” should be on one line inside the card’s yaml.
