End-user documentation

[Mike Lambert]

I have completed a new build, and am obliged to document "how to operate Loxone" in a House User Manual. I was horrified to learn that Loxone produces absolutely NO end-user manuals or documentation, saying (with some truth) that the system and user interface can be configured any-which-way. But there doesn't even seem to be any consistent definition of basic terms, or explanation of manual v automatic v autopilot modes in straight-forward English.

Has anyone been obliged to create such instructions? If they could share them, even better.

Thanks in advance.

Mike

[Harry Phelps]

I have never done it for Loxone but have for Crestron, you're on your own with them as well! I would C&P liberally from the website and try to keep things as generic as possible in order to be able to use this one as the basis for the next.

[Mike Lambert]

On Monday, 2 October 2017 18:27:40 UTC+1, Mike Lambert wrote:

[Clegger]

I believe you only need to document for the end user, so I'd keep it very simple. A couple of paragraphs overview of the system and then a brief explanation of how each system (eg, heating, lighting) works should be fine.

I don't think you need to document how every room works - just a couple of examples should be fine.

Is this something your building control officer seems particularly interested in? If not, I doubt they'll much care. Mine's given us a final list of what he wants from us for signoff and he hasn't even mentioned documentation.

[Julián Medrano Silvestre]

Write me by mail and I will send you an example (in Spanish) with the end-user manual that I always give with all my projects.
I also make 2 or 3 presentations to my customers to show them the basics about the system.
My mail: medranotele...@gmail.com
Regards

[Mike Lambert]

Thanks for your help and advice.

On Monday, 2 October 2017 18:27:40 UTC+1, Mike Lambert wrote: