The docs are never going to match what the code can do and what is in the SNAPSHOTS or in the milestones. Especially if there are new features. You are running with Alpha and Beta level software at that point. The SNAPSHOTS are not even ALPHA. They are literally everything that was merged into the baseline yesterday.
If you want the docs to match, you have to use the releases, not the testing versions.
Have you filed an issue? Have you created a PR to mention this in the docs?
Again, nothing I’ve said applies to newbys. None of it. Not one word. I don’t expect newbes to know this stuff. I do expect them to supply them when asked for them.
And adding logging to a rule doesn’t required any reconfiguration of the loggers config. It’s only if someone might have a bug or misconfiguration on a binding that someone here might ask that user to enable debug or trace logging. No one expects any user, let alone a new user to know to do that or to know how to do that. It’s unreasonable. But if you are an intermediate user who has been using OH for awhile, you should know that logs will be required.
You may not know what the error means but any user can figure out what line of code an error occurs on just by adding logs. Sometimes that’s enough to solve the problem. If not, it certainly will help us solve the problem.
I do not set the bar that high. If you are a newbe, I expect the docs to at least have been consulted and a search of the forum made. That’s it. I don’t expect you to understand what you’ve read. I don’t expect you to know to do anything that I put in the OP above. Newbes get a complete and total pass (until such time that information requests is not given, replies are not ready thoroughly, or there is a refusal to try anything themselves when asked). I’m fine with coddling new users. This stuff is hard even for programmers and technically inclined people.
But if you’ve been using OH for awhile, you should know at least that logs are needed. Most of the time the default settings for the logs generate everything we need to know. I don’t require you to know how to reconfigure the loggers or anything like that. But at least post the logs when asking the question. Especially post logs when asked. I require you to have spent at least a minimum amount of time trying out a few things on your own. I expect you to have a look at the docs. Tried a few experiments. Maybe bothered to look at the actual states of the relevant Items (I can’t count how many problems I’ve helped experienced users with that ended up being because their Items are NULL in the past couple of months).
Frankly, I just don’t have a lot of sympathy for users who can’t manage to find a log file on the file system. If that’s too hard I can’t imagine that user will ever be successful with home automation.
And a final word on the docs. There are far too few contributing to them. Even so, to the best of our knowledge, when OH 3 was released, every word of them were still relevant to OH 3 or were rewritten for OH 3. I can’t speak to the Add-ons docs as those are wholly written by and updated by the maintainers of the individual bindings. But the core docs that are there are all applicable, as written, to OH 3. But docs have bugs and are missing features too. If you find something wrong or missing in the docs, and you are an intermediate to experienced user, file an issue! Even better, make the fix!
