Closed stuarts0011 closed 4 years ago
To fix this, in Lines 82 and 87 of sesnor.py change "0" to "1"
What about a way to compare if price displayed is accurate with Post code set/time zone?
PR #12 fixes this.
@lewisbenge this can be closed, fixed in #12
The sensors are displaying the price for the preceding 30 minute period, not the current.
This is also reflected in the fact that there are two attribute readings for the ACTUAL price, but the first is for the preceding period. The second is the correct one and what the sensor should be returning.