Yes, i already put it on my Dashboard, but it doesn´t look very User friendly…
I think, i have to wait until someone invites a Integration for this Problem.
Yes, i already put it on my Dashboard, but it doesn´t look very User friendly…
I think, i have to wait until someone invites a Integration for this Problem.
Hello, so for me its working but since i switched to smartenergy its not updating the prices.
The forcastcard is showing at 17:00 (bc SE is providing data at 17:00).
I changed code also to 17:00 but for some reason its not updating the chart.
Only after I manually refresh the integration its loading.
What can it be?
I have the same Problem. But i just use awattar.at for tomorrow, because it doesn´t matter if the Price is 15,6C or 15,2C in Forecast for me.
The SmartENERGY API is often down. Please check with the browser.
If you configure the tax and surcharges properly, you should get the correct values also if you use awattar.
hallo,
bin grad völlig neu hier, und stehe etwas auf der Leitung.
Den Graph und Epex habe ich hinbekommen.
Aber jetzt hier mit den Sensoren und der Automatisierung scheitere ich gerade.
Wo muss der Sensor erstellt werden? in der configuration.yaml? einfach reinkopieren? und die Automatisierung?
Am ENDE des Tages möchte ich meinen Boiler zum niedrigsten Tarif aufheizen,
DAnke im Voraus
Andreas
Schau mal hier:
Damit kannst Du Dir alles so einstellen, wie Du es brauchst.
This has started happening since last week. The API has been super spotty and hasn’t been updating at 17:00. It’s 18:25 as I’m writing this and the API still doesn’t have tomorrow’s prices.
I wrote an automation that tries to get the latest prices, but you can’t do much if the API doesn’t update.
EDIT: Seems the API updated some time past 20:30…
alias: Refresh EPEX Spot Data
description: >-
Fetches Data when "sensor.display_tomorrow_s_energy_graph_between_17_00_00_00"
turns True.
trigger:
- platform: state
entity_id:
- sensor.display_tomorrow_s_energy_graph_between_17_00_00_00
to: "True"
condition: []
action:
- delay:
hours: 0
minutes: 0
seconds: 30
milliseconds: 0
- service: epex_spot.fetch_data
metadata: {}
data: {}
- repeat:
sequence:
- if:
- condition: and
conditions:
- condition: state
entity_id: sensor.dishwasher_start_time
state: Waiting for new data
- condition: state
entity_id: sensor.next_60deg_batch_end_time
state: Waiting for new data
- condition: state
entity_id: sensor.next_30deg_batch_end_time
state: Waiting for new data
then:
- delay:
hours: 0
minutes: 1
seconds: 0
milliseconds: 0
- service: epex_spot.fetch_data
metadata: {}
data: {}
else:
- stop: Data refreshed successfully
count: 3
- if:
- condition: and
conditions:
- condition: state
entity_id: sensor.dishwasher_start_time
state: Waiting for new data
- condition: state
entity_id: sensor.next_60deg_batch_end_time
state: Waiting for new data
- condition: state
entity_id: sensor.next_30deg_batch_end_time
state: Waiting for new data
then:
- service: homeassistant.reload_config_entry
metadata: {}
data: {}
target:
device_id: 58693c8242f2fdb0458c5f4d22f7e066
else:
- stop: Data refreshed successfully
- if:
- condition: and
conditions:
- condition: state
entity_id: sensor.dishwasher_start_time
state: Waiting for new data
- condition: state
entity_id: sensor.next_60deg_batch_end_time
state: Waiting for new data
- condition: state
entity_id: sensor.next_30deg_batch_end_time
state: Waiting for new data
then:
- service: notify.mobile_app_oneplus_7t_pro
metadata: {}
data:
title: EPEX Data not refreshed
message: Is the damn API down again?
else:
- stop: Data refreshed successfully
mode: single
Schau mal die Dokumentation vom Hauptplugin auf Github. Da hab ich ziemlich viel erweitert mit verschieden Beispiele und noch mehr Details in ein Paar “Show and Tell” Diskussion Posts. Vielleicht hilft dir das
Die Beispiele in der Dokumentation sind hauptsächlich zeitbasiert, aber für deiner Anwendungsfall, sollte es eigentlich die Ranks reichen.
Die einfachste Automatisierungsmöglichkeit wäre irgendwas in Richtung “If Rank < 4, then switch Boiler on”.
Guten Abend,
bin wohl leider zu doof für HA.
Habe die EPEX Sensoren drinnen, “start boiler wenn preis am niedrigsten”…
Aber wie kann ich mit dem Signal “Sensor” einen shelly 1pm ansteuern?
bitte um Hilfe, danke
Muss dafür ein Automation schreiben. Ich kann empfehlen, einige YouTube tutorials anzuschauen. Wird mMn viel einfacher
doch nicht, anscheinend keine Auswertung wann der niedirgste Tarif ist, start immer um 0:00:00
kann hier jemand helfen? sync worker problem?
die Preise kommen (richtig), min und max wird angezeigt, jedoch ist die Startzeit immer um 00:00:00
Ich BITTE um eure Hilfe.
Danke
2024-04-05 18:14:47.112 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration epex_spot_sensor which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-05 18:14:47.115 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration scheduler which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-05 18:14:47.118 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration epex_spot which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-05 18:14:47.120 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-05 18:14:55.361 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration ‘hacs’ accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at Issues · hacs/integration · GitHub
2024-04-05 18:14:58.675 ERROR (MainThread) [homeassistant.helpers.template] Template variable error: ‘resp’ is undefined when rendering 'template:
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/template.py”, line 712, in async_render_to_info
render_info._result = self.async_render(
^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/helpers/template.py”, line 588, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: UndefinedError: ‘resp’ is undefined
2024-04-05 18:14:58.701 ERROR (MainThread) [homeassistant.helpers.template] Template variable error: ‘resp’ is undefined when rendering 'template:
@roadjet Please maintain indentation when pasting configuration data. Otherwise the info is unusable.
good evening, can someone please tell me what I’m doing wrong?
I am getting the current daily values and the values for the next day. However, the sensor always wants to start at 0:00:00.
Thanks in advance.
Hey, danke für die Arbeit diese Integration zu bauen. Ich bin bei Awattar und versuche gerade nachzuvollziehen, wie der Nettopreis pro kWh den die Integration ausspuckt zustande kommt um sicherzustellen, dass der Wert wirklich richtig ist.
So wie sich das für mich gerade darstellt, kann der Nettopreis aber eigentlich nicht richtig sein, da die Integration einen absoluten Aufschlag + Surcharge in % + MwSt. draufschlägt. Awattar schlägt aber absolute Beträge nach Jahr / Monat / Verbrauch etc. drauf und ich denke das wird hier nicht berücksichtigt. Liege ich damit richtig?
Bei meiner Rechnung kommt zum Nettpreis für die kWh dazu:
# Zusätzlich kommt dazu (ohne MwSt.)
# --------
# Grundgebühr: 4,88 EUR / Monat
# Netznutzungsentgelt: 4,66 cent/kWh
# Netzverlustentgelt: 0,80 cent/kWh
# Messentgelt: 26,16 EUR / Jahr; 0,071945 EUR / Tag
# Leistungspauschale: 36,- EUR / Jahr; 0,098630 EUR / Tag
# Elektrizitätsabgabe: 0,10 cent/kWh
Hat jemand geschafft das abzubilden bzw. habe ich hier vielleicht irgendwo einen Denkfehler? Mein Ziel wäre schon vorher zu wisssen, was auf der Rechnung stehen wird.
@tom-x1 Hi, die EPEX Spot Integration, wie auch HA selbst, berücksichtigen nur die Kosten pro kWh. Sonstige Kosten (monatlich/jährlich) müsstest Du selbst drauf rechnen.
Danke. Verstehe ich das dann richtig, dass die Optionen für surcharges + Tax in der Integrationskonfiguration für Awattar nicht relevant sind? Per Default sind da bereits Werte hinterlegt welche auf den Nettopreis aufgeschlagen werden.
In Wirklichkeit müssten diese aber bei Awattar alle auf 0 stehen und die Kosten die dazu kommen muss man selbst draufrechnen?
Soweit ich weiss stellt Awattar die Preise ohne Gebühren/Steuer zur Verfügung. Das heisst, falls Du Deinen Nettopreis haben möchtest, muss die Surcharges und Taxes entsprechend konfigurieren.
Hi!
I was able to use ‘powersaver’ nodes with epex data in nodered to get the cheapest hours:
here you have the code:
[{"id":"153f65b59d1179db","type":"ps-strategy-lowest-price","z":"9033a393.73d5a","name":"Lowest 3h Price","fromTime":"22","toTime":"22","hoursOn":"3","maxPrice":"","doNotSplit":false,"sendCurrentValueWhenRescheduling":true,"outputValueForOn":"true","outputValueForOff":"true","outputValueForOntype":"bool","outputValueForOfftype":"bool","outputIfNoSchedule":"false","outputOutsidePeriod":"false","contextStorage":"memory","x":840,"y":840,"wires":[["dea65f8e2836d43a","acabc9ced064f374"],["49416e2450c613bd","c1219a4d08aceda2"],[]]},{"id":"4df208401ec5d0b6","type":"ps-strategy-lowest-price","z":"9033a393.73d5a","name":"Lowest 8Price","fromTime":"22","toTime":"22","hoursOn":"8","maxPrice":"","doNotSplit":false,"sendCurrentValueWhenRescheduling":true,"outputValueForOn":"true","outputValueForOff":"false","outputValueForOntype":"bool","outputValueForOfftype":"bool","outputIfNoSchedule":"true","outputOutsidePeriod":"false","contextStorage":"memory","x":840,"y":1060,"wires":[["b76b45f5e3eac781","7ccdde304b6f55eb"],["94fdbedf12f3f2b1","7ae85dc21f672f4f"],[]]},{"id":"cf6656888c0fe1ac","type":"inject","z":"9033a393.73d5a","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"00 21 * * *","once":true,"onceDelay":0.1,"topic":"","payload":"","payloadType":"date","x":130,"y":760,"wires":[["3af57e696732e4f0"]]},{"id":"1dfd79141aa50b10","type":"function","z":"9033a393.73d5a","name":"convert EPEX data","func":"// Extract the original data array\nlet data = msg.data.attributes.data;\n\n// Initialize the new priceData array\nlet priceData = [];\n\n// Loop through each data point and transform it\nfor (let i = 0; i < data.length; i++) {\n let dataPoint = data[i];\n let newDataPoint = {\n value: dataPoint.price_ct_per_kwh / 100, // Convert price to dollars/kWh\n start: dataPoint.start_time // Use the start_time as is\n };\n priceData.push(newDataPoint);\n}\n\n// Assign the new priceData array to msg.payload.priceData\nmsg.payload = { priceData: priceData };\n\n// Return the modified message\nreturn msg;","outputs":1,"timeout":0,"noerr":0,"initialize":"","finalize":"","libs":[],"x":610,"y":840,"wires":[["4df208401ec5d0b6","153f65b59d1179db"]]},{"id":"3af57e696732e4f0","type":"api-current-state","z":"9033a393.73d5a","name":"","server":"1284480.46e1db8","version":3,"outputs":1,"halt_if":"","halt_if_type":"str","halt_if_compare":"is","entity_id":"sensor.epex_spot_data_price","state_type":"str","blockInputOverrides":false,"outputProperties":[{"property":"payload","propertyType":"msg","value":"","valueType":"entityState"},{"property":"data","propertyType":"msg","value":"","valueType":"entity"}],"for":"0","forType":"num","forUnits":"minutes","override_topic":false,"state_location":"payload","override_payload":"msg","entity_location":"data","override_data":"msg","x":310,"y":840,"wires":[["1dfd79141aa50b10"]]},{"id":"1284480.46e1db8","type":"server","name":"Home Assistant","addon":true,"rejectUnauthorizedCerts":true,"ha_boolean":"","connectionDelay":false,"cacheJson":false,"heartbeat":false,"heartbeatInterval":"","statusSeparator":"","enableGlobalContextStore":false}]