:warning: Leakbot Only Allows One Login:: If you use this integration the token your mobile app is connected to becomes invalid and you get logged out. This happens also if you re-log back into the app it invalidates the token for the integration, however the integration should automatically re-authenticate.
An integration for homeassistant (via HACS) to connect to Leakbot via the leakbot cloud api.
NOTES:
The preferred and easiest way to install this is from the Home Assistant Community Store (HACS). Follow the link in the badge above for details on HACS.
Go to HACS and integraitons, then select to download Leakbot from HACS.
Go to the Home Assistant UI, go to "Configuration" -> "Integrations" click "+" and search for "Leakbot" follow the configuration screen.
If you want to see Beta versions open the Leakbot in HACS, after download, and click the three dots on the top right and select re-download. Here you will se an option to see beta versions.
It is possible to show the info and debug logs for the Leakbot integration, to do this you need to enable logging in the configuration.yaml, example below:
Logs do not remove sensitive information so careful what you share, check what you are about to share and blank identifying information. Note the diagnostic info attempts to redact sensitive information.
logger:
default: warning
logs:
# Log for Leakbot
custom_components.leakbot: info
To install manually, if you really want to: I won't support this.
configuration.yaml
).custom_components
directory (folder) there, you need to create it.custom_components
directory (folder) create a new folder called leakbot
.custom_components/leakbot/
directory (folder) in this repository.I have set this up to be able to run development or testing using Visual Studio Code with Docker or Podman in line with the integration blueprint.
To setup just copy the .devcontainer-template.json to .devcontainer.json
If using podman uncomment the section runArgs to avoid permission issues. Update BUILD_TYPE to "run" to run an instance of Home Assistant and "dev" to do development with pytest.
Debugging in Pythong 3.12 seems slow to startup: To enable vscode debugging a sample /.vscode/launch.json is:
{
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
// Example of Debugging Tests.
"name": "Python: Debug Tests",
"type": "debugpy",
"request": "launch",
"program": "${file}",
"purpose": [
"debug-test"
],
"console": "integratedTerminal",
"justMyCode": true,
"env": {
"PYTEST_ADDOPTS": "--no-cov"
}
},
{
// Example of attaching to local debug server
"name": "Python: Attach Local",
"type": "debugpy",
"request": "attach",
"connect": {
"host": "localhost",
"port": 5678
},
"pathMappings": [
{
"localRoot": "${workspaceFolder}",
"remoteRoot": "."
}
],
}
]
}
If you want to contribute to this please read the Contribution guidelines
Or just raise a feature request, would be useful to have a use-case, what system you have and what you want to get done.