This is a duplicate complaint to the one I raised here about 2 months ago, to which I have had zero feedback so far by the way... Today just after 1800, the Wellington price spiked. I understand that will happen.
I have your app set to notify me about these price changes, and it DIDNT WORK.
I get regular notifications about Co2 emissions, which are interesting and prove that the notifications can work, but in the absence of the really important price notifications are a bit of a slap in the face. I subscribe to a 3rd party price notification system for price spikes, as I don't trust your app given my last piece of ignored feedback, and it did email me the information below.
When will your notification system be rendered reliable?
I suggest to you, that to continue to offer this service when it patently doesn't work, is at least misleading and could be exposing Flick to an increase of poor customer experience feedback (like this one) , if not legal issues.
Node watch email below:
At 18:40 on 16/05/2016, the 5-minute electricity price at TKR0331 rose above $140.00/MWh (from $116.86 to $243.45/MWh) (If you no longer wish to receive emails about this node and price threshold, follow this link: http://www.nodewatch .......... Warm Regards, The Nodewatch Team
Let's see what they come up with...
I think it's the fact I got no useful feedback apart from denials last time that gets my goat ...
Had a really good phone call from one of the Flick management this afternoon which I appreciated. Flick acknowledged to me that it didn't get notifications to all its Wellington customers affected by the price spike due to a number or reasons. The price for some customers got close, but didn't exceed the original threshold they had in place for sending notifications . This threshold was changed late this afternoon to provide a more meaningful alert in most cases.
I didn't realise that although nodewatch uses a 5 minute integration period to asses the spot price, flick uses the less volatile 30 minute period. This means that there will be times that nodewatch reacts quickly to a price change, and flick doesn't, and often doesn't need to as the price will have levelled out.
Great to get some meaningful and intelligent dialog on the subject.
I had the same call, very useful. Also apparently prices spiked on one Wellington node but not others, so there was variable data. As has been said before Flick is pretty new and is learning, their tools will evolve over time.
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.