Skip to main content

franklinwh-ha-notify

Home Assistant notifications with buttons, shared by the FranklinWH bridges (the Direct Connect bridge and the Modbus bridge). It finds the targets that can receive notifications, sends them with buttons, receives the taps, and keeps a record of both.

It holds no FranklinWH device code. What a button does is up to the bridge.

The design, decisions and plan are in docs/DESIGN.md.

What it does

Piece Module
Find each HA instance's notify.* targets; mark which can show buttons (notify.mobile_app_*) targets
Send one notification to many targets, with a delivery count send
Receive taps over HA's WebSocket (mobile_app_notification_action), reconnecting listener
Single-use, expiring requests; wait for an answer with a timeout actions
Title and message templates per event, with variables and reset templates
A record of every send and tap, kept for a number of days. create=False leaves the table to the bridge's own migration (apply SCHEMA) ledger
All of the above behind one object Notifier

The button contract

A button's action id is FWH_<VERB>_<request id>, for example FWH_YES_3f9c0a1b2c3d4e5f. The request id is inside the action id because every Companion app echoes action back, while other data fields come back differently on iOS and Android. Buttons without the FWH_ prefix (Snooze and the like, added by the phone) are ignored.

A tap resolves as one of:

  • accepted: the bridge's handler runs;
  • unknown: never issued, or lost in a restart;
  • expired;
  • used: already answered;
  • not-allowed: a button the request didn't offer.

Every outcome is recorded.

Taps arrive only over the bridge's own authenticated WebSocket to Home Assistant. There is no webhook and nothing on the bridge accepts an unauthenticated call.

Use

import sqlite3
from franklinwh_ha_notify import (YES, NO, Button, Event, HAInstance, Ledger, Notifier,
                                  Templates, discover)

ha = HAInstance("home", "http://supervisor/core", token=lambda: os.environ["SUPERVISOR_TOKEN"])
templates = Templates()
templates.register(Event("force_left_running", "Force still running on {gateway}",
                         "A force from before the restart is still running. Release it?"))
n = Notifier({"home": ha}, Ledger(sqlite3.connect("data/bridge.db")), templates,
             enabled=lambda: settings.notifications_on)

async def release(request, answer):
    if answer.verb == YES:
        await bridge.release_force(request.gateway)     # the bridge's own gated command
        return "released"
    return "kept"

n.on("force_left_running", release)
n.listen()                                   # one tap listener per HA instance

targets = [t for t in await discover(ha) if t.buttons]
await n.ask("force_left_running", targets, [Button(YES, "Release"), Button(NO, "Keep")],
            ttl_s=900, gateway="Home")

# Or wait for the answer inline, as a scheduler step does:
answer = await n.ask_and_wait("ok_to_charge", targets, [Button(YES, "Yes"), Button(NO, "No")],
                              timeout_s=300, gateway="Home")
if answer.timed_out:
    ...                                      # the step's "if no reply" rule

Development

python3.12 -m venv .venv && .venv/bin/pip install -e ".[test]"
.venv/bin/pytest -q

The tests run against a fake Home Assistant: REST through an httpx mock transport, and a real local WebSocket server that speaks HA's auth and subscribe_events handshake.

Releases: bump version in pyproject.toml, add the CHANGELOG section, tag v<version>. The publish workflow tests, checks the tag matches, and publishes to PyPI.

Licence

MIT

Metadata

Release files for franklinwh-ha-notify 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for franklinwh-ha-notify 0.1.1
File Size Uploaded Provenance Actions
franklinwh_ha_notify-0.1.1.tar.gz 18.1 kB With provenance Details for franklinwh_ha_notify-0.1.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for franklinwh-ha-notify 0.1.1
File Interpreter ABI Platform Actions
franklinwh_ha_notify-0.1.1-py3-none-any.whl Python 3 none any Details for franklinwh_ha_notify-0.1.1-py3-none-any.whl

Total release size: 34.4 kB

Release files / franklinwh_ha_notify-0.1.1.tar.gz

Download URL franklinwh_ha_notify-0.1.1.tar.gz
Size 18.1 kB
Tags Source
SHA-256 checksum
How to use checksums
091a3339ca801eb61bbf0e11d71e90e477faf1b97445fcd7d3ee11b6a70a0ada
BLAKE2b-256 checksum
How to use checksums
3a28f2b9665e926d1a419341423b5cd64168c7dffcb0a2b3158913d3031a3049
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.

Transparency log

Release files / franklinwh_ha_notify-0.1.1-py3-none-any.whl

Download URL franklinwh_ha_notify-0.1.1-py3-none-any.whl
Size 16.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
42f3f21c498e37f024d330462ad979eb452a52a026aaa7703b5d83840fa74fbd
BLAKE2b-256 checksum
How to use checksums
92cee81447521f97e9740fd7ddbf5eeaa75f693cbff9c4bae11a447c7cdb8c7d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.

Transparency log

Security for franklinwh-ha-notify 0.1.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for franklinwh_ha_notify-0.1.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page