Version 2026-09-25b. This is the text you accept before ElectriFix will touch anything to do with a lock, alarm, camera, gate, garage door, valve or water heater.
By default this service will not go anywhere near those devices. It refuses, in code, before anything is proposed. That default is right for almost every job — but not for the customer who wants driveway detection, or who is having trouble setting up a lock. This waiver is how you lift the default for your job only. It applies to this one job and disappears when the job ends.
ElectriFix writes and repairs configuration: automations, references to entities, integration settings, reloads. Every change is still shown to you as a plan first, still ticked by you one change at a time, and still applied through the same snapshot-and-revert safety cycle as every other change.
ElectriFix will never operate your security devices. It will not lock or unlock a lock, arm or disarm an alarm, open a garage door or a gate, turn a camera on or off, or move a valve — not as part of a fix, and not to test one. This is enforced in code, not by policy, and accepting this waiver does not change it.
How far that check reaches. It covers what a change does directly, and what it does one step removed — if a change runs one of your scripts, scenes or automations, we read that too and refuse it on the same grounds. What it does not cover is what your own existing automations do in response to a change afterwards: those are yours, they run on their own triggers, and nothing we can read tells us what they will do next. That is the honest limit of what this check can see, stated plainly rather than left for you to discover.
ElectriFix cannot pair a device, enter a password or a credential, or set up an account with a manufacturer. Pairing and credentials are out of scope: they need someone at the property with the device in their hands. If that is what your problem needs, the honest answer is that this service cannot do it remotely.
After any change, you test the device yourself. Walk to the door, try the lock, watch the camera, listen for the siren. Do not rely on a security device until you have. A change that reads as applied is not the same as a device that works, and only you are standing in front of it.
ElectriFix is not liable for how the device itself operates — a lock that does not lock, an alarm that does not sound, a camera that does not record. ElectriFix is responsible for the configuration it writes and for reverting a change that breaks something, which is what the safety guard is for. Nothing here limits any right or remedy you have under the Australian Consumer Law or any other law that cannot lawfully be excluded.
You confirm that you own or control these premises and this Home Assistant system, and that you are entitled to authorise changes to its security devices. If you are a tenant, a housemate or a guest, ask the person who is.
Before this is lifted you go through these steps, in order, on your job page. Each one proves something different, and each is checked on the server:
We record when you accepted, from which address and browser, which version of this text you read, and what satisfied the second step: the fingerprint of your new token, or, on ElectriFix Connect, that the integration was connected. We never record a token itself, and no token is ever sent to an AI model.