When changing the ‘period selected’ on the iOS VRM dashboard. Titel = empty and the description seems to point to a different cell in the background.
Row inserted without an update to the links? @guystewart minor update for the iOS app descriptions
@nickdb is bovenstaande verwacht of afwijkend in de iOS app? Nog iets gevonden mbt de prognoses/forecast: ‘morgen’ had een aantal uur zonder baseload met enkel EVCS in de cijfers. Nu heb ik eerst EVCS gewist op de uren, kan dan echter niet opnieuw de invulvelden omhoog krijgen om base in te voeren.
Wel bij een uur waar nog een heel kleine 0,05 base in stond niet bij alle uren waar niets meer in staat.
heb ik te dikke vingers of is het nu zo gemaakt dat enkel een aanwezige staaf aangepast kan worden. Dus trigger bij selectie, wat niet werkt als er niets meer is?
Hi!
The Dutch VRM translator copied over the wrong text in the translation program, I’ve just fixed it and the correct word should become visible in a couple of minutes.
On the adjustable consumption: you can adjust the consumption even for 0 hours, you can first tap the ‘-’ and then the pop up where you can enter values should appear.
We’ll work on making the adjustable consumption a bit better on mobile, this was the first implementation to see how many people would use it 
Hi @Barbara , is there a specific place to give additional feedback on the detailed forecast. It’s better this way but also somethings to consider or correct in future development. Has VE got a specific topic for this input? (Or colleague to @)
for example suspected EVloading is spread over all hours of a day on SOME days. Instead of being grouped together. I think this forecast is theoretically near impossible since there is a minimum 5A charge limit and the fridge and freezer are definitely running all hours of the day, every day.
Haven’t found out what makes the EVCS forecast spread or bunch together yet.
In aggregate the influence might not be to big, but ‘charging when solar availability is high’ and dynamic price is low isn’t reflected on these days. Not a breaking issue for me just input for improvements towards the future.
Again some strange changes to a manually edited forecast when the algorithm is running over it again it changes the expected loads/consumption. But in doing so it doesn’t follow the human input and adds some on top. It falsely replaces the human input baseload with 100% of load being the (re)newly EVCS load. The one that I previously removed when manually editing. And of course the load in our home ESS will never be only EVCS.
The forecast is better now, still improvements can be made to the ‘if needed add on top, don’t replace manual input’ logic. IMO
