You keep saying that but it’s simply not true and never has been true. The Getting Started tutorial was in the forum because we wanted to make it easier for people who are not proficient with GitHub to contribute. Apparently we shouldn’t have bothered. But the devs have been making *tons of edits to the core docs at next.openhab.org.
This is a perfect example.
The config file for logging is located in the userdata/etc folder (manual setup) or in /var/lib/openhab/etc (apt/deb-based setup).
Attention OH2 users
The format and filename to store log settings has changed. It used to be org.ops4j.pax.logging.cfg in openHAB 2 and became log4j2.xmlin openHAB 3.
and further on down the page is a link to the full docs for how to configure logging.
Maybe actually go look at the docs rather than assuming that we don’t give a s%^&* about docs and have decided that OH 3 doesn’t need them.
No, the developers have been updating then for months as they make changes to the code that require doc changes.
Maybe we do but I suspect that OH will never have documentation that fits your definition. So why harp on it? It doesn’t help anyone and frankly it only serves to destroy the moral of those few volunteers who have spent hours and hours volunteering their time to create and update the docs, as completely inept and inadequate those efforts are apparently in your opinion. It’s not like you’re sleeping to to help.
I know you help out the best ways you can and as much as you can but you don’t have to denigrate the rest of our efforts. We’re doing the best we can too.
That’s correct, it used to display the OH2 docs until that was changed some days ago.
But the following is also true.
So Bruce be more careful with your claims, Rich is right this is destructive to volunteers’ moral.
You should be really in the know when you put up judgements in public.
In the advent of Christmas - greetings to all developers and volunteers!
The direction this thread took has not been my intention. Although as a user one hopes for a stable and well documented package (Christmas again ;-), we have to realize that this is not done by paid staff and all people here are spending amounts of their private time on it.
Leaving this - not the Christmas mood! - behind, maybe one final question: while OH3 is still not released, should I prefer to read the docs directly from github or from next.openhab.org?
Yes, until the release you should look to next.openhab.org for OH 3 info. And if you find something not yet updated to oh 3 that you think should be by this point (I just noticed that the docs for executeCommandLine have but been updated in the Actions page) it wouldn’t hurt to drop a note in the forum. Someone may be working on it already, or it may be something we missed.
But how would I filter for custom strings? How would I suppress, for example, entries containing Unable to connect Netatmo API?
Pretty sure it would be by appending a filter to the correct logger (ThingStatusInfoChangedEvent?), but how is the syntax for that?
And since we are talking syntax / examples - the documentations also mentions Redirect the log to a text file - how is the syntax for that? Would the following write all events related to BindingX into a file called bindingX.log?