Ciao! Io ho provato ad installarla ma non la trovo da nessuna parte,non trovo dove configurarla…un fantasma in pratica 
Tu ci sei riuscito a farla funzionare?
Ciao, si, l’ho installata e funziona a meraviglia.
Devi aggiungere in HACS la repository,come da istruzioni:
Installare usando HACS tramite il menu con i tre puntini nell’angolo in alto a destra e scegliendo Add custom repository e aggiungendo l’URL GitHub - virtualdj/pun_sensor: Prezzi PUN del mese - Home Assistant Integration alla lista.
Ciao
Andrea
Dopo aver installato con hacs, e riavviato, bisogna ancora andare nelle integrazioni e aggiungerla (con le opzioni che si desidera) da lì.
A quel punto compaiono le entità correlate.
esatto, era proprio questo passaggio che mi mancava
comunque neanche questo dà il valore che voglio io…
sto provando a sniffare la pagina che interessa a me e sembra funzionare 
sono riuscito a prendere tutte le medie mensili (creando 12 sensori), ora devo capire come creare un ulteriore sensore me mi vada a leggere il valore del sensore del mese corrente.
spero di essermi spiegato
Onestamente no, non ti seguo.
Sicuramente avrai un buon motivo per acquisire tutte le medie mensili passate (per curiosità chiedo: quale motivo?).
Peró la media corrente che vedo io è esattamente quella del sito che hai riportato tu.
Hai spuntato la casella in fase di configurazione?
Cito la pagina del dev:
Se la casella di controllo Usa solo dati reali ad inizio mese è attivata all’inizio del mese quando non ci sono i prezzi per tutte le fasce orarie questi vengono disabilitati (non viene mostrato quindi un prezzo in €/kWh finché i dati non sono sufficiente); nel caso invece la casella fosse disattivata (default) nel conteggio vengono inclusi gli ultimi giorni del mese precedente in modo da avere sempre un valore in €/kWh.
Il motivo che mi son preso tutti i mesi è per il semplice fatto che una volta che ho capito come fare ,me li sono portati tutti in HA, e poi li mi sarà più facile gestirli.
In realtà a me ne basterebbero due… O addirittura uno, ma non saprei come far cambiare la lettura al cambio mese.
Tipo adesso a me interessa avere la media di giugno (che ovviamente è parziale) per avere un idea di come sta andando il mercato , e la media di maggio per calcolare i costi del mese appena passato.
No, quella casella non ho provato a spuntarla… Questa sera ci provo.
A te escono esattamente le medie della mia pagina?
Confermo che una volta spuntata quella casella sia l’altro giono che oggi il sensore “sensor.pun_mono_orario” mi da lo stesso valore che leggo per il mese di Giugno alla pagina
https://www.mercatoelettrico.org/It/Statistiche/ME/DatiSintesi.aspx
Stessi valori fino all’ultimo decimale.
Per il fatto di avere il valore del mese precedente, forse si riesce a farlo semplicemente con un helper…ma non c’ho ancora pensato…
Ciao
1 Like
ottimo, allora abbandono la mia strada e uso quell’integrazione. grazie
1 Like
Let me share for Turkish energy prices:
Water (for Istanbul): (in multiscrape.yaml)
- resource: https://www.iski.gov.tr/web/tr-TR/musteri-hizmetleri/su-birim-fiyatlari1
scan_interval: 28800
timeout: 15
sensor:
- unique_id: water_low_price
name: Water Low Price
unit_of_measurement: "TL/m3"
icon: mdi-water
select: "table > tbody > tr:nth-child(3) > td:nth-child(2) > p"
value_template: '{{ value.split("\n\t\t\t\t\t")[1].replace(",",".") }}'
- unique_id: water_high_price
name: Water High Price
unit_of_measurement: "TL/m3"
icon: mdi-water
select: "table > tbody > tr:nth-child(4) > td:nth-child(2) > p"
value_template: '{{ value.split("\n\t\t\t\t\t")[1].replace(",",".") }}'
Electricity (all country across) (in multiscrape.yaml using multiscrape)
- resource: https://www.encazip.com/elektrik-fiyatlari
scan_interval: 28800
timeout: 15
sensor:
- unique_id: elk_aktif_enerji_dusuk_birim_fiyatı
name: Elektrik Aktif Enerji Düsük Birim Fiyatı
unit_of_measurement: "TL/kwh"
icon: mdi-home-lightning-bolt
select: ".content-table > tbody:nth-child(2) > tr:nth-child(1) > td:nth-child(2)"
value_template: '{{ value.split(" TL/kWh")[0] }}'
- unique_id: elk_aktif_enerji_yuksek_birim_fiyatı
name: Elektrik Aktif Enerji Yüksek Birim Fiyatı
unit_of_measurement: "TL/kwh"
icon: mdi-home-lightning-bolt
select: ".content-table > tbody:nth-child(2) > tr:nth-child(2) > td:nth-child(2)"
value_template: '{{ value.split(" TL/kWh")[0] }}'
- unique_id: elk_dagitim_bedeli_birim_fiyatı
name: Elektrik Dağıtım Bedeli Birim Fiyatı
unit_of_measurement: "TL/kwh"
icon: mdi-home-lightning-bolt
select: ".content-table > tbody:nth-child(2) > tr:nth-child(1) > td:nth-child(3)"
value_template: '{{ value.split(" TL/kWh")[0] }}'
Gas ( for only igdas istanbul) (in sensor.yaml using rest)
make sure you enter your installation_number and contrat_number
- platform: rest
resource_template: https://www.igdas.istanbul/WebServices/duzeltmekatsayisi.aspx?inst={installation_number}&contract={contrat_number}&date1={{(now()-timedelta(days=1)).strftime('%Y-%m-%d')}}&date2={{now().strftime('%Y-%m-%d')}}
scan_interval: 3600
name: Gaz Fiyatlar
value_template: "Gas_Price"
json_attributes:
- UstIsilDeger
- KFaktoru
- OrtalamaBirimFiyat
- ErrorCode
(Sorry for resuscitating an old thread 
)
I’m using the integration and I really like it, but I have the need to pull the hourly PUN values to perform (through another add-on) some energy optimization.
So the multiscrape approach is what I needed and I found the example above really helpful.
If compared to that I’m using the XML approach as it allows me to easily query any day by relying on templates.
I’m pasting my solution here if anybody else needs it and linking the thread were I got some support on how to use the multiscrape (maybe there will be some evolution in the discussion and it may still be useful).
multiscrape:
- resource_template: 'https://www.mercatoelettrico.org/It/WebServerDataStore/MGP_Prezzi/{{ as_timestamp(now()) | timestamp_custom("%Y%m%d", True) }}MGPPrezzi.xml'
scan_interval: 3600
parser: 'lxml'
name: 'PUN oggi'
button:
unique_id: 'aggiorna_misure_pun_oggi'
name: 'Aggiorna misure PUN oggi'
log_response: true
form_submit:
submit_once: false
resource: 'https://www.mercatoelettrico.org/It/Tools/Accessodati.aspx'
select: '#form1'
input:
'ctl00$ContentPlaceHolder1$CBAccetto1': 'on'
'ctl00$ContentPlaceHolder1$CBAccetto2': 'on'
'ctl00$ContentPlaceHolder1$Button1': 'Accetto'
input_filter:
- 'ctl00$ContentPlaceHolder1$Button2'
- 'ctl00$vai'
- 'ctl00$LinkButton2'
- 'ctl00$LoginButton'
sensor:
- select: 'NewDataSet:nth-child(1) > Prezzi:nth-child(2) > PUN:nth-child(4)'
name: 'PUN oggi 00'
unique_id: 'pun_oggi_00'
icon: 'mdi:currency-eur'
unit_of_measurement: '€/kWh'
value_template: '{{ value | replace (",", ".") |float | int / 1000}}'
- select: 'NewDataSet:nth-child(1) > Prezzi:nth-child(3) > PUN:nth-child(4)'
name: 'PUN oggi 01'
unique_id: 'pun_oggi_01'
icon: 'mdi:currency-eur'
unit_of_measurement: '€/kWh'
value_template: '{{ value | replace (",", ".") |float | int / 1000}}'
2 Likes
“I have a photovoltaic system, and I need to assess whether it’s worthwhile to consume the energy myself or feed it into the grid, especially if there will be very low prices the following day. Since the GME (Italian Wholesale Electricity Market) publishes the “Day-Ahead Market Prices (MGP)” around 1:00 PM, I would need to create sensors that fetch data for the next day like this:”
resource_template: 'https://www.mercatoelettrico.org/It/WebServerDataStore/MGP_Prezzi/{{ (as_timestamp(now()) + (24*3600)) | timestamp_custom("%Y%m%d", True) }}MGPPrezzi.xml'
# PUN RID TOMORROW
- resource_template: 'https://www.mercatoelettrico.org/It/WebServerDataStore/MGP_Prezzi/{{ (as_timestamp(now()) + (24*3600)) | timestamp_custom("%Y%m%d", True) }}MGPPrezzi.xml'
scan_interval: 3600
parser: 'lxml'
name: 'PUN Domani'
button:
unique_id: 'aggiorna_pun_domani'
name: 'Aggiorna PUN domani'
log_response: true
form_submit:
submit_once: false
resource: 'https://www.mercatoelettrico.org/It/Tools/Accessodati.aspx'
select: '#form1'
input:
'ctl00$ContentPlaceHolder1$CBAccetto1': 'on'
'ctl00$ContentPlaceHolder1$CBAccetto2': 'on'
'ctl00$ContentPlaceHolder1$Button1': 'Accetto'
input_filter:
- 'ctl00$ContentPlaceHolder1$Button2'
- 'ctl00$vai'
- 'ctl00$LinkButton2'
- 'ctl00$LoginButton'
sensor:
- select: 'NewDataSet:nth-child(1) > Prezzi:nth-child(2) > PUN:nth-child(4)'
name: 'PUN Domani Ora 00'
unique_id: 'tomorr_energy_pun_0'
icon: 'mdi:currency-eur'
unit_of_measurement: '€/kWh'
value_template: '{{ value | replace (",", ".") |float | int / 1000}}'
- select: 'NewDataSet:nth-child(1) > Prezzi:nth-child(3) > PUN:nth-child(4)'
name: 'PUN Domani Ora 01'
unique_id: 'tomorr_energy_pun_1'
icon: 'mdi:currency-eur'
unit_of_measurement: '€/kWh'
value_template: '{{ value | replace (",", ".") |float | int / 1000}}'
# create sensor for tomorrow RID hour Calabria
- sensor:
- name: "MGP PO Calabria Tomorrow"
unit_of_measurement: "€/kWh"
unique_id: energy_pun_tomorrow
icon: mdi:currency-eur
state: >
{{ states('sensor.tomorr_energy_pun_' + (now().hour | string)) }}
ps. Today’s sensor code is the same as yours
1 Like
If you need to optimize the charge/discharge cycle of your battery, depending on costs, load, PV prod and so on I would suggest you to give a try to this add-on, I’m already playing with:
For more details about how to use it you can have a look at this thread (not add-on specific but everything you see there is valid for it as well - if you use the add-on, of course):
https://community.home-assistant.io/t/emhass-an-energy-management-for-home-assistant/338126
Interesting, for the moment I’ve applied an average cost difference between buying and “ritiro dedicato (RID)” sales prices; I’ll have a look to see if it’s more precise and allows me to make this little step automatic.
GSE RID price is calculated in this way: the Hourly Zonal Price (PO), which is the price in the electricity market and depending on the time at which the energy is fed grid and the market zone in which the facility is located, so RID is multiplied by kWh fed to grid.
This in my HA:
1)
# energy meter fed to grid hourly
hourly_energy_grid_exported:
source: sensor.grid_exported
cycle: hourly
# RID Price zone Calabria
multiscrape:
- resource_template: 'https://www.mercatoelettrico.org/It/WebServerDataStore/MGP_Prezzi/{{ as_timestamp(now()) | timestamp_custom("%Y%m%d", True) }}MGPPrezzi.xml'
scan_interval: 3600
parser: 'lxml'
name: 'PUN oggi'
button:
Nodered at xx:59:58 of every hour Every hour will multiply RID by kWh.
[{"id":"d8ccf8aecbf986ec","type":"tab","label":"Flow RID CALA","disabled":false,"info":"","env":[]},{"id":"0e6fc28155b6e376","type":"api-current-state","z":"d8ccf8aecbf986ec","name":"gmepo","server":"1c37c350.3f926d","version":3,"outputs":1,"halt_if":"","halt_if_type":"str","halt_if_compare":"is","entity_id":"sensor.mgp_pun_attuale","state_type":"num","blockInputOverrides":false,"outputProperties":[{"property":"payload","propertyType":"msg","value":"","valueType":"entityState"},{"property":"topic","propertyType":"msg","value":"input_1","valueType":"str"}],"for":"0","forType":"num","forUnits":"minutes","override_topic":false,"state_location":"payload","override_payload":"msg","entity_location":"data","override_data":"msg","x":310,"y":40,"wires":[["df859bcd22d81e32"]]},{"id":"a12479a3c1d97fd0","type":"api-current-state","z":"d8ccf8aecbf986ec","name":"energy","server":"1c37c350.3f926d","version":3,"outputs":1,"halt_if":"","halt_if_type":"str","halt_if_compare":"is","entity_id":"sensor.hourly_energy_grid_exported","state_type":"num","blockInputOverrides":false,"outputProperties":[{"property":"payload","propertyType":"msg","value":"","valueType":"entityState"},{"property":"topic","propertyType":"msg","value":"input_2","valueType":"str"}],"for":"0","forType":"num","forUnits":"minutes","override_topic":false,"state_location":"payload","override_payload":"msg","entity_location":"data","override_data":"msg","x":310,"y":140,"wires":[["df859bcd22d81e32"]]},{"id":"ed370677f6b728e9","type":"function","z":"d8ccf8aecbf986ec","name":"function 1","func":"msg.payload = (msg.payload.input_1 * msg.payload.input_2).toFixed(4);\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":540,"y":180,"wires":[["f76cebf3f1c4efb9","c153013cd9ecd1e4"]]},{"id":"f76cebf3f1c4efb9","type":"debug","z":"d8ccf8aecbf986ec","name":"debug 2","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"payload","targetType":"msg","statusVal":"","statusType":"auto","x":640,"y":40,"wires":[]},{"id":"df859bcd22d81e32","type":"join","z":"d8ccf8aecbf986ec","name":"","mode":"custom","build":"object","property":"payload","propertyType":"msg","key":"topic","joiner":"\\n","joinerType":"str","accumulate":true,"timeout":"","count":"2","reduceRight":false,"reduceExp":"","reduceInit":"","reduceInitType":"","reduceFixup":"","x":470,"y":100,"wires":[["ed370677f6b728e9"]]},{"id":"c153013cd9ecd1e4","type":"ha-sensor","z":"d8ccf8aecbf986ec","name":"RIDCALA","entityConfig":"288828a3536cdefe","version":0,"state":"payload","stateType":"msg","attributes":[{"property":"last_update","value":"","valueType":"date"}],"inputOverride":"allow","outputProperties":[],"x":740,"y":120,"wires":[["43b86b7a647ad72f"]]},{"id":"43b86b7a647ad72f","type":"debug","z":"d8ccf8aecbf986ec","name":"debug 3","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","statusVal":"","statusType":"auto","x":900,"y":120,"wires":[]},{"id":"e76bf60247ce0fb0","type":"cronplus","z":"d8ccf8aecbf986ec","name":"Every 59min","outputField":"payload","timeZone":"","persistDynamic":false,"storeName":"","commandResponseMsgOutput":"output1","outputs":1,"options":[{"name":"schedule1","topic":"topic1","payloadType":"default","payload":"","expressionType":"cron","expression":"58 59 * * * *","location":"","offset":"0","solarType":"all","solarEvents":"sunrise,sunset"}],"x":110,"y":60,"wires":[["a12479a3c1d97fd0","0e6fc28155b6e376"]]},{"id":"0be4d7a852d0df17","type":"inject","z":"d8ccf8aecbf986ec","name":"Test","props":[{"p":"debug","v":"true","vt":"bool"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","x":110,"y":200,"wires":[["0e6fc28155b6e376","a12479a3c1d97fd0"]]},{"id":"1c37c350.3f926d","type":"server","name":"Home Assistant","version":5,"addon":true,"rejectUnauthorizedCerts":true,"ha_boolean":"y|yes|true|on|home|open","connectionDelay":true,"cacheJson":true,"heartbeat":false,"heartbeatInterval":"30","areaSelector":"id","deviceSelector":"id","entitySelector":"id","statusSeparator":"at: ","statusYear":"hidden","statusMonth":"short","statusDay":"numeric","statusHourCycle":"h23","statusTimeFormat":"h:m","enableGlobalContextStore":true},{"id":"288828a3536cdefe","type":"ha-entity-config","server":"1c37c350.3f926d","deviceConfig":"3cf3d12d268fc427","name":"calcolo rid orario","version":"6","entityType":"sensor","haConfig":[{"property":"name","value":"calcolo rid orario"},{"property":"icon","value":""},{"property":"entity_category","value":""},{"property":"entity_picture","value":""},{"property":"device_class","value":"monetary"},{"property":"unit_of_measurement","value":"EUR"},{"property":"state_class","value":"measurement"}],"resend":false,"debugEnabled":false},{"id":"3cf3d12d268fc427","type":"ha-device-config","name":"calcolo rid orario","hwVersion":"","manufacturer":"Node-RED","model":"","swVersion":""}]
many thanks I will try this component 
1 Like
I may be wrong but I fear it’s not just the Zonal Price, updated hour by hour and day by day, but it’s rather the average over the month, per zone, per band (now I remember why I applied an average delta using current PUN as a basis, instead of pulling from the XML).
Have a look here:
- https://www.gse.it/servizi-per-te/fotovoltaico/ritiro-dedicato/documenti
- https://www.gse.it/documenti_site/Documenti%20GSE/Servizi%20per%20te/RITIRO%20DEDICATO/Altri%20contenuti/Prezzi%20medi%20RID%20aggiornato%2008-2023.pdf
But please let me know if you have evidence/knowledge I’m wrong.
1 Like
In Italy we have 2 methods of compensating for energy fed to the grid:
- RID
- SSP
1. RID: PO x kWh fed to grid
I took my GSE RID contract as an example (the data was taken from the GSE website):
I took last invoice of august, year 2023:
kWh fed to grid: 307
Total payment by GSE: € 28,24 (VAT excl.) (the screenshot is for last august day: 31)
so, in GSE website i downloaded billing details:
as you can see for each day kWh fed to the grid is multiplied for PO price zone and every hour of every day matches PO GME price data (august, 31, 2023 PO Calabria in my example pictures)
On may 2023 I bought a Tesla Model 3 so energy fed to grid is very low .
2. For SSP (Scambio Sul Posto) price calculation is quite different and a bit more complicated.
1 Like
I verified and you are right, but (at least for me) I think you may also need to consider the loss coefficient (coeff_perd = 1,052).
This is the formula I found in my detailed RID payments:
energia * coeff_perd * max(prz_ora;0)
where prz_ora is, as you said, the PUN of your geographic area.
If I sum the results of the formula, day by day, hour by hour, I get the amount I receive.
1 Like
Thank you both for the very useful inputs. I’ve successfully added the MULTISCRAPE integration from HACS and the code in configuration.yalm (see below).
Just one technical question: I’ve copied/pasted your code " - select: ‘NewDataSet:nth-child(1) > Prezzi:nth-child(2) > PUN:nth-child(4)’", I understood how to change the hour (increase the number after Prezzi:nth-child( ) , but how to change the zone? Currently all the values are the same, but maybe it will be different in the future…
Another question, why did you search for the day doc named of the day after? (as_timestamp(now()) + (24*3600) ) ?
Example: to calculate the price of the energy on at 00:30 on 29-01-2024 I should look in the document named 29-01-2024 and in the time range 1:
<Prezzi>
<Data>20240129</Data>
<Mercato>MGP</Mercato>
<Ora>1</Ora>
<PUN>75,110000</PUN>
Am I right?
Thank you again,
Andrea
-sensor:
# create sensor for tomorrow RID hour
- platform: template
sensors:
mgp_po_tomorrow:
friendly_name: "MGP PO tomorrow"
unique_id: "MGP PO tomorrow"
value_template: "{{ (states('sensor.tomorr_energy_pun_' + (now().hour | string))) }}"
unit_of_measurement: €/kWh
multiscrape:
# PUN RID TOMORROW
- resource_template: 'https://www.mercatoelettrico.org/It/WebServerDataStore/MGP_Prezzi/{{ (as_timestamp(now()) + (10)) | timestamp_custom("%Y%m%d", True) }}MGPPrezzi.xml'
scan_interval: 3600
parser: 'lxml'
name: 'PUN Domani'
button:
unique_id: 'aggiorna_pun_domani'
name: 'Aggiorna PUN domani'
log_response: true
form_submit:
submit_once: false
resource: 'https://www.mercatoelettrico.org/It/Tools/Accessodati.aspx'
select: '#form1'
input:
'ctl00$ContentPlaceHolder1$CBAccetto1': 'on'
'ctl00$ContentPlaceHolder1$CBAccetto2': 'on'
'ctl00$ContentPlaceHolder1$Button1': 'Accetto'
input_filter:
- 'ctl00$ContentPlaceHolder1$Button2'
- 'ctl00$vai'
- 'ctl00$LinkButton2'
- 'ctl00$LoginButton'
sensor:
- select: 'NewDataSet:nth-child(1) > Prezzi:nth-child(2) > PUN:nth-child(4)'
name: 'PUN Domani Ora 00'
unique_id: 'tomorr_energy_pun_0'
icon: 'mdi:currency-eur'
unit_of_measurement: '€/kWh'
value_template: '{{ value | replace (",", ".") |float | int / 1000}}'
- select: 'NewDataSet:nth-child(1) > Prezzi:nth-child(3) > PUN:nth-child(4)'
name: 'PUN Domani Ora 01'
unique_id: 'tomorr_energy_pun_1'
icon: 'mdi:currency-eur'
unit_of_measurement: '€/kWh'
value_template: '{{ value | replace (",", ".") |float | int / 1000}}'
- select: 'NewDataSet:nth-child(1) > Prezzi:nth-child(4) > PUN:nth-child(4)'
name: 'PUN Domani Ora 02'
unique_id: 'tomorr_energy_pun_2'
icon: 'mdi:currency-eur'
unit_of_measurement: '€/kWh'
value_template: '{{ value | replace (",", ".") |float | int / 1000}}'
That’s the “tricky” part of multiscrape. You have to look into the CSS code to retrieve that; try to follow the instructions of the component here.
Once you find the right column you can select the rows by increasing the index (or inspect all of them - as you prefer).
You are right. We just needed tomorrow’s prices as well.
1 Like
I need today’s and tomorrow’s prices for the RID in the Calabria area (for my PV, to calculate the price of the energy fed into the grid). Tomorrow’s prices are uploaded by the GME at 14:00 every day so I can visualize them on the dashboard 24 hours in advance. It’s a pity that the limitations of Home Assistant can’t create a sensor with future data and therefore I can’t represent them graphically, but to manage they are more than fine 
to scrape the hourly PUN instead I use this code (used for the energy purchased and not for the energy sold as the RID):
# MGP PUN Giornaliero
- resource: "https://www.mercatoelettrico.org/it/default.aspx"
name: PUN MGP Daily Average
scan_interval: 3600
log_response: true
form_submit:
submit_once: True
resource: "https://www.mercatoelettrico.org/It/Tools/Accessodati.aspx?ReturnUrl=%2fIt%2fdefault.aspx"
select: "#form1"
input:
"ctl00$ContentPlaceHolder1$CBAccetto1": "on"
"ctl00$ContentPlaceHolder1$CBAccetto2": "on"
"ctl00$ContentPlaceHolder1$Button1": "Accetto"
input_filter:
- "ctl00$ContentPlaceHolder1$Button2"
- "ctl00$vai"
- "ctl00$LinkButton2"
- "ctl00$LoginButton"
sensor:
- select: "#ContentPlaceHolder1_lblMedia"
name: "PUN INDEX daily average"
unique_id: daily_pun_avg
unit_of_measurement: "€/kWh"
icon: mdi:transmission-tower-import
device_class: monetary
state_class: measurement
value_template: '{{ (value | replace (",", ".") | float / 1000) | round(6) }}'
on_error:
value: last
and for the single-hour PUN on a monthly basis I use this (it is used to calculate the cost of the PUN on your bill if you have a single-hour rate):
multiscrape:
# MGP PUN Mensile
- resource: "https://www.mercatoelettrico.org/it/Statistiche/ME/DatiSintesi.aspx"
name: PUN MPG
scan_interval: 3600
log_response: true
form_submit:
submit_once: True
resource: "https://www.mercatoelettrico.org/It/Tools/Accessodati.aspx?ReturnUrl=%2fIt%2fStatistiche%2fME%2fDatiSintesi.aspx"
select: "#form1"
input:
"ctl00$ContentPlaceHolder1$CBAccetto1": "on"
"ctl00$ContentPlaceHolder1$CBAccetto2": "on"
"ctl00$ContentPlaceHolder1$Button1": "Accetto"
input_filter:
- "ctl00$ContentPlaceHolder1$Button2"
- "ctl00$vai"
- "ctl00$LinkButton2"
- "ctl00$LoginButton"
sensor:
- select: "#ContentPlaceHolder1_GridView2_lblMedia2_1"
name: "January"
unique_id: jan_pun_avg
unit_of_measurement: "€/kWh"
icon: mdi:transmission-tower-import
device_class: monetary
state_class: measurement
value_template: '{{ (value | replace (",", ".") | float / 1000) | round(6) }}'
on_error:
value: last
- select: "#ContentPlaceHolder1_GridView2_lblMedia2_2"
name: "February"
unique_id: feb_pun_avg
unit_of_measurement: "€/kWh"
icon: mdi:transmission-tower-import
device_class: monetary
state_class: measurement
value_template: '{{ (value | replace (",", ".") | float / 1000) | round(6) }}'
on_error:
value: last
- select: "#ContentPlaceHolder1_GridView2_lblMedia2_3"
name: "March"
unique_id: mar_pun_avg
unit_of_measurement: "€/kWh"
icon: mdi:transmission-tower-import
device_class: monetary
state_class: measurement
value_template: '{{ (value | replace (",", ".") | float / 1000) | round(6) }}'
on_error:
value: last
