also I see a problem here, the sensor swaps data between daily and monthly???
sensor.energy_consumed 16.28
friendly_name: Daily energy consumption
sensor.energy_consumed_2 7.08
friendly_name: Monthly energy consumption
where do you live timezone?
I am in ROme, put 60, but I sensor gets updated at 2am … ???
UK - GMT timezone.
It seems ok to me.
There again, I am only interested in the real-time consumption.
you are in UK and put 120? I thought GMT should be 0 offset, and Rome (GMT+1) should be 60 …
I’m in Greece, gmt +2 and it does reset at 4am now that I think of it.
Never bothered me tho… 
thought it was default to reset at 4.
I’ll check it out tho. Thanks for the pointer
mmhh so with 60 it updates at 2 with 120 updates at 4am. Strange, should be at 3am … I don’t know
Well the thing of updating at mignight, is just to have a measure from 00:00 to 23:59, as a classic 24 hour day, important maybe if you use other sensors that use the data, otherwise, should be fine too
We have the efergy sensor directly connected to the supply of a ground source heat pump. The new version of Homeassistant gives much better historical graphs. My next “challenge” is to convert the database to MySQL as it runs rather slowly at the moment…
Mines still broken! amended the instant_readings to current_values, now instead of it not giving a reading, and HADashboard showing “nanW” i now get “entity not found: sensor.energy_usage”
my config
- platform: efergy
app_token: myapptokenhere
utc_offset: +10
monitored_variables:
- type: current_values
- type: cost
period: day
currency: $is yours working now?
All 4 of mine working at the moment.
I was concerned as it was showing zero but, as it is now directly connected to the heat pump, the stand-by current of the heat pump is too low to read. It has been working perfectly though.