The only contact channel for this site is email. There is no phone number, no postal address and no contact form, because a form would mean storing what you type.
Email: [email protected]
What to write about
- A recipe that failed in a real house. Include the hub you run, the device model, and what the log showed. Corrections that come with a log are usually published as an update to the affected recipe.
- A hardware model we should name or drop. If a device in a recipe has been discontinued, silently revised, or behaves differently on current firmware, say so.
- A correction to the YAML. Automation dialects drift between hub versions. If a payload no longer validates on your version, send the version number and the error.
- Security reports. If you find something exploitable in how this site or its generated figures are served, write with enough detail to reproduce it. Please do not test against anything you do not own.
- Advertising and legal enquiries. Anything about the advertising served on this site, privacy requests, or rights holders' notices should go to the same address and will be routed to the person who handles it.
What we cannot help with
We cannot remotely troubleshoot your wiring, size a circuit for you, or tell you whether a specific installation complies with your local code. Those questions need a licensed electrician who can see the installation. We also cannot recover an automation that already ran and did something unwanted — that is what the fail-safe and the manual override in each recipe are for.
Response times
This is a small editorial operation, so replies are not instant. Corrections to a published recipe are usually handled within a few working days; general questions can take longer. Advertising and legal correspondence is prioritised.