yeah bruce i read that
I have 2 issues after update from 2.5 to 3.0…
I followed the instructions and all configurations,items,influx database were moved ok.
I can see al info running through grafana server but…
if I’m logging at http.//localhost:8080 I can see the old dashboad vers 2.5.9 and without any items,things,rules, all gone.
But I removed all directoy belong to openhab2, why do I have still the old dashboard?
tks
I don’t recognise an answer to this. From my point of view there is currently no select all feature. In addition tehre is no copy feature to copy and thing or items as a base for a new thing/item.
The only was to speed it up is to click faster 
Sounds to me as if you still have your openhab2 instance running in parallel - can you rule this out?
We are still waiting for something that can be included, but instead of helping moving things forward, Scott seems to prefer to play dead and not respond anymore. Maybe just to my questions, so I will stop trying now and focus instead on the hundreds of other maintainers who contribute valuable features and are waiting patiently since months for reviews and feedback.
checked.
no one software related to openhub2 or coming from the old directories is running.
only openhab service… and I rebooted the server after installation
cleaned cache of browsers
maybe during the installation not all files were replaced.
yes, i store values and restore on startup !
Strategies {
everyMinute : "0 * * * * ?"
everyHour : "0 0 * * * ?"
everyDay : "0 0 0 * * ?"
default = everyChange
}
Items {
* : strategy = everyMinute, restoreOnStartup
}
Thanks @4u2fast, By now, althought not 100% confirmed, it seems that this can be the origin of the problem, you can follow the Github issue that was previously mentioned in that thread.
Is the next milestone release planned for early next month @Kai? It would be nice to know for everyone working on fixes or waiting for them to be part of a milestone release.
No date set yet. Just tell me once you think enough fixes have piled up .
What might make sense is to do the 2.5.10 patch release this weekend (Oct 25) and the 3.0.0.M2 the week after (Nov 1) - that will keep me busy. Wdyt?
Sounds good to me because I think a lot will be fixed by that time!
Heads up for everyone having trouble with rrd4j error messages when restoring values, we should soon have a fix in place with https://github.com/openhab/openhab-addons/pull/8815.
What’s the approved successor of expire binding? Just noticed my countdown timers were no longer working and finally figured out it was because of expire being 1.0.
It will be replaced with equivalent functionality in openhab-core:
Thank you. I will avoid recoding everything and move back to OH2.5 for the moment first in that case.
I do support a better implementation of timers raised by boc-tothefuture though. Perhaps the OH1 way of creating a dummy timer item and separate rule for a simple functionality of countdown timer is a little bit outdated.
He didn’t. What you linked to is a statement from him before I asked the question. My question requires only a yes/no answer and I would assume that is possible even when being busy with other projects, if there is any will in resolving the situation.
Do you happen to have a link to that proposal? Thanks 
It’s right at the end of the github issue for the expire binding. Since the expire binding is used as a middleman anyway, might as well move it into the rules engine entirely while it’s being refactored.